Home
last modified time | relevance | path

Searched full:around (Results 1 – 25 of 2188) sorted by relevance

12345678910>>...88

/Linux-v5.4/arch/x86/kernel/
Dsmp.c62 * 2AP. worked around in hardware
65 * 4AP. worked around in hardware
87 * 3AP. We work around this
91 * 6AP. not affected - worked around in hardware
92 * 7AP. not affected - worked around in hardware
93 * 8AP. worked around in hardware - we get explicit CS errors if not
97 * 10AP. not affected - worked around in hardware
101 * 12AP. not affected - worked around in hardware
102 * 13AP. not affected - worked around in hardware
104 * 15AP. not affected - worked around in hardware
[all …]
/Linux-v5.4/include/linux/
Dtimecounter.h20 * 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.
Dcompiler-gcc.h46 * To work around it we hide the relationship of the pointer and the object
50 * RELOC_HIDE could trash r30. The bug can be worked around by changing
87 * Adding an empty inline assembly before it works around the problem
116 * Work it around via a compiler barrier quirk suggested by Jakub Jelinek.
Dkref.h99 * 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
Decryptfs.h28 * be passed around or referenced on the command line */
49 * For convenience, we may need to pass around the encrypted session
/Linux-v5.4/arch/powerpc/platforms/8xx/
DKconfig20 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
/Linux-v5.4/arch/powerpc/platforms/44x/
DKconfig341 bool "Enable linker work around for PPC476FPE errata #46"
343 This option enables a work around for an icache bug on 476
348 The work around enables the appropriate linker options and
350 page boundaries. The work around is only required when
/Linux-v5.4/arch/mips/include/asm/
Dwar.h15 * 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:
146 * This is a DUART workaround related to glitches around register accesses
/Linux-v5.4/Documentation/vm/
Dz3fold.rst22 compression ratio goes to around 2.7x while zbud's one is around 1.7x.
/Linux-v5.4/Documentation/driver-api/usb/
Derror-codes.rst68 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.4/drivers/media/pci/saa7164/
Dsaa7164-bus.c196 /* 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.4/drivers/misc/mic/scif/
Dscif_rb.c38 /* Copies a message to the ring buffer -- handles the wrap around case */
45 /* Need to call two copies if it wraps around */ in memcpy_torb()
56 /* Copies a message from the ring buffer -- handles the wrap around case */
63 /* Need to call two copies if it wraps around */ in memcpy_fromrb()
/Linux-v5.4/Documentation/core-api/
Datomic_ops.rst244 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.4/Documentation/process/
D6.Followthrough.rst37 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.4/drivers/gpu/drm/amd/display/
DTODO23 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.4/drivers/gpu/drm/
Ddrm_fb_helper.c549 * A wrapper around unregister_framebuffer, to release the fb_info
606 * drm_fb_helper_unlink_fbi - wrapper around unlink_framebuffer
609 * A wrapper around unlink_framebuffer implemented by fbdev core
725 * drm_fb_helper_sys_read - wrapper around fb_sys_read
731 * A wrapper around fb_sys_read implemented by fbdev core
741 * drm_fb_helper_sys_write - wrapper around fb_sys_write
747 * A wrapper around fb_sys_write implemented by fbdev core
764 * drm_fb_helper_sys_fillrect - wrapper around sys_fillrect
768 * A wrapper around sys_fillrect implemented by fbdev core
780 * drm_fb_helper_sys_copyarea - wrapper around sys_copyarea
[all …]
Ddrm_memory.c102 /** Wrapper around agp_free_memory() */
108 /** Wrapper around agp_bind_memory() */
114 /** Wrapper around agp_unbind_memory() */
/Linux-v5.4/Documentation/timers/
Dtimekeeping.rst31 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.4/kernel/sched/
Dmembarrier.c75 * Matches memory barriers around rq->curr modification in in membarrier_global_expedited()
125 * waiting for the last IPI. Matches memory barriers around in membarrier_global_expedited()
154 * Matches memory barriers around rq->curr modification in in membarrier_private_expedited()
192 * waiting for the last IPI. Matches memory barriers around in membarrier_private_expedited()
/Linux-v5.4/arch/sh/include/uapi/asm/
Dstat.h44 * insane amounts of padding around dev_t's.
101 * insane amounts of padding around dev_t's.
/Linux-v5.4/Documentation/accounting/
Dtaskstats-struct.rst108 * 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.4/arch/sh/drivers/pci/
Dops-dreamcast.c22 * 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.4/include/uapi/linux/
Dtaskstats.h65 * 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.4/Documentation/scsi/
Dscsi-changer.txt23 changer device this is a "don't care", he *only* shuffles around the
31 media transport - this one shuffles around the media, i.e. the
162 I wrote this driver using the famous mailing-patches-around-the-world
/Linux-v5.4/arch/arm/crypto/
DKconfig91 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>>...88