| /qemu/docs/system/ |
| H A D | cpu-hotplug.rst | 5 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 D | virtio-net-failover.rst | 33 another host QEMU will unplug the primary device via the PCIe based hotplug
64 A new migration state wait-unplug was added for this feature. If failover primary
66 It will wait until the device unplug is completed in the guest and then move into
|
| /qemu/hw/s390x/ |
| H A D | css-bridge.c | 37 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 D | ccw-device.h | 40 void (*unplug)(HotplugHandler *, DeviceState *, Error **); member
|
| H A D | ap-bridge.c | 69 hc->unplug = qdev_simple_device_unplug_cb; in ap_bridge_class_init()
|
| /qemu/tests/functional/ |
| H A D | test_x86_64_hotplug_blk.py | 56 def unplug(self) -> None: member in HotPlugBlk
81 self.unplug()
|
| /qemu/hw/core/ |
| H A D | hotplug.c | 55 if (hdc->unplug) { in hotplug_handler_unplug()
56 hdc->unplug(plug_handler, plugged_dev, errp); in hotplug_handler_unplug()
|
| /qemu/hw/usb/ |
| H A D | hcd-uhci.c | 1295 k->exit = info->unplug ? usb_uhci_exit : NULL; in uhci_data_class_init()
1299 if (!info->unplug) { in uhci_data_class_init()
1319 .unplug = true,
1326 .unplug = true,
1333 .unplug = false,
1340 .unplug = false,
1347 .unplug = false,
1354 .unplug = false,
1361 .unplug = false,
1368 .unplug = false,
|
| H A D | vt82c686-uhci-pci.c | 37 .unplug = true,
|
| H A D | hcd-uhci.h | 87 bool unplug; member
|
| /qemu/docs/ |
| 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
84 Two monitor commands are used to hot unplug memory:
|
| /qemu/accel/tcg/ |
| H A D | tcg-accel-ops-rr.c | 133 if (cpu->unplug && !cpu_can_run(cpu)) { in rr_deal_with_unplugged_cpus()
277 if (cpu->unplug) { in rr_cpu_thread_fn()
|
| H A D | tcg-accel-ops-mttcg.c | 118 } while (!cpu->unplug || cpu_can_run(cpu)); in mttcg_cpu_thread_fn()
|
| /qemu/include/hw/ |
| H A D | hotplug.h | 61 hotplug_fn unplug; member
|
| /qemu/include/standard-headers/linux/ |
| H A D | virtio_mem.h | 132 struct virtio_mem_req_unplug unplug; member
|
| /qemu/accel/ |
| H A D | dummy-cpus.c | 60 } while (!cpu->unplug); in dummy_cpu_thread_fn()
|
| /qemu/docs/specs/ |
| H A D | acpi_mem_hotplug.rst | 94 | device_del +---->+ device unplug request +----->+Send SCI to guest,|
118 | set OST event & status | | call device unplug cb |
|
| H A D | ppc-spapr-hotplug.rst | 17 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
|
| /qemu/target/i386/nvmm/ |
| H A D | nvmm-accel-ops.c | 55 } while (!cpu->unplug || cpu_can_run(cpu)); in qemu_nvmm_cpu_thread_fn()
|
| /qemu/target/i386/whpx/ |
| H A D | whpx-accel-ops.c | 55 } while (!cpu->unplug || cpu_can_run(cpu)); in whpx_cpu_thread_fn()
|
| /qemu/accel/kvm/ |
| H A D | kvm-accel-ops.c | 57 } while (!cpu->unplug || cpu_can_run(cpu)); in kvm_vcpu_thread_fn()
|
| /qemu/qapi/ |
| H A D | qdev.json | 52 # broke hot-unplug
148 # Emitted when a device hot unplug fails due to a guest reported
|
| /qemu/hw/remote/ |
| H A D | machine.c | 132 hc->unplug = remote_machine_dev_unplug_cb; in remote_machine_class_init()
|
| /qemu/hw/pci-bridge/ |
| H A D | pcie_pci_bridge.c | 156 hc->unplug = pci_bridge_dev_unplug_cb; in pcie_pci_bridge_class_init()
|
| /qemu/hw/pci/ |
| H A D | pcie_port.c | 222 hc->unplug = pcie_cap_slot_unplug_cb; in pcie_slot_class_init()
|