From: Christopher Covington <cov@codeaurora.org>
To: Shlomo Pongratz <shlomopongratz@gmail.com>,
qemu-devel@nongnu.org, p.fedin@samsung.com
Cc: peter.maydell@linaro.org, imammedo@redhat.com,
shannon.zhao@linaro.org, ashoks@broadcom.com,
eric.auger@linaro.org
Subject: Re: [Qemu-devel] [PATCH RFC V4 4/4] Add virt-v3 machine that uses GIC-500
Date: Thu, 24 Sep 2015 14:03:22 -0400 [thread overview]
Message-ID: <56043AEA.6080907@codeaurora.org> (raw)
In-Reply-To: <1442511496-24050-5-git-send-email-shlomopongratz@gmail.com>
Hi,
On 09/17/2015 01:38 PM, Shlomo Pongratz wrote:
> From: Pavel Fedin <p.fedin@samsung.com>
>
> I would like to offer this, slightly improved implementation. The key thing is a new
> kernel_irqchip_type member in Machine class. Currently it it used only by virt machine for
> its internal purposes, however in future it is to be passed to KVM in
> kvm_irqchip_create(). The variable is defined as int in order to be architecture agnostic,
> for potential future users.
>
> Signed-off-by: Pavel Fedin <p.fedin@samsung.com>
> ---
> hw/arm/virt.c | 72 +++++++++++++++++++++++++++++++++++++++++++++------
> include/hw/arm/fdt.h | 2 ++
> include/hw/arm/virt.h | 1 +
> target-arm/machine.c | 7 ++++-
> 4 files changed, 73 insertions(+), 9 deletions(-)
>
> diff --git a/hw/arm/virt.c b/hw/arm/virt.c
> index 4d15309..4c2ae7f 100644
> --- a/hw/arm/virt.c
> +++ b/hw/arm/virt.c
> @@ -445,6 +462,14 @@ static void create_gic(VirtBoardInfo *vbi, qemu_irq *pic, int type, bool secure)
> sysbus_mmio_map(gicbusdev, 1, vbi->memmap[VIRT_GIC_CPU].base);
> }
>
> + if (type == 3) {
> + /* Connect GIC to CPU */
> + for (i = 0; i < smp_cpus; i++) {
> + CPUState *cpu = qemu_get_cpu(i);
> + aatch64_registers_with_opaque_set(OBJECT(cpu), (void *)gicdev);
Typo--should be "aarch64".
With that, feel free to add the following if it's any use:
Tested-by: Christopher Covington <cov@codeaurora.org>
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-09-24 18:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 17:38 [Qemu-devel] [PATCH RFC V4 0/4] Implement GIC-500 from GICv3 family for arm64 Shlomo Pongratz
2015-09-17 17:38 ` [Qemu-devel] [PATCH RFC V4 1/4] hw/intc: Implement GIC-500 support files Shlomo Pongratz
2015-09-17 17:38 ` [Qemu-devel] [PATCH RFC V4 2/4] hw/intc: Implment GIC-500 Shlomo Pongratz
2015-09-17 17:38 ` [Qemu-devel] [PATCH RFC V4 3/4] target-arm/cpu64 GICv3 system instructions support Shlomo Pongratz
2015-09-17 17:38 ` [Qemu-devel] [PATCH RFC V4 4/4] Add virt-v3 machine that uses GIC-500 Shlomo Pongratz
2015-09-24 18:03 ` Christopher Covington [this message]
2015-09-24 19:16 ` Christopher Covington
2015-09-28 15:20 ` Shlomo Pongratz
2015-09-17 17:52 ` [Qemu-devel] [PATCH RFC V4 0/4] Implement GIC-500 from GICv3 family for arm64 Peter Maydell
2015-09-17 18:18 ` Shlomo Pongratz
2015-09-17 18:33 ` Peter Maydell
2015-09-17 18:54 ` Shlomo Pongratz
2015-09-17 19:03 ` Peter Maydell
2015-09-24 9:55 ` 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=56043AEA.6080907@codeaurora.org \
--to=cov@codeaurora.org \
--cc=ashoks@broadcom.com \
--cc=eric.auger@linaro.org \
--cc=imammedo@redhat.com \
--cc=p.fedin@samsung.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhao@linaro.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).