> From: Alex Williamson <alex.williamson@xxxxxxxxxx> > Sent: Wednesday, February 5, 2020 7:18 AM > To: kvm@xxxxxxxxxxxxxxx > Subject: Re: [RFC PATCH 0/7] vfio/pci: SR-IOV support > > > Promised example QEMU test case... > > commit 3557c63bcb286c71f3f7242cad632edd9e297d26 > Author: Alex Williamson <alex.williamson@xxxxxxxxxx> > Date: Tue Feb 4 13:47:41 2020 -0700 > > vfio-pci: QEMU support for vfio-pci VF tokens > > Example support for using a vf_token to gain access to a device as > well as using the VFIO_DEVICE_FEATURE interface to set the VF token. > Note that the kernel will disregard the additional option where it's > not required, such as opening the PF with no VF users, so we can > always provide it. > > NB. It's unclear whether there's value to this QEMU support without > further exposure of SR-IOV within a VM. This is meant mostly as a > test case where the real initial users will likely be DPDK drivers. > > Signed-off-by: Alex Williamson <alex.williamson@xxxxxxxxxx> Just curious how UUID is used across the test. Should the QEMU which opens VFs add the vfio_token=UUID or the QEMU which opens PF add the vfio_token=UUID? or both should add vfio_token=UUID. Regards, Yi Liu
