Home
last modified time | relevance | path

Searched full:potential (Results 1 – 25 of 807) sorted by relevance

12345678910>>...33

/Linux-v6.1/Documentation/admin-guide/aoe/
Dtodo.rst4 There is a potential for deadlock when allocating a struct sk_buff for
9 not been observed, but it would be nice to eliminate any potential for
16 efficiently allocate sk_buffs without introducing any potential for
/Linux-v6.1/include/linux/
Ddma-fence-unwrap.h20 * @chain: potential dma_fence_chain, but can be other fence as well
24 * @array: potential dma_fence_array, but can be other fence as well
44 * potential fences in them. If @head is just a normal fence only that one is
Dshrinker.h47 * be executed due to potential deadlocks to be run at a later call when the
54 * due to potential deadlocks. If SHRINK_STOP is returned, then no further
Dmigrate_mode.h7 * on most operations but not ->writepage as the potential stall time
Drbtree_types.h20 * size vs number of potential users that could benefit
/Linux-v6.1/tools/testing/selftests/bpf/verifier/
Dref_tracking.c2 "reference tracking: leak potential reference",
13 "reference tracking: leak potential reference to sock_common",
24 "reference tracking: leak potential reference on stack",
38 "reference tracking: leak potential reference on stack 2",
53 "reference tracking: zero potential reference",
64 "reference tracking: zero potential reference to sock_common",
75 "reference tracking: copy and zero potential references",
192 "reference tracking: leak potential reference to user key",
210 "reference tracking: leak potential reference to system key",
/Linux-v6.1/Documentation/timers/
Dhrtimers.rst68 with other potential users for precise timers gives another reason to
71 Another potential benefit is that such a separation allows even more
123 potential for code sharing either.
/Linux-v6.1/security/safesetid/
Dlsm.c206 * Kill this process to avoid potential security vulnerabilities in safesetid_task_fix_setuid()
230 * Kill this process to avoid potential security vulnerabilities in safesetid_task_fix_setgid()
251 * Kill this process to avoid potential security vulnerabilities in safesetid_task_fix_setgroups()
/Linux-v6.1/kernel/irq/
Dautoprobe.c27 * and a mask of potential interrupt lines is returned.
142 * @val: mask of potential interrupts (unused)
/Linux-v6.1/tools/perf/pmu-events/arch/x86/amdzen1/
Dbranch.json16 … "PublicDescription": "Indirect Branch Prediction for potential multi-target branch (speculative)."
/Linux-v6.1/drivers/net/ethernet/dec/tulip/
Dtimer.c133 /* mod_timer synchronizes us with potential add_timer calls in tulip_media_task()
167 /* mod_timer synchronizes us with potential add_timer calls in comet_timer()
/Linux-v6.1/Documentation/ABI/testing/
Dsysfs-driver-xen-blkfront8 is 32 - higher value means more potential throughput but more
/Linux-v6.1/arch/parisc/math-emu/
Dfpu.h29 * is through the potential type field from the PDC_MODEL call.
/Linux-v6.1/drivers/parisc/
DREADME.dino4 ** "HP has discovered a potential system defect that can affect
/Linux-v6.1/Documentation/process/
Dembargoed-hardware-issues.rst48 identified a potential hardware flaw.
110 or anyone becomes aware of a potential violation, please report it
300 to participate in the communication send a list of potential subscribers to
/Linux-v6.1/tools/perf/pmu-events/arch/x86/amdzen2/
Dbranch.json16 … "PublicDescription": "Indirect Branch Prediction for potential multi-target branch (speculative)."
/Linux-v6.1/Documentation/devicetree/bindings/input/touchscreen/
Dimx6ul_tsc.txt16 even potential distribution ready.
/Linux-v6.1/Documentation/admin-guide/mm/
Dzswap.rst20 potential configurations and workloads that exist. For this reason, zswap
23 Some potential benefits:
/Linux-v6.1/drivers/usb/musb/
DMakefile32 # PIO only, or DMA (several potential schemes).
/Linux-v6.1/drivers/staging/media/atomisp/pci/
Dia_css_err.h25 * the SP FW could indicate potential performance issue
/Linux-v6.1/Documentation/riscv/
Dpatch-acceptance.rst30 Foundation. To avoid the maintenance complexity and potential
/Linux-v6.1/Documentation/devicetree/bindings/rtc/
Drenesas,sh-rtc.yaml33 # first (if it exists). Additionally, potential clock counting sources
/Linux-v6.1/tools/testing/selftests/powerpc/tm/
Dtm-sigreturn.c11 * restoring the potential TM SPRS from the signal frame is requiring to not be
/Linux-v6.1/arch/mips/include/asm/
Dcompiler.h21 * reordered loads or stores. See this potential GCC fix for details:
/Linux-v6.1/Documentation/virt/
Dguest-halt-polling.rst83 large value has the potential to drive the cpu usage to 100% on a machine

12345678910>>...33