From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>,
Daniel Walker <danielwa@cisco.com>,
"Guilherme G. Piccoli" <guilherme@gpiccoli.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
xe-kernel@external.cisco.com, linux-kernel@vger.kernel.org,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org,
Mauro Rodrigues <maurosr@linux.vnet.ibm.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] arch: powerpc: pci-common: fix wrong return value check on phd_id
Date: Thu, 21 Jun 2018 10:38:46 +1000 [thread overview]
Message-ID: <c03e5e63fb64d2bf503bb2e00101bf352e396ceb.camel@kernel.crashing.org> (raw)
In-Reply-To: <87in6dvv89.fsf@concordia.ellerman.id.au>
On Thu, 2018-06-21 at 10:28 +1000, Michael Ellerman wrote:
>
> That's true, though I think yours is the first report we've had of
> problems.
>
> The old behaviour relied on device tree ordering in nearly all cases, so
> you basically get whatever order your firmware happened to flatten the
> device tree in.
>
> That tends to be consistent on a single system or with a single firmware
> version, but it's not stable in general. If your firmware changes, or
> you kexec then the ordering can change.
>
> So I'd definitely prefer we didn't go back to that behaviour, because
> it's basically "random order".
>
> If there's anything you can do on your end to cope with the ne
I think the numbering change has to be coped with. However:
The main issue I see is that it somewhat hard wires that "reg"
is a 64-bit property with the "interesting" bits in the bottom,
and that "interesting" part somewhat happens to fit in 16-bits.
It would have been better to get the full address out of reg (using the
appropriate size specified in the parent #address-cells) and hash it.
Cheers,
Ben.
prev parent reply other threads:[~2018-06-21 0:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 16:57 [PATCH] arch: powerpc: pci-common: fix wrong return value check on phd_id Daniel Walker
2018-06-19 15:29 ` Guilherme Piccoli
[not found] ` <c56f43f5-7902-f7c8-20e1-955ad064c4d0@cisco.com>
2018-06-19 16:26 ` Guilherme G. Piccoli
2018-06-19 16:57 ` Daniel Walker
2018-06-21 0:28 ` Michael Ellerman
2018-06-21 0:38 ` Benjamin Herrenschmidt [this message]
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=c03e5e63fb64d2bf503bb2e00101bf352e396ceb.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=danielwa@cisco.com \
--cc=guilherme@gpiccoli.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maurosr@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=xe-kernel@external.cisco.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).