| /openbmc/qemu/docs/ |
| H A D | pcie_pci_bridge.txt | 10 But due to its strict limitations - no support of hot-plug,
16 can be hot-plugged into appropriate root port (requires additional actions,
17 see 'PCIE-PCI bridge hot-plug' section),
18 and supports devices hot-plug into the bridge itself
21 Hot-plug of legacy PCI devices into the bridge
22 is provided by bridge's built-in Standard hot-plug Controller.
25 PCIE-PCI bridge hot-plug
27 Guest OSes require extra efforts to enable PCIE-PCI bridge hot-plug.
30 to a hot-plugged devices in future.
36 that is planned to have PCIE-PCI bridge hot-plugged in.
[all …]
|
| H A D | pcie.txt | 43 Note: Integrated Endpoints are not hot-pluggable.
137 device in question will be incapable of hot-unplugging.
220 5. Hot-plug
223 do not support hot-plug, so any devices plugged into Root Complexes
224 cannot be hot-plugged/hot-unplugged:
230 Be aware that PCI Express Downstream Ports can't be hot-plugged into
233 PCI devices can be hot-plugged into PCI Express to PCI and PCI-PCI Bridges.
234 The PCI hot-plug into PCI-PCI bridge is ACPI based, whereas hot-plug into
236 the PCI Express native hot-plug.
238 PCI Express devices can be natively hot-plugged/hot-unplugged into/from
[all …]
|
| H A D | memory-hotplug.txt | 77 RAM hot-unplug
80 In order to be able to hot unplug pc-dimm device, QEMU has to be told the ids
81 of pc-dimm device and memory backend object. The ids were assigned when you hot
84 Two monitor commands are used to hot unplug memory:
|
| /openbmc/linux/tools/testing/selftests/memory-hotplug/ |
| H A D | mem-on-off-test.sh | 31 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 …]
|
| /openbmc/openbmc/meta-fii/meta-kudo/recipes-kudo/kudo-sys-utility/kudo-cmd/ |
| H A D | kudo-ras.sh | 73 REG79=$(i2cget -f -y "${I2C_S0_SMPRO[0]}" 0x"${I2C_S0_SMPRO[1]}" 0x79 w) # VRD Hot
74 REG7A=$(i2cget -f -y "${I2C_S0_SMPRO[0]}" 0x"${I2C_S0_SMPRO[1]}" 0x7A w) # DIMM Hot Error
288 echo " SoC VR HOT/Warn/Fault "
291 echo " Core VR HOT/Warn/Fault "
294 echo " DIMM HOT/Warn/Fault "
302 echo " DIMM HOT "
406 echo " VRD Hot: "
408 echo " SoC VRD is HOT "
411 echo " Core VRD1 is HOT "
414 echo " Core VRD2 is HOT "
[all …]
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | smpro-hwmon.rst | 56 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
|
| /openbmc/openbmc/meta-ampere/meta-jade/recipes-phosphor/gpio/phosphor-gpio-monitor/ |
| H A D | ampere_psu_reset_hotswap.sh | 13 # by disabling HOT SWAP and then enabling HOT SWAP through pmbus command
17 # In case hot swap occurs during BMC reset, BMC still not in operation state,
61 echo "Reset Hot swap output on PSU $PSU"
62 # Disable Hot swap output
66 # Enable Hot swap output
|
| /openbmc/linux/drivers/hv/ |
| H A D | hv_balloon.c | 125 * 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 …]
|
| /openbmc/qemu/include/hw/hyperv/ |
| H A D | dynmem-proto.h | 104 * limitations on hot-add, the guest can specify
329 * Hot add request message. Message sent from the host to the guest.
331 * range: Memory range to hot add.
332 * region: Explicit hot add memory region for guest to use. Optional.
348 * Hot add response message.
349 * This message is sent by the guest to report the status of a hot add request.
351 * assume all further hot add requests will fail, since this indicates that
354 * Hot adds may also fail due to low resources; in this case, the guest must
355 * not complete this message until the hot add can succeed, and the host must
356 * not send a new hot add request until the response is sent.
[all …]
|
| /openbmc/linux/arch/arm64/include/asm/ |
| H A D | module.lds.h | 8 * 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) }
|
| /openbmc/linux/arch/powerpc/platforms/pseries/ |
| H A D | hotplug-memory.c | 293 * 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 …]
|
| /openbmc/linux/Documentation/admin-guide/mm/damon/ |
| H A D | lru_sort.rst | 31 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 …]
|
| /openbmc/linux/drivers/platform/surface/ |
| H A D | Kconfig | 87 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
|
| H A 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.
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");
|
| /openbmc/linux/Documentation/admin-guide/laptops/ |
| H A 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 …]
|
| /openbmc/qemu/docs/system/ |
| H A D | cpu-hotplug.rst | 5 A complete example of vCPU hotplug (and hot-unplug) using QMP
60 hot-plugged (no "qom-path" member). From its output in step (3), we
62 while hot-plugging a CPU into socket 0 core 1 requires passing the listed
117 vCPU hot-unplug
135 vCPU hot-unplug requires guest cooperation; so the ``device_del``
|
| /openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/gpio/phosphor-gpio-monitor/ |
| H A D | yosemite4-phosphor-multi-gpio-monitor.json | 159 "slot-hot-plug@1.service",
175 "slot-hot-plug@2.service",
191 "slot-hot-plug@3.service",
207 "slot-hot-plug@4.service",
223 "slot-hot-plug@5.service",
239 "slot-hot-plug@6.service",
255 "slot-hot-plug@7.service",
271 "slot-hot-plug@8.service",
|
| /openbmc/qemu/docs/specs/ |
| H A D | acpi_mem_hotplug.rst | 4 ACPI BIOS GPE.3 handler is dedicated for notifying OS about memory hot-add
5 and hot-remove events.
7 Memory hot-plug interface (IO port 0xa00-0xa17, 1-4 byte access)
83 - write accesses to memory hot-plug registers not documented above are ignored
84 - read accesses to memory hot-plug registers not documented above return
87 Memory hot remove process diagram
|
| H A D | ppc-spapr-hotplug.rst | 6 to handle hot plugging of dynamic "physical" resources like PCI cards, or
17 To manage hot plug/unplug of these resources, a firmware abstraction known as
31 such as the DRCs managing PCI slots on a hot plugged PHB. In this case the
33 for hot plugged resources described under :ref:`guest-host-interface`.
185 ``2``: ``identify``, used to visually identify slot for interactive hot plug.
193 hot plug/unplug) the pre-allocation of the resource is implied and this sensor
312 Hot plug/unplug events
329 :ref:`hot-plug-unplug-event-structure`. Note that these events are not formally
331 also described below under :ref:`hot-plug-unplug-event-structure`, and so are
343 addition of a ``hot-plug-events`` node under ``/event-sources`` node of the
[all …]
|
| /openbmc/linux/arch/arm/boot/dts/qcom/ |
| H A D | qcom-ipq8064.dtsi | 65 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 …]
|
| /openbmc/linux/drivers/staging/sm750fb/ |
| H A 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) */
|
| /openbmc/qemu/qapi/ |
| H A D | qdev.json | 52 # broke hot-unplug
96 # from the guest. Hot removal is an operation that requires guest
98 # the hot removal process. Completion of the device removal
101 # guest-side error in the hot removal process is detected, the
148 # Emitted when a device hot unplug fails due to a guest reported
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | memory-hotplug.rst | 2 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 …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| H A D | uncore-power.json | 170 … 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…
|
| /openbmc/linux/include/linux/surface_aggregator/ |
| H A D | device.h | 155 * 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 …]
|