[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [virtio-comment] Re: [virtio-dev] Re: [virtio-comment] [RFC PATCH] admin-queue: bind the group member to the device
> From: Michael S. Tsirkin <mst@redhat.com> > Sent: Monday, June 26, 2023 8:35 AM > > Yet to catch up on the thread, so likely I am missing something. > > > > The flow is for one OS (Linux) is: > > 1. user enable SR-IOV on the PF device in a host, which creates SR-IOV VFs in > the device. > > (num_vfs and vf enable bit in the PCI capability) > > > > 2. VFs are created at the PCI level in the host system and also inside > > the device > > > > 3. A user on the host may bind these VFs to the VF driver > > (virtionet/blk or vfio or vp_vdpa or some other) > > > > Between step #2 and #3, a user may configure one or multiple attributes of > the VF. > > This includes feature bits, config space fields, vf msix vectors and more. > > This is to be using admin command. > > These admin commands definition is due. > > To be frank, I am not sure binding to an ID necessarily needs to be gated on > provisioning commands. > What was not explained at all is what purpose does this extra level of > indirection serve. I didn't suggest gating binding on provisioning. As written above _may_configure_. So provisioning is optional.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]