From: Jason Gunthorpe <jgg@nvidia.com>
To: Zhangfei Gao <zhangfei.gao@linaro.org>
Cc: Joao Martins <joao.m.martins@oracle.com>,
iommu@lists.linux.dev, Kevin Tian <kevin.tian@intel.com>,
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
Lu Baolu <baolu.lu@linux.intel.com>, Yi Liu <yi.l.liu@intel.com>,
Yi Y Sun <yi.y.sun@intel.com>, Nicolin Chen <nicolinc@nvidia.com>,
Joerg Roedel <joro@8bytes.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Zhenzhong Duan <zhenzhong.duan@intel.com>,
Alex Williamson <alex.williamson@redhat.com>,
kvm@vger.kernel.org, Shameer Kolothum <shamiali2008@gmail.com>,
"Wangzhou (B)" <wangzhou1@hisilicon.com>
Subject: Re: [PATCH v6 00/18] IOMMUFD Dirty Tracking
Date: Wed, 30 Oct 2024 12:36:19 -0300 [thread overview]
Message-ID: <20241030153619.GG6956@nvidia.com> (raw)
In-Reply-To: <CABQgh9HRq8oXgm04XhY2ajvGrg-jJO_KirXvfZxRsn9WiZi7Dg@mail.gmail.com>
On Wed, Oct 30, 2024 at 11:15:02PM +0800, Zhangfei Gao wrote:
> hw/vfio/migration.c
> if (vfio_viommu_preset(vbasedev)) {
> error_setg(&err, "%s: Migration is currently not supported "
> "with vIOMMU enabled", vbasedev->name);
> goto add_blocker;
> }
The viommu driver itself does not support live migration, it would
need to preserve all the guest configuration and bring it all back. It
doesn't know how to do that yet.
Jason
next prev parent reply other threads:[~2024-10-30 15:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 13:50 [PATCH v6 00/18] IOMMUFD Dirty Tracking Joao Martins
2023-10-24 13:50 ` [PATCH v6 01/18] vfio/iova_bitmap: Export more API symbols Joao Martins
2023-10-24 13:50 ` [PATCH v6 02/18] vfio: Move iova_bitmap into iommufd Joao Martins
2023-10-24 13:50 ` [PATCH v6 03/18] iommufd/iova_bitmap: Move symbols to IOMMUFD namespace Joao Martins
2023-10-24 13:50 ` [PATCH v6 04/18] iommu: Add iommu_domain ops for dirty tracking Joao Martins
2023-10-24 13:50 ` [PATCH v6 05/18] iommufd: Add a flag to enforce dirty tracking on attach Joao Martins
2023-10-24 13:50 ` [PATCH v6 06/18] iommufd: Add IOMMU_HWPT_SET_DIRTY_TRACKING Joao Martins
2023-10-24 13:50 ` [PATCH v6 07/18] iommufd: Add IOMMU_HWPT_GET_DIRTY_BITMAP Joao Martins
2023-10-24 13:50 ` [PATCH v6 08/18] iommufd: Add capabilities to IOMMU_GET_HW_INFO Joao Martins
2023-10-24 13:51 ` [PATCH v6 09/18] iommufd: Add a flag to skip clearing of IOPTE dirty Joao Martins
2023-10-24 13:51 ` [PATCH v6 10/18] iommu/amd: Add domain_alloc_user based domain allocation Joao Martins
2023-10-24 13:51 ` [PATCH v6 11/18] iommu/amd: Access/Dirty bit support in IOPTEs Joao Martins
2023-10-24 13:51 ` [PATCH v6 12/18] iommu/vt-d: Access/Dirty bit support for SS domains Joao Martins
2023-10-24 13:51 ` [PATCH v6 13/18] iommufd/selftest: Expand mock_domain with dev_flags Joao Martins
2023-10-24 13:51 ` [PATCH v6 14/18] iommufd/selftest: Test IOMMU_HWPT_ALLOC_DIRTY_TRACKING Joao Martins
2023-10-24 13:51 ` [PATCH v6 15/18] iommufd/selftest: Test IOMMU_HWPT_SET_DIRTY_TRACKING Joao Martins
2023-10-24 13:51 ` [PATCH v6 16/18] iommufd/selftest: Test IOMMU_HWPT_GET_DIRTY_BITMAP Joao Martins
2023-10-24 13:51 ` [PATCH v6 17/18] iommufd/selftest: Test out_capabilities in IOMMU_GET_HW_INFO Joao Martins
2023-10-24 13:51 ` [PATCH v6 18/18] iommufd/selftest: Test IOMMU_HWPT_GET_DIRTY_BITMAP_NO_CLEAR flag Joao Martins
2023-10-24 15:55 ` [PATCH v6 00/18] IOMMUFD Dirty Tracking Jason Gunthorpe
2023-10-24 18:11 ` Nicolin Chen
2024-10-29 2:35 ` Zhangfei Gao
2024-10-29 2:52 ` Yi Liu
2024-10-29 8:05 ` Zhangfei Gao
2024-10-29 9:34 ` Yi Liu
2024-10-30 15:15 ` Zhangfei Gao
2024-10-30 15:36 ` Jason Gunthorpe [this message]
2024-10-30 15:47 ` Joao Martins
2024-10-30 15:57 ` Shameerali Kolothum Thodi
2024-10-30 16:56 ` Joao Martins
2024-10-30 18:41 ` Shameerali Kolothum Thodi
2024-10-30 20:37 ` Joao Martins
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=20241030153619.GG6956@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=joao.m.martins@oracle.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shamiali2008@gmail.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=wangzhou1@hisilicon.com \
--cc=will@kernel.org \
--cc=yi.l.liu@intel.com \
--cc=yi.y.sun@intel.com \
--cc=zhangfei.gao@linaro.org \
--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