From: Pavel Fedin <p.fedin@samsung.com>
To: qemu-devel@nongnu.org
Cc: Diana Craciun <diana.craciun@freescale.com>,
Peter Maydell <peter.maydell@linaro.org>,
Shlomo Pongratz <shlomopongratz@gmail.com>,
Vijay Kilari <vijay.kilari@gmail.com>,
Shlomo Pongratz <shlomo.pongratz@huawei.com>
Subject: [Qemu-devel] [RFC PATCH v3 0/4] GICv3 live migration support
Date: Thu, 22 Oct 2015 17:02:26 +0300 [thread overview]
Message-ID: <cover.1445522263.git.p.fedin@samsung.com> (raw)
This series introduces support for GICv3 live migration. It is based on
kernel API which is not released yet, therefore i post it as an RFC.
Kernel patches which implement this functionality are:
- [PATCH v5 0/7] KVM: arm64: Implement API for vGICv3 live migration
http://www.spinics.net/lists/kvm/msg122040.html
One more prerequisite for this series is:
- [PATCH] target-arm: Extract some external ARM CPU API
http://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg05269.html
The main purpose of this RFC is to agree on GICv3 state data format,
because software implementation of GICv3 is also going to use it. In order
to simplify GICv3 software emulation development, parts 1 and 2 of this
patchset can be accepted right now, without waiting for the kernel part.
v2 => v3:
- Integrated state manipulation macros from Shlomo Pongratz' GICv3 RFC
(with some changes)
- Added fields for SGI source masks
- Do not use mp-affinity property every time, cache IDs internally instead
- Removed mp-affinity property patch, now a part of prerequisite
v1 => v2:
- Use different kernel API, agreed upon by KVM developers
- Reworked state representation, do not duplicate SPI fields any more
- Added basic LPI support (PROPBASER and PENDBASER).
Pavel Fedin (4):
hw/intc/arm_gicv3_common: Add state information
kernel: Add definitions for GICv3 attributes
hw/intc/arm_gicv3_kvm: Implement get/put functions
hw/intc/arm_gicv3_common: Add vmstate descriptors
hw/intc/arm_gicv3_common.c | 185 ++++++++++++++-
hw/intc/arm_gicv3_kvm.c | 456 ++++++++++++++++++++++++++++++++++++-
hw/intc/gicv3_internal.h | 265 +++++++++++++++++++++
include/hw/intc/arm_gicv3_common.h | 93 +++++++-
include/migration/vmstate.h | 9 +
linux-headers/asm-arm64/kvm.h | 17 +-
6 files changed, 1011 insertions(+), 14 deletions(-)
create mode 100644 hw/intc/gicv3_internal.h
--
2.4.4
next reply other threads:[~2015-10-22 14:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 14:02 Pavel Fedin [this message]
2015-10-22 14:02 ` [Qemu-devel] [RFC PATCH v3 1/4] hw/intc/arm_gicv3_common: Add state information Pavel Fedin
2015-10-23 13:57 ` Peter Maydell
2015-10-24 12:30 ` Shlomo Pongratz
2015-10-24 12:35 ` Peter Maydell
2015-10-26 7:43 ` Pavel Fedin
2015-10-26 10:59 ` Peter Maydell
2015-10-22 14:02 ` [Qemu-devel] [RFC PATCH v3 2/4] kernel: Add definitions for GICv3 attributes Pavel Fedin
2015-10-22 14:02 ` [Qemu-devel] [RFC PATCH v3 3/4] hw/intc/arm_gicv3_kvm: Implement get/put functions Pavel Fedin
2015-10-23 13:57 ` Peter Maydell
2015-10-26 7:59 ` Pavel Fedin
2015-10-26 11:09 ` Peter Maydell
2015-10-22 14:02 ` [Qemu-devel] [RFC PATCH v3 4/4] hw/intc/arm_gicv3_common: Add vmstate descriptors Pavel Fedin
2015-10-23 13:57 ` 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=cover.1445522263.git.p.fedin@samsung.com \
--to=p.fedin@samsung.com \
--cc=diana.craciun@freescale.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shlomo.pongratz@huawei.com \
--cc=shlomopongratz@gmail.com \
--cc=vijay.kilari@gmail.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).