From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
mst@redhat.com, Juan Quintela <quintela@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Amit Shah <amit.shah@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/2] VT-d migration support
Date: Fri, 6 Jan 2017 13:27:38 +0000 [thread overview]
Message-ID: <20170106132738.GD2461@work-vm> (raw)
In-Reply-To: <1483675573-12636-1-git-send-email-peterx@redhat.com>
* Peter Xu (peterx@redhat.com) wrote:
> This series enables VT-d IOMMU migration.
>
> v3:
> - save/load for csr [Jason]
>
> v2:
> - remove SaveStateEntry.priority, let priority store only in one
> place, which is VMStateDescription. Meanwhile, provide another
> helper to fetch the priority.
> - add enum MigrationPriority to unify the ordering, rather than use
> magic numbers like 100 everywhere [Dave]
> - fix commit log where proper
>
> First patch is an enhancement to current migration framework to allow
> prioritized save state entry. This is required to let VT-d migrate
> properly.
>
> The second patch enables the migration for the vIOMMU.
>
> Please check commit message for more information.
>
> Test done:
>
> Smoke test is done with parameter:
>
> $qemu -M q35,kernel-irqchip=off -enable-kvm \
> -device intel-iommu,intremap=on \
> -netdev user,id=net0 \
> -device e1000,netdev=net0 \
> -m 512M -monitor stdio \
> $param /var/lib/libvirt/images/vm1.qcow2
>
> Please review, thanks.
>
> (P.S. I found that split irqchip cannot work well with migration. Is
> this an known issue?)
How did it fail?
Dave
> Peter Xu (2):
> migration: allow to prioritize save state entries
> intel_iommu: allow migration
>
> hw/i386/intel_iommu.c | 22 +++++++++++++++++++++-
> include/migration/vmstate.h | 7 +++++++
> migration/savevm.c | 34 ++++++++++++++++++++++++++++++----
> 3 files changed, 58 insertions(+), 5 deletions(-)
>
> --
> 2.7.4
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2017-01-06 13:27 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
2017-01-06 13:27 ` Dr. David Alan Gilbert [this message]
2017-01-09 2:18 ` [Qemu-devel] [PATCH v3 0/2] VT-d migration support 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=20170106132738.GD2461@work-vm \
--to=dgilbert@redhat.com \
--cc=amit.shah@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@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).