From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 3/3] spapr: make irq customizable via qdev
Date: Tue, 07 Jun 2011 11:05:42 +0200 [thread overview]
Message-ID: <4DEDE9E6.5030304@redhat.com> (raw)
In-Reply-To: <m3r576axl3.fsf@blackfin.pond.sub.org>
On 06/07/2011 09:51 AM, Markus Armbruster wrote:
>> > diff --git a/hw/spapr_vio.c b/hw/spapr_vio.c
>> > index 6f34159..a193caa 100644
>> > --- a/hw/spapr_vio.c
>> > +++ b/hw/spapr_vio.c
>> > @@ -52,6 +52,10 @@
>> > static struct BusInfo spapr_vio_bus_info = {
>> > .name = "spapr-vio",
>> > .size = sizeof(VIOsPAPRBus),
>> > + .props = (Property[]) {
>> > + DEFINE_PROP_UINT32("irq", VIOsPAPRDevice, vio_irq_num, 0), \
>> > + DEFINE_PROP_END_OF_LIST(),
>> > + },
>> > };
>
> Out of this patch's scope, but I need to ask anyway: do devices on a
> spapr-vio bus have a unique address? If yes, what is it?
That would be the "reg" value in DEFINE_SPAPR_PROPERTIES (patch 2). I
didn't make it a bus property because the default values varies
according to the device type.
> Is it okay to share interrupts?
Seems to work. :)
Paolo
next prev parent reply other threads:[~2011-06-07 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 14:16 [Qemu-devel] [PATCH v3 0/3] spapr qdevification Paolo Bonzini
2011-06-06 14:16 ` [Qemu-devel] [PATCH v3 1/3] spapr: proper qdevification Paolo Bonzini
2011-06-06 14:16 ` [Qemu-devel] [PATCH v3 2/3] spapr: prepare for qdevification of irq Paolo Bonzini
2011-06-06 14:16 ` [Qemu-devel] [PATCH v3 3/3] spapr: make irq customizable via qdev Paolo Bonzini
2011-06-07 7:51 ` Markus Armbruster
2011-06-07 9:05 ` Paolo Bonzini [this message]
2011-06-07 9:19 ` Markus Armbruster
2011-06-07 11:14 ` Paolo Bonzini
2011-07-06 11:32 ` [Qemu-devel] [PATCH v3 0/3] spapr qdevification Paolo Bonzini
2011-07-07 14:15 ` 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=4DEDE9E6.5030304@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).