Home
last modified time | relevance | path

Searched refs:unplugged (Results 1 – 8 of 8) sorted by relevance

/openbmc/dbus-sensors/docs/mctp/
H A Dopenbmc_usb_mctp.tla12 DeviceStateType == { "unplugged", "plugged" }
15 UnplugEvent(dev) == [ dev |-> dev, state |-> "unplugged"]
277 \/ /\ ev.state = "unplugged"
287 \/ /\ ev.state = "unplugged"
/openbmc/qemu/docs/system/
H A Dvirtio-net-failover.rst9 virtio-net device. Before migration the vfio device is unplugged and data flows
/openbmc/qemu/docs/devel/
H A Dqom.rst451 Likewise only some can be unplugged after creation and need an
454 Devices can only be unplugged if their ``parent_bus`` has a registered
/openbmc/qemu/docs/
H A Dpcie.txt224 cannot be hot-plugged/hot-unplugged:
238 PCI Express devices can be natively hot-plugged/hot-unplugged into/from
/openbmc/qemu/ui/
H A Dconsole.c1219 static const char unplugged[] = in graphic_console_close() local
1232 surface = qemu_create_placeholder_surface(width, height, unplugged); in graphic_console_close()
/openbmc/u-boot/drivers/core/
H A DKconfig63 it causes unplugged devices to linger around in the dm-tree, and it
/openbmc/phosphor-power/phosphor-power-sequencer/docs/
H A Dchassis_status.md182 failure or an unplugged power cord. See the sub-sections below for more
/openbmc/qemu/docs/system/s390x/
H A Dvfio-ap.rst630 A vfio-ap device can be unplugged from a running KVM guest if a vfio-ap device
915 unplugged before migrating the guest (see `Hot unplug a vfio-ap device from a