Home
last modified time | relevance | path

Searched refs:risk (Results 1 – 46 of 46) sorted by relevance

/linux-4.1.27/include/trace/events/
Drcu.h597 char cb, char nr, char iit, char risk),
599 TP_ARGS(rcuname, callbacks_invoked, cb, nr, iit, risk),
607 __field(char, risk)
616 __entry->risk = risk;
624 __entry->risk ? 'R' : '.')
729 #define trace_rcu_batch_end(rcuname, callbacks_invoked, cb, nr, iit, risk) \ argument
/linux-4.1.27/Documentation/
Dirqflags-tracing.txt20 rather straightforward and risk-free manner.
44 in general there is no risk from having an incomplete irq-flags-tracing
Dstable_kernel_rules.txt17 As these fixes are not as obvious and have a higher risk of a subtle
Dvfio.txt41 greatest risk to the overall system integrity.
43 To help mitigate this risk, many modern IOMMUs now incorporate
Dsysfs-rules.txt9 To minimize the risk of breaking users of sysfs, which are in most cases
D00-INDEX4 alphabetical order as well, or risk being hunted down like a rabid dog.
Dapplying-patches.txt128 anyway, then there's a high risk that either your local source tree or the
DHOWTO243 risk of causing regressions with such a change as long as the change
/linux-4.1.27/Documentation/misc-devices/
Dics932s40131 do this, as you risk damaging your system!
/linux-4.1.27/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).
/linux-4.1.27/drivers/net/wireless/ath/carl9170/
DKconfig56 other rng source and you can afford to take the risk.
/linux-4.1.27/Documentation/usb/
Dohci.txt25 transfers. Previously, using periods of one frame would risk data loss due
Dusb-serial.txt137 NOTE: This has NOT been tested. Use at your own risk.
/linux-4.1.27/Documentation/filesystems/
Dhfsplus.txt48 or locked. Use at your own risk.
Dgfs2-uevents.txt49 cannot add any more functions to it without running the risk of
Docfs2.txt101 nodes, which gains high performance at risk of getting
/linux-4.1.27/Documentation/i2c/busses/
Di2c-sis96x43 AND is willing to risk crashing & burning an otherwise well-behaved kernel
/linux-4.1.27/Documentation/arm/nwfpe/
DTODO66 risk of becoming isolated if and when hardware FP emulation comes out
/linux-4.1.27/arch/arm/boot/dts/
Dam335x-bone-common.dtsi229 * mode and risk hardware damage if this mode is entered.
/linux-4.1.27/Documentation/vm/
Dtranshuge.txt88 to eliminate any risk of wasting any precious byte of memory and to
92 risk to lose memory by using hugepages, should use
99 avoid the risk of consuming more memory resources) or enabled system
/linux-4.1.27/Documentation/isdn/
DREADME.sc10 risk. There is NO SUPPORT for this software. Some help may be available
13 total risk by using this driver, we encourage you to join the beta
DREADME.x255 This is alpha/beta test code. Use it completely at your own risk.
/linux-4.1.27/Documentation/blockdev/
Dramdisk.txt26 to support an unlimited number of RAM disks (at your own risk). Just change
/linux-4.1.27/Documentation/hwmon/
Dnct6775163 Untested; use at your own risk.
/linux-4.1.27/Documentation/sound/alsa/
Dtimestamping.txt134 the hardware, there is a risk of misalignment with the avail and delay
/linux-4.1.27/Documentation/timers/
Dtimekeeping.txt42 potentially being updated in between leading to the risk of very strange
/linux-4.1.27/Documentation/scsi/
Dtmscsim.txt179 it, but that's out of adapter spec, on your own risk and unlikely to improve
274 parameter lines have the risk to be misinterpreted and the length of kernel
Daic79xx.txt179 only be used at the customer's own risk.
/linux-4.1.27/Documentation/development-process/
D3.Early-stage29 onto processes which they would not otherwise have) and a risk to system
D2.Process376 represent a potential hazard to developers, who risk getting buried under a
/linux-4.1.27/Documentation/input/
Dalps.txt14 table, with the risk of regression testing existing devices, or isolate
Djoystick-parport.txt10 it will be true. So, use it at your own risk. The possible damages that can
/linux-4.1.27/Documentation/filesystems/cifs/
DREADME210 of the standard mount options "noexec" and "nosuid" to reduce the risk of
519 very slow, and some servers may be reliable enough (to risk
522 applications that fsync too much, at a small risk of server
/linux-4.1.27/Documentation/RCU/
Dchecklist.txt50 actuarial risk of your kernel.
/linux-4.1.27/Documentation/scheduler/
Dsched-deadline.txt151 Moreover, if the total utilisation is larger than M, then we risk starving
/linux-4.1.27/mm/
DKconfig443 madvise(MADV_HUGEPAGE) but it won't risk to increase the
/linux-4.1.27/Documentation/cgroups/
Dunified-hierarchy.txt439 shortcut comes with high risk. We go through what we go through for
Dcpusets.txt446 across partially overlapping sets of CPUs would risk unstable dynamics
/linux-4.1.27/Documentation/networking/
Dscaling.txt398 change without the risk of generating out of order packets. The
Dip-sysctl.txt882 datagrams, or risk confusing the switch and leaving groups you don't
/linux-4.1.27/drivers/char/
DKconfig131 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
/linux-4.1.27/Documentation/netlabel/
Ddraft-ietf-cipso-ipsecurity-01.txt561 however at the risk of restricting creativity and limiting vendor
/linux-4.1.27/arch/blackfin/
DKconfig1440 manuals. There is a theoretical risk that during VDDINT transitions
/linux-4.1.27/drivers/video/fbdev/
DKconfig952 totally untested. Use at your own risk. If unsure, say N.
1143 risk.
/linux-4.1.27/Documentation/laptops/
Dthinkpad-acpi.txt156 sent to mainline for merging, you do so on your own risk: these features
/linux-4.1.27/arch/x86/
DKconfig1069 your own risk.