[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] [PATCH v2 10/25] qemu: capabilities: Add virtio/vhost {non-}transitional



On Wed, Jan 23, 2019 at 04:32:38PM -0500, Cole Robinson wrote:
This adds QEMU_CAPS flags for the following devices

   virtio-blk-pci-transitional
   virtio-blk-pci-non-transitional
   virtio-net-pci-transitional
   virtio-net-pci-non-transitional
   vhost-scsi-pci-transitional
   vhost-scsi-pci-non-transitional
   virtio-rng-pci-transitional
   virtio-rng-pci-non-transitional
   virtio-9p-pci-transitional
   virtio-9p-pci-non-transitional
   virtio-balloon-pci-transitional
   virtio-balloon-pci-non-transitional
   vhost-vsock-pci-transitional
   vhost-vsock-pci-non-transitional
   virtio-input-host-pci-transitional
   virtio-input-host-pci-non-transitional
   virtio-scsi-pci-transitional
   virtio-scsi-pci-non-transitional
   virtio-serial-pci-transitional
   virtio-serial-pci-non-transitional

Signed-off-by: Cole Robinson <crobinso redhat com>
---
src/qemu/qemu_capabilities.c                  | 48 +++++++++++++++++++
src/qemu/qemu_capabilities.h                  | 28 +++++++++++
.../caps_4.0.0.x86_64.xml                     | 20 ++++++++
3 files changed, 96 insertions(+)

This seems excessive, is there a plan to retire the transitional
devices? I don't expect anyone creating a QEMU build that e.g.:
a) supports virtio-rng-pci-transitional but not virtio-rng-pci-non-transitional
b) supports virtio-scsi-pci-transitional but not virtio-input-host-pci-transitional

For the disable-legacy property, we only have
QEMU_CAPS_VIRTIO_PCI_DISABLE_LEGACY, that is checked on multiple (but
not all possible) PCI devices.

Jano

Attachment: signature.asc
Description: PGP signature


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]