[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v5 00/13] hw/iommufd: IOMMUFD Dirty Tracking
From: |
Joao Martins |
Subject: |
Re: [PATCH v5 00/13] hw/iommufd: IOMMUFD Dirty Tracking |
Date: |
Fri, 19 Jul 2024 13:13:56 +0100 |
Hey Cedric,
On 19/07/2024 13:04, Joao Martins wrote:
> The unmap case is deferred until further vIOMMU support with migration
> is added[3] which will then introduce the usage of
> IOMMU_HWPT_GET_DIRTY_BITMAP_NO_CLEAR in GET_DIRTY_BITMAP ioctl in the
> dma unmap bitmap flow.
>
A couple notes with respect to this series:
- The first 2 patches I think are needed because it addresses a regression
- This paragraph is meant to state that this doesn't support vIOMMU, and so I
haven't changed in that area. I am assuming that when the vIOMMU will get resent
for 9.2 where I would address the IOMMUFD counterpart.
In case this be merged, the next Qemu stages after this series are:
1) Mixed mode of VF with IOMMUFD dirty tracking
2) vIOMMU support (with the relaxing vIOMMU patch and IOMMUFD support)
It's not listed in terms of priority, just wanted to make it obvious on the gaps
that are on my list.
- Re: [PATCH v5 09/13] vfio/iommufd: Probe and request hwpt dirty tracking capability, (continued)
[PATCH v5 03/13] backends/iommufd: Extend iommufd_backend_get_device_info() to fetch HW capabilities, Joao Martins, 2024/07/19
[PATCH v5 13/13] vfio/common: Allow disabling device dirty page tracking, Joao Martins, 2024/07/19
[PATCH v5 05/13] vfio/iommufd: Introduce auto domain creation, Joao Martins, 2024/07/19
Re: [PATCH v5 00/13] hw/iommufd: IOMMUFD Dirty Tracking,
Joao Martins <=
[PATCH v5.1 12/13] vfio/migration: Don't block migration device dirty tracking is unsupported, Joao Martins, 2024/07/19
Re: [PATCH v5 00/13] hw/iommufd: IOMMUFD Dirty Tracking, Cédric Le Goater, 2024/07/22