From: Alex Williamson <alex.williamson@redhat.com> To: Keith Busch <keith.busch@intel.com> Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>, linux-nvme@lists.infradead.org, Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@infradead.org> Subject: Re: [PATCH 1/2] pci: Error disabling SR-IOV if in VFs assigned Date: Tue, 17 May 2016 16:08:32 -0600 [thread overview] Message-ID: <20160517160832.51fc0304@t450s.home> (raw) In-Reply-To: <1463521199-16604-1-git-send-email-keith.busch@intel.com> On Tue, 17 May 2016 15:39:58 -0600 Keith Busch <keith.busch@intel.com> wrote: > Every sriov capable driver has to check if any guest is using a virtual > function prior to disabling, so let's make it common code. This is not true, the PCI_DEV_FLAGS_ASSIGNED flag is inherently racy, so checking it is really only a courtesy for broken drivers that still make use of it. I don't object to adding it here, though I wish the entire interface was deprecated, but it's only a minimal amount of insurance as a VF might get assigned immediately following your added test or might not participate in the assigned device flagging at all. I believe the better way to handle this is with proper host drivers for assigned devices that manage the driver .remove callback properly while devices are in use. The only reason to handle assigned devices specially in this case is when they don't have proper host drivers managing them, which is a problem that we've fixed. Thanks, Alex > Signed-off-by: Keith Busch <keith.busch@intel.com> > --- > drivers/pci/pci-sysfs.c | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/drivers/pci/pci-sysfs.c b/drivers/pci/pci-sysfs.c > index 342b691..5011fa9 100644 > --- a/drivers/pci/pci-sysfs.c > +++ b/drivers/pci/pci-sysfs.c > @@ -487,6 +487,11 @@ static ssize_t sriov_numvfs_store(struct device *dev, > > if (num_vfs == 0) { > /* disable VFs */ > + if (pci_vfs_assigned(pdev)) { > + dev_warn(&pdev->dev, > + "Cannot disable SR-IOV VFs while assigned\n"); > + return -EPERM; > + } > ret = pdev->driver->sriov_configure(pdev, 0); > if (ret < 0) > return ret;
WARNING: multiple messages have this Message-ID (diff)
From: alex.williamson@redhat.com (Alex Williamson) Subject: [PATCH 1/2] pci: Error disabling SR-IOV if in VFs assigned Date: Tue, 17 May 2016 16:08:32 -0600 [thread overview] Message-ID: <20160517160832.51fc0304@t450s.home> (raw) In-Reply-To: <1463521199-16604-1-git-send-email-keith.busch@intel.com> On Tue, 17 May 2016 15:39:58 -0600 Keith Busch <keith.busch@intel.com> wrote: > Every sriov capable driver has to check if any guest is using a virtual > function prior to disabling, so let's make it common code. This is not true, the PCI_DEV_FLAGS_ASSIGNED flag is inherently racy, so checking it is really only a courtesy for broken drivers that still make use of it. I don't object to adding it here, though I wish the entire interface was deprecated, but it's only a minimal amount of insurance as a VF might get assigned immediately following your added test or might not participate in the assigned device flagging at all. I believe the better way to handle this is with proper host drivers for assigned devices that manage the driver .remove callback properly while devices are in use. The only reason to handle assigned devices specially in this case is when they don't have proper host drivers managing them, which is a problem that we've fixed. Thanks, Alex > Signed-off-by: Keith Busch <keith.busch at intel.com> > --- > drivers/pci/pci-sysfs.c | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/drivers/pci/pci-sysfs.c b/drivers/pci/pci-sysfs.c > index 342b691..5011fa9 100644 > --- a/drivers/pci/pci-sysfs.c > +++ b/drivers/pci/pci-sysfs.c > @@ -487,6 +487,11 @@ static ssize_t sriov_numvfs_store(struct device *dev, > > if (num_vfs == 0) { > /* disable VFs */ > + if (pci_vfs_assigned(pdev)) { > + dev_warn(&pdev->dev, > + "Cannot disable SR-IOV VFs while assigned\n"); > + return -EPERM; > + } > ret = pdev->driver->sriov_configure(pdev, 0); > if (ret < 0) > return ret;
next prev parent reply other threads:[~2016-05-17 22:08 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-05-17 21:39 [PATCH 1/2] pci: Error disabling SR-IOV if in VFs assigned Keith Busch 2016-05-17 21:39 ` Keith Busch 2016-05-17 21:39 ` [PATCH 2/2] nvme/pci: Enable SR-IOV capabilities Keith Busch 2016-05-17 21:39 ` Keith Busch 2016-05-23 10:52 ` Christoph Hellwig 2016-05-23 10:52 ` Christoph Hellwig 2016-05-23 17:06 ` Bjorn Helgaas 2016-05-23 17:06 ` Bjorn Helgaas 2016-05-23 17:09 ` Christoph Hellwig 2016-05-23 17:09 ` Christoph Hellwig 2016-05-23 17:21 ` Keith Busch 2016-05-23 17:21 ` Keith Busch 2016-05-23 21:51 ` Bjorn Helgaas 2016-05-23 21:51 ` Bjorn Helgaas 2016-05-17 22:08 ` Alex Williamson [this message] 2016-05-17 22:08 ` [PATCH 1/2] pci: Error disabling SR-IOV if in VFs assigned Alex Williamson 2016-05-23 10:55 ` Christoph Hellwig 2016-05-23 10:55 ` Christoph Hellwig 2016-05-23 15:07 ` Alex Williamson 2016-05-23 15:07 ` Alex Williamson 2016-05-23 15:10 ` Christoph Hellwig 2016-05-23 15:10 ` Christoph Hellwig 2016-06-13 21:14 ` Bjorn Helgaas 2016-06-13 21:14 ` Bjorn Helgaas 2016-06-13 21:28 ` Keith Busch 2016-06-13 21:28 ` Keith Busch 2016-06-13 21:57 ` Keith Busch 2016-06-13 21:57 ` Keith Busch 2016-06-13 22:26 ` Bjorn Helgaas 2016-06-13 22:26 ` Bjorn Helgaas 2016-06-13 22:35 ` Keith Busch 2016-06-13 22:35 ` Keith Busch 2016-06-15 10:26 ` Christoph Hellwig 2016-06-15 10:26 ` Christoph Hellwig 2016-06-15 15:38 ` Bjorn Helgaas 2016-06-15 15:38 ` Bjorn Helgaas
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=20160517160832.51fc0304@t450s.home \ --to=alex.williamson@redhat.com \ --cc=axboe@fb.com \ --cc=bhelgaas@google.com \ --cc=hch@infradead.org \ --cc=keith.busch@intel.com \ --cc=linux-nvme@lists.infradead.org \ --cc=linux-pci@vger.kernel.org \ /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: linkBe 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.