From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Russell Currey <ruscur@russell.cc>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [v2,1/3] powerpc/powernv/pci: Reduce spam when dumping PEST
Date: Thu, 29 Jun 2017 22:21:09 +1000 (AEST) [thread overview]
Message-ID: <3wyzKK2P0Lz9s82@ozlabs.org> (raw)
In-Reply-To: <20170614042000.1258-1-ruscur@russell.cc>
On Wed, 2017-06-14 at 04:19:58 UTC, Russell Currey wrote:
> Dumping the PE State Tables (PEST) can be highly verbose if a number of PEs
> are affected, especially in the case where the whole PHB is frozen and 512
> lines get printed. Check for duplicates when dumping the PEST to reduce
> useless output.
>
> For example:
>
> PE[0f8] A/B: 9700002600000000 80000080d00000f8
> PE[0f9] A/B: 8000000000000000 0000000000000000
> PE[..0fe] A/B: as above
> PE[0ff] A/B: 8440002b00000000 0000000000000000
>
> instead of:
>
> PE[0f8] A/B: 9700002600000000 80000080d00000f8
> PE[0f9] A/B: 8000000000000000 0000000000000000
> PE[0fa] A/B: 8000000000000000 0000000000000000
> PE[0fb] A/B: 8000000000000000 0000000000000000
> PE[0fc] A/B: 8000000000000000 0000000000000000
> PE[0fd] A/B: 8000000000000000 0000000000000000
> PE[0fe] A/B: 8000000000000000 0000000000000000
> PE[0ff] A/B: 8440002b00000000 0000000000000000
>
> and you can imagine how much worse it can get for 512 PEs.
>
> Signed-off-by: Russell Currey <ruscur@russell.cc>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/31bbd45af313c3b1cdaa98e5a2de65
cheers
prev parent reply other threads:[~2017-06-29 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 4:19 [PATCH v2 1/3] powerpc/powernv/pci: Reduce spam when dumping PEST Russell Currey
2017-06-14 4:19 ` [PATCH v2 2/3] powerpc/powernv/pci: Dynamically allocate PHB diag data Russell Currey
2017-06-14 4:20 ` [PATCH v2 3/3] powerpc/powernv/pci: Add support for PHB4 diagnostics Russell Currey
2017-06-29 12:21 ` Michael Ellerman [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=3wyzKK2P0Lz9s82@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--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).