[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v4 00/12] hw/iommufd: IOMMUFD Dirty Tracking
From: |
Joao Martins |
Subject: |
Re: [PATCH v4 00/12] hw/iommufd: IOMMUFD Dirty Tracking |
Date: |
Tue, 16 Jul 2024 10:22:26 +0100 |
On 16/07/2024 09:20, Duan, Zhenzhong wrote:
>
>
>> -----Original Message-----
>> From: Joao Martins <joao.m.martins@oracle.com>
>> Subject: [PATCH v4 00/12] hw/iommufd: IOMMUFD Dirty Tracking
>>
>> This small series adds support for IOMMU dirty tracking support via the
>> IOMMUFD backend. The hardware capability is available on most recent x86
>> hardware. The series is divided organized as follows:
>>
>> * Patch 1-2: Fixes a regression into mdev support with IOMMUFD. This
>> one is independent of the series but happened to cross it
>> while testing mdev with this series
>
> I guess VFIO ap/ccw may need fixes too.
> Will you help on that or I can take it if you want to focus on dirty tracking.
> The fix may be trivial, just assign VFIODevice->mdev = true.
>
If you have something in mind already by all means go ahead.
But from the code are we sure these are mdev bus devices? Certainly are grepping
with 'mdev' but unclear if that's abbreviation for 'My Device' or actually bus
mdev/mediated-device?
- Re: [PATCH v4 11/12] vfio/migration: Don't block migration device dirty tracking is unsupported, (continued)
Re: [PATCH v4 11/12] vfio/migration: Don't block migration device dirty tracking is unsupported, Eric Auger, 2024/07/17
[PATCH v4 06/12] vfio/{iommufd,container}: Remove caps::aw_bits, Joao Martins, 2024/07/12
RE: [PATCH v4 00/12] hw/iommufd: IOMMUFD Dirty Tracking, Duan, Zhenzhong, 2024/07/16
- Re: [PATCH v4 00/12] hw/iommufd: IOMMUFD Dirty Tracking,
Joao Martins <=