From: Pavel Fedin <p.fedin@samsung.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Shlomo Pongratz <shlomopongratz@gmail.com>,
Shlomo Pongratz <shlomo.pongratz@huawei.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
Eric Auger <eric.auger@linaro.org>
Subject: [Qemu-devel] [PATCH v7 0/6] vGICv3 support
Date: Fri, 24 Jul 2015 12:55:42 +0300 [thread overview]
Message-ID: <cover.1437731107.git.p.fedin@samsung.com> (raw)
This series introduces support for GICv3 by KVM. Software emulation is
currently not supported.
Differences from v6:
- Wrap own GIC type definitions on top of KVM ones. Fixed build on
non-ARM-Linux hosts
Differences from v5:
- Fixed various checkpatch.pl style warnings
- Removed TODO in gicv3_init_irqs_and_mmio(), relevant memory API patch
included
- gicv3_init_irqs_and_mmio() now takes 3 arguments instead of 4. It is more
convenient to pass MMIO descriptors as array
Differences from v4:
- Do not reintroduce several constants shared with GICv2, reuse them instead.
- Added gicv3_init_irqs_and_mmio() in base class, to be used by both software
emulation and KVM code. Avoids code duplication.
- Do not add NULL msi-parent phandle to PCI device in the FDT
- Removed a couple of stale things from virt.c
Differences from v3:
- Fixed stupid build breakage in patch 0002
- Rebased on top of current master, patch 0003 adjusted according to
kvm_irqchip_create() changes
- Added assertion against uninitialized kernel_irqchip_type
- Removed kernel_irqchip_type initialization from models which do not
use KVM vGIC
Differences from v2:
- Removed some unrelated and unnecessary changes from virt machine,
occasionally slipped in; some of them caused qemu to crash on ARM32.
- Fixed build for ARM32; vGICv3 code requires definitions which are
present only in ARM64 kernel
Differences from v1:
- Base class included, taken from the series by Shlomo Pongratz:
http://lists.nongnu.org/archive/html/qemu-devel/2015-06/msg01512.html
The code is refactored as little as possible in order to simplify
further addition of software emulation:
- Minor fixes in code style and comments, according to old reviews
- Removed REV_V3 definition because it's currently not used, and it does
not add any meaning to number 3.
- Removed reserved regions for MBI and ITS (except for 'virt' machine
memory map). These should go to separate classes when implemented.
- Improved commit messages
- vGIC patches restructured
- Use 'gicversion' option instead of virt-v3 machine
Pavel Fedin (5):
Merge memory_region_init_reservation() into memory_region_init_io()
Extract some reusable vGIC code
Introduce irqchip type specification for KVM
Initial implementation of vGICv3
Add gicversion option to virt machine
Shlomo Pongratz (1):
Implement GIC-500 base class
hw/arm/vexpress.c | 1 +
hw/arm/virt.c | 140 +++++++++++++++++----
hw/intc/Makefile.objs | 4 +
hw/intc/arm_gic_kvm.c | 84 ++++++-------
hw/intc/arm_gicv3_common.c | 249 +++++++++++++++++++++++++++++++++++++
hw/intc/arm_gicv3_kvm.c | 155 +++++++++++++++++++++++
hw/intc/gicv3_internal.h | 156 +++++++++++++++++++++++
hw/intc/vgic_common.h | 43 +++++++
include/exec/memory.h | 14 ++-
include/hw/arm/fdt.h | 2 +-
include/hw/arm/virt.h | 6 +-
include/hw/boards.h | 1 +
include/hw/intc/arm_gicv3_common.h | 112 +++++++++++++++++
include/sysemu/kvm.h | 3 +-
kvm-all.c | 2 +-
memory.c | 10 +-
stubs/kvm.c | 2 +-
target-arm/kvm-consts.h | 6 +
target-arm/kvm.c | 13 +-
19 files changed, 917 insertions(+), 86 deletions(-)
create mode 100644 hw/intc/arm_gicv3_common.c
create mode 100644 hw/intc/arm_gicv3_kvm.c
create mode 100644 hw/intc/gicv3_internal.h
create mode 100644 hw/intc/vgic_common.h
create mode 100644 include/hw/intc/arm_gicv3_common.h
--
1.9.5.msysgit.0
next reply other threads:[~2015-07-24 9:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 9:55 Pavel Fedin [this message]
2015-07-24 9:55 ` [Qemu-devel] [PATCH v7 1/6] Merge memory_region_init_reservation() into memory_region_init_io() Pavel Fedin
2015-07-24 16:20 ` Peter Maydell
2015-07-24 9:55 ` [Qemu-devel] [PATCH v7 2/6] Implement GIC-500 base class Pavel Fedin
2015-07-24 16:37 ` Peter Maydell
2015-07-26 13:52 ` Pavel Fedin
2015-07-26 19:10 ` Peter Maydell
2015-07-31 15:38 ` Peter Maydell
2015-08-03 12:18 ` Pavel Fedin
2015-07-26 14:03 ` Pavel Fedin
2015-07-26 14:45 ` Shlomo Pongratz
2015-07-24 9:55 ` [Qemu-devel] [PATCH v7 3/6] Extract some reusable vGIC code Pavel Fedin
2015-07-24 9:55 ` [Qemu-devel] [PATCH v7 4/6] Introduce irqchip type specification for KVM Pavel Fedin
2015-07-24 16:42 ` Peter Maydell
2015-07-26 13:46 ` Pavel Fedin
2015-07-28 17:37 ` Peter Maydell
2015-07-24 9:55 ` [Qemu-devel] [PATCH v7 5/6] Initial implementation of vGICv3 Pavel Fedin
2015-07-30 17:00 ` Peter Maydell
2015-07-31 9:32 ` Pavel Fedin
2015-07-31 10:08 ` Peter Maydell
2015-07-31 10:22 ` Peter Maydell
2015-07-31 11:12 ` Pavel Fedin
2015-07-31 11:12 ` Peter Maydell
2015-07-31 11:15 ` Pavel Fedin
2015-07-31 11:24 ` Peter Maydell
2015-08-03 15:30 ` Pavel Fedin
2015-07-24 9:55 ` [Qemu-devel] [PATCH v7 6/6] Add gicversion option to virt machine Pavel Fedin
2015-07-31 15:44 ` Peter Maydell
2015-08-03 7:19 ` Pavel Fedin
2015-08-03 7:57 ` Peter Maydell
2015-08-03 11:41 ` Shlomo Pongratz
2015-08-03 12:01 ` 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.1437731107.git.p.fedin@samsung.com \
--to=p.fedin@samsung.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shlomo.pongratz@huawei.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.