From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 3 Aug 2022 02:43:49 -0400 From: "Michael S. Tsirkin" Subject: Re: [PATCH v6 1/5] Introduce device group Message-ID: <20220803024231-mutt-send-email-mst@kernel.org> References: <20220731154354.15698-1-mgurtovoy@nvidia.com> <20220731154354.15698-2-mgurtovoy@nvidia.com> <20220802092302-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Disposition: inline To: Jason Wang Cc: Max Gurtovoy , virtio-comment@lists.oasis-open.org, Cornelia Huck , Virtio-Dev , Oren Duer , Parav Pandit , Shahaf Shuler , Ariel Adam , virtio@lists.oasis-open.org, eperezma List-ID: On Wed, Aug 03, 2022 at 12:44:38PM +0800, Jason Wang wrote: > > A VF now is a member of a SRIOV and SIOV type groups and we > > can use type to distinguish between these. > > > > We should probably be explicit that each of these groups has to > > have a distinct group type then. > > > > And this raises the question: different types have different > > capabilities. So let's say admin queue is used to both > > control features for SRIOV VFs and to create SIOV SFs. > > I don't get how the admin queue can be used to control VF features > considering VF has its capabilities. (SR-IOV lacks the ability to > provision a single VF). I mean, VF exists, but it does not have to consume lots of resources. We can if we want to require that drivers only attach to VFs which have been enabled through a special command. -- MST