netdev - [pci PATCH v3 0/3] Add support for unmanaged SR-IOV

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 06 Mar 2018 11:29:08 -0800
From:   Alexander Duyck <alexander.duyck@...il.com>
To:     bhelgaas@...gle.com, alexander.h.duyck@...el.com,
        linux-pci@...r.kernel.org
Cc:     virtio-dev@...ts.oasis-open.org, kvm@...r.kernel.org,
        netdev@...r.kernel.org, dan.daly@...el.com,
        linux-kernel@...r.kernel.org, mheyne@...zon.de,
        liang-min.wang@...el.com, mark.d.rustad@...el.com,
        dwmw2@...radead.org, dwmw@...zon.co.uk
Subject: [pci PATCH v3 0/3] Add support for unmanaged SR-IOV

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
v3: Updated Documentation to clarify when sriov_unmanaged_autoprobe is used
    Wrapped vfio_pci_sriov_configure to fix build errors w/o SR-IOV in kernel

Cc: Mark Rustad <mark.d.rustad@...el.com>
Cc: Maximilian Heyne <mheyne@...zon.de>
Cc: Liang-Min Wang <liang-min.wang@...el.com>
Cc: David Woodhouse <dwmw@...zon.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 |   24 +++++++++++++
 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             |   59 +++++++++++++++++++++++++++++++
 drivers/virtio/virtio_pci_common.c      |    4 ++
 include/linux/pci.h                     |    1 +
 8 files changed, 158 insertions(+), 2 deletions(-)

--