David Gibson ad45c52fbe runtime/device: Record guest PCI path for VFIO devices ...

For several device types which correspond to a PCI device in the guest
we record the device's PCI path in the guest.  We don't currently do
that for VFIO devices, but we're going to need to for better handling
of SR-IOV devices.

To accomplish this, we have to determine the guest PCI path from the
information the VMM gives us:

For qemu, we query the slot of the device and its bridge from QMP.

For cloud-hypervisor, the device add interface gives us a guest PCI
address.  In fact this represents a design error in the clh API -
there's no way it can really know the guest PCI address in general.
It works in this case, because clh doesn't use PCI bridges, so the
device will always be on the root bus.  Based on that, the PCI path is
simply the device's slot number.

Signed-off-by: David Gibson <david@gibson.dropbear.id.au>

2021-09-27 12:46:33 +10:00

..

api

runtime: Fix ordering of trace spans

2021-03-16 17:39:28 -07:00

config

runtime/device: Record guest PCI path for VFIO devices

2021-09-27 12:46:33 +10:00

drivers

runtime: virtcontainers/device: fix govet fieldalignment

2021-07-20 11:59:15 -05:00

manager

runtime: virtcontainers/device: fix govet fieldalignment

2021-07-20 11:59:15 -05:00