From: "Cédric Le Goater" <clg@kaod.org>
To: Andrea Bolognani <abologna@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
David Gibson <david@gibson.dropbear.id.au>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] ppc/pnv: Add model for Power8 PHB3 PCIe Host bridge
Date: Wed, 27 Jun 2018 15:03:28 +0200 [thread overview]
Message-ID: <06a913d3-d694-0be4-c04b-bc6c8c8c88c6@kaod.org> (raw)
In-Reply-To: <c071d87d3b3ad43c7c17de17ef5116ada666ef6f.camel@redhat.com>
On 06/27/2018 12:40 PM, Andrea Bolognani wrote:
> On Wed, 2018-06-27 at 18:41 +1000, Benjamin Herrenschmidt wrote:
>> On Wed, 2018-06-27 at 09:46 +0200, Cédric Le Goater wrote:
>>> So the "IBM PHB3 PCIE Root Port" is already user createable.
>>>
>>> I can take a look at user createable PHB3s. I think this is OK from a model
>>> perspective. The object is rather standalone, it needs the machine for
>>> the XICS fabric and a couple of ids, phb id and chip id. These can come
>>> from the command line.
>>>
>>> We want at least one PHB3 per socket/chip though.
>>
>> We don't want the user to specify the SCOM addresses though (for the
>> MMIO windows we should get skiboot to assign them).
>>
>> If the user gets to specify a thing it would be which of the 3 or 4 HW
>> PHBs of the chip it is, the SCOM addresses gets deduced.
>
> For pSeries guests libvirt will either automatically create, or
> allow users to configure manually, PHBs with something like
>
> <controller type='pci' index='1' model='pci-root'>
> <target index='1'/>
> </controller>
>
> which is ultimately converted to
>
> -device spapr-pci-host-bridge,index=1,id=pci.1
>
> Ideally the interface for PowerNV guests can be made to be similar
> if not identical at the libvirt level, without having to add too
> many hacks... It would certainly help a lot if the QEMU interface
> for PowerNV PHBs didn't stray too far from the above.
>
I think that we will need an extra attribute to specify the chip, but
only in the case of a multichip system, which is not the common scenario.
So the 'index' attribute should work fine.
Thanks,
C.
next prev parent reply other threads:[~2018-06-27 13:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 13:59 [Qemu-devel] [PATCH] ppc/pnv: Add model for Power8 PHB3 PCIe Host bridge Cédric Le Goater
2018-06-26 15:57 ` Andrea Bolognani
2018-06-26 17:02 ` Cédric Le Goater
2018-06-27 10:22 ` Andrea Bolognani
2018-06-27 12:18 ` Cédric Le Goater
2018-06-27 19:48 ` Cédric Le Goater
2018-06-28 3:59 ` David Gibson
2018-06-28 8:00 ` Andrea Bolognani
2018-06-28 10:04 ` Cédric Le Goater
2018-06-28 11:40 ` Andrea Bolognani
2018-06-28 12:20 ` Cédric Le Goater
2018-06-28 13:05 ` Cédric Le Goater
2018-06-28 12:14 ` Benjamin Herrenschmidt
2018-07-02 6:23 ` David Gibson
2018-06-26 22:21 ` Benjamin Herrenschmidt
2018-06-27 0:35 ` Michael S. Tsirkin
2018-06-27 1:38 ` Benjamin Herrenschmidt
2018-06-27 2:39 ` Michael S. Tsirkin
2018-06-27 7:28 ` David Gibson
2018-06-27 7:46 ` Cédric Le Goater
2018-06-27 8:41 ` Benjamin Herrenschmidt
2018-06-27 10:40 ` Andrea Bolognani
2018-06-27 13:03 ` Cédric Le Goater [this message]
2018-06-27 11:51 ` Cédric Le Goater
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=06a913d3-d694-0be4-c04b-bc6c8c8c88c6@kaod.org \
--to=clg@kaod.org \
--cc=abologna@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--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).