Home
last modified time | relevance | path

Searched full:risk (Results 1 – 25 of 778) sorted by relevance

12345678910>>...32

/kernel/linux/linux-4.19/Documentation/
Dirqflags-tracing.txt22 rather straightforward and risk-free manner.
46 In general there is no risk from having an incomplete irq-flags-tracing
/kernel/linux/linux-5.10/Documentation/core-api/irq/
Dirqflags-tracing.rst22 rather straightforward and risk-free manner.
46 In general there is no risk from having an incomplete irq-flags-tracing
/kernel/linux/linux-4.19/Documentation/x86/x86_64/
Dmachinecheck54 how hard the kernel tries to recover even at some risk of
56 with the risk of a crash or even corruption (for tolerant >= 3).
/kernel/linux/linux-4.19/tools/power/cpupower/debug/i386/
Dintel_gsic.c53 "RISK.\n"); in main()
60 "RISK.\n"); in main()
/kernel/linux/linux-5.10/tools/power/cpupower/debug/i386/
Dintel_gsic.c52 "RISK.\n"); in main()
59 "RISK.\n"); in main()
/kernel/linux/linux-4.19/include/trace/events/
Drcu.h632 * and the sixth argument (risk) is the return value from
638 char cb, char nr, char iit, char risk),
640 TP_ARGS(rcuname, callbacks_invoked, cb, nr, iit, risk),
648 __field(char, risk)
657 __entry->risk = risk;
665 __entry->risk ? 'R' : '.')
779 #define trace_rcu_batch_end(rcuname, callbacks_invoked, cb, nr, iit, risk) \ argument
/kernel/linux/linux-5.10/Documentation/x86/x86_64/
Dmachinecheck.rst56 how hard the kernel tries to recover even at some risk of
58 with the risk of a crash or even corruption (for tolerant >= 3).
/kernel/linux/linux-5.10/include/trace/events/
Drcu.h663 * and the sixth argument (risk) is the return value from
669 char cb, char nr, char iit, char risk),
671 TP_ARGS(rcuname, callbacks_invoked, cb, nr, iit, risk),
679 __field(char, risk)
688 __entry->risk = risk;
696 __entry->risk ? 'R' : '.')
/kernel/linux/linux-5.10/drivers/gpu/drm/etnaviv/
DKconfig24 Say Y unless you want to risk burning your SoC.
/kernel/linux/linux-4.19/drivers/gpu/drm/etnaviv/
DKconfig24 Say Y unless you want to risk burning your SoC.
/kernel/linux/linux-5.10/mm/
DKconfig.debug71 reduce the risk of information leaks from freed data. This does
133 mappings after applying NX, as such mappings are a security risk.
/kernel/linux/linux-4.19/Documentation/misc-devices/
Dics932s40131 do this, as you risk damaging your system!
/kernel/linux/linux-5.10/Documentation/misc-devices/
Dics932s401.rst36 do this, as you risk damaging your system!
/kernel/linux/linux-4.19/drivers/net/wireless/ath/carl9170/
DKconfig54 other rng source and you can afford to take the risk.
/kernel/linux/linux-5.10/drivers/net/wireless/ath/carl9170/
DKconfig53 other rng source and you can afford to take the risk.
/kernel/linux/linux-5.10/Documentation/usb/
Dohci.rst29 transfers. Previously, using periods of one frame would risk data loss due
/kernel/linux/linux-4.19/drivers/staging/erofs/
DTODO3 for all productive uses. play at your own risk :)
/kernel/linux/linux-4.19/Documentation/usb/
Dohci.txt25 transfers. Previously, using periods of one frame would risk data loss due
/kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/
Datomisp_internal.h115 * The bigger the value, the higher risk that the ISP is not
117 * vertical blanking time, increasing risk of dropped frames.
/kernel/linux/linux-5.10/arch/powerpc/platforms/pseries/
Dkexec.c23 * Don't risk a hypervisor call if we're crashing in pseries_kexec_cpu_down()
/kernel/linux/linux-4.19/Documentation/admin-guide/mm/
Dtranshuge.rst82 to eliminate any risk of wasting any precious byte of memory and to
86 risk to lose memory by using hugepages, should use
99 regions (to avoid the risk of consuming more memory resources) or enabled
/kernel/linux/linux-4.19/Documentation/filesystems/
Dhfsplus.txt48 or locked. Use at your own risk.
/kernel/linux/linux-5.10/Documentation/filesystems/
Dhfsplus.rst50 or locked. Use at your own risk.
/kernel/linux/linux-4.19/arch/powerpc/platforms/pseries/
Dkexec.c27 * Don't risk a hypervisor call if we're crashing in pseries_kexec_cpu_down()
/kernel/linux/linux-4.19/include/linux/
Ddelay.h30 * risk overflow for high loops_per_jiffy (high bogomips) machines. The

12345678910>>...32