From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] intel_iommu: fix migration breakage on mr switch
Date: Thu, 29 Jun 2017 16:35:04 +0300 [thread overview]
Message-ID: <20170629163418-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1498710417-7807-1-git-send-email-peterx@redhat.com>
On Thu, Jun 29, 2017 at 12:26:57PM +0800, Peter Xu wrote:
> Migration is broken after the vfio integration work:
>
> qemu-kvm: AHCI: Failed to start FIS receive engine: bad FIS receive buffer address
> qemu-kvm: Failed to load ich9_ahci:ahci
> qemu-kvm: error while loading state for instance 0x0 of device '0000:00:1f.2/ich9_ahci'
> qemu-kvm: load of migration failed: Operation not permitted
>
> The problem is that vfio work introduced dynamic memory region
> switching (actually it is also used for future PT mode), and this memory
> region layout is not properly delivered to destination when migration
> happens. Solution is to rebuild the layout in post_load.
>
> Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1459906
> Fixes: 558e0024 ("intel_iommu: allow dynamic switch of IOMMU region")
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
> hw/i386/intel_iommu.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/hw/i386/intel_iommu.c b/hw/i386/intel_iommu.c
> index a9b59bd..36b231d 100644
> --- a/hw/i386/intel_iommu.c
> +++ b/hw/i386/intel_iommu.c
> @@ -2332,11 +2332,28 @@ static void vtd_iommu_notify_flag_changed(MemoryRegion *iommu,
> }
> }
>
> +static int vtd_post_load(void *opaque, int version_id)
> +{
> + IntelIOMMUState *iommu = opaque;
> +
> + /*
> + * Since commit 558e00 ("intel_iommu: allow dynamic switch of
> + * IOMMU region"),
I would drop this part of the comment. It isn't of interest
to people reading code directly, while people reading git
history see the commit log.
> memory regions are dynamically turned on/off
> + * depending on context entry configurations from the guest. After
> + * migration, we need to make sure the memory regions are still
> + * correct.
> + */
> + vtd_switch_address_space_all(iommu);
> +
> + return 0;
> +}
> +
> static const VMStateDescription vtd_vmstate = {
> .name = "iommu-intel",
> .version_id = 1,
> .minimum_version_id = 1,
> .priority = MIG_PRI_IOMMU,
> + .post_load = vtd_post_load,
> .fields = (VMStateField[]) {
> VMSTATE_UINT64(root, IntelIOMMUState),
> VMSTATE_UINT64(intr_root, IntelIOMMUState),
> --
> 2.7.4
next prev parent reply other threads:[~2017-06-29 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 4:26 [Qemu-devel] [PATCH] intel_iommu: fix migration breakage on mr switch Peter Xu
2017-06-29 13:35 ` Michael S. Tsirkin [this message]
2017-06-30 6:30 ` Peter Xu
2017-06-30 3:12 ` Jason Wang
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=20170629163418-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.com \
--cc=lvivier@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).