Home
last modified time | relevance | path

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

12345678910>>...28

/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 …]
/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 …]
/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)
/linux-5.10/arch/powerpc/platforms/pseries/
Dhotplug-memory.c356 * 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 …]
/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 …]
/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) */
Dddk750_sii164.c302 * 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-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
/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()
Dbitblit.c296 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()
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()
Dfbcon_ud.c319 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()
393 cursor.hot.x = ops->cursor_state.hot.x; in ud_cursor()
394 cursor.hot.y = ops->cursor_state.hot.y; in ud_cursor()
/linux-5.10/arch/arm/boot/dts/
Drk3288-veyron-mickey.dts105 * - 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-5.10/drivers/infiniband/ulp/srp/
Dib_srp.h140 /* 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 */
/linux-5.10/arch/arm64/boot/dts/marvell/
Darmada-ap80x.dtsi336 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 {
/linux-5.10/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-5.10/drivers/gpu/drm/
Ddrm_bridge_connector.c70 * hot-plug detection notification, if any (see &DRM_BRIDGE_OP_HPD).
93 * Bridge Connector Hot-Plug Handling
132 * drm_bridge_connector_enable_hpd - Enable hot-plug detection for the connector
135 * This function enables hot-plug detection for the given bridge connector.
151 * drm_bridge_connector_disable_hpd - Disable hot-plug detection for the
155 * This function disables hot-plug detection for the given bridge connector.
Ddrm_bridge.c1107 * drm_bridge_hpd_enable - enable hot plug detection for the bridge
1109 * @cb: hot-plug detection callback
1110 * @data: data to be passed to the hot-plug detection callback
1113 * and @data as hot plug notification callback. From now on the @cb will be
1115 * until hot plug notification gets disabled with drm_bridge_hpd_disable().
1117 * Hot plug detection is supported only if the DRM_BRIDGE_OP_HPD flag is set in
1120 * Only one hot plug detection callback can be registered at a time, it is an
1121 * error to call this function when hot plug detection is already enabled for
1134 if (WARN(bridge->hpd_cb, "Hot plug detection already enabled\n")) in drm_bridge_hpd_enable()
1149 * drm_bridge_hpd_disable - disable hot plug detection for the bridge
[all …]
/linux-5.10/Documentation/devicetree/bindings/power/supply/
Dcharger-manager.txt36 -hot : critical hot temperature of battery for charging
67 cm-battery-hot = <800>;
/linux-5.10/drivers/acpi/
Dthermal.c112 u8 hot:1; member
152 struct acpi_thermal_hot hot; member
318 tz->trips.hot.flags.valid = 0; in acpi_thermal_trips_update()
320 "No hot threshold\n")); in acpi_thermal_trips_update()
322 tz->trips.hot.temperature = tmp; in acpi_thermal_trips_update()
323 tz->trips.hot.flags.valid = 1; in acpi_thermal_trips_update()
325 "Found hot threshold [%lu]\n", in acpi_thermal_trips_update()
326 tz->trips.hot.temperature)); in acpi_thermal_trips_update()
485 tz->trips.hot.flags.valid | in acpi_thermal_get_trip_points()
542 if (tz->trips.hot.flags.valid) { in thermal_get_trip_type()
[all …]
/linux-5.10/Documentation/devicetree/bindings/thermal/
Dthermal-zones.yaml142 - hot # send notification to driver
145 There are four valid trip types: active, passive, hot,
154 The hot trip type can be used to send a notification to
316 type = "hot";
338 type = "hot";
Dmax77620_thermal.txt48 pmic_die_warn_temp_thresh: hot-die {
50 type = "hot";
/linux-5.10/tools/perf/util/
Dstream.c68 * The cnodes with high hit number are hot callchains.
84 * Considering a few number of hot streams, only use simple in evsel_streams__set_hot_cnode()
308 printf("[ Matched hot streams ]\n"); in callchain_streams_report()
318 printf("\n[ Hot streams in old perf data only ]\n"); in callchain_streams_report()
328 printf("\n[ Hot streams in new perf data only ]\n"); in callchain_streams_report()
/linux-5.10/mm/
DKconfig56 memory hot-plug systems. This is normal.
60 hot-plug and hot-remove.
134 # Also, memblocks are updated with memory hot(un)plug.
154 bool "Allow for memory hot-add"
175 Say Y here if you want all hot-plugged memory blocks to appear in
177 Say N here if you want the default policy to keep all hot-plugged
181 bool "Allow for memory hot remove"
/linux-5.10/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.

12345678910>>...28