[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v10 03/12] vfio/migration: Allow migration without VFIO IOMMU
|
From: |
Jason Gunthorpe |
|
Subject: |
Re: [PATCH v10 03/12] vfio/migration: Allow migration without VFIO IOMMU dirty tracking support |
|
Date: |
Wed, 15 Feb 2023 16:38:10 -0400 |
On Wed, Feb 15, 2023 at 01:14:35PM -0700, Alex Williamson wrote:
> We'll need to consider whether we want to keep "dumb" dirty tracking,
> or even any form of dirty tracking in the type1 uAPI, under an
> experimental opt-in. Thanks,
I was expecting we'd delete the kernel code for type 1 dirty tracking
once the v2 parts are merged to qemu since we don't and won't have any
kernel implementation of it..
The big point of this to allow qmeu to continue on with a future
kernel that no longer reports it supports this.
Jason
[PATCH v10 04/12] migration/qemu-file: Add qemu_file_get_to_fd(), Avihai Horon, 2023/02/09
[PATCH v10 05/12] vfio/common: Change vfio_devices_all_running_and_saving() logic to equivalent one, Avihai Horon, 2023/02/09
[PATCH v10 06/12] vfio/migration: Block multiple devices migration, Avihai Horon, 2023/02/09
[PATCH v10 08/12] vfio/migration: Rename functions/structs related to v1 protocol, Avihai Horon, 2023/02/09
[PATCH v10 07/12] vfio/migration: Move migration v1 logic to vfio_migration_init(), Avihai Horon, 2023/02/09