Home
last modified time | relevance | path

Searched refs:unplug (Results 1 – 25 of 39) sorted by relevance

12

/openbmc/qemu/hw/usb/
H A Dhcd-uhci-pci.c
H A Dhcd-uhci-pci.h
H A Dvt82c686-uhci-pci.c37 .unplug = true,
H A Dhcd-uhci.c1301 k->exit = info->unplug ? usb_uhci_exit : NULL; in uhci_data_class_init()
1305 if (!info->unplug) { in uhci_data_class_init()
1325 .unplug = true,
1332 .unplug = true,
1339 .unplug = false,
1346 .unplug = false,
1353 .unplug = false,
1360 .unplug = false,
1367 .unplug = false,
1374 .unplug = false,
H A Dhcd-uhci.h87 bool unplug; member
/openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/gpio/phosphor-gpio-monitor/
H A Dslot-unplug@.service2 Description=slot-unplug %i
6 ExecStart=/usr/libexec/phosphor-gpio-monitor/slot-unplug %i
7 SyslogIdentifier=slot-unplug %i
/openbmc/qemu/docs/system/
H A Dcpu-hotplug.rst5 A complete example of vCPU hotplug (and hot-unplug) using QMP
117 vCPU hot-unplug
135 vCPU hot-unplug requires guest cooperation; so the ``device_del``
137 unplug". At this point, the guest will get a System Control
140 QEMU to unplug it.
H A Dvirtio-net-failover.rst33 guest is live-migrated to another host QEMU will unplug the primary
68 A new migration state wait-unplug was added for this feature. If
70 will go into this state. It will wait until the device unplug is
/openbmc/qemu/hw/s390x/
H A Dcss-bridge.c37 if (k->unplug) { in ccw_device_unplug()
38 k->unplug(hotplug_dev, dev, &err); in ccw_device_unplug()
125 hc->unplug = ccw_device_unplug; in virtual_css_bridge_class_init()
H A Dccw-device.h40 void (*unplug)(HotplugHandler *, DeviceState *, Error **); member
H A Dap-bridge.c69 hc->unplug = qdev_simple_device_unplug_cb; in ap_bridge_class_init()
/openbmc/qemu/hw/core/
H A Dhotplug.c55 if (hdc->unplug) { in hotplug_handler_unplug()
56 hdc->unplug(plug_handler, plugged_dev, errp); in hotplug_handler_unplug()
/openbmc/qemu/tests/functional/
H A Dtest_x86_64_hotplug_blk.py
/openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/gpio/
H A Dphosphor-gpio-monitor_%.bbappend33 file://slot-unplug@.service \
34 file://slot-unplug \
65 slot-unplug@.service \
91 install -m 0644 ${UNPACKDIR}/slot-unplug@.service ${D}${systemd_system_unitdir}/
108 install -m 0755 ${UNPACKDIR}/slot-unplug ${D}${libexecdir}/${PN}/
/openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/console/obmc-console/
H A D10-host-console-dependency.conf.in3 Conflicts=obmc-host-stop@@HOST_ID@.target slot-unplug@@HOST_ID@.service
/openbmc/qemu/include/hw/
H A Dhotplug.h61 hotplug_fn unplug; member
/openbmc/qemu/include/standard-headers/linux/
H A Dvirtio_mem.h132 struct virtio_mem_req_unplug unplug; member
/openbmc/qemu/docs/
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
84 Two monitor commands are used to hot unplug memory:
/openbmc/qemu/docs/specs/
H A Dacpi_mem_hotplug.rst94 | device_del +---->+ device unplug request +----->+Send SCI to guest,|
118 | set OST event & status | | call device unplug cb |
H A Dppc-spapr-hotplug.rst17 To manage hot plug/unplug of these resources, a firmware abstraction known as
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
347 .. _hot-plug-unplug-event-structure:
349 Hot plug/unplug event structure
/openbmc/qemu/hw/remote/
H A Dmachine.c132 hc->unplug = remote_machine_dev_unplug_cb; in remote_machine_class_init()
/openbmc/qemu/hw/pci-bridge/
H A Dpcie_pci_bridge.c156 hc->unplug = pci_bridge_dev_unplug_cb; in pcie_pci_bridge_class_init()
H A Dpci_bridge_dev.c261 hc->unplug = pci_bridge_dev_unplug_cb; in pci_bridge_dev_class_init()
/openbmc/qemu/hw/pci/
H A Dpcie_port.c222 hc->unplug = pcie_cap_slot_unplug_cb; in pcie_slot_class_init()
/openbmc/qemu/hw/intc/
H A Dloongarch_ipi.c211 hc->unplug = loongarch_ipi_cpu_unplug; in loongarch_ipi_class_init()

12