Searched full:around (Results 1 – 25 of 2306) sorted by relevance
12345678910>>...93
| /Linux-v5.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 …]
|
| /Linux-v5.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 | 28 * To work around it we hide the relationship of the pointer and the object
32 * RELOC_HIDE could trash r30. The bug can be worked around by changing
63 * Adding an empty inline assembly before it works around the problem
92 * 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
|
| D | ecryptfs.h | 28 * be passed around or referenced on the command line */
49 * For convenience, we may need to pass around the encrypted session
|
| /Linux-v5.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:
|
| /Linux-v5.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
|
| /Linux-v5.10/Documentation/vm/ |
| D | z3fold.rst | 22 compression ratio goes to around 2.7x while zbud's one is around 1.7x.
|
| /Linux-v5.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
|
| /Linux-v5.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
|
| /Linux-v5.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()
|
| /Linux-v5.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
|
| /Linux-v5.10/Documentation/process/ |
| D | 6.Followthrough.rst | 37 still be around and under development a decade from now.
76 around.
85 around. So it is always a good idea to remind reviewers of previously
181 it with the assumption that you will not be around to maintain it
201 eventually flow around you and get into the mainline anyway. In the Linux
|
| /Linux-v5.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
|
| /Linux-v5.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
|
| /Linux-v5.10/Documentation/timers/ |
| D | timekeeping.rst | 31 n bits which count from 0 to (2^n)-1 and then wraps around to 0 and start over.
76 Since a 32-bit counter at say 100 MHz will wrap around to zero after some 43
80 code knows when the counter will wrap around and can insert the necessary
155 drift between the CPUs on the system. The kernel can work around this by
|
| /Linux-v5.10/drivers/gpu/drm/ |
| D | drm_memory.c | 103 /** Wrapper around agp_free_memory() */
109 /** Wrapper around agp_bind_memory() */
115 /** Wrapper around agp_unbind_memory() */
|
| D | drm_fb_helper.c | 568 * A wrapper around unregister_framebuffer, to release the fb_info
687 * drm_fb_helper_sys_read - wrapper around fb_sys_read
693 * A wrapper around fb_sys_read implemented by fbdev core
703 * drm_fb_helper_sys_write - wrapper around fb_sys_write
709 * A wrapper around fb_sys_write implemented by fbdev core
726 * drm_fb_helper_sys_fillrect - wrapper around sys_fillrect
730 * A wrapper around sys_fillrect implemented by fbdev core
742 * drm_fb_helper_sys_copyarea - wrapper around sys_copyarea
746 * A wrapper around sys_copyarea implemented by fbdev core
758 * drm_fb_helper_sys_imageblit - wrapper around sys_imageblit
[all …]
|
| /Linux-v5.10/Documentation/accounting/ |
| D | taskstats-struct.rst | 108 * xxx_delay_total wraps around to zero on overflow
134 * and wraps around to zero silently on overflow
142 * and wraps around to zero silently on overflow
|
| /Linux-v5.10/arch/sh/drivers/pci/ |
| D | ops-dreamcast.c | 22 * someone implicitly messes around with the last devfn value.. otherwise we
30 * I suppose if someone actually gets around to ripping the chip out of
|
| /Linux-v5.10/Documentation/devicetree/bindings/net/ |
| D | mdio.yaml | 72 broken-turn-around:
76 the turn around line low at end of the control phase of the
|
| /Linux-v5.10/include/uapi/linux/ |
| D | taskstats.h | 65 * xxx_delay_total wraps around to zero on overflow
91 * and wraps around to zero silently on overflow
99 * and wraps around to zero silently on overflow
|
| /Linux-v5.10/Documentation/arm/ |
| D | netwinder.rst | 6 to run Linux. It is based around the StrongARM RISC processor,
7 DC21285 PCI bridge, with PC-type hardware glued around it.
|
| /Linux-v5.10/Documentation/dev-tools/ |
| D | kasan.rst | 122 Memory state around the buggy address:
138 In the last section the report shows memory state around the accessed address.
153 For tag-based KASAN this last report section shows the memory tags around the
277 To avoid the difficulties around swapping mappings around, we expect
|
| /Linux-v5.10/arch/arm/crypto/ |
| D | Kconfig | 91 Bit sliced AES gives around 45% speedup on Cortex-A15 for CTR mode
93 around 25%. (CBC encryption speed is not affected by this driver.)
|
12345678910>>...93
