| /kernel/linux/linux-6.6/include/linux/atomic/ |
| D | atomic-long.h | 30 * Safe to use in noinstr code; prefer atomic_long_read() elsewhere.
50 * Safe to use in noinstr code; prefer atomic_long_read_acquire() elsewhere.
71 * Safe to use in noinstr code; prefer atomic_long_set() elsewhere.
92 * Safe to use in noinstr code; prefer atomic_long_set_release() elsewhere.
113 * Safe to use in noinstr code; prefer atomic_long_add() elsewhere.
134 * Safe to use in noinstr code; prefer atomic_long_add_return() elsewhere.
155 * Safe to use in noinstr code; prefer atomic_long_add_return_acquire() elsewhere.
176 * Safe to use in noinstr code; prefer atomic_long_add_return_release() elsewhere.
197 * Safe to use in noinstr code; prefer atomic_long_add_return_relaxed() elsewhere.
218 * Safe to use in noinstr code; prefer atomic_long_fetch_add() elsewhere.
[all …]
|
| D | atomic-arch-fallback.h | 437 * Safe to use in noinstr code; prefer atomic_read() elsewhere.
453 * Safe to use in noinstr code; prefer atomic_read_acquire() elsewhere.
483 * Safe to use in noinstr code; prefer atomic_set() elsewhere.
500 * Safe to use in noinstr code; prefer atomic_set_release() elsewhere.
526 * Safe to use in noinstr code; prefer atomic_add() elsewhere.
543 * Safe to use in noinstr code; prefer atomic_add_return() elsewhere.
570 * Safe to use in noinstr code; prefer atomic_add_return_acquire() elsewhere.
597 * Safe to use in noinstr code; prefer atomic_add_return_release() elsewhere.
623 * Safe to use in noinstr code; prefer atomic_add_return_relaxed() elsewhere.
646 * Safe to use in noinstr code; prefer atomic_fetch_add() elsewhere.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/hw-vuln/ |
| D | srso.rst | 58 * 'Vulnerable: Safe RET, no microcode':
60 The "Safe RET" mitigation (see below) has been applied to protect the
64 * 'Vulnerable: Microcode, no safe RET':
85 * 'Mitigation: Safe RET':
91 Selected by default or by spec_rstack_overflow=safe-ret
95 Similar protection as "safe RET" above but employs an IBPB barrier on
123 default one is 'Mitigation: safe RET' which should take care of most
132 As one can surmise, 'Mitigation: safe RET' does come at the cost of some
142 Mitigation: Safe RET
148 the CPU to mispredict every function return using a 'safe return'
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/common/ |
| D | dmabounce.c | 54 /* safe buffer info */
56 void *safe; member
104 /* allocate a 'safe' buffer and keep track of it */
137 buf->safe = dma_pool_alloc(pool->pool, GFP_ATOMIC, in alloc_safe_buffer()
140 buf->safe = dma_alloc_coherent(dev, size, &buf->safe_dma_addr, in alloc_safe_buffer()
144 if (buf->safe == NULL) { in alloc_safe_buffer()
165 /* determine if a buffer is from our "safe" pool */
199 dma_pool_free(buf->pool->pool, buf->safe, buf->safe_dma_addr); in free_safe_buffer()
201 dma_free_coherent(device_info->dev, buf->size, buf->safe, in free_safe_buffer()
263 buf->safe, buf->safe_dma_addr); in map_single()
[all …]
|
| /kernel/linux/linux-6.6/arch/nios2/include/asm/ |
| D | asm-macros.h | 36 * It is safe to use the same register for reg1 & reg2.
55 * It is safe to use the same register for reg1 & reg2.
75 * It is safe to use the same register for reg1 & reg2.
94 * It is safe to use the same register for reg1 & reg2.
106 * It is safe to use the same register for reg1 & reg2.
118 * It is NOT safe to use the same register for reg1 & reg2.
139 * It is NOT safe to use the same register for reg1 & reg2.
160 * It is NOT safe to use the same register for reg1 & reg2.
182 * It is NOT safe to use the same register for reg1 & reg2.
195 * It is NOT safe to use the same register for reg1 & reg2.
[all …]
|
| /kernel/linux/linux-5.10/arch/nios2/include/asm/ |
| D | asm-macros.h | 36 * It is safe to use the same register for reg1 & reg2.
55 * It is safe to use the same register for reg1 & reg2.
75 * It is safe to use the same register for reg1 & reg2.
94 * It is safe to use the same register for reg1 & reg2.
106 * It is safe to use the same register for reg1 & reg2.
118 * It is NOT safe to use the same register for reg1 & reg2.
139 * It is NOT safe to use the same register for reg1 & reg2.
160 * It is NOT safe to use the same register for reg1 & reg2.
182 * It is NOT safe to use the same register for reg1 & reg2.
195 * It is NOT safe to use the same register for reg1 & reg2.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/i2c/ |
| D | dma-considerations.rst | 11 Therefore, it is *not* mandatory that the buffer of an I2C message is DMA safe.
13 rarely used. However, it is recommended to use a DMA-safe buffer if your
19 safe buffers always, because USB requires it.
24 For clients, if you use a DMA safe buffer in i2c_msg, set the I2C_M_DMA_SAFE
33 SMBus transactions via I2C, the buffers for block transfers are DMA safe. Users
34 of i2c_master_send() and i2c_master_recv() functions can now use DMA safe
36 know their buffers are DMA safe. Users of i2c_transfer() must set the
42 Bus master drivers wishing to implement safe DMA can use helper functions from
43 the I2C core. One gives you a DMA-safe buffer for a given i2c_msg as long as a
|
| /kernel/linux/linux-6.6/Documentation/i2c/ |
| D | dma-considerations.rst | 11 Therefore, it is *not* mandatory that the buffer of an I2C message is DMA safe.
13 rarely used. However, it is recommended to use a DMA-safe buffer if your
19 safe buffers always, because USB requires it.
24 For clients, if you use a DMA safe buffer in i2c_msg, set the I2C_M_DMA_SAFE
33 SMBus transactions via I2C, the buffers for block transfers are DMA safe. Users
34 of i2c_master_send() and i2c_master_recv() functions can now use DMA safe
36 know their buffers are DMA safe. Users of i2c_transfer() must set the
42 Bus master drivers wishing to implement safe DMA can use helper functions from
43 the I2C core. One gives you a DMA-safe buffer for a given i2c_msg as long as a
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/hw-vuln/ |
| D | srso.rst | 61 - 'Mitigation: safe RET' Software-only mitigation. It complements
67 spec_rstack_overflow=safe-ret
69 - 'Mitigation: IBPB' Similar protection as "safe RET" above
96 default one is 'Mitigation: safe RET' which should take care of most
105 As one can surmise, 'Mitigation: safe RET' does come at the cost of some
115 Mitigation: safe RET
121 the CPU to mispredict every function return using a 'safe return'
125 safe return sequence is itself free from attacker interference. In Zen3
127 untraining function srso_alias_untrain_ret() and the safe return
129 poisoned BTB entry and using that safe one for all function returns.
|
| /kernel/linux/linux-5.10/fs/ntfs/ |
| D | Kconfig | 9 safe, write support available. For write support you must also
28 Linux on your computer it is safe to say N.
56 This enables the partial, but safe, write support in the NTFS driver.
66 damaged someones data so we assume it is perfectly safe to use.
68 Note: While write support is safe in this version (a rewrite from
71 is not safe.
79 It is perfectly safe to say N here.
|
| /kernel/linux/linux-6.6/fs/ntfs/ |
| D | Kconfig | 10 safe, write support available. For write support you must also
29 Linux on your computer it is safe to say N.
58 This enables the partial, but safe, write support in the NTFS driver.
68 damaged someones data so we assume it is perfectly safe to use.
70 Note: While write support is safe in this version (a rewrite from
73 is not safe.
81 It is perfectly safe to say N here.
|
| /kernel/linux/linux-6.6/drivers/remoteproc/ |
| D | Kconfig | 24 It's safe to say N if you don't want to use this interface.
35 It's safe to say N here.
46 It's safe to say N here.
65 It's safe to say N here.
83 It's safe to say N here if you're not interested in multimedia
128 It's safe to say n here if you're not interested in multimedia
138 It's safe to say N here if you're not interested in the Keystone
161 processors on various TI SoCs. It's safe to say N here if you're
339 It's safe to say N here if you're not interested in utilizing
352 It's safe to say N here if you're not interested in utilizing
[all …]
|
| /kernel/linux/linux-6.6/drivers/parport/ |
| D | Kconfig | 32 and it is safe to compile all the corresponding drivers into the
85 is safe to say N.
101 called parport_ip32. If in doubt, saying N is the safe plan.
110 called parport_amiga. If in doubt, saying N is the safe plan.
119 parport_mfc3. If in doubt, saying N is the safe plan.
128 called parport_atari. If in doubt, saying N is the safe plan.
151 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
|
| /kernel/linux/linux-5.10/drivers/remoteproc/ |
| D | Kconfig | 24 It's safe to say N if you don't want to use this interface.
33 It's safe to say N here.
52 It's safe to say N here.
70 It's safe to say N here if you're not interested in multimedia
115 It's safe to say n here if you're not interested in multimedia
125 It's safe to say N here if you're not interested in the Keystone
275 It's safe to say N here if you're not interested in utilizing
288 It's safe to say N here if you're not interested in utilizing
|
| /kernel/linux/linux-5.10/drivers/parport/ |
| D | Kconfig | 32 and it is safe to compile all the corresponding drivers into the
84 is safe to say N.
100 called parport_ip32. If in doubt, saying N is the safe plan.
109 called parport_amiga. If in doubt, saying N is the safe plan.
118 parport_mfc3. If in doubt, saying N is the safe plan.
127 called parport_atari. If in doubt, saying N is the safe plan.
161 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | percpu-refcount.h | 24 * it's safe to drop the initial ref.
35 * and it's then safe to drop the initial ref with percpu_ref_put().
196 * This function is safe to call as long as @ref is between init and exit.
218 * This function is safe to call as long as @ref is between init and exit.
233 * This function is safe to call as long as @ref is between init and exit.
262 * This function is safe to call as long as @ref is between init and exit.
273 * This function is safe to call as long as @ref is between init and exit.
304 * This function is safe to call as long as @ref is between init and exit.
324 * This function is safe to call as long as @ref is between init and exit.
347 * This function is safe to call as long as @ref is between init and exit.
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | percpu-refcount.h | 24 * it's safe to drop the initial ref.
35 * and it's then safe to drop the initial ref with percpu_ref_put().
196 * This function is safe to call as long as @ref is between init and exit.
218 * This function is safe to call as long as @ref is between init and exit.
233 * This function is safe to call as long as @ref is between init and exit.
262 * This function is safe to call as long as @ref is between init and exit.
282 * This function is safe to call as long as @ref is between init and exit.
311 * This function is safe to call as long as @ref is between init and exit.
334 * This function is safe to call as long as @ref is between init and exit.
347 * This function is safe to call as long as @ref is between init and exit
|
| /kernel/linux/linux-5.10/drivers/usb/serial/ |
| D | safe_serial.c | 3 * Safe Encapsulated USB Serial Driver
75 static bool safe = true; variable
79 #define DRIVER_DESC "USB Safe Encapsulated Serial"
85 module_param(safe, bool, 0);
86 MODULE_PARM_DESC(safe, "Turn Safe Encapsulation On/Off");
196 if (!safe) in safe_process_read_urb()
232 trailer_len = safe ? 2 : 0; in safe_prepare_write_buffer()
236 if (!safe) in safe_prepare_write_buffer()
|
| /kernel/linux/linux-6.6/drivers/usb/serial/ |
| D | safe_serial.c | 3 * Safe Encapsulated USB Serial Driver
75 static bool safe = true; variable
79 #define DRIVER_DESC "USB Safe Encapsulated Serial"
85 module_param(safe, bool, 0);
86 MODULE_PARM_DESC(safe, "Turn Safe Encapsulation On/Off");
196 if (!safe) in safe_process_read_urb()
232 trailer_len = safe ? 2 : 0; in safe_prepare_write_buffer()
236 if (!safe) in safe_prepare_write_buffer()
|
| /kernel/linux/linux-5.10/security/apparmor/include/ |
| D | cred.h | 72 * If @task != current needs to be called in RCU safe critical section
85 * of the label so it is safe to call when inside of locks.
97 * This fn will not update the tasks cred, so it is safe inside of locks
131 * safe to call inside locks
153 * Not safe to call inside locks
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/tegra/ |
| D | nvidia,tegra124-sor.yaml | 119 - description: safe reference clock for the SOR clock
131 - const: safe
141 - description: safe reference clock for the SOR clock
152 - const: safe
182 clock-names = "sor", "out", "parent", "dp", "safe";
|
| /kernel/linux/linux-6.6/Documentation/scsi/ |
| D | dc395x.rst | 10 be safe to use. Testing with hard disks has not been done to any
28 safe
31 If safe is set to 1 then the adapter will use conservative
32 ("safe") default settings. This sets:
99 dc395x. (eg "dc395x.safe=1")
|
| /kernel/linux/linux-6.6/arch/um/drivers/ |
| D | Kconfig | 38 It is safe to say 'Y' here.
48 It is safe to say 'Y' here.
57 It is safe to say 'Y' here.
65 It is safe to say 'Y' here.
86 It is safe to leave this unchanged.
96 It is safe to leave this unchanged, although you may wish to change
108 It is safe to leave this unchanged, although you may wish to change
120 It is safe to say 'Y' here.
|
| /kernel/linux/linux-5.10/arch/um/drivers/ |
| D | Kconfig | 38 It is safe to say 'Y' here.
48 It is safe to say 'Y' here.
57 It is safe to say 'Y' here.
65 It is safe to say 'Y' here.
79 It is safe to leave this unchanged.
89 It is safe to leave this unchanged, although you may wish to change
101 It is safe to leave this unchanged, although you may wish to change
113 It is safe to say 'Y' here.
|
| /kernel/linux/linux-5.10/arch/arm64/include/asm/ |
| D | cpufeature.h | 26 * The safe value of a CPUID feature field is dependent on the implications
33 * a field when EXACT is specified, failing which, the safe value specified
38 FTR_EXACT, /* Use a predefined safe value */
39 FTR_LOWER_SAFE, /* Smaller value is safe */
40 FTR_HIGHER_SAFE, /* Bigger value is safe */
41 FTR_HIGHER_OR_ZERO_SAFE, /* Bigger value is safe, but 0 is biggest */
63 s64 safe_val; /* safe value for FTR_EXACT features */
69 * @sys_val Safe value across the CPUs (system view)
144 * kernel), the kernel should make sure that it is safe to use the CPU,
245 /* Is it safe for a late CPU to miss this capability when system has it */
[all …]
|