| /kernel/linux/linux-5.10/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
175 # Online all hot-pluggable memory
178 echo -e "\t online all hot-pluggable memory in offline state:"
187 echo -e "\t\t SKIPPED - no hot-pluggable memory in offline state"
191 # Offline $ratio percent of hot-pluggable memory
195 echo -e "\t offline $ratio% hot-pluggable memory in online state"
211 # Online all hot-pluggable memory again
214 echo -e "\t online all hot-pluggable memory in offline state:"
223 echo -e "\t\t SKIPPED - no hot-pluggable memory in offline state"
[all …]
|
| /kernel/linux/linux-4.19/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
175 # Online all hot-pluggable memory
178 echo -e "\t online all hot-pluggable memory in offline state:"
187 echo -e "\t\t SKIPPED - no hot-pluggable memory in offline state"
191 # Offline $ratio percent of hot-pluggable memory
195 echo -e "\t offline $ratio% hot-pluggable memory in online state"
211 # Online all hot-pluggable memory again
214 echo -e "\t online all hot-pluggable memory in offline state:"
223 echo -e "\t\t SKIPPED - no hot-pluggable memory in offline state"
[all …]
|
| /kernel/linux/linux-4.19/drivers/hv/ |
| D | hv_balloon.c | 128 * limitations on hot-add, the guest can specify
350 * Hot add request message. Message sent from the host to the guest.
352 * mem_range: Memory range to hot add.
354 * On Linux we currently don't support this since we cannot hot add
364 * Hot add response message.
365 * This message is sent by the guest to report the status of a hot add request.
367 * assume all further hot add requests will fail, since this indicates that
370 * Hot adds may also fail due to low resources; in this case, the guest must
371 * not complete this message until the hot add can succeed, and the host must
372 * not send a new hot add request until the response is sent.
[all …]
|
| /kernel/linux/linux-5.10/drivers/hv/ |
| D | hv_balloon.c | 121 * limitations on hot-add, the guest can specify
343 * Hot add request message. Message sent from the host to the guest.
345 * mem_range: Memory range to hot add.
355 * Hot add response message.
356 * This message is sent by the guest to report the status of a hot add request.
358 * assume all further hot add requests will fail, since this indicates that
361 * Hot adds may also fail due to low resources; in this case, the guest must
362 * not complete this message until the hot add can succeed, and the host must
363 * not send a new hot add request until the response is sent.
364 * If VSC fails to hot add memory DYNMEM_NUMBER_OF_UNSUCCESSFUL_HOTADD_ATTEMPTS
[all …]
|
| /kernel/linux/linux-4.19/tools/testing/selftests/cpu-hotplug/ |
| D | cpu-on-off-test.sh | 56 # list all hot-pluggable CPUs
213 # Online all hot-pluggable CPUs
220 # Offline all hot-pluggable CPUs
227 # Online all hot-pluggable CPUs again
261 # Offline all hot-pluggable CPUs
269 # Test CPU hot-add error handling (offline => online)
277 # Online all hot-pluggable CPUs
285 # Test CPU hot-remove error handling (online => offline)
|
| /kernel/linux/linux-5.10/tools/testing/selftests/cpu-hotplug/ |
| D | cpu-on-off-test.sh | 56 # list all hot-pluggable CPUs
213 # Online all hot-pluggable CPUs
220 # Offline all hot-pluggable CPUs
227 # Online all hot-pluggable CPUs again
261 # Offline all hot-pluggable CPUs
269 # Test CPU hot-add error handling (offline => online)
277 # Online all hot-pluggable CPUs
285 # Test CPU hot-remove error handling (online => offline)
|
| /kernel/linux/linux-4.19/Documentation/laptops/ |
| D | thinkpad-acpi.txt | 169 Hot keys
176 some important events and also keyboard hot key presses to the operating
181 The driver enables the HKEY ("hot key") event reporting automatically
188 Some of these events refer to hot key presses, but not all of them.
190 The driver will generate events over the input layer for hot keys and
193 assigned to each hot key.
195 The hot key bit mask allows some control over which hot keys generate
202 modified do anything. Not all hot keys can be individually controlled
224 echo 0xffffffff > /proc/acpi/ibm/hotkey -- enable all hot keys
225 echo 0 > /proc/acpi/ibm/hotkey -- disable all possible hot keys
[all …]
|
| /kernel/linux/linux-5.10/arch/powerpc/platforms/pseries/ |
| D | hotplug-memory.c | 356 * Don't hot-remove memory that falls in fadump boot memory area in lmb_is_removable()
408 pr_info("Attempting to hot-remove %d LMB(s)\n", lmbs_to_remove); in dlpar_memory_remove_by_count()
444 pr_err("Memory hot-remove failed, adding LMB's back\n"); in dlpar_memory_remove_by_count()
465 pr_info("Memory at %llx was hot-removed\n", in dlpar_memory_remove_by_count()
482 pr_info("Attempting to hot-remove LMB, drc index %x\n", drc_index); in dlpar_memory_remove_by_index()
500 pr_info("Failed to hot-remove memory at %llx\n", in dlpar_memory_remove_by_index()
503 pr_info("Memory at %llx was hot-removed\n", lmb->base_addr); in dlpar_memory_remove_by_index()
514 pr_info("Attempting to hot-remove %u LMB(s) at %x\n", in dlpar_memory_remove_by_ic()
568 pr_info("Memory at %llx (drc index %x) was hot-removed\n", in dlpar_memory_remove_by_ic()
657 pr_info("Attempting to hot-add %d LMB(s)\n", lmbs_to_add); in dlpar_memory_add_by_count()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/laptops/ |
| D | thinkpad-acpi.rst | 180 Hot keys
188 some important events and also keyboard hot key presses to the operating
193 The driver enables the HKEY ("hot key") event reporting automatically
200 Some of these events refer to hot key presses, but not all of them.
202 The driver will generate events over the input layer for hot keys and
205 assigned to each hot key.
207 The hot key bit mask allows some control over which hot keys generate
214 modified do anything. Not all hot keys can be individually controlled
237 echo 0xffffffff > /proc/acpi/ibm/hotkey -- enable all hot keys
238 echo 0 > /proc/acpi/ibm/hotkey -- disable all possible hot keys
[all …]
|
| /kernel/linux/linux-4.19/arch/powerpc/platforms/pseries/ |
| D | hotplug-memory.c | 360 * Don't hot-remove memory that falls in fadump boot memory area in lmb_is_removable()
416 pr_info("Attempting to hot-remove %d LMB(s)\n", lmbs_to_remove); in dlpar_memory_remove_by_count()
452 pr_err("Memory hot-remove failed, adding LMB's back\n"); in dlpar_memory_remove_by_count()
473 pr_info("Memory at %llx was hot-removed\n", in dlpar_memory_remove_by_count()
490 pr_info("Attempting to hot-remove LMB, drc index %x\n", drc_index); in dlpar_memory_remove_by_index()
508 pr_info("Failed to hot-remove memory at %llx\n", in dlpar_memory_remove_by_index()
511 pr_info("Memory at %llx was hot-removed\n", lmb->base_addr); in dlpar_memory_remove_by_index()
556 pr_info("Attempting to hot-remove %u LMB(s) at %x\n", in dlpar_memory_remove_by_ic()
610 pr_info("Memory at %llx (drc index %x) was hot-removed\n", in dlpar_memory_remove_by_ic()
701 pr_info("Attempting to hot-add %d LMB(s)\n", lmbs_to_add); in dlpar_memory_add_by_count()
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | memory-hotplug.txt | 20 4. Physical memory hot-add phase
22 4.2 Notify memory hot-add event by hand
23 5. Logical Memory hot-add phase
90 administrator. For the hot-add case, it must be executed after Physical Hotplug
123 - Allow for memory hot-add (CONFIG_MEMORY_HOTPLUG)
126 - Allow for memory hot remove (CONFIG_MEMORY_HOTREMOVE)
220 Physical memory hot-add phase
230 Linux's ACPI handler does hot-add memory to the system and calls a hotplug udev
244 Notify memory hot-add event by hand
262 memory_block_size] memory range is hot-added. In this case, hotplug script is
[all …]
|
| /kernel/linux/linux-5.10/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) */
|
| /kernel/linux/linux-4.19/drivers/staging/sm750fb/ |
| D | ddk750_sii164.h | 7 /* Hot Plug detection mode structure */
9 SII164_HOTPLUG_DISABLE = 0, /* Disable Hot Plug output bit (always high). */
12 SII164_HOTPLUG_USE_HTPLG /* Use Hot Plug detect bit. */
107 /* Hot Plug detect Input (HTPLG) */
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/mm/ |
| D | memory-hotplug.rst | 71 administrator. For the hot-add case, it must be executed after Physical Hotplug
102 - Allow for memory hot-add (``CONFIG_MEMORY_HOTPLUG``)
105 - Allow for memory hot remove (``CONFIG_MEMORY_HOTREMOVE``)
202 Physical memory hot-add phase
212 Linux's ACPI handler does hot-add memory to the system and calls a hotplug udev
225 Notify memory hot-add event by hand
244 memory_block_size] memory range is hot-added. In this case, hotplug script is
248 Logical Memory hot-add phase
268 When the memory is hot-added, the kernel decides whether or not to "online"
438 - allowing memory hot-add to ZONE_MOVABLE. maybe we need some switch like
|
| /kernel/linux/linux-4.19/drivers/infiniband/ulp/srp/ |
| D | ib_srp.h | 135 /* These are RW in the hot path, and commonly used together */
140 /* These are read-only in the hot path */
150 /* Everything above this point is used in the hot path of
187 /* read and written in the hot path */
190 /* read only in the hot path */
|
| /kernel/linux/linux-5.10/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()
370 cursor.hot.x = ops->cursor_state.hot.x; in ccw_cursor()
371 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()
353 cursor.hot.x = ops->cursor_state.hot.x; in cw_cursor()
354 cursor.hot.y = ops->cursor_state.hot.y; in cw_cursor()
|
| D | bitblit.c | 296 if (ops->cursor_state.hot.x || ops->cursor_state.hot.y || in bit_cursor()
298 ops->cursor_state.hot.x = cursor.hot.y = 0; in bit_cursor()
366 cursor.hot.x = ops->cursor_state.hot.x; in bit_cursor()
367 cursor.hot.y = ops->cursor_state.hot.y; in bit_cursor()
|
| /kernel/linux/linux-4.19/drivers/video/fbdev/core/ |
| D | bitblit.c | 296 if (ops->cursor_state.hot.x || ops->cursor_state.hot.y || in bit_cursor()
298 ops->cursor_state.hot.x = cursor.hot.y = 0; in bit_cursor()
366 cursor.hot.x = ops->cursor_state.hot.x; in bit_cursor()
367 cursor.hot.y = ops->cursor_state.hot.y; in bit_cursor()
|
| 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()
370 cursor.hot.x = ops->cursor_state.hot.x; in ccw_cursor()
371 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()
353 cursor.hot.x = ops->cursor_state.hot.x; in cw_cursor()
354 cursor.hot.y = ops->cursor_state.hot.y; in cw_cursor()
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| 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 */
|
| /kernel/linux/linux-5.10/drivers/infiniband/ulp/srp/ |
| D | ib_srp.h | 140 /* These are RW in the hot path, and commonly used together */
145 /* These are read-only in the hot path */
156 /* Everything above this point is used in the hot path of
192 /* read and written in the hot path */
195 /* read only in the hot path */
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/power/supply/ |
| D | charger-manager.txt | 28 -hot : critical hot temperature of battery for charging
57 cm-battery-hot = <800>;
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/marvell/ |
| D | armada-ap80x.dtsi | 336 cpu0_hot: cpu0-hot {
349 map0_hot: map0-hot {
369 cpu1_hot: cpu1-hot {
382 map1_hot: map1-hot {
402 cpu2_hot: cpu2-hot {
415 map2_hot: map2-hot {
435 cpu3_hot: cpu3-hot {
|