From: Alexander Duyck <alexander.duyck@gmail.com> To: bhelgaas@google.com, alexander.h.duyck@intel.com, linux-pci@vger.kernel.org Cc: virtio-dev@lists.oasis-open.org, kvm@vger.kernel.org, netdev@vger.kernel.org, dan.daly@intel.com, linux-kernel@vger.kernel.org, mheyne@amazon.de, liang-min.wang@intel.com, mark.d.rustad@intel.com, dwmw2@infradead.org, dwmw@amazon.co.uk Subject: [PATCH 0/3] pci-iov: Add support for unmanaged SR-IOV Date: Fri, 02 Mar 2018 15:44:05 -0800 [thread overview] Message-ID: <20180302234218.3337.16486.stgit@localhost.localdomain> (raw) This series is meant to add support for SR-IOV on devices when the VFs are not managed by the kernel. Examples of recent patches attempting to do this include: virto - https://patchwork.kernel.org/patch/10241225/ pci-stub - https://patchwork.kernel.org/patch/10109935/ vfio - https://patchwork.kernel.org/patch/10103353/ uio - https://patchwork.kernel.org/patch/9974031/ Since this is quickly blowing up into a multi-driver problem it is probably best to implement this solution as generically as possible. This series is an attempt to do that. What we do with this patch set is provide a generic framework to enable SR-IOV in the case that the PF driver doesn't support managing the VFs itself. I based my patch set originally on the patch by Mark Rustad but there isn't much left after going through and cleaning out the bits that were no longer needed, and after incorporating the feedback from David Miller. At this point the only items to be fully reused was his patch description which is now present in patch 3 of the set. I have included the authors of the original 4 patches above in the Cc here. My hope is to get feedback and/or review on if this works for their use cases. My hope is that for now the pci-stub and uio driver approaches can be addressed using the current patch that enables vfio-pci support. The only limitation is that it is also setting the taint flag until we have a better solution. v2: Reduced scope back to just virtio_pci and vfio-pci Broke into 3 patch set from single patch Changed autoprobe behavior to always set when num_vfs is set non-zero Cc: Mark Rustad <mark.d.rustad@intel.com> Cc: Maximilian Heyne <mheyne@amazon.de> Cc: Liang-Min Wang <liang-min.wang@intel.com> Cc: David Woodhouse <dwmw@amazon.co.uk> --- Alexander Duyck (3): pci-iov: Add support for unmanaged SR-IOV vfio: Add support for unmanaged or userspace managed SR-IOV virtio_pci: Add support for unmanaged SR-IOV on virtio_pci devices Documentation/ABI/testing/sysfs-bus-pci | 17 +++++++++ drivers/pci/iov.c | 37 ++++++++++++++++++++ drivers/pci/pci-driver.c | 2 + drivers/pci/pci-sysfs.c | 29 ++++++++++++++++ drivers/pci/pci.h | 4 ++ drivers/vfio/pci/vfio_pci.c | 57 +++++++++++++++++++++++++++++++ drivers/virtio/virtio_pci_common.c | 4 ++ include/linux/pci.h | 1 + 8 files changed, 149 insertions(+), 2 deletions(-) --
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Duyck <alexander.duyck@gmail.com> To: bhelgaas@google.com, alexander.h.duyck@intel.com, linux-pci@vger.kernel.org Cc: virtio-dev@lists.oasis-open.org, kvm@vger.kernel.org, netdev@vger.kernel.org, dan.daly@intel.com, linux-kernel@vger.kernel.org, mheyne@amazon.de, liang-min.wang@intel.com, mark.d.rustad@intel.com, dwmw2@infradead.org, dwmw@amazon.co.uk Subject: [virtio-dev] [PATCH 0/3] pci-iov: Add support for unmanaged SR-IOV Date: Fri, 02 Mar 2018 15:44:05 -0800 [thread overview] Message-ID: <20180302234218.3337.16486.stgit@localhost.localdomain> (raw) This series is meant to add support for SR-IOV on devices when the VFs are not managed by the kernel. Examples of recent patches attempting to do this include: virto - https://patchwork.kernel.org/patch/10241225/ pci-stub - https://patchwork.kernel.org/patch/10109935/ vfio - https://patchwork.kernel.org/patch/10103353/ uio - https://patchwork.kernel.org/patch/9974031/ Since this is quickly blowing up into a multi-driver problem it is probably best to implement this solution as generically as possible. This series is an attempt to do that. What we do with this patch set is provide a generic framework to enable SR-IOV in the case that the PF driver doesn't support managing the VFs itself. I based my patch set originally on the patch by Mark Rustad but there isn't much left after going through and cleaning out the bits that were no longer needed, and after incorporating the feedback from David Miller. At this point the only items to be fully reused was his patch description which is now present in patch 3 of the set. I have included the authors of the original 4 patches above in the Cc here. My hope is to get feedback and/or review on if this works for their use cases. My hope is that for now the pci-stub and uio driver approaches can be addressed using the current patch that enables vfio-pci support. The only limitation is that it is also setting the taint flag until we have a better solution. v2: Reduced scope back to just virtio_pci and vfio-pci Broke into 3 patch set from single patch Changed autoprobe behavior to always set when num_vfs is set non-zero Cc: Mark Rustad <mark.d.rustad@intel.com> Cc: Maximilian Heyne <mheyne@amazon.de> Cc: Liang-Min Wang <liang-min.wang@intel.com> Cc: David Woodhouse <dwmw@amazon.co.uk> --- Alexander Duyck (3): pci-iov: Add support for unmanaged SR-IOV vfio: Add support for unmanaged or userspace managed SR-IOV virtio_pci: Add support for unmanaged SR-IOV on virtio_pci devices Documentation/ABI/testing/sysfs-bus-pci | 17 +++++++++ drivers/pci/iov.c | 37 ++++++++++++++++++++ drivers/pci/pci-driver.c | 2 + drivers/pci/pci-sysfs.c | 29 ++++++++++++++++ drivers/pci/pci.h | 4 ++ drivers/vfio/pci/vfio_pci.c | 57 +++++++++++++++++++++++++++++++ drivers/virtio/virtio_pci_common.c | 4 ++ include/linux/pci.h | 1 + 8 files changed, 149 insertions(+), 2 deletions(-) -- --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next reply other threads:[~2018-03-02 23:44 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-02 23:44 Alexander Duyck [this message] 2018-03-02 23:44 ` [virtio-dev] [PATCH 0/3] pci-iov: Add support for unmanaged SR-IOV Alexander Duyck 2018-03-02 23:44 ` [PATCH 1/3] " Alexander Duyck 2018-03-02 23:44 ` [virtio-dev] " Alexander Duyck 2018-03-02 23:59 ` Alex Williamson 2018-03-03 0:20 ` Alexander Duyck 2018-03-03 0:20 ` [virtio-dev] " Alexander Duyck 2018-03-02 23:44 ` [PATCH 2/3] vfio: Add support for unmanaged or userspace managed SR-IOV Alexander Duyck 2018-03-02 23:44 ` [virtio-dev] " Alexander Duyck 2018-03-06 4:49 ` kbuild test robot 2018-03-02 23:45 ` [PATCH 3/3] virtio_pci: Add support for unmanaged SR-IOV on virtio_pci devices Alexander Duyck 2018-03-02 23:45 ` [virtio-dev] " Alexander Duyck
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=20180302234218.3337.16486.stgit@localhost.localdomain \ --to=alexander.duyck@gmail.com \ --cc=alexander.h.duyck@intel.com \ --cc=bhelgaas@google.com \ --cc=dan.daly@intel.com \ --cc=dwmw2@infradead.org \ --cc=dwmw@amazon.co.uk \ --cc=kvm@vger.kernel.org \ --cc=liang-min.wang@intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=mark.d.rustad@intel.com \ --cc=mheyne@amazon.de \ --cc=netdev@vger.kernel.org \ --cc=virtio-dev@lists.oasis-open.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.