From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
Kevin Tian <kevin.tian@intel.com>,
kvm@vger.kernel.org
Subject: [PATCH 0/8] vfio: Split the container code into a clean layer and dedicated file
Date: Tue, 30 Aug 2022 22:01:54 -0300 [thread overview]
Message-ID: <0-v1-a805b607f1fb+17b-vfio_container_split_jgg@nvidia.com> (raw)
This creates an isolated layer around the container FD code and everything
under it, including the VFIO iommu drivers. All this code is placed into
container.c, along with the "struct vfio_container" to compartmentalize
it.
Future patches will provide an iommufd based layer that gives the same API
as the container layer and choose which layer to go to based on how
userspace operates.
The patches continue to split up existing functions and finally the last
patch just moves every function that is a "container" function to the new
file and creates the global symbols to link them together.
Cross-file container functions are prefixed with vfio_container_* for
clarity.
The last patch can be defered and queued during the merge window to manage
conflicts. The earlier patches should be fine immediately conflicts wise.
This is the last big series I have to enable basic iommufd functionality.
As part of the iommufd series the entire container.c becomes conditionally
compiled:
https://github.com/jgunthorpe/linux/commits/vfio_iommufd
This applies on top of the prior two series:
Break up ioctl dispatch functions to one function per ioctl
Remove private items from linux/vfio_pci_core.h
Jason Gunthorpe (8):
vfio: Add header guards and includes to drivers/vfio/vfio.h
vfio: Rename __vfio_group_unset_container()
vfio: Split the container logic into vfio_container_attach_group()
vfio: Remove #ifdefs around CONFIG_VFIO_NOIOMMU
vfio: Split out container code from the init/cleanup functions
vfio: Rename vfio_ioctl_check_extension()
vfio: Split the register_device ops call into functions
vfio: Move container code into drivers/vfio/container.c
drivers/vfio/Makefile | 1 +
drivers/vfio/container.c | 680 +++++++++++++++++++++++++++++++++++++
drivers/vfio/vfio.h | 57 ++++
drivers/vfio/vfio_main.c | 709 ++-------------------------------------
4 files changed, 766 insertions(+), 681 deletions(-)
create mode 100644 drivers/vfio/container.c
base-commit: 456bc2e671af7852f8a028c8069906b6b6fa1ff9
--
2.37.2
next reply other threads:[~2022-08-31 1:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 1:01 Jason Gunthorpe [this message]
2022-08-31 1:01 ` [PATCH 1/8] vfio: Add header guards and includes to drivers/vfio/vfio.h Jason Gunthorpe
2022-08-31 8:42 ` Tian, Kevin
2022-08-31 15:36 ` Jason Gunthorpe
2022-08-31 18:02 ` Alex Williamson
2022-08-31 18:24 ` Jason Gunthorpe
2022-09-01 2:17 ` Tian, Kevin
2022-08-31 1:01 ` [PATCH 2/8] vfio: Rename __vfio_group_unset_container() Jason Gunthorpe
2022-08-31 8:46 ` Tian, Kevin
2022-09-02 0:28 ` Jason Gunthorpe
2022-09-02 3:51 ` Tian, Kevin
2022-09-02 14:39 ` Alex Williamson
2022-09-02 16:24 ` Jason Gunthorpe
2022-09-06 3:35 ` Tian, Kevin
2022-09-06 19:38 ` Alex Williamson
2022-09-06 23:06 ` Jason Gunthorpe
2022-08-31 1:01 ` [PATCH 3/8] vfio: Split the container logic into vfio_container_attach_group() Jason Gunthorpe
2022-08-31 8:47 ` Tian, Kevin
2022-09-02 0:42 ` Jason Gunthorpe
2022-08-31 1:01 ` [PATCH 4/8] vfio: Remove #ifdefs around CONFIG_VFIO_NOIOMMU Jason Gunthorpe
2022-08-31 8:48 ` Tian, Kevin
2022-08-31 15:28 ` Jason Gunthorpe
2022-09-01 2:18 ` Tian, Kevin
2022-08-31 1:01 ` [PATCH 5/8] vfio: Split out container code from the init/cleanup functions Jason Gunthorpe
2022-08-31 8:49 ` Tian, Kevin
2022-08-31 1:02 ` [PATCH 6/8] vfio: Rename vfio_ioctl_check_extension() Jason Gunthorpe
2022-08-31 8:50 ` Tian, Kevin
2022-08-31 1:02 ` [PATCH 7/8] vfio: Split the register_device ops call into functions Jason Gunthorpe
2022-09-02 3:52 ` Tian, Kevin
2022-08-31 1:02 ` [PATCH 8/8] vfio: Move container code into drivers/vfio/container.c Jason Gunthorpe
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=0-v1-a805b607f1fb+17b-vfio_container_split_jgg@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=kevin.tian@intel.com \
--cc=kvm@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).