From: Peter Xu <peterx@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>,
mst@redhat.com, "Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Amit Shah <amit.shah@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 2/2] intel_iommu: allow migration
Date: Fri, 6 Jan 2017 12:04:54 +0800 [thread overview]
Message-ID: <20170106040454.GC4135@pxdev.xzpeter.org> (raw)
In-Reply-To: <c297a765-a4e4-a6d3-de49-14ddb4af4149@redhat.com>
On Fri, Jan 06, 2017 at 11:42:30AM +0800, Jason Wang wrote:
>
>
> On 2017年01月06日 11:08, Peter Xu wrote:
> >IOMMU needs to be migrated before all the PCI devices (in case there are
> >devices that will request for address translation). So marking it with a
> >priority higher than the default (which PCI devices and other belong).
> >Migration framework handled the rest.
> >
> >Signed-off-by: Peter Xu <peterx@redhat.com>
> >---
> > hw/i386/intel_iommu.c | 21 ++++++++++++++++++++-
> > include/migration/vmstate.h | 1 +
> > 2 files changed, 21 insertions(+), 1 deletion(-)
> >
> >diff --git a/hw/i386/intel_iommu.c b/hw/i386/intel_iommu.c
> >index 5f3e351..ea9e526 100644
> >--- a/hw/i386/intel_iommu.c
> >+++ b/hw/i386/intel_iommu.c
> >@@ -1996,7 +1996,26 @@ static void vtd_iommu_notify_flag_changed(MemoryRegion *iommu,
> > static const VMStateDescription vtd_vmstate = {
> > .name = "iommu-intel",
> >- .unmigratable = 1,
> >+ .version_id = 1,
> >+ .minimum_version_id = 1,
> >+ .priority = MIG_PRI_IOMMU,
> >+ .fields = (VMStateField[]) {
> >+ VMSTATE_UINT64(root, IntelIOMMUState),
> >+ VMSTATE_UINT64(intr_root, IntelIOMMUState),
> >+ VMSTATE_UINT64(iq, IntelIOMMUState),
> >+ VMSTATE_UINT32(intr_size, IntelIOMMUState),
> >+ VMSTATE_UINT16(iq_head, IntelIOMMUState),
> >+ VMSTATE_UINT16(iq_tail, IntelIOMMUState),
> >+ VMSTATE_UINT16(iq_size, IntelIOMMUState),
> >+ VMSTATE_UINT16(next_frcd_reg, IntelIOMMUState),
> >+ VMSTATE_UINT8(iq_last_desc_type, IntelIOMMUState),
> >+ VMSTATE_BOOL(root_extended, IntelIOMMUState),
> >+ VMSTATE_BOOL(dmar_enabled, IntelIOMMUState),
> >+ VMSTATE_BOOL(qi_enabled, IntelIOMMUState),
> >+ VMSTATE_BOOL(intr_enabled, IntelIOMMUState),
> >+ VMSTATE_BOOL(intr_eime, IntelIOMMUState),
> >+ VMSTATE_END_OF_LIST()
> >+ }
> > };
>
> Looks like register values were missed (e.g csr[]) ?
Oops, I missed the most important thing. :)
And obviously it even escaped from smoke test... Thanks Jason. Will
repost.
-- peterx
prev parent reply other threads:[~2017-01-06 4:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 3:08 [Qemu-devel] [PATCH v2 0/2] VT-d migration support Peter Xu
2017-01-06 3:08 ` [Qemu-devel] [PATCH v2 1/2] migration: allow to prioritize save state entries Peter Xu
2017-01-06 3:08 ` [Qemu-devel] [PATCH v2 2/2] intel_iommu: allow migration Peter Xu
2017-01-06 3:42 ` Jason Wang
2017-01-06 4:04 ` Peter Xu [this message]
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=20170106040454.GC4135@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.