Home
last modified time | relevance | path

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

12345678910>>...100

/linux-6.12.1/arch/x86/kernel/
Dsmp.c65 * 2AP. worked around in hardware
68 * 4AP. worked around in hardware
90 * 3AP. We work around this
94 * 6AP. not affected - worked around in hardware
95 * 7AP. not affected - worked around in hardware
96 * 8AP. worked around in hardware - we get explicit CS errors if not
100 * 10AP. not affected - worked around in hardware
104 * 12AP. not affected - worked around in hardware
105 * 13AP. not affected - worked around in hardware
107 * 15AP. not affected - worked around in hardware
[all …]
/linux-6.12.1/include/linux/
Doverflow.h62 * Returns true on wrap-around, false otherwise.
65 * wrap-around occurred.
76 * Return the potentially wrapped-around addition without
77 * tripping any wrap-around sanitizers that may be enabled.
91 * Increments @var by @offset with wrap-around. Returns the resulting
92 * value of @var. Will not trip any wrap-around sanitizers.
108 * Returns true on wrap-around, false otherwise.
111 * wrap-around occurred.
122 * Return the potentially wrapped-around subtraction without
123 * tripping any wrap-around sanitizers that may be enabled.
[all …]
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.
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
Dcompiler-gcc.h23 * To work around it we hide the relationship of the pointer and the object
27 * RELOC_HIDE could trash r30. The bug can be worked around by changing
51 * Adding an empty inline assembly before it works around the problem
/linux-6.12.1/Documentation/devicetree/bindings/display/panel/
Dsamsung,lms397kf04.yaml9 description: The datasheet claims this is based around a display controller
30 usually around 3.0 V
34 around 1.8 V
44 maximum 300 ns minimum cycle which gives around 3 MHz max frequency
Dsamsung,lms380kf01.yaml38 usually around 3.0 V
42 around 1.8 V
/linux-6.12.1/lib/
DKconfig.ubsan21 the kernel size by around 5%, due to adding all the debugging
120 bool "Perform checking for signed arithmetic wrap-around"
128 for wrap-around of any arithmetic operations with signed integers.
131 arithmetic undefined behavior into wrap-around arithmetic. Future
132 sanitizer versions will allow for wrap-around checking (rather than
/linux-6.12.1/arch/powerpc/platforms/44x/
DKconfig304 bool "Enable linker work around for PPC476FPE errata #46"
306 This option enables a work around for an icache bug on 476
311 The work around enables the appropriate linker options and
313 page boundaries. The work around is only required when
/linux-6.12.1/arch/arm64/
DKconfig441 This option adds an alternative code sequence to work around Ampere
464 This option adds an alternative code sequence to work around ARM
486 This option adds an alternative code sequence to work around ARM
508 This option adds an alternative code sequence to work around ARM
531 This option adds an alternative code sequence to work around ARM
552 This option adds an alternative code sequence to work around ARM
570 This option adds an alternative code sequence to work around ARM
607 This option adds an alternative code sequence to work around ARM
721 Work around this by adding the affected CPUs to the list that needs
755 Work around the erratum by triggering a dummy step exception
[all …]
/linux-6.12.1/Documentation/sphinx/
Dkernellog.py4 # only goes back to 1.6. So here's a wrapper layer to keep around for
7 # We don't support 1.4 anymore, but we'll keep the wrappers around until
/linux-6.12.1/Documentation/process/
D6.Followthrough.rst37 still be around and under development a decade from now.
58 to get around a problem actually needs to become a generalized
83 around.
92 around. So it is always a good idea to remind reviewers of previously
188 it with the assumption that you will not be around to maintain it
208 eventually flow around you and get into the mainline anyway. In the Linux
/linux-6.12.1/tools/perf/util/
Dmutex.h9 * A function-like feature checking macro that is a wrapper around
69 * A wrapper around the mutex implementation that allows perf to error check
76 /* A wrapper around the condition variable implementation. */
/linux-6.12.1/arch/powerpc/platforms/8xx/
DKconfig20 development around the MPC86X processor families.
30 development around the MPC885 processor family.
120 to disable it if you have worked around the bug in the compiler
/linux-6.12.1/Documentation/mm/
Dz3fold.rst20 compression ratio goes to around 2.7x while zbud's one is around 1.7x.
/linux-6.12.1/Documentation/driver-api/usb/
Derror-codes.rst71 some problem that could not be worked around.
111 prescribed bus turn-around time
116 prescribed bus turn-around time
127 prescribed bus turn-around time. This error
173 be worked around, such as a physical
/linux-6.12.1/arch/xtensa/
DKconfig.debug43 bool "Dump user code around unhandled exception address"
45 Enable this option to display user code around PC of the unhandled
/linux-6.12.1/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-6.12.1/drivers/gpu/drm/tests/
Ddrm_modes_test.c58 * pixel clock of 13.5 MHz, a pixel takes around 74ns, so we in drm_test_modes_analog_tv_ntsc_480i()
105 * clock of 13.5 MHz, a pixel takes around 74ns, so we need to in drm_test_modes_analog_tv_pal_576i()
152 * clock of 13.5 MHz, a pixel takes around 74ns, so we need to in drm_test_modes_analog_tv_mono_576i()
/linux-6.12.1/tools/testing/selftests/rseq/
Dcompiler.h5 * Work-around asm goto compiler bugs.
23 * Work around these issues by adding a volatile inline asm with
/linux-6.12.1/tools/testing/selftests/kvm/x86_64/
Dvmx_nested_tsc_scaling_test.c152 printf("real TSC frequency is around: %"PRIu64"\n", l0_tsc_freq); in main()
180 printf("L1's TSC frequency is around: %"PRIu64 in main()
188 printf("L2's TSC frequency is around: %"PRIu64 in main()
/linux-6.12.1/tools/perf/arch/arm64/util/
Darm-spe.c387 * wrapped around. Otherwise, continue to detect if head might have wrapped. in arm_spe_buffer_has_wrapped()
400 * head has numerically wrapped around. To find we need to check if we have data at the in arm_spe_buffer_has_wrapped()
419 * numerically wrapped around at least once. in arm_spe_buffer_has_wrapped()
448 * Check to see if *head has wrapped around. If it hasn't only the in arm_spe_find_snapshot()
451 * wrapped around the entire size of the AUX ring buffer it taken. in arm_spe_find_snapshot()
469 * *head has wrapped around - adjust *head and *old to pickup the in arm_spe_find_snapshot()
/linux-6.12.1/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-6.12.1/Documentation/devicetree/bindings/phy/
Dmediatek,mt7988-xfi-tphy.yaml43 problem in 10GBase-R mode which needs a work-around in the driver.
44 This flag enables a work-around adjusting an analog phy setting and
/linux-6.12.1/Documentation/hwmon/
Dbpa-rs600.rst69 temp1_input Measured temperature around input connector
72 temp2_input Measured temperature around output connector

12345678910>>...100