From: Michael Ellerman <mpe@ellerman•id.au>
To: Nicholas Piggin <npiggin@gmail•com>, linuxppc-dev@lists•ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail•com>
Subject: Re: [RFC PATCH] powerpc: improve accounting of non maskable interrupts
Date: Mon, 31 Jul 2017 20:17:13 +1000 [thread overview]
Message-ID: <87efsw6hcm.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20170729132257.8132-1-npiggin@gmail.com>
Nicholas Piggin <npiggin@gmail•com> writes:
> This fixes a case of double counting MCEs on PowerNV.
>
> Adds a counter for the system reset interrupt, which will
> see more use as a debugging NMI.
>
> Adds a soft-NMI counter for the 64s watchdog. Although this could cause
> confusion because it only fires when interrupts are soft-disabled, so it
> won't increment much even when the watchdog is running.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail•com>
> ---
> I can split these out or drop any objectionable bits. At least the
> MCE we should fix, not sure if the other bits are wanted.
Yeah if you can split it please that would be good.
I'm not sure how useful it is to count the SOFT NMIs. I guess it's not
much overhead so we may as well, if nothing else it might be handy for
us debugging.
If you can make the ifdef look less horrendous that would be great :D -
perhaps a kconfig symbol that keys off both.
cheers
next prev parent reply other threads:[~2017-07-31 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-29 13:22 [RFC PATCH] powerpc: improve accounting of non maskable interrupts Nicholas Piggin
2017-07-31 10:17 ` Michael Ellerman [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-29 13:22 Nicholas Piggin
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=87efsw6hcm.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=npiggin@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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