From: "Tiwei Bie" <tiwei.btw@antgroup.com>
To: richard@nod.at, anton.ivanov@cambridgegreys.com,
johannes@sipsolutions.net
Cc: <linux-um@lists.infradead.org>, "Tiwei Bie" <tiwei.btw@antgroup.com>
Subject: [RFC PATCH 0/3] um: Add VFIO-based PCI passthrough support
Date: Mon, 10 Mar 2025 15:40:54 +0800 [thread overview]
Message-ID: <20250310074057.3977758-1-tiwei.btw@antgroup.com> (raw)
This patchset adds a new virt-pci driver to UML that allows users to
pass through host PCI devices to UML via VFIO. Currently, only MSI-X
capable devices are supported, and drivers are assumed to use MSI-X.
This driver has been tested with virtio-net-pci, virtio-blk-pci and
nvme in a QEMU virtual machine with virtual IOMMU enabled. Regression
testing for virtio_pcidev has been limited as I haven't been able to
find a virtio_pcidev vhost-user backend implementation.
This patchset is based on the following patchset:
https://lore.kernel.org/all/20250306150747.2926434-1-tiwei.btw@antgroup.com/
Tiwei Bie (3):
um: Rewrite the sigio workaround based on epoll and tgkill
um: virt-pci: Refactor virtio_pcidev into its own module
um: Add VFIO-based virtual PCI driver
arch/um/drivers/Kconfig | 20 +-
arch/um/drivers/Makefile | 5 +-
arch/um/drivers/random.c | 2 +-
arch/um/drivers/rtc_user.c | 2 +-
arch/um/drivers/vfio_kern.c | 648 +++++++++++++++++++++++++++++
arch/um/drivers/vfio_user.c | 323 +++++++++++++++
arch/um/drivers/vfio_user.h | 44 ++
arch/um/drivers/virt-pci.c | 699 ++++++--------------------------
arch/um/drivers/virt-pci.h | 41 ++
arch/um/drivers/virtio_pcidev.c | 628 ++++++++++++++++++++++++++++
arch/um/include/shared/os.h | 2 +-
arch/um/include/shared/sigio.h | 1 -
arch/um/kernel/sigio.c | 26 --
arch/um/os-Linux/sigio.c | 330 ++-------------
14 files changed, 1866 insertions(+), 905 deletions(-)
create mode 100644 arch/um/drivers/vfio_kern.c
create mode 100644 arch/um/drivers/vfio_user.c
create mode 100644 arch/um/drivers/vfio_user.h
create mode 100644 arch/um/drivers/virt-pci.h
create mode 100644 arch/um/drivers/virtio_pcidev.c
--
2.34.1
next reply other threads:[~2025-03-10 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 7:40 Tiwei Bie [this message]
2025-03-10 7:40 ` [RFC PATCH 1/3] um: Rewrite the sigio workaround based on epoll and tgkill Tiwei Bie
2025-03-10 7:40 ` [RFC PATCH 2/3] um: virt-pci: Refactor virtio_pcidev into its own module Tiwei Bie
2025-03-10 7:40 ` [RFC PATCH 3/3] um: Add VFIO-based virtual PCI driver Tiwei Bie
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=20250310074057.3977758-1-tiwei.btw@antgroup.com \
--to=tiwei.btw@antgroup.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).