Home
last modified time | relevance | path

Searched refs:critical (Results 1 – 162 of 162) sorted by relevance

/linux-4.1.27/Documentation/hwmon/
Dsmm66552 Each monitored channel has its own high and low limits, plus a critical
120 in1_lcrit 12v input critical minimum voltage (mV)
121 in2_lcrit 3.3V (VDD) input critical minimum voltage (mV)
122 in3_lcrit Channel A critical minimum voltage (mV)
123 in4_lcrit Channel B critical minimum voltage (mV)
124 in5_lcrit Channel C critical minimum voltage (mV)
125 in6_lcrit Channel D critical minimum voltage (mV)
126 in7_lcrit Channel E critical minimum voltage (mV)
127 in8_lcrit Channel F critical minimum voltage (mV)
128 in9_lcrit AIN1 critical minimum voltage (mV)
[all …]
Dzl6100121 in1_lcrit_alarm Input voltage critical low alarm.
122 in1_crit_alarm Input voltage critical high alarm.
130 in2_lcrit_alarm VMON/VDRV voltage critical low alarm.
131 in2_crit_alarm VMON/VDRV voltage critical high alarm.
140 inX_lcrit_alarm Critical output voltage critical low alarm.
141 inX_crit_alarm Critical output voltage critical high alarm.
149 curr1_lcrit_alarm Output current critical low alarm.
150 curr1_crit_alarm Output current critical high alarm.
159 temp[12]_lcrit_alarm Chip temperature critical low alarm.
160 temp[12]_crit_alarm Chip temperature critical high alarm.
Dadt741035 exceeded, as well as a critical temperature (CT) pin to indicate that the
36 critical temperature set point has been exceeded. Both pins can be set up with a
56 maximum and critical temperature, it can only be set for temp#_max_hyst.
67 temp#_crit - critical temperature setpoint
70 temp#_crit_hyst - hysteresis for critical temperature (read-only)
73 temp#_crit_alarm - critical temperature alarm flag
Dltc297871 in1_lcrit_alarm Input voltage critical low alarm.
73 in1_crit_alarm Input voltage critical high alarm.
92 in[N]_lcrit_alarm Output voltage critical low alarm.
93 in[N]_crit_alarm Output voltage critical high alarm.
114 temp[N]_lcrit_alarm Temperature critical low alarm.
115 temp[N]_crit_alarm Temperature critical high alarm.
153 curr[N]_crit_alarm Output current critical high alarm.
154 curr[N]_lcrit_alarm Output current critical low alarm. LTC2974 only.
Dmax868851 in1_lcrit_alarm Voltage critical low alarm. From VOLTAGE_UV_FAULT status.
52 in1_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT status.
61 curr1_crit_alarm Current critical high alarm. From IOUT_OC_FAULT status.
71 temp1_crit_alarm Chip temperature critical high alarm. Set by comparing
Ducd920063 in1_lcrit_alarm Voltage critical low alarm. From VIN_UV_FAULT status.
64 in1_crit_alarm Voltage critical high alarm. From VIN_OV_FAULT status.
74 in[2-5]_lcrit_alarm Voltage critical low alarm. From VOLTAGE_UV_FAULT status.
75 in[2-5]_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT status.
87 curr[2-5]_crit_alarm Current critical high alarm. From IOUT_OC_FAULT status.
108 temp[1-5]_crit_alarm Temperature critical high alarm.
Dpmbus46 Each monitored channel has its own high and low limits, plus a critical
158 inX_lcrit_alarm Voltage critical low alarm.
160 inX_crit_alarm Voltage critical high alarm.
175 currX_lcrit_alarm Output current critical low alarm.
177 currX_crit_alarm Current critical high alarm.
189 powerX_crit_alarm Output power critical high alarm.
207 tempX_lcrit_alarm Chip temperature critical low alarm. Set by comparing
210 tempX_crit_alarm Chip temperature critical high alarm. Set by comparing
Dlm7722 critical (temp1_crit.) It also implements an hysteresis mechanism which
29 difference staying unchanged. For example, if the old critical limit
31 the critical limit to 90 degrees C, then the hysteresis will
Dlm2506676 in1_lcrit_alarm Input voltage critical low alarm (LM25063 only).
77 in1_crit_alarm Input voltage critical high alarm. (LM25063 only).
101 curr1_crit_alarm Input current critical high alarm (LM25063 only).
120 temp1_crit_alarm Chip temperature critical high alarm.
Dmax1606451 in[1-4]_lcrit_alarm Voltage critical low alarm. From VOLTAGE_UV_FAULT status.
52 in[1-4]_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT status.
62 temp1_crit_alarm Chip temperature critical high alarm. Set by comparing
Demc140342 (tempX_max) and critical (tempX_crit.) The chips also implement an
50 difference staying unchanged. For example, if the old critical limit
52 the critical limit to 90 degrees C, then the hysteresis will
Ducd900079 in[1-12]_lcrit_alarm Voltage critical low alarm. From VOLTAGE_UV_FAULT status.
80 in[1-12]_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT status.
89 curr[1-12]_crit_alarm Current critical high alarm. From IOUT_OC_FAULT status.
100 temp[1-2]_crit_alarm Temperature critical high alarm.
Dmax3444082 in[1-6]_lcrit_alarm Voltage critical low alarm. From VOLTAGE_UV_FAULT status.
83 in[1-6]_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT status.
95 curr[1-6]_crit_alarm Current critical high alarm. From IOUT_OC_FAULT status.
118 temp[1-8]_crit_alarm Temperature critical high alarm.
Dtps4042251 curr1_crit_alarm Current critical high alarm. From IOUT_OC_FAULT status.
60 temp1_crit_alarm Chip temperature critical high alarm. Set by comparing
Dlm9524531 Each sensor has its own critical limit. Additionally, there is a relative
32 hysteresis value common to both critical limits. To make life easier to
Dmax669756 tempX_crit RW temperature critical threshold
57 tempX_crit_alarm RO temperature critical threshold alarm
Dmax1606551 Each monitored channel has its own low and high critical limits. MAX16065,
93 in[0-11]_lcrit Low critical limit.
95 in[0-11]_crit High critical limit.
Djc4275 and critical temperature can be configured. There are alarms for high, low,
76 and critical thresholds.
102 temp1_crit_alarm Temperature critical alarm
Dlm90150 family is that it features critical limits with hysteresis, and an
159 * ALERT is triggered by temperatures over critical limits.
187 * Second critical temperature limit
197 * Second critical temperature limit
218 Each sensor has its own high and low limits, plus a critical limit.
219 Additionally, there is a relative hysteresis value common to both critical
Dw83627ehf172 critical temperature protection
177 0x6b: only on DHG, SYS fan critical temperature
178 0x6c: only on DHG, CPU fan0 critical temperature
179 0x6d: only on DHG, AUX fan critical temperature
180 0x6e: only on DHG, CPU fan1 critical temperature
Dsysfs-interface109 in[0-*]_lcrit Voltage critical min value.
120 in[0-*]_crit Voltage critical max value.
341 temp[1-*]_crit Temperature critical max value, typically greater than
347 Temperature hysteresis value for critical limit.
350 from the critical value.
367 temp[1-*]_lcrit Temperature critical min value, typically lower than
373 Temperature hysteresis value for critical min limit.
376 from the critical min value.
435 curr[1-*]_lcrit Current critical low value
439 curr[1-*]_crit Current critical high value.
Dabx50022 raises interrupt when critical temperature reached.
Dadm103131 Each temperature channel has its own high and low limits, plus a critical
Dlm6336 - No critical limit for local temperature.
38 will consider that the critical limit is read-only.
Dlm9232 alarms for high, low, and critical thresholds. There's also an hysteresis to
Dnct677548 can be monitored and compared against minimum, maximum, and critical
174 critical temperature mode, in which the fans should run at full speed.
184 Temperature tolerance for critical temperature,
Dlm9523436 have a critical limit.
Dlineage-pem57 in1_crit Output voltage critical alarm
Dlm8379 Each sensor has its own high limit, but the critical limit is common to
Dit87262 must be programmed to the critical CPU temperature.
/linux-4.1.27/Documentation/virtual/
Dparavirt_ops.txt8 hypervisors. It allows each hypervisor to override critical operations and
13 corresponding to low level critical instructions and high level
15 time by enabling binary patching of the low-ops critical operations
25 Usually these operations correspond to low level critical instructions. They
26 are called frequently and are performance critical. The overhead is
32 them are very performance critical.
/linux-4.1.27/Documentation/RCU/
Dlockdep.txt5 critical section. Each flavor of RCU is tracked separately (but note
27 Check for RCU read-side critical section.
29 Check for RCU-bh read-side critical section.
31 Check for RCU-sched read-side critical section.
33 Check for SRCU read-side critical section.
86 1. An RCU read-side critical section (implicit), or
91 RCU read-side critical sections, in case (2) the ->file_lock prevents
102 complain if this was used in an RCU read-side critical section unless one
111 being in an RCU read-side critical section. In the future, separate
Dlockdep-splat.txt9 RCU read-side critical section or (2) holding the right update-side lock.
67 This form says that it must be in a plain vanilla RCU read-side critical
79 code was invoked either from within an RCU read-side critical section
84 On the other hand, perhaps we really do need an RCU read-side critical
85 section. In this case, the critical section must span the use of the
99 read-side critical section, which again would have suppressed the
DwhatisRCU.txt78 critical sections.
138 entering an RCU read-side critical section. It is illegal
139 to block while in an RCU read-side critical section, though
141 read-side critical sections. Any RCU-protected data structure
142 accessed during an RCU read-side critical section is guaranteed to
143 remain unreclaimed for the full duration of that critical section.
152 exiting an RCU read-side critical section. Note that RCU
153 read-side critical sections may be nested and/or overlapping.
161 read-side critical sections on all CPUs have completed.
163 any subsequent RCU read-side critical sections to complete.
[all …]
DUP.txt47 all RCU read-side critical sections currently executing have completed.
65 the same critical section, then the code would need to create
102 list, and is therefore within an RCU read-side critical section.
104 read-side critical section, and is not permitted to block.
119 the process-context critical section. This would result in
132 of an RCU read-side critical section. If synchronize_rcu()
Dchecklist.txt45 2. Do the RCU read-side critical sections make proper use of
136 of an RCU read-side critical section. See lockdep.txt
167 be traversed by an RCU read-side critical section.
294 critical section or must be protected by appropriate update-side
295 locks. RCU read-side critical sections are delimited by
307 10. Conversely, if you are in an RCU read-side critical section,
315 critical sections complete. It does -not- necessarily guarantee
318 read-side critical sections are protected by something other
341 interrupting that acquisition's critical section.
362 RCU, it -is- permissible to block in an SRCU read-side critical
[all …]
Drcu.txt34 read-side critical sections. So, if we remove an item from a
42 RCU read-side critical sections. SRCU also uses CPU-local
44 critical sections. These variants of RCU detect grace periods
86 boosting of preempted RCU read-side critical sections. This is
Dtrace.txt368 read-side critical section blocks the current grace
370 at least one task blocked in an RCU read-side critical
374 critical section, regardless of whether any current
462 in an RCU read-side critical section.
Dstallwarn.txt180 o A CPU looping in an RCU read-side critical section.
206 read-side critical section. This is especially damaging if
Drcubarrier.txt8 and unbounded latency. RCU read-side critical sections are delimited
Dtorture.txt82 read-side critical sections.
DRTFP.txt151 preemption of RCU realtime critical sections [PaulMcKenney05a,
156 RCU [PaulEMcKenney2006b], but priority-boosting of RCU read-side critical
158 blocking in read-side critical sections appeared [PaulEMcKenney2006c],
1248 preemptable RCU read side critical sections.
/linux-4.1.27/drivers/acpi/
Dthermal.c128 u8 critical:1; member
168 struct acpi_thermal_critical critical; member
297 tz->trips.critical.temperature = tmp; in acpi_thermal_trips_update()
305 tz->trips.critical.flags.valid = 0; in acpi_thermal_trips_update()
311 tz->trips.critical.flags.valid = 0; in acpi_thermal_trips_update()
313 tz->trips.critical.flags.valid = 1; in acpi_thermal_trips_update()
316 tz->trips.critical.temperature)); in acpi_thermal_trips_update()
318 if (tz->trips.critical.flags.valid == 1) { in acpi_thermal_trips_update()
320 tz->trips.critical.flags.valid = 0; in acpi_thermal_trips_update()
326 if (crt_k > tz->trips.critical.temperature) in acpi_thermal_trips_update()
[all …]
/linux-4.1.27/arch/powerpc/platforms/pseries/
Dras.c190 int critical; in ras_epow_interrupt() local
196 critical = 1; /* Time Critical */ in ras_epow_interrupt()
198 critical = 0; in ras_epow_interrupt()
206 critical, __pa(&ras_log_buf), in ras_epow_interrupt()
/linux-4.1.27/include/net/
Dgeneve.h50 u8 critical:1; member
56 u8 critical:1;
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-driver-intel-rapid-start8 critical level
13 critical level.
/linux-4.1.27/arch/arm/boot/dts/
Drk3288-thermal.dtsi35 type = "critical";
63 type = "critical";
Dexynos5440-trip-points.dtsi23 type = "critical";
Domap5-gpu-thermal.dtsi25 type = "critical";
Domap5-core-thermal.dtsi25 type = "critical";
Dexynos5420-trip-points.dtsi33 type = "critical";
Domap4-cpu-thermal.dtsi30 type = "critical";
Dexynos4-cpu-thermal.dtsi39 type = "critical";
Dorion5x-maxtor-shared-storage-2.dts64 * accidentally erasing critical flash sectors. We thus define
Dorion5x-lacie-ethernet-disk-mini-v2.dts85 * accidentally erasing critical flash sectors. We thus define
Dorion5x-lacie-d2-network.dts104 * accidentally erasing critical flash sectors. We thus define
Dste-snowball.dts331 trip3-type = "critical";
Dam57xx-beagle-x15.dts603 type = "critical";
Dtegra124-jetson-tk1.dts1912 type = "critical";
1926 type = "critical";
1940 type = "critical";
Dsun5i-a13.dtsi89 type = "critical";
Dsun4i-a10.dtsi115 type = "critical";
Dsun7i-a20.dtsi154 type = "critical";
/linux-4.1.27/Documentation/
Dpi-futex.txt38 I.e. critical RT apps often choose lock structures to protect critical
59 non-preemptible in a critical section, so the 'use spinlocks' argument
67 even if all critical sections are coded carefully to be deterministic
68 (i.e. all critical sections are short in duration and only execute a
72 executes the critical section, and could delay it indefinitely.
Dpreempt-locking.txt42 switch. For example, on x86, entering and exiting FPU mode is now a critical
68 duration of the critical region.
105 critical variables. Another example:
Dvolatile-considered-harmful.txt44 to shared_data _within_ the critical section, when we know that nobody else
52 accesses within a critical section. But, within the kernel, I/O memory
75 each accessor call becomes a little critical section on its own and
Dio_ordering.txt7 critical section of code protected by spinlocks. This would ensure that
DSM501.txt51 functions, which are transient and thus their location is less critical
Dstable_kernel_rules.txt14 critical.
Dkref.txt249 it's important that kref_get_unless_zero is enclosed in the same critical
Dstatic-keys.txt137 Tracepoints are disabled by default, and can be placed in performance critical
Dkmemleak.txt116 To test a critical section on demand with a clean kmemleak do:
Dintel_txt.txt207 any other macrocode and its correct operation is critical to the
Dmemory-barriers.txt460 words, within a given variable's critical section, all accesses of all
461 previous critical sections for that variable are guaranteed to have
1818 one-way barriers is that the effects of instructions outside of a critical
1819 section may seep into the inside of the critical section.
1848 Without smp_mb__after_unlock_lock(), the CPU's execution of the critical
1887 With smp_mb__after_unlock_lock(), the two critical sections cannot overlap.
2475 issued prior to unlocking the critical section.
2492 form of locking), such that the critical operations are all contained within
Dthis_cpu_ops.txt138 access local per cpu data in a critical section. When preemption
Dcpu-hotplug.txt120 Just remember the critical section cannot call any
Dinitrd.txt137 (if space is critical, you may want to use the Minix FS instead of Ext2)
DManagementStyle115 healthy dose of critical thinking on what they do.
Dvfio.txt39 by far the most critical aspect for maintaining a secure environment
Dapplying-patches.txt273 critical fixes for security problems or significant regressions discovered
Dkernel-parameters.txt657 some critical bits.
1876 2 (KERN_CRIT) critical conditions
3573 -1: disable all critical trip points in all thermal zones
3574 <degrees C>: override all critical trip points
3578 critical and hot trip points.
DDMA-API.txt309 critical that the driver do something, in the case of a block driver
DHOWTO268 relatively small and critical fixes for security problems or significant
DIPMI.txt670 * Sensor Type: 0x20 (OS critical stop sensor)
DCodingStyle364 it's performance-critical, and it will probably do a better job of it
/linux-4.1.27/Documentation/devicetree/bindings/thermal/
Ddb8500-thermal.txt13 "critical";
42 trip2-type = "critical";
Dthermal.txt99 "critical": Hardware not reliable.
274 type = "critical";
349 type = "critical";
376 type = "critical";
403 type = "critical";
569 type = "critical";
Drockchip-thermal.txt56 type = "critical";
/linux-4.1.27/Documentation/devicetree/bindings/power_supply/
Dcharger-manager.txt26 -cold : critical cold temperature of battery for charging
28 -hot : critical hot temperature of battery for charging
/linux-4.1.27/arch/powerpc/include/uapi/asm/
Dkvm_para.h39 __u64 critical; /* Guest may not get interrupts if == r1 */ member
/linux-4.1.27/crypto/asymmetric_keys/
Dx509.asn158 critical BOOLEAN DEFAULT,
/linux-4.1.27/Documentation/locking/
Dspinlocks.txt10 ... critical section here ..
50 readers to be in the same critical region at once, but if somebody wants
54 simple spinlocks. Unless the reader critical section is long, you
64 .. critical section that only reads the info ...
Dlocktorture.txt16 different critical region behaviors. The amount of contention on the lock
17 can be simulated by either enlarging this critical region hold time and/or
Dlglock.txt29 resulting in a globally visible critical section.
45 lock at the end of the critical section even if migrated. This should
Drt-mutex.txt28 well-designed applications to use userspace locks in critical parts of
Dmutex-design.txt155 Unless the strict semantics of mutexes are unsuitable and/or the critical
Drt-mutex-design.txt91 entering critical sections simultaneously.
538 latency of that critical section (since the low priority process just entered
/linux-4.1.27/net/hsr/
DKconfig25 relying on this code in a safety critical system!
/linux-4.1.27/Documentation/vm/
Dremap_file_pages.txt18 virtual address space. This use-case is not critical anymore since 64-bit
Dtranshuge.txt5 Performance critical computing applications dealing with large memory
93 madvise(MADV_HUGEPAGE) on their critical mmapped regions.
372 performance critical and they must work natively on hugepages like
Dfrontswap.txt205 entirely unpredictable. This is critical to the definition of frontswap
Dhugetlbpage.txt10 This optimization is more critical now as bigger and bigger physical memories
/linux-4.1.27/include/linux/mfd/
Dabx500.h202 int critical; member
/linux-4.1.27/Documentation/thermal/
Dsysfs-api.txt205 |---temp[1-*]_critical: The critical trip point of thermal zone [1-*]
248 E.g. it can be one of critical, hot, passive, active[0-*] for ACPI
316 ACPI thermal zone may support multiple trip points like critical, hot,
317 passive, active. If an ACPI thermal zone supports critical, passive,
334 |---trip_point_0_type: critical
/linux-4.1.27/Documentation/parisc/
Ddebugging31 Certain, very critical code has to clear the Q bit in the PSW. What
/linux-4.1.27/include/linux/mfd/abx500/
Dab8500-bm.h377 int critical; member
/linux-4.1.27/drivers/thermal/
DKconfig146 It supports one critical trip point and one passive trip point. The
164 ADC (TS-ADC) found on Rockchip SoCs. It supports one critical
261 notification methods.The other trip is a critical trip point, which
/linux-4.1.27/drivers/hwmon/
Dlm85.c275 s8 critical; /* "All fans ON" temp limit */ member
521 data->zone[i].critical = in lm85_update_device()
528 data->zone[i].critical -= 64; in lm85_update_device()
1243 return sprintf(buf, "%d\n", TEMP_FROM_REG(data->zone[nr].critical)); in show_temp_auto_temp_crit()
1260 data->zone[nr].critical = TEMP_TO_REG(val); in set_temp_auto_temp_crit()
1262 data->zone[nr].critical); in set_temp_auto_temp_crit()
/linux-4.1.27/kernel/
DKconfig.preempt42 all kernel code (that is not executing in a critical section)
/linux-4.1.27/Documentation/powerpc/
Dcpu_features.txt24 several paths that are performance-critical and would suffer if an array
Dpci_iov_resource_on_powernv.txt27 that's not critical.
/linux-4.1.27/arch/parisc/kernel/
Dtraps.c160 #define parisc_printk_ratelimited(critical, regs, fmt, ...) { \ argument
161 if ((critical || show_unhandled_signals) && __ratelimit(&_hppa_rs)) { \
/linux-4.1.27/net/openvswitch/
Dvport-geneve.c94 (geneveh->critical ? TUNNEL_CRIT_OPT : 0); in geneve_rcv()
/linux-4.1.27/drivers/power/
Dab8500_bmdata.c396 .critical = 2,
Dab8500_fg.c1163 if (percent <= di->bm->cap_levels->critical || in ab8500_fg_capacity_level()
/linux-4.1.27/Documentation/filesystems/
Dbefs.txt83 instructions on this critical step.
Dfiles.txt53 critical section.
Dpath-lookup.txt227 child of this parent snapshot, we open d_seq critical section on the child
228 before closing d_seq critical section on the parent. This gives an interlocking
Dvfat.txt145 -- specify FAT behavior on critical errors: panic, continue
Dntfs.txt176 errors=opt What to do when critical filesystem errors are found.
/linux-4.1.27/arch/arm/common/
Dmcpm_head.S159 @ Leave the cluster setup critical section:
/linux-4.1.27/Documentation/watchdog/
Dhpwdt.txt40 enables the users of NMIs for non critical events to be work as expected.
/linux-4.1.27/security/integrity/ima/
DKconfig25 whether or not critical system files have been modified.
/linux-4.1.27/arch/s390/kernel/
Dentry.S123 lghi %r11,\savearea # inside critical section, do cleanup
281 j .Lsysc_return # beware of critical section cleanup
587 j .Lio_return # beware of critical section cleanup
722 jno .Lmcck_panic # no -> skip cleanup critical
/linux-4.1.27/Documentation/x86/i386/
DIO-APIC.txt34 none of those IRQ sources is performance-critical.
/linux-4.1.27/net/ipv4/
Dgeneve.c90 geneveh->critical = !!(tun_flags & TUNNEL_CRIT_OPT); in geneve_build_header()
/linux-4.1.27/drivers/usb/
DKconfig133 slower than on a PCI/ISA Parallel Port, so timing critical
/linux-4.1.27/Documentation/filesystems/pohmelfs/
Ddesign_notes.txt49 Only a few non-performance critical operations use the write-through cache and
/linux-4.1.27/arch/arm/kernel/
Dentry-armv.S899 @ 1b = first critical insn, 2b = last critical insn.
/linux-4.1.27/Documentation/networking/
Dnetdev-FAQ.txt118 for networking, Dave collects up patches he deems critical for the
147 explicitly indicate why it is a critical fix and exactly what users are
Dnetconsole.txt173 enable the logging of even the most critical kernel bugs. It works
Dbonding.txt153 It is critical that either the miimon or arp_interval and
/linux-4.1.27/Documentation/arm/
Dvlocks.txt8 These are intended to be used to coordinate critical activity among CPUs
Dcluster-pm-race-avoidance.txt27 means that we need some coordination in order to ensure that critical
/linux-4.1.27/arch/xtensa/kernel/
Dvectors.S318 beq a2, a3, .Lunrecoverable_fixup # critical section
/linux-4.1.27/Documentation/spi/
Dpxa2xx106 used to configure the SSP hardware fifo. These fields are critical to the
/linux-4.1.27/arch/powerpc/boot/dts/
Dtaishan.dts73 interrupts = <0x1 0x4 0x0 0x4>; /* cascade - first non-critical */
/linux-4.1.27/Documentation/laptops/
Ddisk-shock-protection.txt25 the internal hard drive and park its heads on the ramp when critical
/linux-4.1.27/arch/powerpc/include/asm/
Dkvm_ppc.h601 SHARED_WRAPPER(critical, 64)
/linux-4.1.27/Documentation/power/
Dcharger-manager.txt196 and others critical to chargers, the system should be configured to wake up.
/linux-4.1.27/drivers/xen/
DKconfig35 It is very useful on critical systems which require long
/linux-4.1.27/Documentation/timers/
Dhrtimers.txt94 used in various performance-critical areas of e.g. memory management and
/linux-4.1.27/kernel/trace/
DKconfig177 This option measures the time spent in irqs-off critical
201 This option measures the time spent in preemption-off critical
/linux-4.1.27/Documentation/cgroups/
Dcpusets.txt103 kernel to avoid any additional impact on the critical scheduler or
139 into the rest of the kernel, none in performance critical paths:
593 In order to minimize the impact of cpusets on critical kernel
Dcgroups.txt181 and in performance-critical code, whereas operations that require a
193 into the rest of the kernel, none in performance-critical paths:
Dmemory.txt793 The "critical" level means that the system is actively thrashing, it is
826 cgroup experience a critical pressure:
/linux-4.1.27/Documentation/ia64/
Dfsys.txt83 normal Linux system call handler. For performance-critical system
/linux-4.1.27/drivers/platform/x86/
DKconfig407 firmware alerts (like critical battery condition), or misled
861 timeout or when the system battery reaches a critical state,
/linux-4.1.27/Documentation/blockdev/
DREADME.DAC960339 drives are offline or critical or any non-standby physical drives are dead.
379 should never be used on a dead drive that is part of a critical logical
/linux-4.1.27/Documentation/usb/
Dpower-management.txt482 critical section, the best way is to lock the device and call
484 critical section). Holding the device semaphore will block all
/linux-4.1.27/Documentation/development-process/
D5.Posting94 changes in the same patch. If a single patch fixes a critical security
/linux-4.1.27/arch/powerpc/kernel/
Dasm-offsets.c711 critical)); in main()
/linux-4.1.27/arch/x86/math-emu/
DREADME298 For arguments close to critical angles (which occur at multiples of
/linux-4.1.27/Documentation/PCI/
Dpci-error-recovery.txt303 A driver can still return a critical failure for this function if
/linux-4.1.27/Documentation/scsi/
DChangeLog.megaraid_sas45 1. Return DID_ERROR for scsi io, when controller is in critical h/w error.
DBusLogic.txt42 be depended upon for high performance mission critical applications. All of
/linux-4.1.27/arch/powerpc/kvm/
Dbooke.c384 ulong crit_raw = vcpu->arch.shared->critical; in kvmppc_booke_irqprio_deliver()
/linux-4.1.27/drivers/scsi/aic7xxx/
Daic7xxx.seq1620 * critical section here to guard against a timeout triggering
2388 * Modifying the disconnected list is a critical(pause dissabled) section.
Daic79xx.seq699 * Once we are out of the select_out critical section,
1183 * critical section here to guard against a timeout triggering
/linux-4.1.27/Documentation/gpio/
Dgpio-legacy.txt64 and that can be critical for glue logic.
/linux-4.1.27/lib/
DKconfig.debug1055 held, inside an rcu read side critical section, inside preempt disabled
/linux-4.1.27/init/
DKconfig508 permits arbitrary sleeping or blocking within RCU read-side critical
/linux-4.1.27/Documentation/devicetree/
Dbooting-without-of.txt417 way to avoid overriding critical things like, on Open Firmware