Home
last modified time | relevance | path

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

12345678910>>...26

/Linux-v5.4/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 …]
/Linux-v5.4/drivers/hv/
Dhv_balloon.c118 * limitations on hot-add, the guest can specify
340 * Hot add request message. Message sent from the host to the guest.
342 * mem_range: Memory range to hot add.
344 * On Linux we currently don't support this since we cannot hot add
354 * Hot add response message.
355 * This message is sent by the guest to report the status of a hot add request.
357 * assume all further hot add requests will fail, since this indicates that
360 * Hot adds may also fail due to low resources; in this case, the guest must
361 * not complete this message until the hot add can succeed, and the host must
362 * not send a new hot add request until the response is sent.
[all …]
/Linux-v5.4/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)
/Linux-v5.4/Documentation/admin-guide/laptops/
Dthinkpad-acpi.rst179 Hot keys
187 some important events and also keyboard hot key presses to the operating
192 The driver enables the HKEY ("hot key") event reporting automatically
199 Some of these events refer to hot key presses, but not all of them.
201 The driver will generate events over the input layer for hot keys and
204 assigned to each hot key.
206 The hot key bit mask allows some control over which hot keys generate
213 modified do anything. Not all hot keys can be individually controlled
236 echo 0xffffffff > /proc/acpi/ibm/hotkey -- enable all hot keys
237 echo 0 > /proc/acpi/ibm/hotkey -- disable all possible hot keys
[all …]
/Linux-v5.4/arch/powerpc/platforms/pseries/
Dhotplug-memory.c354 * 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()
548 pr_info("Attempting to hot-remove %u LMB(s) at %x\n", in dlpar_memory_remove_by_ic()
602 pr_info("Memory at %llx (drc index %x) was hot-removed\n", in dlpar_memory_remove_by_ic()
692 pr_info("Attempting to hot-add %d LMB(s)\n", lmbs_to_add); in dlpar_memory_add_by_count()
[all …]
/Linux-v5.4/drivers/staging/sm750fb/
Dddk750_sii164.h7 /* 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) */
Dddk750_sii164.c292 * This function selects the mode of the hot plug detection.
323 * This function enables the Hot Plug detection.
325 * enableHotPlug - Enable (=1) / disable (=0) Hot Plug detection
333 /* Depending on each DVI controller, need to enable the hot plug based on each in sii164EnableHotPlugDetection()
384 * Clear the hot plug interrupt.
/Linux-v5.4/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
/Linux-v5.4/drivers/video/fbdev/core/
Dbitblit.c305 if (ops->cursor_state.hot.x || ops->cursor_state.hot.y || in bit_cursor()
307 ops->cursor_state.hot.x = cursor.hot.y = 0; in bit_cursor()
375 cursor.hot.x = ops->cursor_state.hot.x; in bit_cursor()
376 cursor.hot.y = ops->cursor_state.hot.y; in bit_cursor()
Dfbcon_ccw.c297 if (ops->cursor_state.hot.x || ops->cursor_state.hot.y || in ccw_cursor()
299 ops->cursor_state.hot.x = cursor.hot.y = 0; in ccw_cursor()
379 cursor.hot.x = ops->cursor_state.hot.x; in ccw_cursor()
380 cursor.hot.y = ops->cursor_state.hot.y; in ccw_cursor()
Dfbcon_cw.c280 if (ops->cursor_state.hot.x || ops->cursor_state.hot.y || in cw_cursor()
282 ops->cursor_state.hot.x = cursor.hot.y = 0; in cw_cursor()
362 cursor.hot.x = ops->cursor_state.hot.x; in cw_cursor()
363 cursor.hot.y = ops->cursor_state.hot.y; in cw_cursor()
Dfbcon_ud.c328 if (ops->cursor_state.hot.x || ops->cursor_state.hot.y || in ud_cursor()
330 ops->cursor_state.hot.x = cursor.hot.y = 0; in ud_cursor()
402 cursor.hot.x = ops->cursor_state.hot.x; in ud_cursor()
403 cursor.hot.y = ops->cursor_state.hot.y; in ud_cursor()
/Linux-v5.4/arch/arm/boot/dts/
Drk3288-veyron-mickey.dts97 * - 1.2 GHz - 1.0 GHz (almost hot)
98 * - 800 MHz (hot)
100 * - 696 MHz - min (very hot)
131 /* At very hot, don't let GPU go over 300 MHz */
192 /* When hot, GPU goes down to 300 MHz */
198 /* When really hot, don't let GPU go _above_ 300 MHz */
/Linux-v5.4/drivers/infiniband/ulp/srp/
Dib_srp.h148 /* These are RW in the hot path, and commonly used together */
153 /* These are read-only in the hot path */
166 /* Everything above this point is used in the hot path of
202 /* read and written in the hot path */
205 /* read only in the hot path */
/Linux-v5.4/Documentation/devicetree/bindings/power/supply/
Dcharger-manager.txt28 -hot : critical hot temperature of battery for charging
57 cm-battery-hot = <800>;
/Linux-v5.4/arch/arm64/boot/dts/marvell/
Darmada-ap806.dtsi333 cpu0_hot: cpu0-hot {
346 map0_hot: map0-hot {
366 cpu1_hot: cpu1-hot {
379 map1_hot: map1-hot {
399 cpu2_hot: cpu2-hot {
412 map2_hot: map2-hot {
432 cpu3_hot: cpu3-hot {
/Linux-v5.4/Documentation/driver-api/dmaengine/
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-v5.4/include/linux/power/
Dsmb347-charger.h56 * @soft_hot_temp_limit: soft hot temperature limit [%40 - %55] (in degree C),
60 * @hard_hot_temp_limit: hard hot temperature limit [%50 - %65] (in degree C),
84 * hot limit to be %53 deg C, @hard_hot_temp_limit should be set to %50.
/Linux-v5.4/drivers/acpi/
Dthermal.c111 u8 hot:1; member
151 struct acpi_thermal_hot hot; member
317 tz->trips.hot.flags.valid = 0; in acpi_thermal_trips_update()
319 "No hot threshold\n")); in acpi_thermal_trips_update()
321 tz->trips.hot.temperature = tmp; in acpi_thermal_trips_update()
322 tz->trips.hot.flags.valid = 1; in acpi_thermal_trips_update()
324 "Found hot threshold [%lu]\n", in acpi_thermal_trips_update()
325 tz->trips.hot.temperature)); in acpi_thermal_trips_update()
484 tz->trips.hot.flags.valid | in acpi_thermal_get_trip_points()
588 if (tz->trips.hot.flags.valid) { in thermal_get_trip_type()
[all …]
/Linux-v5.4/arch/arm64/boot/dts/nvidia/
Dtegra194-p2972-0000.dts155 cpu_trip_hot: hot {
158 type = "hot";
180 cpu-hot {
/Linux-v5.4/drivers/soc/fsl/qbman/
DKconfig60 bool "QMan 'hot potato' data-stashing self-test"
64 This performs a "hot potato" style test enqueuing/dequeuing a frame
/Linux-v5.4/Documentation/hwmon/
Dadc128d818.rst25 When the HOT Temperature Limit is crossed, this will cause an alarm that will
26 be reasserted until the temperature drops below the HOT Hysteresis.
/Linux-v5.4/Documentation/devicetree/bindings/thermal/
Dmax77620_thermal.txt48 pmic_die_warn_temp_thresh: hot-die {
50 type = "hot";
/Linux-v5.4/arch/ia64/include/asm/
Dnodedata.h51 * "local_node_data" at hot-plug phase. The local_node_data
53 * just executing cpu. However, when new node is hot-added,
/Linux-v5.4/include/linux/
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>>...26