From: Marcel Apfelbaum <marcel@redhat.com>
To: Cao jin <caoj.fnst@cn.fujitsu.com>, qemu-devel@nongnu.org
Cc: marcel@redhat.com, ehabkost@redhat.com, laine@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH V4] hw/pxb: add chassis_nr property
Date: Tue, 15 Mar 2016 13:44:23 +0200 [thread overview]
Message-ID: <56E7F597.9060506@redhat.com> (raw)
In-Reply-To: <56E7C13B.6010601@cn.fujitsu.com>
On 03/15/2016 10:00 AM, Cao jin wrote:
> Hi,
>
> On 03/03/2016 10:18 PM, Marcel Apfelbaum wrote:
>> Add a chassis_nr property instead of using PXB bus number
>> as internal bridge's chassis nr.
>>
>> Suggested-by: Michael S. Tsirkin <mst@redhat.com>
>> Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
>> ---
>> v3->v4:
>> - re-coded to fit current codebase
>> v2->v3:
>> - use bus nr if chassis nr is 0 (Micahel S. Tsirkin)
>> v1->v2:
>> - Rebased on master
>>
>> docs/pci_expander_bridge.txt | 7 +++----
>> hw/pci-bridge/pci_expander_bridge.c | 21 +++++++++++++++++++--
>> 2 files changed, 22 insertions(+), 6 deletions(-)
>>
>
>>
>> @@ -286,6 +294,8 @@ static Property pxb_dev_properties[] = {
>> /* Note: 0 is not a legal a PXB bus number. */
>
> better remove the latter "a", or I guess it will conflict with my previous pxb cleanup patch.
sure, thanks for bringing it up.
>
>> DEFINE_PROP_UINT8("bus_nr", PXBDev, bus_nr, 0),
>> DEFINE_PROP_UINT16("numa_node", PXBDev, numa_node, NUMA_NODE_UNASSIGNED),
>> + /* Note: 0 is not a legal chassis number. */
>> + DEFINE_PROP_UINT8("chassis_nr", PXBDev, chassis_nr, 0),
>> DEFINE_PROP_END_OF_LIST(),
>> };
>>
>> @@ -322,6 +332,13 @@ static int pxb_pcie_dev_initfn(PCIDevice *dev)
>> return pxb_dev_init_common(dev, true);
>> }
>>
>> +static Property pxb_pcie_dev_properties[] = {
>> + /* Note: 0 is not a legal a PXB bus number. */
>
> likewise
ok
>
>> + DEFINE_PROP_UINT8("bus_nr", PXBDev, bus_nr, 0),
>> + DEFINE_PROP_UINT16("numa_node", PXBDev, numa_node, NUMA_NODE_UNASSIGNED),
>> + DEFINE_PROP_END_OF_LIST(),
>> +};
>
> And I have another personal question: In qemu design, it seems every pci bridge reside in a separate chassis, what`s benefit? why don`t put them all in the main chassis?
Please have a look on pci-to-pci bridge specification, chapter 13, slot numbering.
Thanks for the review,
Marcel
>
next prev parent reply other threads:[~2016-03-15 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 14:18 [Qemu-devel] [PATCH V4] hw/pxb: add chassis_nr property Marcel Apfelbaum
2016-03-14 15:21 ` Marcel Apfelbaum
2016-03-15 8:00 ` Cao jin
2016-03-15 11:44 ` Marcel Apfelbaum [this message]
2016-03-17 10:02 ` Cao jin
2016-03-24 15:34 ` Marcel Apfelbaum
2016-03-25 6:28 ` Cao jin
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=56E7F597.9060506@redhat.com \
--to=marcel@redhat.com \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=ehabkost@redhat.com \
--cc=laine@redhat.com \
--cc=mst@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).