From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45336) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fY7sF-00037N-PW for qemu-devel@nongnu.org; Wed, 27 Jun 2018 06:40:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fY7sA-0005nz-Pj for qemu-devel@nongnu.org; Wed, 27 Jun 2018 06:40:31 -0400 Message-ID: From: Andrea Bolognani Date: Wed, 27 Jun 2018 12:40:21 +0200 In-Reply-To: <9f9a4454bec8e7009a02d544d7a98f6215bd1fa0.camel@kernel.crashing.org> References: <20180626135928.23950-1-clg@kaod.org> <20180627033321-mutt-send-email-mst@kernel.org> <1d70c0f9179990cd33d7c82c5190179e60ae4ce3.camel@kernel.crashing.org> <20180627072825.GH14434@umbus.fritz.box> <65c545f3-6279-62af-9bd8-2be93a3d7d18@kaod.org> <9f9a4454bec8e7009a02d544d7a98f6215bd1fa0.camel@kernel.crashing.org> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH] ppc/pnv: Add model for Power8 PHB3 PCIe Host bridge List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Benjamin Herrenschmidt , =?ISO-8859-1?Q?C=E9dric?= Le Goater , David Gibson Cc: "Michael S. Tsirkin" , qemu-ppc@nongnu.org, qemu-devel@nongnu.org, Marcel Apfelbaum On Wed, 2018-06-27 at 18:41 +1000, Benjamin Herrenschmidt wrote: > On Wed, 2018-06-27 at 09:46 +0200, C=C3=A9dric Le Goater wrote: > > So the "IBM PHB3 PCIE Root Port" is already user createable. > >=20 > > 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 fo= r=20 > > the XICS fabric and a couple of ids, phb id and chip id. These can co= me > > from the command line. > >=20 > > We want at least one PHB3 per socket/chip though.=20 >=20 > We don't want the user to specify the SCOM addresses though (for the > MMIO windows we should get skiboot to assign them). >=20 > 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 which is ultimately converted to -device spapr-pci-host-bridge,index=3D1,id=3Dpci.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. --=20 Andrea Bolognani / Red Hat / Virtualization