| /Linux-v5.15/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 …]
|
| /Linux-v5.15/drivers/hv/ |
| D | hv_balloon.c | 122 * limitations on hot-add, the guest can specify
344 * Hot add request message. Message sent from the host to the guest.
346 * mem_range: Memory range to hot add.
356 * Hot add response message.
357 * This message is sent by the guest to report the status of a hot add request.
359 * assume all further hot add requests will fail, since this indicates that
362 * Hot adds may also fail due to low resources; in this case, the guest must
363 * not complete this message until the hot add can succeed, and the host must
364 * not send a new hot add request until the response is sent.
365 * If VSC fails to hot add memory DYNMEM_NUMBER_OF_UNSUCCESSFUL_HOTADD_ATTEMPTS
[all …]
|
| /Linux-v5.15/arch/arm64/include/asm/ |
| D | module.lds.h | 10 * Outlined checks go into comdat-deduplicated sections named .text.hot.
12 * we otherwise end up with multiple sections with the same .text.hot
18 .text.hot : { *(.text.hot) }
|
| /Linux-v5.15/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)
|
| /Linux-v5.15/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()
469 pr_info("Memory at %llx was hot-removed\n", in dlpar_memory_remove_by_count()
490 pr_debug("Attempting to hot-remove LMB, drc index %x\n", drc_index); in dlpar_memory_remove_by_index()
508 pr_debug("Failed to hot-remove memory at %llx\n", in dlpar_memory_remove_by_index()
511 pr_debug("Memory at %llx was hot-removed\n", lmb->base_addr); in dlpar_memory_remove_by_index()
521 pr_info("Attempting to hot-remove %u LMB(s) at %x\n", in dlpar_memory_remove_by_ic()
593 pr_info("Memory at %llx (drc index %x) was hot-removed\n", in dlpar_memory_remove_by_ic()
678 pr_info("Attempting to hot-add %d LMB(s)\n", lmbs_to_add); in dlpar_memory_add_by_count()
[all …]
|
| /Linux-v5.15/drivers/platform/surface/ |
| D | Kconfig | 137 tristate "Surface Hot-Plug Driver"
140 Driver for out-of-band hot-plug event signaling on Microsoft Surface
141 devices with hot-pluggable PCIe cards.
144 hot-pluggable discrete GPU (dGPU). When not in use, the dGPU on those
146 hot-plug signaling. Thus, without this driver, detaching the base
149 for out-of-band hot-plug notifications, ensuring that the device state
152 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.
216 * however that doesn't have a hot-pluggable PCIe device. It also in surface_hotplug_probe()
281 MODULE_DESCRIPTION("Surface Hot-Plug Signaling Driver for Surface Book Devices");
|
| /Linux-v5.15/Documentation/admin-guide/laptops/ |
| D | thinkpad-acpi.rst | 182 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 …]
|
| /Linux-v5.15/arch/arm/boot/dts/ |
| D | qcom-ipq8064.dtsi | 64 cpu-hot {
67 type = "hot";
84 cpu-hot {
87 type = "hot";
104 cpu-hot {
107 type = "hot";
124 cpu-hot {
127 type = "hot";
144 cpu-hot {
147 type = "hot";
[all …]
|
| 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-v5.15/Documentation/admin-guide/mm/ |
| D | memory-hotplug.rst | 4 Memory Hot(Un)Plug
7 This document describes generic Linux support for memory hot(un)plug with
15 Memory hot(un)plug allows for increasing and decreasing the size of physical
20 Memory hot(un)plug is used for various purposes:
33 Further, the basic memory hot(un)plug infrastructure in Linux is nowadays also
37 Linux only supports memory hot(un)plug on selected 64 bit architectures, such as
40 Memory Hot(Un)Plug Granularity
43 Memory hot(un)plug in Linux uses the SPARSEMEM memory model, which divides the
50 granularity that can be hot(un)plugged. The default size of a memory block is
263 Configuring Memory Hot(Un)Plug
[all …]
|
| /Linux-v5.15/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-v5.15/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()
|
| 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()
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-v5.15/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
191 /* read and written in the hot path */
194 /* read only in the hot path */
|
| /Linux-v5.15/arch/arm64/boot/dts/marvell/ |
| D | armada-ap80x.dtsi | 339 cpu0_hot: cpu0-hot {
352 map0_hot: map0-hot {
372 cpu1_hot: cpu1-hot {
385 map1_hot: map1-hot {
405 cpu2_hot: cpu2-hot {
418 map2_hot: map2-hot {
438 cpu3_hot: cpu3-hot {
|
| /Linux-v5.15/Documentation/driver-api/dmaengine/ |
| D | pxa_dma.rst | 8 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.15/drivers/gpu/drm/ |
| D | drm_bridge_connector.c | 70 * 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.
|
| D | drm_bridge.c | 1120 * drm_bridge_hpd_enable - enable hot plug detection for the bridge
1122 * @cb: hot-plug detection callback
1123 * @data: data to be passed to the hot-plug detection callback
1126 * and @data as hot plug notification callback. From now on the @cb will be
1128 * until hot plug notification gets disabled with drm_bridge_hpd_disable().
1130 * Hot plug detection is supported only if the DRM_BRIDGE_OP_HPD flag is set in
1133 * Only one hot plug detection callback can be registered at a time, it is an
1134 * error to call this function when hot plug detection is already enabled for
1147 if (WARN(bridge->hpd_cb, "Hot plug detection already enabled\n")) in drm_bridge_hpd_enable()
1162 * drm_bridge_hpd_disable - disable hot plug detection for the bridge
[all …]
|
| /Linux-v5.15/drivers/acpi/ |
| D | thermal.c | 109 u8 hot:1; member
149 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()
486 tz->trips.hot.flags.valid | in acpi_thermal_get_trip_points()
535 if (tz->trips.hot.flags.valid) { in thermal_get_trip_type()
[all …]
|
| /Linux-v5.15/tools/perf/util/ |
| D | stream.c | 68 * 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-v5.15/Documentation/devicetree/bindings/thermal/ |
| D | thermal-zones.yaml | 142 - 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";
|
