| /linux-6.12.1/tools/testing/selftests/memory-hotplug/ |
| D | mem-on-off-test.sh | 31 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-6.12.1/Documentation/hwmon/ |
| D | smpro-hwmon.rst | 56 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-6.12.1/drivers/hv/ |
| D | hv_balloon.c | 120 * limitations on hot-add, the guest can specify
336 * Hot add request message. Message sent from the host to the guest.
338 * mem_range: Memory range to hot add.
348 * Hot add response message.
349 * This message is sent by the guest to report the status of a hot add request.
351 * assume all further hot add requests will fail, since this indicates that
354 * Hot adds may also fail due to low resources; in this case, the guest must
355 * not complete this message until the hot add can succeed, and the host must
356 * not send a new hot add request until the response is sent.
357 * If VSC fails to hot add memory DYNMEM_NUMBER_OF_UNSUCCESSFUL_HOTADD_ATTEMPTS
[all …]
|
| /linux-6.12.1/arch/powerpc/platforms/pseries/ |
| D | hotplug-memory.c | 296 * 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-6.12.1/arch/arm64/include/asm/ |
| D | module.lds.h | 8 * Outlined checks go into comdat-deduplicated sections named .text.hot.
10 * we otherwise end up with multiple sections with the same .text.hot
16 .text.hot : { *(.text.hot) }
|
| /linux-6.12.1/Documentation/admin-guide/mm/damon/ |
| D | lru_sort.rst | 31 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-6.12.1/Documentation/admin-guide/laptops/ |
| D | thinkpad-acpi.rst | 183 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-6.12.1/drivers/platform/surface/ |
| D | Kconfig | 87 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
|
| D | surface_hotplug.c | 3 * 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");
|
| /linux-6.12.1/arch/arm/boot/dts/qcom/ |
| D | qcom-ipq8064.dtsi | 65 cpu-hot {
68 type = "hot";
85 cpu-hot {
88 type = "hot";
105 cpu-hot {
108 type = "hot";
125 cpu-hot {
128 type = "hot";
145 cpu-hot {
148 type = "hot";
[all …]
|
| /linux-6.12.1/Documentation/admin-guide/mm/ |
| D | memory-hotplug.rst | 2 Memory Hot(Un)Plug
5 This document describes generic Linux support for memory hot(un)plug with
13 Memory hot(un)plug allows for increasing and decreasing the size of physical
18 Memory hot(un)plug is used for various purposes:
31 Further, the basic memory hot(un)plug infrastructure in Linux is nowadays also
35 Linux only supports memory hot(un)plug on selected 64 bit architectures, such as
38 Memory Hot(Un)Plug Granularity
41 Memory hot(un)plug in Linux uses the SPARSEMEM memory model, which divides the
48 granularity that can be hot(un)plugged. The default size of a memory block is
263 Configuring Memory Hot(Un)Plug
[all …]
|
| /linux-6.12.1/drivers/staging/sm750fb/ |
| D | ddk750_sii164.h | 7 /* Hot Plug detection mode structure */
9 SII164_HOTPLUG_DISABLE = 0, /* Disable Hot Plug output bit
15 SII164_HOTPLUG_USE_HTPLG /* Use Hot Plug detect bit. */
110 /* Hot Plug detect Input (HTPLG) */
|
| D | ddk750_sii164.c | 302 * This function selects the mode of the hot plug detection.
333 * This function enables the Hot Plug detection.
335 * enableHotPlug - Enable (=1) / disable (=0) Hot Plug detection
343 /* Depending on each DVI controller, need to enable the hot plug based in sii164EnableHotPlugDetection()
394 * Clear the hot plug interrupt.
|
| /linux-6.12.1/arch/arm64/boot/dts/qcom/ |
| D | x1e80100-pmics.dtsi | 28 type = "hot";
48 type = "hot";
68 type = "hot";
88 type = "hot";
108 type = "hot";
128 type = "hot";
148 type = "hot";
168 type = "hot";
188 type = "hot";
|
| D | pm8550vs.dtsi | 26 type = "hot";
46 type = "hot";
66 type = "hot";
86 type = "hot";
|
| /linux-6.12.1/include/linux/surface_aggregator/ |
| D | device.h | 155 * 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-6.12.1/drivers/video/fbdev/core/ |
| D | fbcon_ccw.c | 288 if (ops->cursor_state.hot.x || ops->cursor_state.hot.y || in ccw_cursor()
290 ops->cursor_state.hot.x = cursor.hot.y = 0; in ccw_cursor()
361 cursor.hot.x = ops->cursor_state.hot.x; in ccw_cursor()
362 cursor.hot.y = ops->cursor_state.hot.y; in ccw_cursor()
|
| D | fbcon_cw.c | 271 if (ops->cursor_state.hot.x || ops->cursor_state.hot.y || in cw_cursor()
273 ops->cursor_state.hot.x = cursor.hot.y = 0; in cw_cursor()
344 cursor.hot.x = ops->cursor_state.hot.x; in cw_cursor()
345 cursor.hot.y = ops->cursor_state.hot.y; in cw_cursor()
|
| D | bitblit.c | 299 if (ops->cursor_state.hot.x || ops->cursor_state.hot.y || in bit_cursor()
301 ops->cursor_state.hot.x = cursor.hot.y = 0; in bit_cursor()
360 cursor.hot.x = ops->cursor_state.hot.x; in bit_cursor()
361 cursor.hot.y = ops->cursor_state.hot.y; in bit_cursor()
|
| D | fbcon_ud.c | 319 if (ops->cursor_state.hot.x || ops->cursor_state.hot.y || in ud_cursor()
321 ops->cursor_state.hot.x = cursor.hot.y = 0; in ud_cursor()
384 cursor.hot.x = ops->cursor_state.hot.x; in ud_cursor()
385 cursor.hot.y = ops->cursor_state.hot.y; in ud_cursor()
|
| /linux-6.12.1/arch/arm/boot/dts/rockchip/ |
| D | rk3288-veyron-mickey.dts | 105 * - 1.2 GHz - 1.0 GHz (almost hot)
106 * - 800 MHz (hot)
108 * - 696 MHz - min (very hot)
139 /* At very hot, don't let GPU go over 300 MHz */
200 /* When hot, GPU goes down to 300 MHz */
206 /* When really hot, don't let GPU go _above_ 300 MHz */
|
| /linux-6.12.1/drivers/infiniband/ulp/srp/ |
| D | ib_srp.h | 150 /* 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-6.12.1/arch/arm64/boot/dts/marvell/ |
| D | armada-ap80x.dtsi | 343 cpu0_hot: cpu0-hot {
356 map0_hot: map0-hot {
376 cpu1_hot: cpu1-hot {
389 map1_hot: map1-hot {
409 cpu2_hot: cpu2-hot {
422 map2_hot: map2-hot {
442 cpu3_hot: cpu3-hot {
|
| /linux-6.12.1/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| D | uncore-power.json | 213 … a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle t…
223 …This mode is triggered when a sensor on the die determines that we are too hot and must throttle t…
237 "BriefDescription": "VR Hot",
243 …"PublicDescription": "VR Hot : Number of cycles that a CPU SVID VR is hot. Does not cover DRAM VR…
|
| /linux-6.12.1/tools/perf/pmu-events/arch/x86/emeraldrapids/ |
| D | uncore-power.json | 213 … a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle t…
223 …This mode is triggered when a sensor on the die determines that we are too hot and must throttle t…
237 "BriefDescription": "VR Hot",
243 …"PublicDescription": "VR Hot : Number of cycles that a CPU SVID VR is hot. Does not cover DRAM VR…
|