Searched refs:critical (Results 226 – 250 of 709) sorted by relevance
12345678910>>...29
/openbmc/linux/tools/memory-model/Documentation/ |
H A D | explanation.txt | 929 Rcu: This requires that RCU read-side critical sections and 1520 synchronize_rcu(). A read-side critical section (or just critical 1529 For any critical section C and any grace period G, at least 1614 critical section to the start.) 1622 the end of a critical section which starts before Z begins. 1728 critical section and witness that W propagates to the critical 1783 critical section, we have U ->rcu-rscsi L. 1871 same domain. Read-side critical sections and grace periods 1874 to pairs of critical sections and grace periods having the 1894 created two nested (fully overlapping) read-side critical [all …]
|
/openbmc/linux/Documentation/RCU/ |
H A D | rcu_dereference.rst | 133 of an RCU read-side critical section, and the pointer 140 Within an RCU read-side critical section, there is little 393 1. If the access needs to be within an RCU read-side critical 395 RCU flavors, an RCU read-side critical section is entered 400 2. If the access might be within an RCU read-side critical section 408 3. If the access might be within an RCU read-side critical section
|
/openbmc/linux/arch/arm64/boot/dts/qcom/ |
H A D | msm8953.dtsi | 481 interrupt-names = "uplow", "critical"; 1742 type = "critical"; 1765 type = "critical"; 1788 type = "critical"; 1811 type = "critical"; 1834 type = "critical"; 1857 type = "critical"; 1880 type = "critical"; 1903 type = "critical";
|
H A D | pm6150.dtsi | 29 type = "critical";
|
H A D | sc7280.dtsi | 5406 type = "critical"; 5450 type = "critical"; 5494 type = "critical"; 5538 type = "critical"; 5582 type = "critical"; 5626 type = "critical"; 5670 type = "critical"; 5714 type = "critical"; 5758 type = "critical"; 5802 type = "critical"; [all …]
|
H A D | pm6150l.dtsi | 34 type = "critical";
|
H A D | pm8150l.dtsi | 35 type = "critical";
|
H A D | pm8150b.dtsi | 35 type = "critical";
|
H A D | pmm8155au_1.dtsi | 35 type = "critical";
|
H A D | pm8953.dtsi | 33 type = "critical";
|
/openbmc/u-boot/doc/device-tree-bindings/thermal/ |
H A D | rockchip-thermal.txt | 56 type = "critical";
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/ |
H A D | Threshold.interface.yaml | 56 Indicates the critical level.
|
/openbmc/openbmc/meta-ibm/recipes-phosphor/state/ |
H A D | phosphor-state-manager_%.bbappend | 32 # Override critical services to monitor with IBM file
|
/openbmc/linux/Documentation/arch/arm64/ |
H A D | silicon-errata.rst | 15 Category A A critical error without a viable workaround. 16 Category B A significant or critical error with an acceptable
|
/openbmc/linux/kernel/ |
H A D | Kconfig.preempt | 57 all kernel code (that is not executing in a critical section) 80 low level and critical code paths (entry code, scheduler, low
|
/openbmc/linux/arch/arm64/boot/dts/nvidia/ |
H A D | tegra194-p2972-0000.dts | 2372 cpu_trip_critical: critical { 2375 type = "critical"; 2398 cpu-critical { 2426 gpu_alert0: critical { 2429 type = "critical"; 2440 aux_alert0: critical { 2443 type = "critical";
|
H A D | tegra194-p3509-0000.dtsi | 2404 cpu_trip_critical: critical { 2407 type = "critical"; 2430 cpu-critical { 2458 gpu_alert0: critical { 2461 type = "critical"; 2472 aux_alert0: critical { 2475 type = "critical";
|
/openbmc/linux/arch/arm/boot/dts/qcom/ |
H A D | qcom-apq8084.dtsi | 121 type = "critical"; 141 type = "critical"; 161 type = "critical"; 181 type = "critical";
|
/openbmc/linux/Documentation/hwmon/ |
H A D | lm95234.rst | 43 have a critical limit.
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/ptpd/ptpd/ |
H A D | Fixed-100-CPU-using-issue-by-adding-minimum-POSIX-ti.patch | 12 - critical: added minimum POSIX timer interval to prevent from
|
/openbmc/linux/Documentation/mm/ |
H A D | remap_file_pages.rst | 22 virtual address space. This use-case is not critical anymore since 64-bit
|
/openbmc/linux/Documentation/devicetree/bindings/thermal/ |
H A D | ti,j72xx-thermal.yaml | 92 type = "critical";
|
/openbmc/linux/arch/arm64/kernel/ |
H A D | stacktrace.c | 187 STACKINFO_SDEI(critical), in arch_stack_walk()
|
/openbmc/linux/Documentation/driver-api/thermal/ |
H A D | sysfs-api.rst | 399 |---temp[1-*]_critical: The critical trip point of thermal zone [1-*] 406 ACPI thermal zone may support multiple trip points like critical, hot, 407 passive, active. If an ACPI thermal zone supports critical, passive, 425 |---trip_point_0_type: critical 484 On an event of critical trip temperature crossing the thermal framework
|
/openbmc/linux/Documentation/locking/ |
H A D | locktypes.rst | 161 local_lock provides a named scope to critical sections which are protected 215 including PREEMPT_RT kernels. Use raw_spinlock_t only in real critical 219 critical section is tiny, thus avoiding RT-mutex overhead. 474 interrupts, so the critical section must avoid acquiring a regular 475 spinlock_t or rwlock_t, for example, the critical section must avoid
|
12345678910>>...29