[ ... ]
* [v4] vfio: VFIO migration support with vIOMMU
https://lore.kernel.org/qemu-devel/20230622214845.3980-1-joao.m.mart...@oracle.com/
Refreshed the patchset on upstream and pushed on vfio-9.1 branch.
/me nods Probably deserves an item on the list too related to this subject of
vIOMMU and migration after the vIOMMU series is done:
*
https://lore.kernel.org/qemu-devel/20230908120521.50903-1-joao.m.mart...@oracle.com/
* [RFCv2] vfio/iommufd: IOMMUFD Dirty Tracking
https://lore.kernel.org/qemu-devel/20240212135643.5858-1-joao.m.mart...@oracle.com/
I plan on still submitting a follow-up targetting 9.1 likely next week with
Avihai's comments on top of the vfio-9.1 branch after I sent some dirty tracking
fixes in kernel side. Though it is mostly to progress review as I think I am
still dependent on Zhenzhong prep series for merging because of this patch:
https://lore.kernel.org/all/20240605083043.317831-8-zhenzhong.d...@intel.com/
This is ready to be pushed.
As soon as I get an ack, a nod, a smoke sign, from the PCI maintainers
regarding the new PCIIOMMUOps callbacks I will send a PR for:
https://lore.kernel.org/all/20240522170107.289532-1-...@redhat.com
https://lore.kernel.org/all/20240605083043.317831-1-zhenzhong.d...@intel.com
https://lore.kernel.org/all/20240614095402.904691-1-eric.au...@redhat.com
https://lore.kernel.org/all/20240617063409.34393-1-...@redhat.com
Thanks,
C.
