From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
mst@redhat.com, Juan Quintela <quintela@redhat.com>,
peterx@redhat.com, Jason Wang <jasowang@redhat.com>,
Amit Shah <amit.shah@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] VT-d migration support
Date: Thu, 5 Jan 2017 18:09:45 +0800 [thread overview]
Message-ID: <1483610987-24331-1-git-send-email-peterx@redhat.com> (raw)
This series enables VT-d IOMMU migration.
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?)
Peter Xu (2):
migration: allow to prioritize save state entries
intel_iommu: allow migration
hw/i386/intel_iommu.c | 21 ++++++++++++++++++++-
include/migration/vmstate.h | 1 +
migration/savevm.c | 27 +++++++++++++++++++++++----
3 files changed, 44 insertions(+), 5 deletions(-)
--
2.7.4
next reply other threads:[~2017-01-05 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 10:09 Peter Xu [this message]
2017-01-05 10:09 ` [Qemu-devel] [PATCH 1/2] migration: allow to prioritize save state entries Peter Xu
2017-01-05 12:49 ` Dr. David Alan Gilbert
2017-01-06 2:41 ` Peter Xu
2017-01-05 10:09 ` [Qemu-devel] [PATCH 2/2] intel_iommu: allow migration 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=1483610987-24331-1-git-send-email-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=amit.shah@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).