| /linux-4.4.14/include/trace/events/ |
| D | rcu.h | 597 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' : '.')
728 #define trace_rcu_batch_end(rcuname, callbacks_invoked, cb, nr, iit, risk) \ argument
|
| /linux-4.4.14/Documentation/ |
| D | irqflags-tracing.txt | 20 rather straightforward and risk-free manner.
44 in general there is no risk from having an incomplete irq-flags-tracing
|
| D | stable_kernel_rules.txt | 17 As these fixes are not as obvious and have a higher risk of a subtle
|
| D | ntb.txt | 56 hardware. You may override this behavior at your own risk by setting
|
| D | vfio.txt | 41 greatest risk to the overall system integrity.
43 To help mitigate this risk, many modern IOMMUs now incorporate
|
| D | sysfs-rules.txt | 9 To minimize the risk of breaking users of sysfs, which are in most cases
|
| D | 00-INDEX | 4 alphabetical order as well, or risk being hunted down like a rabid dog.
|
| D | applying-patches.txt | 128 anyway, then there's a high risk that either your local source tree or the
|
| D | HOWTO | 243 risk of causing regressions with such a change as long as the change
|
| /linux-4.4.14/Documentation/misc-devices/ |
| D | ics932s401 | 31 do this, as you risk damaging your system!
|
| /linux-4.4.14/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-4.4.14/Documentation/usb/ |
| D | ohci.txt | 25 transfers. Previously, using periods of one frame would risk data loss due
|
| D | usb-serial.txt | 137 NOTE: This has NOT been tested. Use at your own risk.
|
| /linux-4.4.14/drivers/net/wireless/ath/carl9170/ |
| D | Kconfig | 56 other rng source and you can afford to take the risk.
|
| /linux-4.4.14/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-4.4.14/Documentation/i2c/busses/ |
| D | i2c-sis96x | 43 AND is willing to risk crashing & burning an otherwise well-behaved kernel
|
| /linux-4.4.14/Documentation/devicetree/bindings/leds/ |
| D | common.txt | 34 introducing a risk of hardware damage in case an excessive
|
| /linux-4.4.14/Documentation/arm/nwfpe/ |
| D | TODO | 66 risk of becoming isolated if and when hardware FP emulation comes out
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | am335x-bone-common.dtsi | 295 * mode and risk hardware damage if this mode is entered.
|
| /linux-4.4.14/Documentation/vm/ |
| D | transhuge.txt | 88 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.4.14/Documentation/isdn/ |
| D | README.sc | 10 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
|
| D | README.x25 | 5 This is alpha/beta test code. Use it completely at your own risk.
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | ramdisk.txt | 26 to support an unlimited number of RAM disks (at your own risk). Just change
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | nct6775 | 167 Untested; use at your own risk.
|
| /linux-4.4.14/Documentation/timers/ |
| D | timekeeping.txt | 42 potentially being updated in between leading to the risk of very strange
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | timestamping.txt | 134 the hardware, there is a risk of misalignment with the avail and delay
|
| /linux-4.4.14/Documentation/scsi/ |
| D | tmscsim.txt | 179 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
|
| D | aic79xx.txt | 179 only be used at the customer's own risk.
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 3.Early-stage | 29 onto processes which they would not otherwise have) and a risk to system
|
| D | 2.Process | 376 represent a potential hazard to developers, who risk getting buried under a
|
| /linux-4.4.14/Documentation/input/ |
| D | alps.txt | 14 table, with the risk of regression testing existing devices, or isolate
|
| D | joystick-parport.txt | 10 it will be true. So, use it at your own risk. The possible damages that can
|
| /linux-4.4.14/arch/x86/ |
| D | Kconfig.debug | 121 W+X mappings after applying NX, as such mappings are a security risk.
|
| D | Kconfig | 2073 eliminate any risk of ASLR bypass due to the vsyscall
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | README | 210 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.4.14/Documentation/RCU/ |
| D | checklist.txt | 50 actuarial risk of your kernel.
|
| /linux-4.4.14/mm/ |
| D | Kconfig | 426 madvise(MADV_HUGEPAGE) but it won't risk to increase the
|
| /linux-4.4.14/drivers/char/ |
| D | Kconfig | 131 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
|
| /linux-4.4.14/Documentation/networking/ |
| D | scaling.txt | 398 change without the risk of generating out of order packets. The
|
| D | ip-sysctl.txt | 925 datagrams, or risk confusing the switch and leaving groups you don't
|
| /linux-4.4.14/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 561 however at the risk of restricting creativity and limiting vendor
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-deadline.txt | 161 Moreover, if the total utilization is larger than M, then we risk starving
|
| /linux-4.4.14/Documentation/nvdimm/ |
| D | nvdimm.txt | 707 1. Why not "volume" for instance? "volume" ran the risk of confusing
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | unified-hierarchy.txt | 625 shortcut comes with high risk. We go through what we go through for
|
| D | cpusets.txt | 446 across partially overlapping sets of CPUs would risk unstable dynamics
|
| /linux-4.4.14/arch/blackfin/ |
| D | Kconfig | 1440 manuals. There is a theoretical risk that during VDDINT transitions
|
| /linux-4.4.14/drivers/video/fbdev/ |
| D | Kconfig | 952 totally untested. Use at your own risk. If unsure, say N.
1143 risk.
|
| /linux-4.4.14/Documentation/laptops/ |
| D | thinkpad-acpi.txt | 156 sent to mainline for merging, you do so on your own risk: these features
|