qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Fedin <p.fedin@samsung.com>
To: qemu-devel@nongnu.org
Cc: Shlomo Pongratz <shlomopongratz@gmail.com>,
	Pavel Fedin <p.fedin@samsung.com>,
	Ashok Kumar <ashoks@broadcom.com>,
	Eric Auger <eric.auger@linaro.org>
Subject: [Qemu-devel] [PATCH RFC 0/4] vGICv3 support
Date: Fri, 22 May 2015 13:58:40 +0300	[thread overview]
Message-ID: <cover.1432291291.git.p.fedin@samsung.com> (raw)

 This is my alternative to Ashok's vGICv3 patch
(https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg03021.html), which
i am currently working on. It addresses vGIC capability verification issue
(kvm_irqchip_create() / kvm_arch_irqchip_create()), as well as offers better
code structure (v3 code separated from v2).
 This patchset applies on top of this:
https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg00943.html. Note that
GIC type selection still relies on machine name (virt-v3 vs virt), and not on
machine option. Since libvirt has recently introduced support for extra options,
i have absolutely nothing against Ashok's approach. I just did not change this
yet because it would affect my testing environment. The aim of this RFC is to
focus on vGICv3 implementation and related changes. And yes, i agree that v2 and
v3 now have some copypasted code, and this is TBD.

Pavel Fedin (4):
  Add virt-v3 machine that uses GIC-500
  Set kernel_irqchip_type for other ARM boards which use GIC
  First bits of vGICv3 support:
  Initial implementation of vGICv3.

 hw/arm/exynos4_boards.c |   1 +
 hw/arm/realview.c       |   1 +
 hw/arm/vexpress.c       |   1 +
 hw/arm/virt.c           | 148 ++++++++++++++++++++-----
 hw/intc/Makefile.objs   |   1 +
 hw/intc/arm_gicv3_kvm.c | 283 ++++++++++++++++++++++++++++++++++++++++++++++++
 include/hw/boards.h     |   1 +
 include/sysemu/kvm.h    |   3 +-
 kvm-all.c               |   2 +-
 stubs/kvm.c             |   2 +-
 target-arm/kvm.c        |   8 +-
 11 files changed, 419 insertions(+), 32 deletions(-)
 create mode 100644 hw/intc/arm_gicv3_kvm.c

-- 
1.9.5.msysgit.0

             reply	other threads:[~2015-05-22 10:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 10:58 Pavel Fedin [this message]
2015-05-22 10:58 ` [Qemu-devel] [PATCH RFC 1/4] Add virt-v3 machine that uses GIC-500 Pavel Fedin
2015-05-25 14:07   ` Eric Auger
2015-05-25 14:51     ` Pavel Fedin
2015-07-01 10:11   ` Christoffer Dall
2015-05-22 10:58 ` [Qemu-devel] [PATCH RFC 2/4] Set kernel_irqchip_type for other ARM boards which use GIC Pavel Fedin
2015-05-25 14:07   ` Eric Auger
2015-05-25 14:43     ` Pavel Fedin
2015-07-01 10:11   ` Christoffer Dall
2015-05-22 10:58 ` [Qemu-devel] [PATCH RFC 3/4] First bits of vGICv3 support: Pavel Fedin
2015-05-25 14:07   ` Eric Auger
2015-07-01 10:13   ` Christoffer Dall
2015-05-22 10:58 ` [Qemu-devel] [PATCH RFC 4/4] Initial implementation of vGICv3 Pavel Fedin
2015-05-22 15:17   ` Eric Auger
2015-05-22 16:57     ` Pavel Fedin
2015-07-01 10:19       ` Christoffer Dall
2015-07-01 10:21 ` [Qemu-devel] [PATCH RFC 0/4] vGICv3 support Christoffer Dall
2015-07-01 10:26   ` Daniel P. Berrange
2015-07-01 11:14   ` Pavel Fedin
2015-07-01 11:28     ` Christoffer Dall
2015-07-01 12:31       ` Pavel Fedin

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.1432291291.git.p.fedin@samsung.com \
    --to=p.fedin@samsung.com \
    --cc=ashoks@broadcom.com \
    --cc=eric.auger@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shlomopongratz@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).