Home
last modified time | relevance | path

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

12345678910>>...17

/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-5.10/tools/power/cpupower/debug/i386/
Dintel_gsic.c52 "RISK.\n"); in main()
59 "RISK.\n"); in main()
/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-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-5.10/Documentation/misc-devices/
Dics932s401.rst36 do this, as you risk damaging your system!
/kernel/linux/linux-5.10/Documentation/usb/
Dohci.rst29 transfers. Previously, using periods of one frame would risk data loss due
/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/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-5.10/Documentation/filesystems/
Dhfsplus.rst50 or locked. Use at your own risk.
/kernel/linux/linux-5.10/Documentation/doc-guide/
Dmaintainer-profile.rst35 window opens, since the risk of regressions from documentation patches is
/kernel/linux/linux-5.10/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-5.10/arch/arm64/include/asm/
Drwonce.h27 * When building with LTO, there is an increased risk of the compiler
/kernel/linux/linux-5.10/include/linux/
Ddelay.h30 * risk overflow for high loops_per_jiffy (high bogomips) machines. The
/kernel/linux/linux-5.10/tools/testing/selftests/timers/
Dleapcrash.c11 * RUN AT YOUR OWN RISK!
/kernel/linux/linux-5.10/Documentation/driver-api/md/
Draid5-ppl.rst46 are not likely due to high risk of multiple disks failure. Such restriction
/kernel/linux/linux-5.10/Documentation/process/
Ddeprecated.rst58 risk of them overflowing. This could lead to values wrapping around and a
112 compiler flags help reduce the risk of using this function, there is
174 eliminate VLAs, they are also a security risk. Dynamic growth of a stack
/kernel/linux/linux-5.10/drivers/crypto/cavium/zip/
Dzip_inflate.h42 * ENTIRE RISK ARISING OUT OF USE OR PERFORMANCE OF THE SOFTWARE LIES
Dzip_deflate.h42 * ENTIRE RISK ARISING OUT OF USE OR PERFORMANCE OF THE SOFTWARE LIES
Dzip_mem.h42 * ENTIRE RISK ARISING OUT OF USE OR PERFORMANCE OF THE SOFTWARE LIES
/kernel/linux/linux-5.10/drivers/gpu/drm/i915/
Di915_utils.c110 * of the addition and reduce the risk of losing a jiffie. in set_timer_ms()
/kernel/linux/linux-5.10/arch/arm64/kernel/vdso/
Dsigreturn.S29 * much more comprehensive to reduce the risk of further regressions.
/kernel/linux/linux-5.10/Documentation/i2c/busses/
Di2c-sis96x.rst48 AND is willing to risk crashing & burning an otherwise well-behaved kernel

12345678910>>...17