Searched refs:prevent (Results 1 – 25 of 337) sorted by relevance
12345678910>>...14
| /Linux-v5.15/drivers/cpuidle/ |
| D | coupled.c | 104 int prevent; member
480 while (coupled->prevent) { in cpuidle_enter_state_coupled()
529 if (coupled->prevent) { in cpuidle_enter_state_coupled()
670 coupled->prevent++; in cpuidle_coupled_register_device()
714 coupled->prevent++; in cpuidle_coupled_prevent_idle()
737 coupled->prevent--; in cpuidle_coupled_allow_idle()
|
| /Linux-v5.15/Documentation/userspace-api/ |
| D | no_new_privs.rst | 7 programs and file capabilities. To prevent the parent program from
9 careful to prevent the parent from doing anything that could subvert the
41 Note that ``no_new_privs`` does not prevent privilege changes that do not
|
| /Linux-v5.15/Documentation/filesystems/ |
| D | efivarfs.rst | 24 as immutable files. This doesn't prevent removal - "chattr -i" will work -
25 but it does prevent this kind of failure from being accomplished
|
| /Linux-v5.15/Documentation/networking/ |
| D | netfilter-sysctl.rst | 15 with LOG target; this aims to prevent containers from flooding host
|
| /Linux-v5.15/Documentation/core-api/ |
| D | debug-objects.rst | 79 can deactivate an active object in order to prevent damage to the
102 can deactivate an active object in order to prevent damage to the
126 deactivate an active object in order to prevent damage to the subsystem.
156 prevent the usage of invalid objects, which are still available in
166 deactivate an active object in order to prevent damage to the subsystem.
182 prevent damage to the subsystem.
|
| /Linux-v5.15/Documentation/process/ |
| D | volatile-considered-harmful.rst | 22 safe (spinlocks, mutexes, memory barriers, etc.) are designed to prevent
58 architectures. Those accessors are written to prevent unwanted
83 keyword to asm statements will prevent this removal.
|
| /Linux-v5.15/Documentation/power/ |
| D | freezing-of-tasks.rst | 106 1. The principal reason is to prevent filesystems from being damaged after
125 to allocate additional memory and we prevent them from doing that by
130 3. The third reason is to prevent user space processes and some kernel threads
160 4. Another reason for freezing tasks is to prevent user space processes from
213 VI. Are there any precautions to be taken to prevent freezing failures?
238 mutex_[un]lock(&system_transition_mutex). That would prevent freezing failures.
|
| /Linux-v5.15/Documentation/locking/ |
| D | rt-mutex.rst | 66 with ->wait_lock is held. To prevent any fast path cmpxchg to the lock,
72 To prevent a cmpxchg of the owner releasing the lock, we need to
|
| /Linux-v5.15/tools/testing/kunit/configs/ |
| D | broken_on_uml.config | 1 # These are currently broken on UML and prevent allyesconfig from building
|
| /Linux-v5.15/Documentation/powerpc/ |
| D | elfnote.rst | 33 In an ultravisor-enabled system, a bootloader could warn the user or prevent
|
| /Linux-v5.15/tools/testing/selftests/tc-testing/ |
| D | TODO.txt | 4 present, prevent the related categories from running.
|
| /Linux-v5.15/Documentation/x86/ |
| D | buslock.rst | 82 solutions as they have no way to prevent the "untrusted" user code from
86 It's also useful for general computing to prevent guests or user
|
| /Linux-v5.15/arch/arm/boot/dts/ |
| D | rk3288-veyron-sdmmc.dtsi | 34 * Builtin CD line is hooked to ground to prevent JTAG at boot
|
| /Linux-v5.15/kernel/gcov/ |
| D | Kconfig | 54 which are not linked to the kernel image to prevent linker errors.
|
| /Linux-v5.15/Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 46 that does not require per-CPU kthreads. This will prevent these
113 3. Once your application has started, prevent CPU-hotplug operations
125 3. Once your application has started, prevent CPU-hotplug operations
137 3. Once your application has started, prevent CPU-hotplug operations
331 2. Build with CONFIG_RCU_NOCB_CPU=n, which will prevent these
|
| /Linux-v5.15/Documentation/virt/kvm/ |
| D | review-checklist.rst | 40 host/guest memory must be unshared to prevent the host from writing to
|
| /Linux-v5.15/Documentation/security/keys/ |
| D | request-key.rst | 46 does not need to link the key to a keyring to prevent it from being immediately
64 to prevent the key from going away, and returns the serial number of the key to
141 This is provided to prevent excessive repeated spawning of /sbin/request-key
|
| /Linux-v5.15/drivers/pnp/pnpbios/ |
| D | Kconfig | 19 BIOS) say Y here. Also the PNPBIOS can help prevent resource
|
| /Linux-v5.15/tools/testing/selftests/tc-testing/creating-testcases/ |
| D | AddingTestCases.txt | 9 will help prevent conflicts when updating the repository. Refer to
80 the tests are run will be destroyed. This is to prevent inaccurate results
|
| /Linux-v5.15/Documentation/admin-guide/hw-vuln/ |
| D | spectre.rst | 156 macros are used to prevent speculative loading of data.
206 to prevent jumping to gadget code during speculative execution.
245 Predictors (STIBP) :ref:`[4] <spec_ref4>` are turned on to prevent the
429 Copy-from-user code has an LFENCE barrier to prevent the access_ok()
445 in an infinite loop to prevent any speculative execution jumping to
468 before invoking any firmware code to prevent Spectre variant 2 exploits
492 also prevent the program from launching a variant 2 attack
515 Linux kernel uses retpoline or Enhanced IBRS to prevent consumption of
517 flushes the return stack buffer on every VM exit to prevent a return
|
| /Linux-v5.15/arch/mips/loongson2ef/ |
| D | Platform | 17 # We disable this in order to prevent the assembler meddling with the
|
| /Linux-v5.15/Documentation/i2c/ |
| D | old-module-parameters.rst | 15 ``ignore`` (to prevent a driver from probing a given address).
|
| /Linux-v5.15/Documentation/driver-api/ |
| D | frame-buffer.rst | 27 fb_monospecs prevents such things, and if used correctly, can prevent a
|
| /Linux-v5.15/Documentation/hwmon/ |
| D | max1668.rst | 70 Set to non-zero if you wish to prevent write access to alarm thresholds.
|
| /Linux-v5.15/arch/arm/kernel/ |
| D | entry-common.S | 378 mov why, #0 @ prevent syscall restart handling
384 mov why, #0 @ prevent syscall restart handling
|
12345678910>>...14
