Home
last modified time | relevance | path

Searched refs:plug (Results 1 – 25 of 41) sorted by relevance

12

/qemu/docs/
H A Dpcie_pci_bridge.txt10 But due to its strict limitations - no support of hot-plug,
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.
102 Windows 7 and older versions don't support hot-plug devices into the PCIE-PCI bridge.
103 To enable device hot-plug into the bridge on Linux there're 3 ways:
107 which allows the bridge to notify the OS about hot-plug event without having
H A Dpcie.txt67 2.1.1 To plug a device into pcie.0 as a Root Complex Integrated Endpoint use:
145 PCI Express to PCI Bridge until is full and then plug a new PCI-PCI Bridge...
162 2.3.1 To plug a PCI device into pcie.0 as an Integrated Endpoint use:
220 5. Hot-plug
223 do not support hot-plug, so any devices plugged into Root Complexes
234 The PCI hot-plug into PCI-PCI bridge is ACPI based, whereas hot-plug into
236 the PCI Express native hot-plug.
241 5.1 Planning for hot-plug:
265 5.3 Hot-plug example:
/qemu/hw/core/
H A Dhotplug.c33 if (hdc->plug) { in hotplug_handler_plug()
34 hdc->plug(plug_handler, plugged_dev, errp); in hotplug_handler_plug()
/qemu/docs/specs/
H A Dacpi_mem_hotplug.rst7 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
H A Dppc-spapr-hotplug.rst17 To manage hot plug/unplug of these resources, a firmware abstraction known as
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
347 .. _hot-plug-unplug-event-structure:
349 Hot plug/unplug event structure
352 The hot plug specific payload in QEMU is implemented as follows (with all values
/qemu/tests/qtest/
H A Dmeson.build101 'device-plug-test',
104 'cpu-plug-test',
172 (config_all_devices.has_key('CONFIG_PSERIES') ? ['device-plug-test'] : []) + \
179 qtests_pci + ['migration-test', 'numa-test', 'cpu-plug-test', 'drive_del-test']
254 'device-plug-test',
256 'cpu-plug-test',
/qemu/hw/virtio/
H A Dvirtio-mem.c580 uint64_t size, bool plug) in virtio_mem_set_block_state() argument
590 if (!plug) { in virtio_mem_set_block_state()
654 uint16_t nb_blocks, bool plug) in virtio_mem_state_change_request() argument
663 if (plug && (vmem->size + size > vmem->requested_size)) { in virtio_mem_state_change_request()
668 if ((plug && !virtio_mem_is_range_unplugged(vmem, gpa, size)) || in virtio_mem_state_change_request()
669 (!plug && !virtio_mem_is_range_plugged(vmem, gpa, size))) { in virtio_mem_state_change_request()
673 ret = virtio_mem_set_block_state(vmem, gpa, size, plug); in virtio_mem_state_change_request()
677 if (plug) { in virtio_mem_state_change_request()
689 const uint64_t gpa = le64_to_cpu(req->u.plug.addr); in virtio_mem_plug_request()
690 const uint16_t nb_blocks = le16_to_cpu(req->u.plug.nb_blocks); in virtio_mem_plug_request()
/qemu/include/hw/
H A Dhotplug.h59 hotplug_fn plug; member
/qemu/include/standard-headers/linux/
H A Dvirtio_mem.h129 struct virtio_mem_req_plug plug; member
/qemu/docs/config/
H A Dq35-virtio-graphical.cfg69 # We create eight PCI Express Root Ports, and we plug them
135 # We use virtio-scsi here so that we can (hot)plug a large
214 # We plug the QXL video card directly into the PCI Express
H A Dq35-virtio-serial.cfg74 # We create eight PCI Express Root Ports, and we plug them
140 # We use virtio-scsi here so that we can (hot)plug a large
H A Dmach-virt-serial.cfg124 # We create eight PCI Express Root Ports, and we plug them
190 # We use virtio-scsi here so that we can (hot)plug a large
H A Dmach-virt-graphical.cfg118 # We create eight PCI Express Root Ports, and we plug them
184 # We use virtio-scsi here so that we can (hot)plug a large
/qemu/docs/system/devices/
H A Dusb.rst5 plug virtual USB devices or real host USB devices (only works with
219 For all the above USB devices, by default QEMU will plug the device
315 When relaunching QEMU, you may have to unplug and plug again the USB
348 hostaddr isn't stable. The next time you plug the device into the host it
388 the device not responding any more until you power-cycle (aka un-plug
389 and re-plug) it.
H A Divshmem.rst48 master must complete migration before you plug back the other devices.
/qemu/hw/ppc/
H A De500plat.c79 hc->plug = e500plat_machine_device_plug_cb; in e500plat_machine_class_init()
/qemu/docs/system/
H A Dmanaged-startup.rst23 cold plug devices. The experimental ``--preconfig`` command line option
H A Dvm-templating.rst31 use case, which might involve vmgenid, hot(un)plug of NIC, etc..
/qemu/hw/pci-bridge/
H A Dpcie_pci_bridge.c157 hc->plug = pci_bridge_dev_plug_cb; in pcie_pci_bridge_class_init()
H A Dpci_bridge_dev.c261 hc->plug = pci_bridge_dev_plug_cb; in pci_bridge_dev_class_init()
/qemu/hw/pci/
H A Dpcie_port.c233 hc->plug = pcie_cap_slot_plug_cb; in pcie_slot_class_init()
/qemu/tests/qemu-iotests/
H A D240.out1 ==Unplug a SCSI disk and then plug it again==
/qemu/hw/acpi/
H A Dgeneric_event_device.c415 hc->plug = acpi_ged_device_plug_cb; in acpi_ged_class_init()
H A Dpiix4.c647 hc->plug = piix4_device_plug_cb; in piix4_pm_class_init()
/qemu/docs/system/s390x/
H A Dvfio-ap.rst599 Hot plug a vfio-ap device into a running guest
604 to the bus already, whether via the QEMU command line or a prior hot plug
607 To hot plug a vfio-ap device, use the QEMU ``device_add`` command::
632 or a prior hot plug action.

12