linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
	ruscur@russell.cc, gwshan@linux.vnet.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] powerpc/eeh: trivial fix to non-conventional PCI address output on EEH log
Date: Sun, 24 Jul 2016 22:50:02 -0300	[thread overview]
Message-ID: <5795704A.5000200@linux.vnet.ibm.com> (raw)
In-Reply-To: <87fuqy1r3i.fsf@concordia.ellerman.id.au>

On 07/24/2016 09:47 PM, Michael Ellerman wrote:
> "Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com> writes:
>
>> This is a very minor/trivial fix for the output of PCI address on EEH logs.
>> The PCI address on "OF node" field currently is using ":" as a separator
>> for the function, but the usual separator is ".". This patch changes the
>> separator for dot, so the PCI address is printed as usual.
>>
>> No functional changes were introduced.
>
> What consumes the log? Can it cope with us changing the formatting?

Michael, as far as I understand (Russel and Gavin surely knows better 
and can correct me if I'm wrong) the only consumer that doesn't just 
output the error information to screen is pseries' get_log handler, 
which will pass this log information through a rtas_call 
(ibm_slot_error_detail).

Now, I imagine this information might be consumed in the end for the 
FSP, by reporting EEH errors there, but my testing in one LPAR showed me 
no errors in FSP after an EEH (without the patch applied). Maybe I'm 
missing a FSP configuration to be able to show the errors there?

Thanks,


Guilherme


>
> cheers
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>

  parent reply	other threads:[~2016-07-25  1:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-22 17:05 [PATCH] powerpc/eeh: trivial fix to non-conventional PCI address output on EEH log Guilherme G. Piccoli
2016-07-25  0:17 ` Gavin Shan
2016-07-25  0:47 ` Michael Ellerman
2016-07-25  1:46   ` Gavin Shan
2016-07-25  1:54     ` Guilherme G. Piccoli
2016-08-03 13:50     ` Guilherme G. Piccoli
2016-07-25  1:50   ` Guilherme G. Piccoli [this message]
2016-08-09 11:26 ` 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=5795704A.5000200@linux.vnet.ibm.com \
    --to=gpiccoli@linux.vnet.ibm.com \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.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).