RE: [PATCH v3 04/11] vfio: Move storage of allow_unsafe_interrupts to vfio_main.c

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

 



> From: Jason Gunthorpe <jgg@xxxxxxxxxx>
> Sent: Thursday, November 24, 2022 12:38 AM
> 
> On Wed, Nov 23, 2022 at 01:21:30AM +0000, Tian, Kevin wrote:
> 
> > I'm not sure the value of entering this mixed world. I could envision
> > dpdk starting to add cdev/iommufd support when it wants to use
> > new features (pasid, iopf, etc.) which are available only via iommufd
> > native api. Before that point it just stays with full vfio legacy.
> 
> I think the value is for the distro that would benefit from getting
> apps validated and running on iommufd with the least effort invested.
> 
> So I'd like to see all the vfio apps we can convert to the new device
> interface and iommufd just to be converted, even if they don't make
> use of new features.
> 

We'll certainly change Qemu but then it will support either legacy vfio
or new iommufd native. No intermediate step like above.

what'd be the practice to push other vfio apps to do such conversion?




[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