Home
last modified time | relevance | path

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

12345678910>>...58

/kernel/linux/linux-5.10/tools/testing/selftests/memory-hotplug/
Dmem-on-off-test.sh31 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-6.6/tools/testing/selftests/memory-hotplug/
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 …]
/kernel/linux/linux-6.6/Documentation/hwmon/
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
/kernel/linux/linux-5.10/drivers/hv/
Dhv_balloon.c121 * 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-6.6/drivers/hv/
Dhv_balloon.c125 * limitations on hot-add, the guest can specify
347 * Hot add request message. Message sent from the host to the guest.
349 * mem_range: Memory range to hot add.
359 * Hot add response message.
360 * This message is sent by the guest to report the status of a hot add request.
362 * assume all further hot add requests will fail, since this indicates that
365 * Hot adds may also fail due to low resources; in this case, the guest must
366 * not complete this message until the hot add can succeed, and the host must
367 * not send a new hot add request until the response is sent.
368 * If VSC fails to hot add memory DYNMEM_NUMBER_OF_UNSUCCESSFUL_HOTADD_ATTEMPTS
[all …]
/kernel/linux/linux-6.6/arch/arm64/include/asm/
Dmodule.lds.h8 * 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) }
/kernel/linux/linux-5.10/tools/testing/selftests/cpu-hotplug/
Dcpu-on-off-test.sh56 # 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-6.6/arch/powerpc/platforms/pseries/
Dhotplug-memory.c293 * Don't hot-remove memory that falls in fadump boot memory area in lmb_is_removable()
342 pr_info("Attempting to hot-remove %d LMB(s)\n", lmbs_to_remove); in dlpar_memory_remove_by_count()
378 pr_err("Memory hot-remove failed, adding LMB's back\n"); in dlpar_memory_remove_by_count()
403 pr_info("Memory at %llx was hot-removed\n", in dlpar_memory_remove_by_count()
424 pr_debug("Attempting to hot-remove LMB, drc index %x\n", drc_index); in dlpar_memory_remove_by_index()
442 pr_debug("Failed to hot-remove memory at %llx\n", in dlpar_memory_remove_by_index()
445 pr_debug("Memory at %llx was hot-removed\n", lmb->base_addr); in dlpar_memory_remove_by_index()
456 pr_info("Attempting to hot-remove %u LMB(s) at %x\n", in dlpar_memory_remove_by_ic()
528 pr_info("Memory at %llx (drc index %x) was hot-removed\n", in dlpar_memory_remove_by_ic()
613 pr_info("Attempting to hot-add %d LMB(s)\n", lmbs_to_add); in dlpar_memory_add_by_count()
[all …]
/kernel/linux/linux-6.6/Documentation/admin-guide/mm/damon/
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 …]
/kernel/linux/linux-5.10/arch/powerpc/platforms/pseries/
Dhotplug-memory.c358 * Don't hot-remove memory that falls in fadump boot memory area in lmb_is_removable()
410 pr_info("Attempting to hot-remove %d LMB(s)\n", lmbs_to_remove); in dlpar_memory_remove_by_count()
446 pr_err("Memory hot-remove failed, adding LMB's back\n"); in dlpar_memory_remove_by_count()
467 pr_info("Memory at %llx was hot-removed\n", in dlpar_memory_remove_by_count()
484 pr_debug("Attempting to hot-remove LMB, drc index %x\n", drc_index); in dlpar_memory_remove_by_index()
502 pr_debug("Failed to hot-remove memory at %llx\n", in dlpar_memory_remove_by_index()
505 pr_debug("Memory at %llx was hot-removed\n", lmb->base_addr); in dlpar_memory_remove_by_index()
517 pr_info("Attempting to hot-remove %u LMB(s) at %x\n", in dlpar_memory_remove_by_ic()
571 pr_info("Memory at %llx (drc index %x) was hot-removed\n", in dlpar_memory_remove_by_ic()
660 pr_info("Attempting to hot-add %d LMB(s)\n", lmbs_to_add); in dlpar_memory_add_by_count()
[all …]
/kernel/linux/linux-6.6/drivers/platform/surface/
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
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.
209 * however that doesn't have a hot-pluggable PCIe device. It also in surface_hotplug_probe()
274 MODULE_DESCRIPTION("Surface Hot-Plug Signaling Driver for Surface Book Devices");
/kernel/linux/linux-5.10/Documentation/admin-guide/laptops/
Dthinkpad-acpi.rst180 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-6.6/Documentation/admin-guide/laptops/
Dthinkpad-acpi.rst182 Hot keys
190 some important events and also keyboard hot key presses to the operating
195 The driver enables the HKEY ("hot key") event reporting automatically
202 Some of these events refer to hot key presses, but not all of them.
204 The driver will generate events over the input layer for hot keys and
207 assigned to each hot key.
209 The hot key bit mask allows some control over which hot keys generate
216 modified do anything. Not all hot keys can be individually controlled
239 echo 0xffffffff > /proc/acpi/ibm/hotkey -- enable all hot keys
240 echo 0 > /proc/acpi/ibm/hotkey -- disable all possible hot keys
[all …]
/kernel/linux/linux-6.6/arch/arm/boot/dts/qcom/
Dqcom-ipq8064.dtsi65 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 …]
/kernel/linux/linux-5.10/drivers/staging/sm750fb/
Dddk750_sii164.h7 /* 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-6.6/drivers/staging/sm750fb/
Dddk750_sii164.h7 /* 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-6.6/Documentation/admin-guide/mm/
Dmemory-hotplug.rst2 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 …]
/kernel/linux/linux-5.10/Documentation/admin-guide/mm/
Dmemory-hotplug.rst71 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-6.6/include/linux/surface_aggregator/
Ddevice.h155 * The device has been hot-removed. Further communication with it may time
262 * ssam_device_mark_hot_removed() - Mark the given device as hot-removed.
263 * @sdev: The device to mark as hot-removed.
265 * Mark the device as having been hot-removed. This signals drivers using the
271 dev_dbg(&sdev->dev, "marking device as hot-removed\n"); in ssam_device_mark_hot_removed()
277 * hot-removed.
280 * Checks if the given device has been marked as hot-removed. See
283 * Return: Returns ``true`` if the device has been marked as hot-removed.
589 * allocated, %-ENODEV if the device is marked as hot-removed. If this is the
598 * hot-removal could happen at any point and we can't protect against in ssam_device_notifier_register()
[all …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/sapphirerapids/
Duncore-power.json170 … a sensor off the die determines that something off-die (like DRAM) is too hot and must throttle t…
178 …This mode is triggered when a sensor on the die determines that we are too hot and must throttle t…
190 "BriefDescription": "VR Hot",
194 …"PublicDescription": "VR Hot : Number of cycles that a CPU SVID VR is hot. Does not cover DRAM VR…
/kernel/linux/linux-5.10/drivers/video/fbdev/core/
Dfbcon_cw.c271 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()
Dfbcon_ccw.c288 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()
Dbitblit.c299 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()
369 cursor.hot.x = ops->cursor_state.hot.x; in bit_cursor()
370 cursor.hot.y = ops->cursor_state.hot.y; in bit_cursor()
/kernel/linux/linux-6.6/drivers/video/fbdev/core/
Dfbcon_cw.c270 if (ops->cursor_state.hot.x || ops->cursor_state.hot.y || in cw_cursor()
272 ops->cursor_state.hot.x = cursor.hot.y = 0; in cw_cursor()
352 cursor.hot.x = ops->cursor_state.hot.x; in cw_cursor()
353 cursor.hot.y = ops->cursor_state.hot.y; in cw_cursor()

12345678910>>...58