> From: Michael S. Tsirkin <m...@redhat.com> > Sent: Thursday, March 2, 2023 8:05 AM > My intent is to try and support both SR-IOV and SIOV usecases with the same > structure and maybe even the same VQ. > > For example, it might make sense to split creating/destroying SIOV devices > from the transport passing data from the guest - the driver would then not > negotiate VIRTIO_F_SR_IOV (which then means auto-provisioning). > > This is out of RFC, since we have two commands which are useful to discover > supported group types (ATM can be none or SR-IOV).
I guess you missed expanding the cover letter for our discussion on [1] to list use cases a little more tangible. So let us have them here. Some I can think of are good starting points are: 1. virtio VF features query and configuration space provisioning 2. virtio VF resource (queues, msix vectors count) provisioning I plan to post the follow-up patch for #1 as the actual use of AQ. [1] https://lists.oasis-open.org/archives/virtio-dev/202302/msg00246.html --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
