From: Peter Xu <peterx@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
mst@redhat.com, Juan Quintela <quintela@redhat.com>,
Amit Shah <amit.shah@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 2/2] intel_iommu: allow migration
Date: Fri, 6 Jan 2017 15:13:14 +0800 [thread overview]
Message-ID: <20170106071314.GD4135@pxdev.xzpeter.org> (raw)
In-Reply-To: <f62ec203-a644-9102-f5e6-4f41cca60d80@redhat.com>
On Fri, Jan 06, 2017 at 03:05:47PM +0800, Jason Wang wrote:
>
>
> On 2017年01月06日 12:06, 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 | 22 +++++++++++++++++++++-
> > include/migration/vmstate.h | 1 +
> > 2 files changed, 22 insertions(+), 1 deletion(-)
> >
> >diff --git a/hw/i386/intel_iommu.c b/hw/i386/intel_iommu.c
> >index 5f3e351..119217b 100644
> >--- a/hw/i386/intel_iommu.c
> >+++ b/hw/i386/intel_iommu.c
> >@@ -1996,7 +1996,27 @@ 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_ARRAY(csr, IntelIOMMUState, DMAR_REG_SIZE),
>
> Do we need migrate wmask, w1cmask, womask too?
Should not. Although we are using arrays here, they should be only
configured during vtd_define_*() and should be constant values for the
whole lifecycle of the device (which is mostly decided by the spec).
Thanks,
-- peterx
next prev parent reply other threads:[~2017-01-06 7:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 4:06 [Qemu-devel] [PATCH v3 0/2] VT-d migration support Peter Xu
2017-01-06 4:06 ` [Qemu-devel] [PATCH v3 1/2] migration: allow to prioritize save state entries Peter Xu
2017-01-06 13:19 ` Dr. David Alan Gilbert
2017-01-06 4:06 ` [Qemu-devel] [PATCH v3 2/2] intel_iommu: allow migration Peter Xu
2017-01-06 7:05 ` Jason Wang
2017-01-06 7:13 ` Peter Xu [this message]
2017-01-06 13:27 ` [Qemu-devel] [PATCH v3 0/2] VT-d migration support Dr. David Alan Gilbert
2017-01-09 2:18 ` Peter Xu
2017-01-09 8:45 ` Peter Xu
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=20170106071314.GD4135@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 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).