Home
last modified time | relevance | path

Searched full:hot (Results 1 – 25 of 673) sorted by relevance

12345678910>>...27

/linux/tools/testing/selftests/memory-hotplug/
H A Dmem-on-off-test.sh31 echo $msg no hot-pluggable memory >&2
37 # list all hot-pluggable memory
184 # Online all hot-pluggable memory
187 echo -e "\t online all hot-pluggable memory in offline state:"
196 echo -e "\t\t SKIPPED - no hot-pluggable memory in offline state"
200 # Offline $ratio percent of hot-pluggable memory
204 echo -e "\t offline $ratio% hot-pluggable memory in online state"
223 # Online all hot-pluggable memory again
226 echo -e "\t online all hot-pluggable memory in offline state:"
235 echo -e "\t\t SKIPPED - no hot-pluggable memory in offline state"
[all …]
/linux/Documentation/hwmon/
H A Dsmpro-hwmon.rst56 temp2_crit millicelsius RO SoC VRD HOT Threshold temperature
60 temp5_crit millicelsius RO MEM HOT Threshold for all DIMMs
62 temp6_crit millicelsius RO MEM HOT Threshold for all DIMMs
64 temp7_crit millicelsius RO MEM HOT Threshold for all DIMMs
66 temp8_crit millicelsius RO MEM HOT Threshold for all DIMMs
68 temp9_crit millicelsius RO MEM HOT Threshold for all DIMMs
70 temp10_crit millicelsius RO MEM HOT Threshold for all DIMMs
72 temp11_crit millicelsius RO MEM HOT Threshold for all DIMMs
74 temp12_crit millicelsius RO MEM HOT Threshold for all DIMMs
/linux/arch/powerpc/platforms/pseries/
H A Dhotplug-memory.c296 * Don't hot-remove memory that falls in fadump boot memory area in lmb_is_removable()
345 pr_info("Attempting to hot-remove %d LMB(s)\n", lmbs_to_remove); in dlpar_memory_remove_by_count()
381 pr_err("Memory hot-remove failed, adding LMB's back\n"); in dlpar_memory_remove_by_count()
406 pr_info("Memory at %llx was hot-removed\n", in dlpar_memory_remove_by_count()
427 pr_debug("Attempting to hot-remove LMB, drc index %x\n", drc_index); in dlpar_memory_remove_by_index()
445 pr_debug("Failed to hot-remove memory at %llx\n", in dlpar_memory_remove_by_index()
448 pr_debug("Memory at %llx was hot-removed\n", lmb->base_addr); in dlpar_memory_remove_by_index()
459 pr_info("Attempting to hot-remove %u LMB(s) at %x\n", in dlpar_memory_remove_by_ic()
531 pr_info("Memory at %llx (drc index %x) was hot-removed\n", in dlpar_memory_remove_by_ic()
619 pr_info("Attempting to hot-add %d LMB(s)\n", lmbs_to_add); in dlpar_memory_add_by_count()
[all …]
/linux/Documentation/admin-guide/mm/damon/
H A Dlru_sort.rst31 DAMON_LRU_SORT finds hot pages (pages of memory regions that showing access
34 user-specified threshold) using DAMON, and prioritizes hot pages while
37 the limit, it prioritizes and deprioritizes more hot and cold pages first,
45 benefits for systems having clear hot/cold access patterns under memory
85 Access frequency threshold for hot memory regions identification in permil.
88 identifies the region as hot, and mark it as accessed on the LRU list, so that
225 Number of hot memory regions that tried to be LRU-sorted.
230 Total bytes of hot memory regions that tried to be LRU-sorted.
235 Number of hot memory regions that successfully be LRU-sorted.
240 Total bytes of hot memory regions that successfully be LRU-sorted.
[all …]
/linux/arch/arm64/include/asm/
H A Dmodule.lds.h9 * Outlined checks go into comdat-deduplicated sections named .text.hot.
11 * we otherwise end up with multiple sections with the same .text.hot
17 .text.hot : { *(.text.hot) }
/linux/Documentation/admin-guide/laptops/
H A Dthinkpad-acpi.rst183 Hot keys
191 some important events and also keyboard hot key presses to the operating
196 The driver enables the HKEY ("hot key") event reporting automatically
203 Some of these events refer to hot key presses, but not all of them.
205 The driver will generate events over the input layer for hot keys and
208 assigned to each hot key.
210 The hot key bit mask allows some control over which hot keys generate
217 modified do anything. Not all hot keys can be individually controlled
240 echo 0xffffffff > /proc/acpi/ibm/hotkey -- enable all hot keys
241 echo 0 > /proc/acpi/ibm/hotkey -- disable all possible hot keys
[all …]
/linux/drivers/platform/surface/
H A DKconfig87 devices can be (hot-)removed. Hub devices and drivers are required to
183 tristate "Surface Hot-Plug Driver"
187 Driver for out-of-band hot-plug event signaling on Microsoft Surface
188 devices with hot-pluggable PCIe cards.
191 hot-pluggable discrete GPU (dGPU). When not in use, the dGPU on those
193 hot-plug signaling. Thus, without this driver, detaching the base
196 for out-of-band hot-plug notifications, ensuring that the device state
199 Select M or Y here, if you want to (fully) support hot-plugging of
H A Dsurface_hotplug.c3 * Surface Book (2 and later) hot-plug driver.
5 * Surface Book devices (can) have a hot-pluggable discrete GPU (dGPU). This
6 * driver is responsible for out-of-band hot-plug event signaling on these
7 * devices. It is specifically required when the hot-plug device is in D3cold
8 * and can thus not generate PCIe hot-plug events itself.
11 * device-check notifications to be picked up by the PCIe hot-plug driver.
207 * however that doesn't have a hot-pluggable PCIe device. It also in surface_hotplug_probe()
272 MODULE_DESCRIPTION("Surface Hot-Plug Signaling Driver for Surface Book Devices");
H A Dsurface_aggregator_hub.c7 * (hot-)removal.
78 * There is a small possibility that hub devices were hot-removed and in ssam_hub_update_workfn()
83 * hot-remove flag set. in ssam_hub_update_workfn()
85 * Therefore, we check whether devices have been hot-removed via an in ssam_hub_update_workfn()
131 /* Mark devices as hot-removed before we remove any. */ in ssam_hub_update()
/linux/Documentation/driver-api/cxl/platform/example-configurations/
H A Dflexible.rst151 Hot Pluggable : 1
163 Hot Pluggable : 1
175 Hot Pluggable : 1
187 Hot Pluggable : 1
199 Hot Pluggable : 1
211 Hot Pluggable : 1
223 Hot Pluggable : 1
/linux/include/linux/surface_aggregator/
H A Ddevice.h155 * The device has been hot-removed. Further communication with it may time
261 * ssam_device_mark_hot_removed() - Mark the given device as hot-removed.
262 * @sdev: The device to mark as hot-removed.
264 * Mark the device as having been hot-removed. This signals drivers using the
270 dev_dbg(&sdev->dev, "marking device as hot-removed\n"); in ssam_device_mark_hot_removed()
276 * hot-removed.
279 * Checks if the given device has been marked as hot-removed. See
282 * Return: Returns ``true`` if the device has been marked as hot-removed.
588 * allocated, %-ENODEV if the device is marked as hot-removed. If this is the
597 * hot-removal could happen at any point and we can't protect against in ssam_device_notifier_register()
[all …]
/linux/drivers/video/fbdev/core/
H A Dbitblit.c315 if (ops->cursor_state.hot.x || ops->cursor_state.hot.y || in bit_cursor()
317 ops->cursor_state.hot.x = cursor.hot.y = 0; in bit_cursor()
376 cursor.hot.x = ops->cursor_state.hot.x; in bit_cursor()
377 cursor.hot.y = ops->cursor_state.hot.y; in bit_cursor()
/linux/arch/arm64/boot/dts/qcom/
H A Dpm8550vs.dtsi26 type = "hot";
46 type = "hot";
66 type = "hot";
86 type = "hot";
/linux/arch/arm64/boot/dts/marvell/
H A Darmada-ap80x.dtsi344 cpu0_hot: cpu0-hot {
357 map0_hot: map0-hot {
377 cpu1_hot: cpu1-hot {
390 map1_hot: map1-hot {
410 cpu2_hot: cpu2-hot {
423 map2_hot: map2-hot {
443 cpu3_hot: cpu3-hot {
/linux/drivers/infiniband/ulp/srp/
H A Dib_srp.h150 /* These are RW in the hot path, and commonly used together */
155 /* These are read-only in the hot path */
166 /* Everything above this point is used in the hot path of
201 /* read and written in the hot path */
204 /* read only in the hot path */
/linux/Documentation/driver-api/dmaengine/
H A Dpxa_dma.rst8 a) Transfers hot queuing
70 c) Transfers hot-chaining
95 restarted. Hot-chaining doesn't break the assumption that
104 - then hot-chaining cannot happen, as the channel must be stopped, the
152 - a driver submitted an aligned tx3 => tx3 is hot-chained
/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/
H A Duncore-power.json211 … a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle t…
221 …This mode is triggered when a sensor on the die determines that we are too hot and must throttle t…
235 "BriefDescription": "VR Hot",
241 …"PublicDescription": "VR Hot : Number of cycles that a CPU SVID VR is hot. Does not cover DRAM VR…
/linux/tools/perf/pmu-events/arch/x86/emeraldrapids/
H A Duncore-power.json211 … a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle t…
221 …This mode is triggered when a sensor on the die determines that we are too hot and must throttle t…
235 "BriefDescription": "VR Hot",
241 …"PublicDescription": "VR Hot : Number of cycles that a CPU SVID VR is hot. Does not cover DRAM VR…
/linux/Documentation/mm/
H A Dmultigen_lru.rst52 The protection of hot pages and the selection of cold pages are based
116 ``MIN_NR_GENS``. The aging promotes hot pages to the youngest
191 promotes hot pages. If the scan was done cacheline efficiently, it
202 PMD has a sufficient number of hot pages, its address is placed in the
208 which may yield hot pages anyway. Parameters of the filter itself can
267 inserting hot densely populated page tables to the Bloom filters.
/linux/include/net/libeth/
H A Dtypes.h12 * struct libeth_rq_napi_stats - "hot" counters to update in Rx polling loop
32 * struct libeth_sq_napi_stats - "hot" counters to update in Tx completion loop
48 * struct libeth_xdpsq_napi_stats - "hot" counters to update in XDP Tx
/linux/tools/perf/pmu-events/arch/x86/snowridgex/
H A Duncore-power.json224 … a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle t…
234 …This mode is triggered when a sensor on the die determines that we are too hot and must throttle t…
248 "BriefDescription": "VR Hot",
254 …"PublicDescription": "VR Hot : Number of cycles that a CPU SVID VR is hot. Does not cover DRAM VR…
/linux/tools/perf/pmu-events/arch/x86/icelakex/
H A Duncore-power.json225 … a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle t…
235 …This mode is triggered when a sensor on the die determines that we are too hot and must throttle t…
249 "BriefDescription": "VR Hot",
255 …"PublicDescription": "VR Hot : Number of cycles that a CPU SVID VR is hot. Does not cover DRAM VR…
/linux/Documentation/arch/s390/
H A Dvfio-ap.rst970 Hot plug/unplug support:
972 An adapter, domain or control domain may be hot plugged into a running KVM
983 * To hot plug a domain, each APQN derived from the Cartesian product
988 An adapter, domain or control domain may be hot unplugged from a running KVM
997 available, it will be automatically hot-plugged into the KVM guest using
1026 | dyn | Indicates hot plug/unplug of AP adapters, domains and control |
1039 its mdev can be hot unplugged from the guest in one of two ways:
1041 1. If the KVM guest was started with libvirt, you can hot unplug the mdev via
1046 For example, to hot unplug mdev 62177883-f1bb-47f0-914d-32a22e3a8804 from
1064 For example, to hot unplug the vfio_ap mediated device identified on the
[all …]
/linux/Documentation/driver-api/
H A Dvfio-mediated-device.rst144 * Mediated device hot plug
237 doesn't support hot unplug.
243 Mediated device Hot plug
246 Mediated devices can be created and assigned at runtime. The procedure to hot
247 plug a mediated device is the same as the procedure to hot plug a PCI device.
/linux/include/linux/
H A Dlru_cache.h43 (in use, or "hot", regions), as we don't know whether or not those WRITEs
57 If we set a hard limit on the area that may be "hot" at any given time, we
80 possible, flushing it to disk again when a previously "hot" (and on-disk
89 Yet an other implementation may keep track of the hot regions, by starting
91 become "hot", or have "cooled down" again.

12345678910>>...27