Home
last modified time | relevance | path

Searched refs:hot (Results 1 – 25 of 288) sorted by relevance

12345678910>>...12

/openbmc/qemu/docs/
H A Dpcie_pci_bridge.txt10 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
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.
94 another plugged into the hot-plugged bridge.
[all …]
H A Dpcie.txt43 Note: Integrated Endpoints are not hot-pluggable.
137 device in question will be incapable of hot-unplugging.
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
241 5.1 Planning for hot-plug:
[all …]
H A Dmemory-hotplug.txt77 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/qemu/docs/specs/
H A Dacpi_mem_hotplug.rst4 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 Dppc-spapr-hotplug.rst6 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
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
352 The hot plug specific payload in QEMU is implemented as follows (with all values
[all …]
/openbmc/qemu/docs/system/
H A Dcpu-hotplug.rst5 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/linux/arch/arm/boot/dts/qcom/
H A 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 …]
/openbmc/linux/arch/arm64/include/asm/
H A Dmodule.lds.h16 .text.hot : { *(.text.hot) }
/openbmc/linux/arch/arm64/boot/dts/qcom/
H A Dpm8550vs.dtsi27 type = "hot";
48 type = "hot";
69 type = "hot";
90 type = "hot";
H A Dpm8010.dtsi27 type = "hot";
48 type = "hot";
H A Dpmr735d.dtsi27 type = "hot";
48 type = "hot";
/openbmc/linux/Documentation/admin-guide/mm/damon/
H A 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 …]
/openbmc/linux/drivers/video/fbdev/core/
H A 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()
H A 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()
H A 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()
H A 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()
/openbmc/linux/arch/arm/boot/dts/rockchip/
H A 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 */
/openbmc/linux/arch/arm64/boot/dts/marvell/
H A Darmada-ap80x.dtsi343 cpu0_hot: cpu0-hot {
356 map0_hot: map0-hot {
376 cpu1_hot: cpu1-hot {
389 map1_hot: map1-hot {
409 cpu2_hot: cpu2-hot {
422 map2_hot: map2-hot {
442 cpu3_hot: cpu3-hot {
/openbmc/linux/drivers/acpi/
H A Dthermal.c115 struct acpi_thermal_trip hot; member
243 tz->trips.hot.valid = false; in __acpi_thermal_trips_update()
247 tz->trips.hot.temperature = tmp; in __acpi_thermal_trips_update()
248 tz->trips.hot.valid = true; in __acpi_thermal_trips_update()
251 tz->trips.hot.temperature); in __acpi_thermal_trips_update()
462 tz->trips.hot.valid | in acpi_thermal_get_trip_points()
576 if (tz->trips.hot.valid) in acpi_thermal_cooling_device_cb()
652 .hot = acpi_thermal_zone_device_hot,
694 if (tz->trips.hot.valid) in acpi_thermal_register_thermal_zone()
717 if (tz->trips.hot.valid) { in acpi_thermal_register_thermal_zone()
[all …]
/openbmc/qemu/qapi/
H A Dqdev.json52 # broke hot-unplug
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/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/gpio/
H A Dphosphor-gpio-monitor_%.bbappend16 file://slot-hot-plug@.service \
47 slot-hot-plug@.service \
72 …install -m 0644 ${UNPACKDIR}/slot-hot-plug@.service ${D}${systemd_system_unitdir}/slot-hot-plug@.s…
/openbmc/linux/Documentation/devicetree/bindings/thermal/
H A Dmax77620_thermal.txt48 pmic_die_warn_temp_thresh: hot-die {
50 type = "hot";
/openbmc/linux/drivers/platform/surface/
H A DKconfig87 devices can be (hot-)removed. Hub devices and drivers are required to
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
/openbmc/linux/Documentation/admin-guide/laptops/
H A Dthinkpad-acpi.rst190 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
252 nor does it allow one to manipulate the hot key mask when the firmware
[all …]
/openbmc/linux/drivers/thermal/intel/
H A Dtherm_throt.c305 bool hot; in throttle_active_work() local
308 get_therm_status(state->level, &hot, &temp); in throttle_active_work()
310 if (!hot && temp > state->baseline_temp) { in throttle_active_work()
409 bool hot; in therm_throt_process() local
412 get_therm_status(state->level, &hot, &temp); in therm_throt_process()

12345678910>>...12