Home
last modified time | relevance | path

Searched full:unplugged (Results 1 – 25 of 55) sorted by relevance

123

/openbmc/qemu/include/standard-headers/linux/
H A Dvirtio_mem.h51 * or unplugged. The device driver is responsible for (un)plugging memory
70 * There are no guarantees what will happen if unplugged memory is
71 * read/written. In general, unplugged memory should not be touched, because
73 * VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE, unplugged memory inside the usable
79 * Usually, during system resets all memory will get unplugged, so the
91 /* unplugged memory must not be accessed */
171 /* State of memory blocks is "unplugged" */
/openbmc/openbmc/meta-ibm/recipes-phosphor/dbus/power-supply-policy/
H A Dpower-supply-policy.yaml103 'If this condition passes power supply0 has been unplugged for more than
108 For a more detailed definition of unplugged, consult the documentation
124 'If this condition passes power supply1 has been unplugged for more than
/openbmc/qemu/include/hw/virtio/
H A Dvirtio-mem.h38 #define VIRTIO_MEM_UNPLUGGED_INACCESSIBLE_PROP "unplugged-inaccessible"
49 /* bitmap used to track unplugged memory */
H A Dvirtio-bus.h68 * This is called by virtio-bus just before the device is unplugged.
H A Dvirtio-serial.h51 * hot-unplugged or removed.
/openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/gpio/phosphor-gpio-monitor/
H A Dslot-unplug38 echo "Slot ${unplugged_slot} unplugged."
/openbmc/openbmc/meta-ibm/recipes-phosphor/dbus/fan-policy/swift/
H A Dwater-cooled.yaml157 'If this condition passes more than one fan has been unplugged
162 For a more detailed definition of unplugged, consult the documentation
H A Dair-cooled.yaml157 'If this condition passes more than one fan has been unplugged
162 For a more detailed definition of unplugged, consult the documentation
H A Dfan-errors.yaml370 'If this condition passes fan0 has been unplugged for more than 20 seconds.'
397 'If this condition passes fan1 has been unplugged for more than 20 seconds.'
424 'If this condition passes fan2 has been unplugged for more than 20 seconds.'
451 'If this condition passes fan3 has been unplugged for more than 20 seconds.'
/openbmc/openbmc/meta-ibm/recipes-phosphor/dbus/fan-policy/witherspoon/
H A Dfan-errors.yaml371 'If this condition passes fan0 has been unplugged for more than 20 seconds.'
398 'If this condition passes fan1 has been unplugged for more than 20 seconds.
429 'If this condition passes fan2 has been unplugged for more than 20 seconds.'
456 'If this condition passes fan3 has been unplugged for more than 20 seconds.'
H A Dwater-cooled.yaml186 'If this condition passes more than one fan has been unplugged
191 For a more detailed definition of unplugged, consult the documentation
H A Dair-cooled.yaml192 'If this condition passes more than one fan has been unplugged
197 For a more detailed definition of unplugged, consult the documentation
/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/hw/remote/
H A Diommu.c34 * - When a device is hot unplugged, the elem->mr reference is dropped so
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Network/
H A DEthernetInterface.interface.yaml97 a carrier signal. It is FALSE when the cable is unplugged, or the
/openbmc/qemu/hw/virtio/
H A Dvirtio-mem.c82 * 2. We avoid placing THPs for plugged blocks that also cover unplugged
151 * anonymous RAM. In any other case, reading unplugged *can* populate a in virtio_mem_has_shared_zeropage()
187 * For precopy, we don't want unplugged blocks in our migration stream, and in virtio_mem_is_busy()
191 * migrate these blocks when they were unplugged). in virtio_mem_is_busy()
537 /* Deactivate all memslots with unplugged blocks in a single transaction. */ in virtio_mem_deactivate_unplugged_memslots()
583 /* Deactivate completely unplugged memslots after updating the state. */ in virtio_mem_set_block_state()
1832 error_setg(errp, "virtio-mem device cannot get unplugged while" in virtio_mem_unplug_request_check()
1838 error_setg(errp, "virtio-mem device cannot get unplugged while some" in virtio_mem_unplug_request_check()
1843 error_setg(errp, "virtio-mem device cannot get unplugged while" in virtio_mem_unplug_request_check()
H A Dvirtio-md-pci.c79 error_setg(errp, "this virtio based memory devices cannot be unplugged"); in virtio_md_pci_unplug_request()
/openbmc/qemu/hw/s390x/
H A Dvirtio-ccw-md.c81 "this virtio based memory devices cannot be unplugged"); in virtio_ccw_md_unplug_request()
/openbmc/qemu/include/hw/mem/
H A Dnvdimm.h120 * the NVDIMM device is plugged or unplugged.
/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/phosphor-hwmon/
H A Dhwmonio.cpp82 * unplugged but the driver is still bound. Retry
/openbmc/u-boot/drivers/core/
H A DKconfig63 it causes unplugged devices to linger around in the dm-tree, and it
/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/accel/tcg/
H A Dtcg-accel-ops-rr.c125 * Destroy any remaining vCPUs which have been unplugged and have
/openbmc/qemu/include/hw/s390x/
H A Ds390-pci-bus.h180 * unplugged

123