[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v4 12/14] vfio/migration: Block migration with vIOMMU
|
From: |
Joao Martins |
|
Subject: |
Re: [PATCH v4 12/14] vfio/migration: Block migration with vIOMMU |
|
Date: |
Tue, 7 Mar 2023 10:31:15 +0000 |
On 07/03/2023 10:22, Cédric Le Goater wrote:
> On 3/7/23 03:02, Joao Martins wrote:
>> Migrating with vIOMMU will require either tracking maximum
>> IOMMU supported address space (e.g. 39/48 address width on Intel)
>> or range-track current mappings and dirty track the new ones
>> post starting dirty tracking. This will be done as a separate
>> series, so add a live migration blocker until that is fixed.
>>
>> Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
>
> Reviewed-by: Cédric Le Goater <clg@redhat.com>
>
Thanks!
- Re: [PATCH v4 08/14] vfio/common: Record DMA mapped IOVA ranges, (continued)
[PATCH v4 09/14] vfio/common: Add device dirty page tracking start/stop, Joao Martins, 2023/03/06
[PATCH v4 10/14] vfio/common: Extract code from vfio_get_dirty_bitmap() to new function, Joao Martins, 2023/03/06
[PATCH v4 11/14] vfio/common: Add device dirty page bitmap sync, Joao Martins, 2023/03/06
[PATCH v4 12/14] vfio/migration: Block migration with vIOMMU, Joao Martins, 2023/03/06
[PATCH v4 13/14] vfio/migration: Query device dirty page tracking support, Joao Martins, 2023/03/06
[PATCH v4 14/14] docs/devel: Document VFIO device dirty page tracking, Joao Martins, 2023/03/06