From: vijay.kilari@gmail.com
To: qemu-arm@nongnu.org, peter.maydell@linaro.org, pbonzini@redhat.com
Cc: p.fedin@samsung.com, qemu-devel@nongnu.org,
Prasun.Kapoor@cavium.com, vijay.kilari@gmail.com,
Vijaya Kumar K <Vijaya.Kumar@cavium.com>
Subject: [Qemu-devel] [RFC PATCH v1 0/2] GICv3 live migration support
Date: Tue, 26 Jul 2016 16:31:54 +0530 [thread overview]
Message-ID: <1469530917-13842-1-git-send-email-vijay.kilari@gmail.com> (raw)
From: Vijaya Kumar K <Vijaya.Kumar@cavium.com>
This series introduces support for GICv3 live migration with
new VGIC implementation in 4.7-rc3 kernel.
In this series, patch 2 & 3 of the previous implementation
are ported.
https://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg05284.html
Kernel patches which implement this functionality are:
http://www.spinics.net/lists/arm-kernel/msg519596.html
This API definition is as per draft version of VGICv3 specification
https://lists.cs.columbia.edu/pipermail/kvmarm/2016-May/020355.html
Patch 1 of this series will be synced with KVM patches
in next revision.
Tested Live migration of Idle VM running with 4 VCPUs and 8GB RAM.
Vijaya Kumar K (2):
kernel: Add definitions for GICv3 attributes
hw/intc/arm_gicv3_kvm: Implement get/put functions
hw/intc/arm_gicv3_common.c | 3 +
hw/intc/arm_gicv3_kvm.c | 496 +++++++++++++++++++++++++++++++++++-
hw/intc/gicv3_internal.h | 113 ++++++++
include/hw/intc/arm_gicv3_common.h | 1 +
linux-headers/asm-arm64/kvm.h | 22 +-
5 files changed, 624 insertions(+), 11 deletions(-)
--
1.7.9.5
next reply other threads:[~2016-07-26 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 11:01 vijay.kilari [this message]
2016-07-26 11:01 ` [Qemu-devel] [RFC PATCH v1 1/2] kernel: Add definitions for GICv3 attributes vijay.kilari
2016-07-26 11:01 ` [Qemu-devel] [RFC PATCH v1 2/2] hw/intc/arm_gicv3_kvm: Implement get/put functions vijay.kilari
2016-07-26 11:06 ` Peter Maydell
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=1469530917-13842-1-git-send-email-vijay.kilari@gmail.com \
--to=vijay.kilari@gmail.com \
--cc=Prasun.Kapoor@cavium.com \
--cc=Vijaya.Kumar@cavium.com \
--cc=p.fedin@samsung.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).