Searched refs:risk (Results 1 – 25 of 73) sorted by relevance
123
| /Linux-v4.19/include/trace/events/ |
| D | rcu.h | 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
|
| /Linux-v4.19/Documentation/ |
| D | irqflags-tracing.txt | 22 rather straightforward and risk-free manner.
46 In general there is no risk from having an incomplete irq-flags-tracing
|
| /Linux-v4.19/drivers/gpu/drm/etnaviv/ |
| D | Kconfig | 24 Say Y unless you want to risk burning your SoC.
|
| /Linux-v4.19/Documentation/misc-devices/ |
| D | ics932s401 | 31 do this, as you risk damaging your system!
|
| /Linux-v4.19/Documentation/x86/x86_64/ |
| D | machinecheck | 54 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).
|
| /Linux-v4.19/drivers/staging/erofs/ |
| D | TODO | 3 for all productive uses. play at your own risk :)
|
| D | Kconfig | 86 Play at your own risk.
|
| /Linux-v4.19/drivers/net/wireless/ath/carl9170/ |
| D | Kconfig | 54 other rng source and you can afford to take the risk.
|
| /Linux-v4.19/Documentation/usb/ |
| D | ohci.txt | 25 transfers. Previously, using periods of one frame would risk data loss due
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | hfsplus.txt | 48 or locked. Use at your own risk.
|
| D | gfs2-uevents.txt | 49 cannot add any more functions to it without running the risk of
|
| D | ocfs2.txt | 101 nodes, which gains high performance at risk of getting
|
| /Linux-v4.19/Documentation/i2c/busses/ |
| D | i2c-sis96x | 43 AND is willing to risk crashing & burning an otherwise well-behaved kernel
|
| /Linux-v4.19/Documentation/md/ |
| D | raid5-ppl.txt | 44 are not likely due to high risk of multiple disks failure. Such restriction
|
| /Linux-v4.19/mm/ |
| D | Kconfig.debug | 48 reduce the risk of information leaks from freed data. This does
|
| /Linux-v4.19/arch/arm64/ |
| D | Kconfig.debug | 49 W+X mappings after applying NX, as such mappings are a security risk.
|
| /Linux-v4.19/Documentation/vm/ |
| D | mmu_notifier.rst | 19 Case A is obvious you do not want to take the risk for the device to write to
|
| /Linux-v4.19/Documentation/i2c/ |
| D | DMA-considerations | 27 updated to use this flag will work like before. And like before, they risk
|
| /Linux-v4.19/Documentation/arm/nwfpe/ |
| D | TODO | 66 risk of becoming isolated if and when hardware FP emulation comes out
|
| /Linux-v4.19/Documentation/admin-guide/mm/ |
| D | transhuge.rst | 82 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
|
| /Linux-v4.19/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 166 is exceeded, even if there isn't an actual risk of missing
|
| D | Kconfig | 117 you own risk.
|
| /Linux-v4.19/Documentation/devicetree/bindings/leds/ |
| D | common.txt | 43 introducing a risk of hardware damage in case an excessive
|
| /Linux-v4.19/arch/arm/boot/dts/ |
| D | am335x-bone-common.dtsi | 307 * mode and risk hardware damage if this mode is entered.
|
| /Linux-v4.19/Documentation/process/ |
| D | stable-kernel-rules.rst | 20 As these fixes are not as obvious and have a higher risk of a subtle
|
123
