From: Bjorn Helgaas <helgaas@kernel.org>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: alex.williamson@redhat.com,
Liang-Min Wang <liang-min.wang@intel.com>,
kvm@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, bhelgaas@google.com,
alexander.h.duyck@intel.com
Subject: Re: [PATCH v2] Enable SR-IOV instantiation through /sys file
Date: Wed, 10 Jan 2018 17:30:29 -0600 [thread overview]
Message-ID: <20180110233029.GH241460@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <20171208214758.6959-1-jeffrey.t.kirsher@intel.com>
On Fri, Dec 08, 2017 at 01:47:58PM -0800, Jeff Kirsher wrote:
> From: Liang-Min Wang <liang-min.wang@intel.com>
>
> When a SR-IOV capable device is bound with vfio-pci, the
> device loses capability of creating SR-IOV instances through /sy/bus/
> pci/devices/.../sriov_numvfs. This patch re-activates this capability
> for a PCIe device that is SR-IOV capable and is bound with vfio-pci.ko.
> This patch also disables drivers_autoprobe attribute of SR-IOV devices
> created from vfio-pci bound device by default, so user-space PF device
> can coordinate the bring-up of SR-IOV devices
Seems like the discussion here petered out without a real conclusion,
so I'm going to drop this one for now and wait for another try.
> Signed-off-by: Liang-Min Wang <liang-min.wang@intel.com>
> ---
> drivers/pci/pci-driver.c | 12 ++++++++++++
> drivers/vfio/pci/vfio_pci.c | 22 ++++++++++++++++++++++
> include/linux/pci.h | 1 +
> 3 files changed, 35 insertions(+)
>
> diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
> index 7f47bb7..19522fe 100644
> --- a/drivers/pci/pci-driver.c
> +++ b/drivers/pci/pci-driver.c
> @@ -1467,6 +1467,18 @@ void pci_dev_put(struct pci_dev *dev)
> }
> EXPORT_SYMBOL(pci_dev_put);
>
> +/**
> + * pci_dev_sriov_autoprobe_set - set device sriov driver autoprobe
> + * @dev: device with which sriov autoprobe will be set
> + *
> + */
> +void pci_dev_sriov_autoprobe_set(struct pci_dev *dev, bool autoprobe)
> +{
> + if (dev && dev->sriov)
> + dev->sriov->drivers_autoprobe = autoprobe;
> +}
> +EXPORT_SYMBOL(pci_dev_sriov_autoprobe_set);
> +
> static int pci_uevent(struct device *dev, struct kobj_uevent_env *env)
> {
> struct pci_dev *pdev;
> diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_pci.c
> index f041b1a..004836c 100644
> --- a/drivers/vfio/pci/vfio_pci.c
> +++ b/drivers/vfio/pci/vfio_pci.c
> @@ -1213,6 +1213,8 @@ static int vfio_pci_probe(struct pci_dev *pdev, const struct pci_device_id *id)
> return -ENOMEM;
> }
>
> + /* disable sriov automatic driver attachment */
> + pci_dev_sriov_autoprobe_set(pdev, false);
> vdev->pdev = pdev;
> vdev->irq_type = VFIO_PCI_NUM_IRQS;
> mutex_init(&vdev->igate);
> @@ -1256,6 +1258,7 @@ static void vfio_pci_remove(struct pci_dev *pdev)
> if (!vdev)
> return;
>
> + pci_disable_sriov(pdev);
> vfio_iommu_group_put(pdev->dev.iommu_group, &pdev->dev);
> kfree(vdev->region);
> kfree(vdev);
> @@ -1303,12 +1306,31 @@ static pci_ers_result_t vfio_pci_aer_err_detected(struct pci_dev *pdev,
> .error_detected = vfio_pci_aer_err_detected,
> };
>
> +static int vfio_sriov_configure(struct pci_dev *pdev, int num_vfs)
> +{
> + int status;
> +
> + if (!num_vfs) {
> + pci_disable_sriov(pdev);
> + return 0;
> + }
> +
> + status = pci_enable_sriov(pdev, num_vfs);
> + if (!status) {
> + pr_crit("Created %d SR-IOV from a user-space driver based upon vfio-pci\n", num_vfs);
> + add_taint(TAINT_USER, LOCKDEP_STILL_OK);
> + }
> +
> + return status;
> +}
> +
> static struct pci_driver vfio_pci_driver = {
> .name = "vfio-pci",
> .id_table = NULL, /* only dynamic ids */
> .probe = vfio_pci_probe,
> .remove = vfio_pci_remove,
> .err_handler = &vfio_err_handlers,
> + .sriov_configure = vfio_sriov_configure,
> };
>
> struct vfio_devices {
> diff --git a/include/linux/pci.h b/include/linux/pci.h
> index 0403894..e04b69d 100644
> --- a/include/linux/pci.h
> +++ b/include/linux/pci.h
> @@ -921,6 +921,7 @@ struct resource *pci_find_parent_resource(const struct pci_dev *dev,
> struct pci_dev *pci_dev_get(struct pci_dev *dev);
> void pci_dev_put(struct pci_dev *dev);
> void pci_remove_bus(struct pci_bus *b);
> +void pci_dev_sriov_autoprobe_set(struct pci_dev *dev, bool autoprobe);
> void pci_stop_and_remove_bus_device(struct pci_dev *dev);
> void pci_stop_and_remove_bus_device_locked(struct pci_dev *dev);
> void pci_stop_root_bus(struct pci_bus *bus);
> --
> 1.9.1
>
prev parent reply other threads:[~2018-01-10 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 21:47 [PATCH v2] Enable SR-IOV instantiation through /sys file Jeff Kirsher
2017-12-08 22:58 ` Alex Williamson
2017-12-08 23:19 ` Alexander Duyck
2017-12-08 23:34 ` Alex Williamson
2017-12-11 14:22 ` Wang, Liang-min
2017-12-11 16:06 ` Duyck, Alexander H
2017-12-11 18:13 ` Alex Williamson
2017-12-11 18:58 ` Wang, Liang-min
2018-01-10 23:30 ` Bjorn Helgaas [this message]
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=20180110233029.GH241460@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=alexander.h.duyck@intel.com \
--cc=bhelgaas@google.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kvm@vger.kernel.org \
--cc=liang-min.wang@intel.com \
--cc=linux-kernel@vger.kernel.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).