From: "Andreas Färber" <afaerber@suse.de>
To: Scott Wood <scottwood@freescale.com>, Alexander Graf <agraf@suse.de>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] kvm/openpic: in-kernel mpic support
Date: Sun, 16 Jun 2013 21:25:04 +0200 [thread overview]
Message-ID: <51BE1110.5000107@suse.de> (raw)
In-Reply-To: <1371069171-20377-1-git-send-email-scottwood@freescale.com>
Subject is misleading: it's intc/openpic_kvm, not kvm/openpic. Alex,
please fix when squashing.
Am 12.06.2013 22:32, schrieb Scott Wood:
> Enables support for the in-kernel MPIC that thas been merged into the
> KVM next branch. This includes irqfd/KVM_IRQ_LINE support from Alex
> Graf (along with some other improvements).
>
> Note from Alex regarding kvm_irqchip_create():
>
> On x86, one would call kvm_irqchip_create() to initialize an
> in-kernel interrupt controller. That function then goes ahead and
> initializes global capability variables as well as the default irq
> routing table.
>
> On ppc, we can't call kvm_irqchip_create() because we can have
> different types of interrupt controllers. So we want to do all the
> things that function would do for us in the in-kernel device init
> handler.
>
> Signed-off-by: Scott Wood <scottwood@freescale.com>
> ---
> v2: fix "llx" -> PRI_x64, and remove some broken leftover code
> involving reg_base.
> ---
> default-configs/ppc-softmmu.mak | 1 +
> default-configs/ppc64-softmmu.mak | 1 +
This breaks KVM-enabled ppcemb-softmmu build with unresolved symbol
kvm_openpic_connect_vcpu() in e500.o. Fix in my patch:
http://patchwork.ozlabs.org/patch/251731/
Because intc/openpic.c gets rebuilt for each of the three ppc*-softmmu,
I added a patch to my qom-cpu-10 series to stop that for openpic. For
openpic_kvm I believe that won't be possible due to sysemu/kvm.h's
inline stubs.
Andreas
> hw/intc/Makefile.objs | 1 +
> hw/intc/openpic_kvm.c | 250 +++++++++++++++++++++++++++++++++++++
> hw/ppc/e500.c | 79 +++++++++++-
> include/hw/ppc/openpic.h | 2 +-
> 6 files changed, 328 insertions(+), 6 deletions(-)
> create mode 100644 hw/intc/openpic_kvm.c
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-06-16 19:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 20:32 [Qemu-devel] [PATCH v2] kvm/openpic: in-kernel mpic support Scott Wood
2013-06-12 20:56 ` Alexander Graf
2013-06-13 11:01 ` Andreas Färber
2013-06-13 17:32 ` Scott Wood
2013-06-14 14:59 ` Andreas Färber
2013-06-14 22:57 ` Scott Wood
2013-06-16 19:11 ` Andreas Färber
2013-06-19 22:25 ` Scott Wood
2013-06-16 18:32 ` [Qemu-devel] [PATCH ppc-next fixup] intc/openpic_kvm: Fix QOM and build issues Andreas Färber
2013-06-16 19:34 ` Andreas Färber
2013-06-16 19:25 ` Andreas Färber [this message]
2013-06-19 21:49 ` [Qemu-devel] [PATCH v2] kvm/openpic: in-kernel mpic support Scott Wood
2013-07-01 16:54 ` Andreas Färber
2013-06-16 19:30 ` [Qemu-devel] [PATCH ppc-next fixup v2] intc/openpic_kvm: Fix QOM and build issues Andreas Färber
2013-06-18 12:39 ` Alexander Graf
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=51BE1110.5000107@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=scottwood@freescale.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).