From: "Andreas Färber" <afaerber@suse.de>
To: Alexander Graf <agraf@suse.de>,
David Gibson <david@gibson.dropbear.id.au>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
qemu-ppc@nongnu.org,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 2/2] pseries: Configure PCI bridge using properties
Date: Wed, 14 Mar 2012 14:30:15 +0100 [thread overview]
Message-ID: <4F609D67.10809@suse.de> (raw)
In-Reply-To: <20120313035024.GH24916@truffala.fritz.box>
Am 13.03.2012 04:50, schrieb David Gibson:
> On Sat, Mar 10, 2012 at 11:40:41PM +0100, Alexander Graf wrote:
>>
>> On 08.03.2012, at 02:12, David Gibson wrote:
>>
>>> Currently, the function spapr_create_phb() uses its parameters to
>>> initialize the correct memory windows for the new PCI Host Bridge
>>> (PHB). This is not the way things are supposed to be done with qdevs,
>>> and means you can't create extra PHBs easily using -device.
>>>
>>> Since pSeries machines can and do have many PHBs with various
>>> configurations, this is a real limitation, not just a theoretical.
>>> This patch, therefore, alters the PHB initialization code to use qdev
>>> properties to set these parameters of the new bridge, moving most of
>>> the code from spapr_create_phb() to spapr_phb_init().
>>>
>>> While we're at it, we change the naming of each PCI bus and its
>>> associated memory regions to be less arbitrary and make it easier to
>>> relate the guest and qemu views of memory to each other.
>>>
>>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>>> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
>>
>> Andreas, could you please (n)ack this version?
>
> Actually, can you review and merge this updated version instead.
> Turns out that libvirt and some other tools assume that there will be
> a PCI bus named simply "pci", which is no longer true with the patch
> above (we call each bus "pci@XXXXXX" to match the guest's device
> tree). The revised version calls the default bus simply "pci" to work
> around libvirt's PC centrism, and allows manually added extra busses
> to be named explicitly with a property, defaulting to "pci@XXXXX".
I was happy with David's improvements but didn't feel comfortable acking
the overall patch.
Reviewed-by: Andreas Färber <afaerber@suse.de>
One minor improvement in case this gets gespun:
* spapr_phb_info could be made static const (was/is static)
Andreas
--
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:[~2012-03-14 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 1:12 [Qemu-devel] [0/2] Updated pseries patches David Gibson
2012-03-08 1:12 ` [Qemu-devel] [PATCH 1/2] pseries: Add support for level interrupts to XICS David Gibson
2012-03-10 22:41 ` Alexander Graf
2012-03-08 1:12 ` [Qemu-devel] [PATCH 2/2] pseries: Configure PCI bridge using properties David Gibson
2012-03-10 22:40 ` Alexander Graf
2012-03-13 3:50 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2012-03-14 13:30 ` Andreas Färber [this message]
2012-03-14 17:11 ` 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=4F609D67.10809@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).