[PATCH v2 0/8] vfio: relax the vIOMMU check

Zhenzhong Duan posted 8 patches 4 weeks ago
Failed in applying to current master (apply log)
There is a newer version of this series
include/hw/vfio/vfio-container.h |  8 ++++--
include/hw/vfio/vfio-device.h    | 10 +++++++
include/system/iommufd.h         |  2 +-
backends/iommufd.c               |  5 ++--
hw/i386/intel_iommu.c            | 42 +++++++++++++++++++++++++++++
hw/vfio-user/container.c         |  5 ++--
hw/vfio/container-legacy.c       | 15 ++++++-----
hw/vfio/container.c              | 20 +++++++-------
hw/vfio/device.c                 |  6 +++++
hw/vfio/iommufd.c                | 46 ++++++++++++++++++++++++++++----
hw/vfio/listener.c               |  6 ++---
hw/vfio/migration.c              | 43 ++++++++++++++++++++++++++---
backends/trace-events            |  2 +-
hw/vfio/trace-events             |  2 +-
14 files changed, 176 insertions(+), 36 deletions(-)
[PATCH v2 0/8] vfio: relax the vIOMMU check
Posted by Zhenzhong Duan 4 weeks ago
Hi,

This series relax the vIOMMU check and allows live migration with vIOMMU
without VFs using device dirty tracking. It's rewritten based on first 4
patches of [1] from Joao.

Currently what block us is the lack of dirty bitmap query with iommufd
before unmap. By adding that query and handle some corner case we can
relax the check.

Based on vfio-next branch:

patch1-2: add dirty bitmap query with iommufd
patch3:   a renaming cleanup
patch4-5: unmap_bitmap optimization
patch6:   fix large iommu notification triggered unmap_bitmap failure
patch7:   add a blocker if VM memory is really quite large for unmap_bitmap
patch8:   relax vIOMMU check


We tested VM live migration (running QAT workload in VM) with QAT
device passthrough, below matrix configs:
1.Scalable mode vIOMMU + IOMMUFD cdev mode
2.Scalable mode vIOMMU + legacy VFIO mode
3.legacy mode vIOMMU + IOMMUFD cdev mode
4.legacy mode vIOMMU + legacy VFIO mode

[1] https://github.com/jpemartins/qemu/commits/vfio-migration-viommu/

Thanks
Zhenzhong

Changelog:
v2:
- add backend_flag parameter to pass DIRTY_BITMAP_NO_CLEAR (Joao, Cedric)
- add a cleanup patch to rename vfio_dma_unmap_bitmap (Cedric)
- add blocker if unmap_bitmap limit check fail (Liuyi)


Joao Martins (1):
  vfio: Add a backend_flag parameter to
    vfio_contianer_query_dirty_bitmap()

Zhenzhong Duan (7):
  vfio/iommufd: Add framework code to support getting dirty bitmap
    before unmap
  vfio/iommufd: Query dirty bitmap before DMA unmap
  vfio/container-legacy: rename vfio_dma_unmap_bitmap() to
    vfio_legacy_dma_unmap_get_dirty_bitmap()
  vfio/iommufd: Add IOMMU_HWPT_GET_DIRTY_BITMAP_NO_CLEAR flag support
  intel_iommu: Fix unmap_bitmap failure with legacy VFIO backend
  vfio/migration: Add migration blocker if VM memory is too large to
    cause unmap_bitmap failure
  vfio/migration: Allow live migration with vIOMMU without VFs using
    device dirty tracking

 include/hw/vfio/vfio-container.h |  8 ++++--
 include/hw/vfio/vfio-device.h    | 10 +++++++
 include/system/iommufd.h         |  2 +-
 backends/iommufd.c               |  5 ++--
 hw/i386/intel_iommu.c            | 42 +++++++++++++++++++++++++++++
 hw/vfio-user/container.c         |  5 ++--
 hw/vfio/container-legacy.c       | 15 ++++++-----
 hw/vfio/container.c              | 20 +++++++-------
 hw/vfio/device.c                 |  6 +++++
 hw/vfio/iommufd.c                | 46 ++++++++++++++++++++++++++++----
 hw/vfio/listener.c               |  6 ++---
 hw/vfio/migration.c              | 43 ++++++++++++++++++++++++++---
 backends/trace-events            |  2 +-
 hw/vfio/trace-events             |  2 +-
 14 files changed, 176 insertions(+), 36 deletions(-)

-- 
2.47.1