From: "KONRAD Frédéric" <fred.konrad@greensocs.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Christoffer Dall" <c.dall@virtualopensystems.com>,
kvm@vger.kernel.org, "Gleb Natapov" <gleb@redhat.com>,
patches@linaro.org, "Marcelo Tosatti" <mtosatti@redhat.com>,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>,
"Blue Swirl" <blauwirbel@gmail.com>,
kvmarm@lists.cs.columbia.edu
Subject: Re: [kvmarm] [RFC v5 7/8] hw/kvm/arm_gic: Implement support for KVM in-kernel ARM GIC
Date: Thu, 31 Jan 2013 11:52:37 +0100 [thread overview]
Message-ID: <510A4CF5.9050006@greensocs.com> (raw)
In-Reply-To: <1359042240-11482-8-git-send-email-peter.maydell@linaro.org>
On 24/01/2013 16:43, Peter Maydell wrote:
> Implement support for using the KVM in-kernel GIC for ARM.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> hw/a15mpcore.c | 8 ++-
> hw/arm/Makefile.objs | 1 +
> hw/kvm/arm_gic.c | 169 ++++++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 177 insertions(+), 1 deletion(-)
> create mode 100644 hw/kvm/arm_gic.c
>
> diff --git a/hw/a15mpcore.c b/hw/a15mpcore.c
> index fe6c34c..1ca6f28 100644
> --- a/hw/a15mpcore.c
> +++ b/hw/a15mpcore.c
> @@ -19,6 +19,7 @@
> */
>
> #include "sysbus.h"
> +#include "sysemu/kvm.h"
>
> /* A15MP private memory region. */
>
> @@ -40,8 +41,13 @@ static int a15mp_priv_init(SysBusDevice *dev)
> {
> A15MPPrivState *s = FROM_SYSBUS(A15MPPrivState, dev);
> SysBusDevice *busdev;
> + const char *gictype = "arm-gic";
s/arm-gic/arm_gic/ ^^ ?
Christoffer and I had trouble with that:
qemu-system-arm: Unknown device 'arm-gic' for default sysbus
Fred
>
> - s->gic = qdev_create(NULL, "arm_gic");
> + if (kvm_irqchip_in_kernel()) {
> + gictype = "kvm-arm-gic";
> + }
> +
> + s->gic = qdev_create(NULL, gictype);
> qdev_prop_set_uint32(s->gic, "num-cpu", s->num_cpu);
> qdev_prop_set_uint32(s->gic, "num-irq", s->num_irq);
next prev parent reply other threads:[~2013-01-31 10:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 15:43 [RFC v5 0/8] QEMU: Support KVM on ARM Peter Maydell
2013-01-24 15:43 ` [RFC v5 1/8] oslib-posix: Align to permit transparent hugepages on ARM Linux Peter Maydell
2013-01-24 15:43 ` [RFC v5 2/8] linux-headers: Add ARM KVM headers (not for upstream) Peter Maydell
2013-01-24 15:43 ` [RFC v5 3/8] ARM: KVM: Add support for KVM on ARM architecture Peter Maydell
2013-01-24 15:43 ` [RFC v5 4/8] ARM KVM: save and load VFP registers from kernel Peter Maydell
2013-01-24 15:43 ` [RFC v5 5/8] hw/arm_gic: Add presave/postload hooks Peter Maydell
2013-01-24 15:43 ` [RFC v5 6/8] target-arm: Use MemoryListener to identify GIC base address for KVM Peter Maydell
2013-01-24 15:43 ` [RFC v5 7/8] hw/kvm/arm_gic: Implement support for KVM in-kernel ARM GIC Peter Maydell
2013-01-31 10:52 ` KONRAD Frédéric [this message]
2013-01-31 10:54 ` [kvmarm] " Andreas Färber
2013-01-31 11:27 ` Peter Maydell
2013-01-24 15:44 ` [RFC v5 8/8] configure: Enable KVM on ARM Peter Maydell
2013-01-25 8:58 ` [RFC v5 0/8] QEMU: Support " Paolo Bonzini
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=510A4CF5.9050006@greensocs.com \
--to=fred.konrad@greensocs.com \
--cc=afaerber@suse.de \
--cc=blauwirbel@gmail.com \
--cc=c.dall@virtualopensystems.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=mtosatti@redhat.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.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