Re: [PATCH v3 0/8] vfio: Split the container code into a clean layer and dedicated file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 22 Sep 2022 16:20:18 -0300
Jason Gunthorpe <jgg@xxxxxxxxxx> wrote:

> 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
> 
> v3:
>  - Rebase over the vfio struct device series

Applied to vfio next branch for v6.1.  Thanks,

Alex




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux