From: Steven Sistare <steven.sistare@oracle.com>
To: "Cédric Le Goater" <clg@redhat.com>, qemu-devel@nongnu.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
Yi Liu <yi.l.liu@intel.com>, Eric Auger <eric.auger@redhat.com>,
Zhenzhong Duan <zhenzhong.duan@intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Peter Xu <peterx@redhat.com>, Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH V1 06/26] vfio/container: preserve DMA mappings
Date: Mon, 3 Feb 2025 17:27:46 -0500 [thread overview]
Message-ID: <5e3fd711-2875-4eaf-a3c6-2a94f7dea6b2@oracle.com> (raw)
In-Reply-To: <d5ec094e-490d-4de4-ac3a-66b1bdae11e2@redhat.com>
On 2/3/2025 1:25 PM, Cédric Le Goater wrote:
> On 1/29/25 15:43, Steve Sistare wrote:
>> Preserve DMA mappings during cpr-transfer.
>>
>> In the container pre_save handler, suspend the use of virtual addresses
>> in DMA mappings with VFIO_DMA_UNMAP_FLAG_VADDR, because guest RAM will
>> be remapped at a different VA after exec. DMA to already-mapped pages
>> continues.
>>
>> Because the vaddr is temporarily invalid, mediated devices cannot be
>> supported, so add a blocker for them. This restriction will not apply
>> to iommufd containers when CPR is added for them in a future patch.
>>
>> In new QEMU, do not register the memory listener at device creation time.
>> Register it later, in the container post_load handler, after all vmstate
>> that may affect regions and mapping boundaries has been loaded. The
>> post_load registration will cause the listener to invoke its callback on
>> each flat section, and the calls will match the mappings remembered by the
>> kernel. Modify vfio_dma_map (which is called by the listener) to pass the
>> new VA to the kernel using VFIO_DMA_MAP_FLAG_VADDR.
>>
>> Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
>> ---
>> hw/vfio/container.c | 44 +++++++++++++++++++++++++++++++++++++++----
>> hw/vfio/cpr-legacy.c | 32 +++++++++++++++++++++++++++++++
>> include/hw/vfio/vfio-common.h | 3 +++
>> 3 files changed, 75 insertions(+), 4 deletions(-)
>>
>> diff --git a/hw/vfio/container.c b/hw/vfio/container.c
>> index 81d0ccc..2b5125e 100644
>> --- a/hw/vfio/container.c
>> +++ b/hw/vfio/container.c
>> @@ -32,6 +32,7 @@
>> #include "trace.h"
>> #include "qapi/error.h"
>> #include "migration/cpr.h"
>> +#include "migration/blocker.h"
>> #include "pci.h"
>> VFIOGroupList vfio_group_list =
>> @@ -132,6 +133,8 @@ static int vfio_legacy_dma_unmap(const VFIOContainerBase *bcontainer,
>> int ret;
>> Error *local_err = NULL;
>> + assert(!container->reused);
>> +
>> if (iotlb && vfio_devices_all_dirty_tracking_started(bcontainer)) {
>> if (!vfio_devices_all_device_dirty_tracking(bcontainer) &&
>> bcontainer->dirty_pages_supported) {
>> @@ -183,12 +186,24 @@ static int vfio_legacy_dma_map(const VFIOContainerBase *bcontainer, hwaddr iova,
>> bcontainer);
>> struct vfio_iommu_type1_dma_map map = {
>> .argsz = sizeof(map),
>> - .flags = VFIO_DMA_MAP_FLAG_READ,
>> .vaddr = (__u64)(uintptr_t)vaddr,
>> .iova = iova,
>> .size = size,
>> };
>> + /*
>> + * Set the new vaddr for any mappings registered during cpr load.
>> + * Reused is cleared thereafter.
>> + */
>> + if (container->reused) {
>> + map.flags = VFIO_DMA_MAP_FLAG_VADDR;
>> + if (ioctl(container->fd, VFIO_IOMMU_MAP_DMA, &map)) {
>> + goto fail;
>> + }
>> + return 0;
>> + }
>
> This is a bit ugly.
>
> When reaching routine vfio_attach_device(), could we detect that CPR is
> in progress and replace the 'VFIOIOMMUClass *' temporarily with a set of
> CPR specific handlers ?
Good idea, I'll try it. I wrote this code years ago before the dma
map and unmap functions were defined in an ops vector.
>> +
>> + map.flags = VFIO_DMA_MAP_FLAG_READ;
>> if (!readonly) {
>> map.flags |= VFIO_DMA_MAP_FLAG_WRITE;
>> }
>> @@ -205,7 +220,11 @@ static int vfio_legacy_dma_map(const VFIOContainerBase *bcontainer, hwaddr iova,
>> return 0;
>> }
>> - error_report("VFIO_MAP_DMA failed: %s", strerror(errno));
>> +fail:
>> + error_report("vfio_dma_map %s (iova %lu, size %ld, va %p): %s",
>> + (container->reused ? "VADDR" : ""), iova, size, vaddr,
>> + strerror(errno));
>> +
>
>
> FYI, I am currently trying to remove this error report.
>
>
>> return -errno;
>> }
>> @@ -689,8 +708,17 @@ static bool vfio_connect_container(VFIOGroup *group, AddressSpace *as,
>> group->container = container;
>> QLIST_INSERT_HEAD(&container->group_list, group, container_next);
>> - bcontainer->listener = vfio_memory_listener;
>> - memory_listener_register(&bcontainer->listener, bcontainer->space->as);
>> + /*
>> + * If reused, register the listener later, after all state that may
>> + * affect regions and mapping boundaries has been cpr load'ed. Later,
>> + * the listener will invoke its callback on each flat section and call
>> + * vfio_dma_map to supply the new vaddr, and the calls will match the
>> + * mappings remembered by the kernel.
>> + */
>> + if (!reused) {
>> + bcontainer->listener = vfio_memory_listener;
>> + memory_listener_register(&bcontainer->listener, bcontainer->space->as);
>> + }
>
> oh ! This is an important change. Please move in its own patch.
OK.
>> if (bcontainer->error) {
>> error_propagate_prepend(errp, bcontainer->error,
>> @@ -1002,6 +1030,13 @@ static bool vfio_legacy_attach_device(const char *name, VFIODevice *vbasedev,
>> return false;
>> }
>> + if (vbasedev->mdev) {
>> + error_setg(&vbasedev->cpr_mdev_blocker,
>> + "CPR does not support vfio mdev %s", vbasedev->name);
>> + migrate_add_blocker_modes(&vbasedev->cpr_mdev_blocker, &error_fatal,
>> + MIG_MODE_CPR_TRANSFER, -1);
>> + }
>
> same here, the cpr blocker for mdev devices should be in its own patch.
OK. It was a separate patch in my workspace then I squashed it :)
>> bcontainer = &group->container->bcontainer;
>> vbasedev->bcontainer = bcontainer;
>> QLIST_INSERT_HEAD(&bcontainer->device_list, vbasedev, container_next);
>> @@ -1018,6 +1053,7 @@ static void vfio_legacy_detach_device(VFIODevice *vbasedev)
>> QLIST_REMOVE(vbasedev, container_next);
>> vbasedev->bcontainer = NULL;
>> trace_vfio_detach_device(vbasedev->name, group->groupid);
>> + migrate_del_blocker(&vbasedev->cpr_mdev_blocker);
>> vfio_put_base_device(vbasedev);
>> vfio_put_group(group);
>> }
>> diff --git a/hw/vfio/cpr-legacy.c b/hw/vfio/cpr-legacy.c
>> index ce6f14e..f3a31d1 100644
>> --- a/hw/vfio/cpr-legacy.c
>> +++ b/hw/vfio/cpr-legacy.c
>> @@ -14,6 +14,21 @@
>> #include "migration/vmstate.h"
>> #include "qapi/error.h"
>> +static bool vfio_dma_unmap_vaddr_all(VFIOContainer *container, Error **errp)
>> +{
>> + struct vfio_iommu_type1_dma_unmap unmap = {
>> + .argsz = sizeof(unmap),
>> + .flags = VFIO_DMA_UNMAP_FLAG_VADDR | VFIO_DMA_UNMAP_FLAG_ALL,
>> + .iova = 0,
>> + .size = 0,
>> + };
>> + if (ioctl(container->fd, VFIO_IOMMU_UNMAP_DMA, &unmap)) {
>> + error_setg_errno(errp, errno, "vfio_dma_unmap_vaddr_all");
>> + return false;
>> + }
>> + return true;
>> +}
>> +
>> static bool vfio_cpr_supported(VFIOContainer *container, Error **errp)
>> {
>> if (!ioctl(container->fd, VFIO_CHECK_EXTENSION, VFIO_UPDATE_VADDR)) {
>> @@ -29,12 +44,27 @@ static bool vfio_cpr_supported(VFIOContainer *container, Error **errp)
>> }
>> }
>> +static int vfio_container_pre_save(void *opaque)
>> +{
>> + VFIOContainer *container = opaque;
>> + Error *err = NULL;
>> +
>> + if (!vfio_dma_unmap_vaddr_all(container, &err)) {
>> + error_report_err(err);
>
> We should modify vmstate_save_state_v() to call .pre_save() handlers
> with an Error ** parameter.
Hmm, that changes the signature of every pre_save handler. That does not
belong in this series, IMO. It would be a separate RFE for migration.
- Steve
>> + return -1;
>> + }
>> + return 0;
>> +}
>> +
>> static int vfio_container_post_load(void *opaque, int version_id)
>> {
>> VFIOContainer *container = opaque;
>> + VFIOContainerBase *bcontainer = &container->bcontainer;
>> VFIOGroup *group;
>> VFIODevice *vbasedev;
>> + bcontainer->listener = vfio_memory_listener;
>> + memory_listener_register(&bcontainer->listener, bcontainer->space->as);
>> container->reused = false;
>> QLIST_FOREACH(group, &container->group_list, container_next) {
>> @@ -49,6 +79,8 @@ static const VMStateDescription vfio_container_vmstate = {
>> .name = "vfio-container",
>> .version_id = 0,
>> .minimum_version_id = 0,
>> + .priority = MIG_PRI_LOW, /* Must happen after devices and groups */
>> + .pre_save = vfio_container_pre_save,
>> .post_load = vfio_container_post_load,
>> .needed = cpr_needed_for_reuse,
>> .fields = (VMStateField[]) {
>> diff --git a/include/hw/vfio/vfio-common.h b/include/hw/vfio/vfio-common.h
>> index a435a90..1e974e0 100644
>> --- a/include/hw/vfio/vfio-common.h
>> +++ b/include/hw/vfio/vfio-common.h
>> @@ -143,6 +143,7 @@ typedef struct VFIODevice {
>> unsigned int flags;
>> VFIOMigration *migration;
>> Error *migration_blocker;
>> + Error *cpr_mdev_blocker;
>> OnOffAuto pre_copy_dirty_page_tracking;
>> OnOffAuto device_dirty_page_tracking;
>> bool dirty_pages_supported;
>> @@ -310,6 +311,8 @@ int vfio_devices_query_dirty_bitmap(const VFIOContainerBase *bcontainer,
>> int vfio_get_dirty_bitmap(const VFIOContainerBase *bcontainer, uint64_t iova,
>> uint64_t size, ram_addr_t ram_addr, Error **errp);
>> +void vfio_listener_register(VFIOContainerBase *bcontainer);
>> +
>> /* Returns 0 on success, or a negative errno. */
>> bool vfio_device_get_name(VFIODevice *vbasedev, Error **errp);
>> void vfio_device_set_fd(VFIODevice *vbasedev, const char *str, Error **errp);
>
next prev parent reply other threads:[~2025-02-03 22:28 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 14:42 [PATCH V1 00/26] Live update: vfio and iommufd Steve Sistare
2025-01-29 14:42 ` [PATCH V1 01/26] migration: cpr helpers Steve Sistare
2025-01-29 14:42 ` [PATCH V1 02/26] migration: lower handler priority Steve Sistare
2025-02-03 16:21 ` Fabiano Rosas
2025-02-03 16:58 ` Peter Xu
2025-02-06 13:39 ` Steven Sistare
2025-01-29 14:42 ` [PATCH V1 03/26] vfio: vfio_find_ram_discard_listener Steve Sistare
2025-02-03 16:57 ` Cédric Le Goater
2025-01-29 14:43 ` [PATCH V1 04/26] vfio/container: register container for cpr Steve Sistare
2025-02-03 17:01 ` Cédric Le Goater
2025-02-03 22:26 ` Steven Sistare
2025-01-29 14:43 ` [PATCH V1 05/26] vfio/container: preserve descriptors Steve Sistare
2025-02-03 17:48 ` Cédric Le Goater
2025-02-03 22:26 ` Steven Sistare
2025-01-29 14:43 ` [PATCH V1 06/26] vfio/container: preserve DMA mappings Steve Sistare
2025-02-03 18:25 ` Cédric Le Goater
2025-02-03 22:27 ` Steven Sistare [this message]
2025-01-29 14:43 ` [PATCH V1 07/26] vfio/container: recover from unmap-all-vaddr failure Steve Sistare
2025-02-04 14:10 ` Cédric Le Goater
2025-02-04 16:13 ` Steven Sistare
2025-01-29 14:43 ` [PATCH V1 08/26] pci: skip reset during cpr Steve Sistare
2025-02-04 14:14 ` Cédric Le Goater
2025-02-04 16:13 ` Steven Sistare
2025-01-29 14:43 ` [PATCH V1 09/26] pci: export msix_is_pending Steve Sistare
2025-01-29 14:43 ` [PATCH V1 10/26] vfio-pci: refactor for cpr Steve Sistare
2025-02-04 14:39 ` Cédric Le Goater
2025-02-04 16:14 ` Steven Sistare
2025-01-29 14:43 ` [PATCH V1 11/26] vfio-pci: skip reset during cpr Steve Sistare
2025-02-04 14:56 ` Cédric Le Goater
2025-02-04 16:15 ` Steven Sistare
2025-01-29 14:43 ` [PATCH V1 12/26] vfio-pci: preserve MSI Steve Sistare
2025-02-05 16:48 ` Cédric Le Goater
2025-02-06 14:41 ` Steven Sistare
2025-01-29 14:43 ` [PATCH V1 13/26] vfio-pci: preserve INTx Steve Sistare
2025-02-05 17:13 ` Cédric Le Goater
2025-02-06 14:43 ` Steven Sistare
2025-01-29 14:43 ` [PATCH V1 14/26] migration: close kvm after cpr Steve Sistare
2025-01-29 14:43 ` [PATCH V1 15/26] migration: cpr_get_fd_param helper Steve Sistare
2025-01-29 14:43 ` [PATCH V1 16/26] vfio: return mr from vfio_get_xlat_addr Steve Sistare
2025-02-04 15:47 ` Cédric Le Goater
2025-02-04 17:42 ` Steven Sistare
2025-02-16 23:19 ` John Levon
2025-01-29 14:43 ` [PATCH V1 17/26] vfio: pass ramblock to vfio_container_dma_map Steve Sistare
2025-01-29 14:43 ` [PATCH V1 18/26] vfio/iommufd: define iommufd_cdev_make_hwpt Steve Sistare
2025-02-04 16:22 ` Cédric Le Goater
2025-02-04 17:42 ` Steven Sistare
2025-01-29 14:43 ` [PATCH V1 19/26] vfio/iommufd: use IOMMU_IOAS_MAP_FILE Steve Sistare
2025-02-05 17:23 ` Cédric Le Goater
2025-02-05 22:01 ` Steven Sistare
2025-01-29 14:43 ` [PATCH V1 20/26] vfio/iommufd: export iommufd_cdev_get_info_iova_range Steve Sistare
2025-02-05 17:33 ` Cédric Le Goater
2025-02-05 22:01 ` Steven Sistare
2025-01-29 14:43 ` [PATCH V1 21/26] iommufd: change process ioctl Steve Sistare
2025-02-05 17:34 ` Cédric Le Goater
2025-02-05 22:02 ` Steven Sistare
2025-01-29 14:43 ` [PATCH V1 22/26] vfio/iommufd: invariant device name Steve Sistare
2025-02-05 17:42 ` Cédric Le Goater
2025-02-05 22:02 ` Steven Sistare
2025-01-29 14:43 ` [PATCH V1 23/26] vfio/iommufd: register container for cpr Steve Sistare
2025-02-05 17:45 ` Cédric Le Goater
2025-02-05 22:03 ` Steven Sistare
2025-01-29 14:43 ` [PATCH V1 24/26] vfio/iommufd: preserve descriptors Steve Sistare
2025-01-29 14:43 ` [PATCH V1 25/26] vfio/iommufd: reconstruct device Steve Sistare
2025-01-29 14:43 ` [PATCH V1 26/26] iommufd: preserve DMA mappings Steve Sistare
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5e3fd711-2875-4eaf-a3c6-2a94f7dea6b2@oracle.com \
--to=steven.sistare@oracle.com \
--cc=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=eric.auger@redhat.com \
--cc=farosas@suse.de \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yi.l.liu@intel.com \
--cc=zhenzhong.duan@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).