From: "Cédric Le Goater" <clg@kaod.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Andrea Bolognani <abologna@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/2] ppc/pnv: Add model for Power8 PHB3 PCIe Host bridge
Date: Fri, 27 Jul 2018 10:25:22 +0200 [thread overview]
Message-ID: <d743b921-d1bc-2bc8-cbad-cd1a90d33850@kaod.org> (raw)
In-Reply-To: <e642d9da57a167aeb5ae65566dd61317fcd37d2c.camel@kernel.crashing.org>
On 07/27/2018 10:08 AM, Benjamin Herrenschmidt wrote:
> On Fri, 2018-07-27 at 15:32 +1000, David Gibson wrote:
>>
>>>> What is this pci bridge representing? I know PCI-e PHBs typically
>>>> have a pseudo P2P bridge right under them, but isn't that represnted
>>>> by the root complex above?
>>>
>>> This is the legacy pci bridge under the pcie bus.
>>
>> Ah, ok. Didn't realise there was a vanilla PCI bridge built in.
>
> There isn't. That should probably be created by the machine.
Each PHB creates a pci-bridge device and the PCI bus that comes with it.
It makes things easier to define PCI devices.
It is still quite complex ... Here is a sample :
qemu-system-ppc64 -m 2G -machine powernv \
-cpu POWER8 -smp 2,cores=2,threads=1 -accel tcg,thread=multi \
-kernel ./zImage.epapr -initrd ./rootfs.cpio.xz -bios ./skiboot.lid \
\
-device megasas,id=scsi0,bus=pci.0,addr=0x1 \
-drive file=./rhel7-ppc64le.qcow2,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none \
-device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=2 \
\
-device ich9-ahci,id=sata0,bus=pci.1,addr=0x1 \
-drive file=./ubuntu-ppc64le.qcow2,if=none,id=drive0,format=qcow2,cache=none \
-device ide-hd,bus=sata0.0,unit=0,drive=drive0,id=ide,bootindex=1 \
-device e1000,netdev=net0,mac=C0:FF:EE:00:00:02,bus=pci.1,addr=0x2 \
-netdev bridge,helper=/usr/libexec/qemu-bridge-helper,br=virbr0,id=net0 \
-device nec-usb-xhci,bus=pci.1,addr=0x7 \
>>> Here is is the qdev hierarchy :
>>>
>>> dev: pnv-phb3, id ""
>>> index = 0 (0x0)
>>> chip-id = 0 (0x0)
>>> bus: phb3-root-bus
>>> type pnv-phb3-root-bus
>>> dev: pnv-phb3-rc, id ""
>>> power_controller_present = true
>>> chassis = 0 (0x0)
>>> slot = 1 (0x1)
>>> port = 0 (0x0)
>>> aer_log_max = 8 (0x8)
>>> addr = 00.0
>>> romfile = ""
>>> rombar = 1 (0x1)
>>> multifunction = false
>>> command_serr_enable = true
>>> x-pcie-lnksta-dllla = true
>>> x-pcie-extcap-init = true
>>> class PCI bridge, addr 00:00.0, pci id 1014:03dc (sub 0000:0000)
>>> bus: pcie.0
>>> type PCIE
>>> dev: pci-bridge, id ""
>>> chassis_nr = 128 (0x80)
>>> msi = "off"
>>> shpc = false
>>> addr = 00.0
>>> romfile = ""
>>> rombar = 1 (0x1)
>>> multifunction = false
>>> command_serr_enable = true
>>> x-pcie-lnksta-dllla = true
>>> x-pcie-extcap-init = true
>>> class PCI bridge, addr 00:00.0, pci id 1b36:0001 (sub 0000:0000)
>>> bus: pci.0
>>> type PCI
>>>
>>> [ ... ]
>>>
>>>>> +static const PropertyInfo pnv_phb3_phb_id_propinfo = {
>>>>> + .name = "irq",
>>>>> + .get = pnv_phb3_get_phb_id,
>>>>> + .set = pnv_phb3_set_phb_id,
>>>>> +};
>>>>
>>>> Can't you use a static DeviceProps style property for this, which is a
>>>> bit simpler?
>>>
>>> OK. We will address user creatable PHBs in some other way. Most
>>> certainly in the realize routine like you suggested.
>>>
>>> Thanks,
>>>
>>> C.
>>>
>>
>
next prev parent reply other threads:[~2018-07-27 8:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 8:36 [Qemu-devel] [PATCH v2 0/2] ppc/pnv: Add model for Power8 PHB3 PCIe Host bridge Cédric Le Goater
2018-06-28 8:36 ` [Qemu-devel] [PATCH v2 1/2] " Cédric Le Goater
2018-07-09 7:22 ` Cédric Le Goater
2018-07-18 6:13 ` David Gibson
2018-07-18 6:12 ` David Gibson
2018-07-18 8:03 ` Benjamin Herrenschmidt
2018-07-23 4:16 ` David Gibson
2018-07-23 23:55 ` Benjamin Herrenschmidt
2018-07-24 2:14 ` David Gibson
2018-07-24 3:49 ` Benjamin Herrenschmidt
2018-07-24 4:10 ` David Gibson
2018-07-23 21:35 ` Cédric Le Goater
2018-07-23 21:37 ` Cédric Le Goater
2018-07-24 1:29 ` David Gibson
2018-07-23 21:38 ` Cédric Le Goater
2018-07-24 12:18 ` Cédric Le Goater
2018-07-27 5:32 ` David Gibson
2018-07-27 7:33 ` Cédric Le Goater
2018-07-27 8:08 ` Benjamin Herrenschmidt
2018-07-27 8:25 ` Cédric Le Goater [this message]
2018-07-27 8:43 ` Benjamin Herrenschmidt
2018-07-27 9:19 ` Cédric Le Goater
2018-07-30 8:56 ` Cédric Le Goater
2018-07-26 9:03 ` Cédric Le Goater
2018-07-26 22:36 ` Benjamin Herrenschmidt
2018-07-27 7:16 ` Cédric Le Goater
2018-07-27 8:18 ` Benjamin Herrenschmidt
2018-06-28 8:36 ` [Qemu-devel] [PATCH v2 2/2] ppc/pnv: make the PHB3 devices user creatable Cédric Le Goater
2018-07-01 18:33 ` [Qemu-devel] [PATCH v2 0/2] ppc/pnv: Add model for Power8 PHB3 PCIe Host bridge no-reply
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=d743b921-d1bc-2bc8-cbad-cd1a90d33850@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).