| /linux/fs/tests/ |
| H A D | exec_kunit.c | 82 /* But raising it another pointer * 4 will provide space for 1 more pointer. */ 89 /* Raising rlim_stack / 4 to _STK_LIM / 4 * 3 will see more space. */ 93 /* But raising it any further will see no increase. */
|
| /linux/block/ |
| H A D | bfq-iosched.c | 54 * mainly, by raising the weight of the queue. So, for brevity, we 55 * call just weight-raising periods the time periods during which a 73 * weight-raising for interactive queues. 271 * When configured for computing the duration of the weight-raising 285 * weight raising to interactive applications. 313 * BFQ uses the above-detailed, time-based weight-raising mechanism to 317 * raising. These applications have basically no benefit from being 328 * finish explaining how the duration of weight-raising for 332 * raising is dynamically adjusted, as a function of the estimated 342 * duration of weight-raising for at least one class of I/O-bound [all …]
|
| H A D | bfq-iosched.h | 341 /* current maximum weight-raising time for this queue */ 352 * Start time of the current weight-raising period if 354 * finish time of the last weight-raising period. 772 /* Maximum weight-raising duration for soft real-time processes */ 775 * Minimum idle period after which weight-raising may be 781 * weight-raising may be reactivated for an already busy async 790 * for computing the maximum duration of weight raising
|
| /linux/ipc/ |
| H A D | namespace.c | 195 * So dropping the refcount, and raising the refcount when 198 * (Clearly, a task raising the refcount on its own ipc_ns
|
| /linux/drivers/atm/ |
| H A D | zeprom.h | 17 #define ZEPROM_SK 0x80000000 /* strobe (probably on raising edge) */
|
| /linux/drivers/media/dvb-frontends/ |
| H A D | s5h1420.h | 24 u8 cdclk_polarity:1; /* 1 == falling edge, 0 == raising edge */
|
| /linux/Documentation/devicetree/bindings/gpio/ |
| H A D | lacie,netxbig-gpio-ext.yaml | 36 description: Latches the new configuration (address, data) on raising edge.
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-xenbus | 40 basis and is known not to be malicious on purpose. Raising
|
| H A D | sysfs-class-power-ltc4162l | 74 until some external power-supply is attached raising the input
|
| /linux/include/linux/ |
| H A D | lp.h | 86 #define LP_PSTROBE 0x01 /* short high output on raising edge */
|
| H A D | mhi_ep.h | 103 * @raise_irq: CB function for raising IRQ to the host
|
| /linux/arch/arm64/kernel/ |
| H A D | sys_compat.c | 104 * if not implemented, rather than raising SIGILL. This in compat_arm_syscall()
|
| /linux/drivers/crypto/caam/ |
| H A D | Kconfig | 82 raising an interrupt, in the range 1-255. Note that a selection
|
| /linux/include/ufs/ |
| H A D | ufs_quirks.h | 37 * the Host UniPro goes into bad state without raising the DFES error
|
| /linux/arch/m68k/coldfire/ |
| H A D | intc.c | 95 * interrupt controller. That is, the device raising the interrupt can also
|
| /linux/Documentation/trace/rv/ |
| H A D | monitor_rtapp.rst | 32 The `pagefault` monitor reports real-time tasks raising page faults. Its
|
| /linux/sound/soc/starfive/ |
| H A D | jh7110_tdm.c | 54 /* tx raising and rx falling */ 56 /* tx falling and rx raising */
|
| /linux/tools/testing/selftests/signal/ |
| H A D | mangle_uc_sigmask.c | 168 * Raising USR2 in handler_verify_ucontext is redundant since it in main()
|
| /linux/Documentation/arch/arm/ |
| H A D | kernel_mode_neon.rst | 70 software assistance, it signals the kernel by raising an undefined instruction
|
| /linux/security/apparmor/ |
| H A D | resource.c | 110 * Control raising the processes hard limit.
|
| /linux/Documentation/PCI/endpoint/ |
| H A D | pci-ntb-function.rst | 192 will ensure there is no difference while raising the doorbell. 198 for raising doorbell interrupt. This will be populated by EPF NTB
|
| /linux/Documentation/admin-guide/ |
| H A D | rtc.rst | 50 for...) It can also function as a 24hr alarm, raising IRQ 8 when the
|
| /linux/arch/powerpc/kvm/ |
| H A D | book3s_hv_rm_xics.c | 201 * flag when raising CPPR, so we need to set it back here if an in icp_rm_try_update() 639 * The processor is raising its priority, this can result in xics_rm_h_cppr()
|
| /linux/Documentation/block/ |
| H A D | bfq-iosched.rst | 215 throughput. For brevity, we call it just "weight-raising" the whole 217 particular, BFQ provides a milder form of weight-raising for
|
| /linux/tools/lib/perf/ |
| H A D | cpumap.c | 207 "Consider raising MAX_NR_CPUS\n", MAX_NR_CPUS); in perf_cpu_map__new()
|