All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Duyck, Alexander H" <alexander.h.duyck@intel.com>
Cc: "virtio-dev@lists.oasis-open.org"
	<virtio-dev@lists.oasis-open.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"alexander.duyck@gmail.com" <alexander.duyck@gmail.com>,
	"virtualization@lists.linux-foundation.org"
	<virtualization@lists.linux-foundation.org>,
	"Wang, Zhihong" <zhihong.wang@intel.com>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"Rustad, Mark D" <mark.d.rustad@intel.com>
Subject: Re: [virtio-dev] [PATCH] virtio_pci: support enabling VFs
Date: Wed, 30 May 2018 20:15:43 +0300	[thread overview]
Message-ID: <20180530201034-mutt-send-email-mst__21575.9478080601$1527700428$gmane$org@kernel.org> (raw)
In-Reply-To: <1527697588.16245.136.camel@intel.com>

On Wed, May 30, 2018 at 04:26:30PM +0000, Duyck, Alexander H wrote:
> On Wed, 2018-05-30 at 19:22 +0300, Michael S. Tsirkin wrote:
> > On Wed, May 30, 2018 at 09:10:57AM -0700, Alexander Duyck wrote:
> > > On Wed, May 30, 2018 at 1:55 AM, Tiwei Bie <tiwei.bie@intel.com> wrote:
> > > > There is a new feature bit allocated in virtio spec to
> > > > support SR-IOV (Single Root I/O Virtualization):
> > > > 
> > > > https://github.com/oasis-tcs/virtio-spec/issues/11
> > > > 
> > > > This patch enables the support for this feature bit in
> > > > virtio driver.
> > > > 
> > > > Signed-off-by: Tiwei Bie <tiwei.bie@intel.com>
> > > 
> > > So from a quick glance it looks like we are leaving SR-IOV enabled if
> > > the driver is removed. Do we want to have that behavior or should we
> > > be adding the code to disable SR-IOV and free the VFs on driver
> > > removal?
> > 
> > Could pci core handle it for us somehow?
> 
> Maybe, but it would require changes to the pci core to do it.
> 
> The problem is some drivers want to leave the VFs there since the PF
> doesn't really do anything, or they have the option of essentially
> putting the VFs into a standby state when the PF is gone.
> 
> My main concern is do we care if VFs are allocated and then somebody
> removes the driver and binds a different driver to the interface? If
> not then this code and be left as is, but I just wanted to be certain
> since I know this isn't just enabling SR-IOV we are having to do a
> number of other checks against the virtio device.

Well the spec says features have to be negotiated, and since we reset
the device when we unbind from it I think it's a given we should keep a
driver bound to the PF.

IOW until we are sure we need the capability to keep it enabled, let's
disable it to be safe.

-- 
MST

  reply	other threads:[~2018-05-30 17:15 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30  8:55 [PATCH] virtio_pci: support enabling VFs Tiwei Bie
2018-05-30  8:55 ` [virtio-dev] " Tiwei Bie
2018-05-30 12:29 ` Stefan Hajnoczi
2018-05-30 12:29 ` Stefan Hajnoczi
2018-05-30 12:41 ` Michael S. Tsirkin
2018-05-30 12:41   ` [virtio-dev] " Michael S. Tsirkin
2018-05-30 12:41 ` Michael S. Tsirkin
2018-05-30 16:03 ` [virtio-dev] " Rustad, Mark D
2018-05-30 16:09   ` Michael S. Tsirkin
2018-05-30 16:09     ` Michael S. Tsirkin
2018-05-31  2:55     ` Tiwei Bie
2018-05-31  2:55       ` Tiwei Bie
2018-06-01  1:21       ` Michael S. Tsirkin
2018-06-01  1:21       ` Michael S. Tsirkin
2018-06-01  1:21         ` Michael S. Tsirkin
2018-06-01  1:36         ` Tiwei Bie
2018-06-01  1:36           ` Tiwei Bie
2018-06-01  1:36         ` Tiwei Bie
2018-05-31  2:55     ` Tiwei Bie
2018-05-30 16:09   ` Michael S. Tsirkin
2018-05-30 16:03 ` Rustad, Mark D
2018-05-30 16:10 ` Alexander Duyck
2018-05-30 16:10   ` Alexander Duyck
2018-05-30 16:22   ` Michael S. Tsirkin
2018-05-30 16:22   ` Michael S. Tsirkin
2018-05-30 16:22     ` Michael S. Tsirkin
2018-05-30 16:26     ` Duyck, Alexander H
2018-05-30 16:26     ` Duyck, Alexander H
2018-05-30 16:26       ` Duyck, Alexander H
2018-05-30 17:15       ` Michael S. Tsirkin [this message]
2018-05-30 17:15       ` Michael S. Tsirkin
2018-05-30 17:15         ` Michael S. Tsirkin
2018-05-30 16:10 ` Alexander Duyck
2018-05-30 16:22 ` Michael S. Tsirkin
2018-05-30 16:22   ` [virtio-dev] " Michael S. Tsirkin
2018-05-30 16:44   ` Rustad, Mark D
2018-05-30 16:44     ` [virtio-dev] " Rustad, Mark D
2018-05-30 16:44     ` Rustad, Mark D
2018-05-30 16:54     ` Duyck, Alexander H
2018-05-30 16:54       ` Duyck, Alexander H
2018-05-30 17:11       ` Rustad, Mark D
2018-05-30 17:11         ` [virtio-dev] " Rustad, Mark D
2018-05-30 17:11         ` Rustad, Mark D
2018-05-31  3:20         ` Tiwei Bie
2018-05-31  3:20           ` [virtio-dev] " Tiwei Bie
2018-05-31 14:27           ` Alexander Duyck
2018-05-31 14:27           ` Alexander Duyck
2018-05-31 14:27             ` [virtio-dev] " Alexander Duyck
2018-06-01  2:30             ` Tiwei Bie
2018-06-01  2:30             ` Tiwei Bie
2018-06-01  2:30               ` [virtio-dev] " Tiwei Bie
2018-05-31  3:20         ` Tiwei Bie
2018-05-30 16:54     ` Duyck, Alexander H
2018-05-30 16:22 ` Michael S. Tsirkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='20180530201034-mutt-send-email-mst__21575.9478080601$1527700428$gmane$org@kernel.org' \
    --to=mst@redhat.com \
    --cc=alexander.duyck@gmail.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mark.d.rustad@intel.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=zhihong.wang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.