Searched full:around (Results 1 – 25 of 3798) sorted by relevance
12345678910>>...152
| /kernel/linux/linux-5.10/arch/x86/kernel/ |
| D | smp.c | 63 * 2AP. worked around in hardware
66 * 4AP. worked around in hardware
88 * 3AP. We work around this
92 * 6AP. not affected - worked around in hardware
93 * 7AP. not affected - worked around in hardware
94 * 8AP. worked around in hardware - we get explicit CS errors if not
98 * 10AP. not affected - worked around in hardware
102 * 12AP. not affected - worked around in hardware
103 * 13AP. not affected - worked around in hardware
105 * 15AP. not affected - worked around in hardware
[all …]
|
| /kernel/linux/linux-4.19/arch/x86/kernel/ |
| D | smp.c | 64 * 2AP. worked around in hardware
67 * 4AP. worked around in hardware
89 * 3AP. We work around this
93 * 6AP. not affected - worked around in hardware
94 * 7AP. not affected - worked around in hardware
95 * 8AP. worked around in hardware - we get explicit CS errors if not
99 * 10AP. not affected - worked around in hardware
103 * 12AP. not affected - worked around in hardware
104 * 13AP. not affected - worked around in hardware
106 * 15AP. not affected - worked around in hardware
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | timecounter.h | 20 * around quickly. Locking rules (if necessary) have to be defined
40 * cycle counter wrap around. Initialize with
45 * more often than the cycle counter wraps around. The nanosecond
46 * counter will only wrap around after ~585 years.
|
| D | compiler-gcc.h | 34 * To work around it we hide the relationship of the pointer and the object
38 * RELOC_HIDE could trash r30. The bug can be worked around by changing
69 * Adding an empty inline assembly before it works around the problem
98 * Work it around via a compiler barrier quirk suggested by Jakub Jelinek.
|
| D | kref.h | 99 * This function is intended to simplify locking around refcounting for
102 * Operations on such objects require at least a read lock around
103 * lookup + kref_get, and a write lock around kref_put + remove from lookup
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/ |
| D | war.h | 13 * Work around certain R4000 CPU errata (as implemented by GCC):
39 * Work around certain R4400 CPU errata (as implemented by GCC):
53 * Work around the "daddi" and "daddiu" CPU errata:
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | timecounter.h | 29 * around quickly. Locking rules (if necessary) have to be defined
49 * cycle counter wrap around. Initialize with
54 * more often than the cycle counter wraps around. The nanosecond
55 * counter will only wrap around after ~585 years.
|
| D | kref.h | 104 * This function is intended to simplify locking around refcounting for
107 * Operations on such objects require at least a read lock around
108 * lookup + kref_get, and a write lock around kref_put + remove from lookup
|
| /kernel/linux/linux-5.10/arch/powerpc/platforms/44x/ |
| D | Kconfig | 313 bool "Enable linker work around for PPC476FPE errata #46"
315 This option enables a work around for an icache bug on 476
320 The work around enables the appropriate linker options and
322 page boundaries. The work around is only required when
|
| /kernel/linux/linux-4.19/arch/powerpc/platforms/8xx/ |
| D | Kconfig | 20 development around the MPC86X processor families.
30 development around the MPC885 processor family.
128 to disable it if you have worked around the bug in the compiler
|
| /kernel/linux/linux-4.19/drivers/gpu/drm/ |
| D | drm_fb_cma_helper.c | 224 * drm_fbdev_cma_set_suspend - wrapper around drm_fb_helper_set_suspend
228 * Calls drm_fb_helper_set_suspend, which is a wrapper around
239 * drm_fbdev_cma_set_suspend_unlocked - wrapper around
244 * Calls drm_fb_helper_set_suspend, which is a wrapper around
|
| D | drm_memory.c | 96 /** Wrapper around agp_free_memory() */
102 /** Wrapper around agp_bind_memory() */
108 /** Wrapper around agp_unbind_memory() */
|
| /kernel/linux/linux-4.19/arch/powerpc/platforms/44x/ |
| D | Kconfig | 368 bool "Enable linker work around for PPC476FPE errata #46"
370 This option enables a work around for an icache bug on 476
375 The work around enables the appropriate linker options and
377 page boundaries. The work around is only required when
|
| /kernel/linux/linux-4.19/Documentation/vm/ |
| D | z3fold.rst | 22 compression ratio goes to around 2.7x while zbud's one is around 1.7x.
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | z3fold.rst | 22 compression ratio goes to around 2.7x while zbud's one is around 1.7x.
|
| /kernel/linux/linux-5.10/arch/powerpc/platforms/8xx/ |
| D | Kconfig | 20 development around the MPC86X processor families.
30 development around the MPC885 processor family.
119 to disable it if you have worked around the bug in the compiler
|
| /kernel/linux/linux-4.19/arch/mips/include/asm/ |
| D | war.h | 15 * Work around certain R4000 CPU errata (as implemented by GCC):
41 * Work around certain R4400 CPU errata (as implemented by GCC):
55 * Work around the "daddi" and "daddiu" CPU errata:
159 * This is a DUART workaround related to glitches around register accesses
|
| /kernel/linux/linux-4.19/Documentation/driver-api/usb/ |
| D | error-codes.rst | 68 some problem that could not be worked around.
108 prescribed bus turn-around time
113 prescribed bus turn-around time
124 prescribed bus turn-around time. This error
170 be worked around, such as a physical
|
| /kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
| D | error-codes.rst | 68 some problem that could not be worked around.
108 prescribed bus turn-around time
113 prescribed bus turn-around time
124 prescribed bus turn-around time. This error
170 be worked around, such as a physical
|
| /kernel/linux/linux-5.10/drivers/media/pci/saa7164/ |
| D | saa7164-bus.c | 196 /* Read didn't wrap around the buffer */ in saa7164_bus_set()
254 /* Additional data wraps around the ring */ in saa7164_bus_set()
350 /* Write doesn't wrap around the ring */ in saa7164_bus_get()
353 /* Write wraps around the ring */ in saa7164_bus_get()
409 /* Write doesn't wrap around the ring */ in saa7164_bus_get()
412 /* Write wraps around the ring */ in saa7164_bus_get()
439 /* Additional data wraps around the ring */ in saa7164_bus_get()
|
| /kernel/linux/linux-4.19/drivers/media/pci/saa7164/ |
| D | saa7164-bus.c | 206 /* Read didn't wrap around the buffer */ in saa7164_bus_set()
264 /* Additional data wraps around the ring */ in saa7164_bus_set()
360 /* Write doesn't wrap around the ring */ in saa7164_bus_get()
363 /* Write wraps around the ring */ in saa7164_bus_get()
419 /* Write doesn't wrap around the ring */ in saa7164_bus_get()
422 /* Write wraps around the ring */ in saa7164_bus_get()
449 /* Additional data wraps around the ring */ in saa7164_bus_get()
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | atomic_ops.rst | 244 Again, these primitives provide explicit memory barrier semantics around
251 provide explicit memory barrier semantics around the operation::
257 This primitive must provide explicit memory barrier semantics around
268 atomic_xchg must provide explicit memory barriers around the operation. ::
277 atomic_cmpxchg must provide explicit memory barriers around the operation,
292 atomic_add_unless must provide explicit memory barriers around the
298 If a caller requires memory barrier semantics around an atomic_t
486 must provide explicit memory barrier semantics around their execution.
510 If explicit memory barriers are required around {set,clear}_bit() (which do
|
| /kernel/linux/linux-4.19/Documentation/core-api/ |
| D | atomic_ops.rst | 244 Again, these primitives provide explicit memory barrier semantics around
251 provide explicit memory barrier semantics around the operation::
257 This primitive must provide explicit memory barrier semantics around
268 atomic_xchg must provide explicit memory barriers around the operation. ::
277 atomic_cmpxchg must provide explicit memory barriers around the operation,
292 atomic_add_unless must provide explicit memory barriers around the
298 If a caller requires memory barrier semantics around an atomic_t
486 must provide explicit memory barrier semantics around their execution.
510 If explicit memory barriers are required around {set,clear}_bit() (which do
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | amd_energy.rst | 75 2P system, the register would wrap around in
79 The Core energy register may wrap around after several days.
81 To improve the wrap around time, a kernel thread is implemented
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/amd/display/ |
| D | TODO | 23 lot of design around what was public/protected, more whatever needed
87 17. There's still a pretty massive layer cake around dp aux and DPCD handling,
97 issue with DC - other drivers, especially around DP sink handling, are equally
|
12345678910>>...152