From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] spapr/pci: populate PCI DT in reverse order
Date: Thu, 17 Dec 2015 09:43:29 +0100 [thread overview]
Message-ID: <20151217094329.112a3bc9@bahia.local> (raw)
In-Reply-To: <20151203155317.46a4f446@bahia.local>
On Thu, 3 Dec 2015 15:53:17 +0100
Greg Kurz <gkurz@linux.vnet.ibm.com> wrote:
> On Tue, 1 Dec 2015 22:48:38 +0100
> Thomas Huth <thuth@redhat.com> wrote:
>
> > On 30/11/15 11:45, Greg Kurz wrote:
> > > Since commit 1d2d974244c6 "spapr_pci: enumerate and add PCI device tree", QEMU
> > > populates the PCI device tree in the opposite order compared to SLOF.
> > >
> > > Before 1d2d974244c6:
> > >
> > > Populating /pci@800000020000000
> > > 00 0000 (D) : 1af4 1000 virtio [ net ]
> > > 00 0800 (D) : 1af4 1001 virtio [ block ]
> > > 00 1000 (D) : 1af4 1009 virtio [ network ]
> > > Populating /pci@800000020000000/unknown-legacy-device@2
> > >
> > >
> > > 7e5294b8 : /pci@800000020000000
> > > 7e52b998 : |-- ethernet@0
> > > 7e52c0c8 : |-- scsi@1
> > > 7e52c7e8 : +-- unknown-legacy-device@2 ok
> > >
> > > Since 1d2d974244c6:
> > >
> > > Populating /pci@800000020000000
> > > 00 1000 (D) : 1af4 1009 virtio [ network ]
> > > Populating /pci@800000020000000/unknown-legacy-device@2
> > > 00 0800 (D) : 1af4 1001 virtio [ block ]
> > > 00 0000 (D) : 1af4 1000 virtio [ net ]
> > >
> > >
> > > 7e5e8118 : /pci@800000020000000
> > > 7e5ea6a0 : |-- unknown-legacy-device@2
> > > 7e5eadb8 : |-- scsi@1
> > > 7e5eb4d8 : +-- ethernet@0 ok
> > >
> > > This behaviour change is not actually a bug since no assumptions should be
> > > made on DT ordering. But it has no real justification either, other than
> > > being the consequence of the way fdt_add_subnode() inserts new elements
> > > to the front of the FDT rather than adding them to the tail.
> > >
> > > This patch reverts to the historical SLOF ordering by walking PCI devices in
> > > reverse order.
> >
> > I've applied your patch here locally, and indeed, the device tree looks
> > nicer to me, too, when the nodes are listed in ascending order.
> >
> > Tested-by: Thomas Huth <thuth@redhat.com>
> >
> >
>
Ping ?
> Thanks for testing !
>
> Cheers.
>
> --
> Greg
>
>
next prev parent reply other threads:[~2015-12-17 8:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 10:45 [Qemu-devel] [PATCH] spapr/pci: populate PCI DT in reverse order Greg Kurz
2015-12-01 21:48 ` Thomas Huth
2015-12-03 14:53 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2015-12-17 8:43 ` Greg Kurz [this message]
2015-12-21 1:56 ` David Gibson
2015-12-21 8:09 ` Greg Kurz
2015-12-23 5:47 ` Nikunj A Dadhania
-- strict thread matches above, loose matches on Subject: below --
2017-02-22 10:56 [Qemu-devel] " Greg Kurz
2017-02-27 22:20 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2017-03-01 1:07 ` David Gibson
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=20151217094329.112a3bc9@bahia.local \
--to=gkurz@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
/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).