From: Sam Mendoza-Jonas <sam@mendozajonas.com>
To: Russell Currey <ruscur@russell.cc>
Cc: Gavin Shan <gwshan@linux.vnet.ibm.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/eeh: Fix PE location code
Date: Thu, 21 Jan 2016 11:08:42 +1100 [thread overview]
Message-ID: <20160121000842.GB10361@localhost.localdomain> (raw)
In-Reply-To: <1453262173.1201.2.camel@russell.cc>
On Wed, Jan 20, 2016 at 02:56:13PM +1100, Russell Currey wrote:
> On Wed, 2015-12-02 at 16:25 +1100, Gavin Shan wrote:
> > In eeh_pe_loc_get(), the PE location code is retrieved from the
> > "ibm,loc-code" property of the device node for the bridge of the
> > PE's primary bus. It's not correct because the property indicates
> > the parent PE's location code.
> >
> > This reads the correct PE location code from "ibm,io-base-loc-code"
> > or "ibm,slot-location-code" property of PE parent bus's device node.
> >
> > Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
> > ---
>
> Tested-by: Russell Currey <ruscur@russell.cc>
Thanks Russell!
W.R.T including this in stable, I don't believe anything actively breaks
without the patch, but in the event of an EEH freeze the wrong slot for
the device will be identified, making troubleshooting more difficult.
> > arch/powerpc/kernel/eeh_pe.c | 33 +++++++++++++++------------------
> > 1 file changed, 15 insertions(+), 18 deletions(-)
> >
> > diff --git a/arch/powerpc/kernel/eeh_pe.c b/arch/powerpc/kernel/eeh_pe.c
> > index 8654cb1..ca9e537 100644
> > --- a/arch/powerpc/kernel/eeh_pe.c
> > +++ b/arch/powerpc/kernel/eeh_pe.c
> > @@ -883,32 +883,29 @@ void eeh_pe_restore_bars(struct eeh_pe *pe)
> > const char *eeh_pe_loc_get(struct eeh_pe *pe)
> > {
> > struct pci_bus *bus = eeh_pe_bus_get(pe);
> > - struct device_node *dn = pci_bus_to_OF_node(bus);
> > + struct device_node *dn;
> > const char *loc = NULL;
> >
> > - if (!dn)
> > - goto out;
> > + while (bus) {
> > + dn = pci_bus_to_OF_node(bus);
> > + if (!dn) {
> > + bus = bus->parent;
> > + continue;
> > + }
> >
> > - /* PHB PE or root PE ? */
> > - if (pci_is_root_bus(bus)) {
> > - loc = of_get_property(dn, "ibm,loc-code", NULL);
> > - if (!loc)
> > + if (pci_is_root_bus(bus))
> > loc = of_get_property(dn, "ibm,io-base-loc-
> > code", NULL);
> > + else
> > + loc = of_get_property(dn, "ibm,slot-location-
> > code",
> > + NULL);
> > +
> > if (loc)
> > - goto out;
> > + return loc;
> >
> > - /* Check the root port */
> > - dn = dn->child;
> > - if (!dn)
> > - goto out;
> > + bus = bus->parent;
> > }
> >
> > - loc = of_get_property(dn, "ibm,loc-code", NULL);
> > - if (!loc)
> > - loc = of_get_property(dn, "ibm,slot-location-code",
> > NULL);
> > -
> > -out:
> > - return loc ? loc : "N/A";
> > + return "N/A";
> > }
> >
> > /**
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
next prev parent reply other threads:[~2016-01-21 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 5:25 [PATCH] powerpc/eeh: Fix PE location code Gavin Shan
2016-01-19 22:41 ` Joel Stanley
2016-01-20 3:56 ` Russell Currey
2016-01-21 0:08 ` Sam Mendoza-Jonas [this message]
2016-01-21 5:59 ` Stewart Smith
2016-01-29 1:58 ` Michael Ellerman
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=20160121000842.GB10361@localhost.localdomain \
--to=sam@mendozajonas.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ruscur@russell.cc \
/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).