From: Don Zickus <dzickus@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: x86@kernel.org, "Peter Zijlstra" <peterz@infradead.org>,
ak@linux.intel.com, gong.chen@linux.intel.com,
LKML <linux-kernel@vger.kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Frédéric Weisbecker" <fweisbec@gmail.com>
Subject: Re: [PATCH 5/5] x86, nmi: Add better NMI stats to /proc/interrupts and show handlers
Date: Wed, 7 May 2014 12:04:39 -0400 [thread overview]
Message-ID: <20140507160439.GR39568@redhat.com> (raw)
In-Reply-To: <20140507154231.GB14926@gmail.com>
On Wed, May 07, 2014 at 05:42:31PM +0200, Ingo Molnar wrote:
>
> * Don Zickus <dzickus@redhat.com> wrote:
>
> > The main reason for this patch is because I have a hard time knowing
> > what NMI handlers are registered on the system when debugging NMI issues.
> >
> > This info is provided in /proc/interrupts for interrupt handlers, so I
> > added support for NMI stuff too. As a bonus it provides stat breakdowns
> > much like the interrupts.
> >
> > The only ugly issue is how to label NMI subtypes using only 3 letters
> > and still make it obvious it is part of the NMI. Adding a /proc/nmi
> > seemed overkill, so I choose to indent things by one space. Sample
> > output is below:
> >
> > [root@dhcp71-248 ~]# cat /proc/interrupts
> > CPU0 CPU1 CPU2 CPU3
> > 0: 29 0 0 0 IR-IO-APIC-edge timer
> > <snip>
> > NMI: 20 774 10986 4227 Non-maskable interrupts
> > LOC: 21 775 10987 4228 Local PMI, arch_bt
> > EXT: 0 0 0 0 External plat
> > UNK: 0 0 0 0 Unknown
> > SWA: 0 0 0 0 Swallowed
> > LOC: 30374 24749 20795 15095 Local timer interrupts
> > SPU: 0 0 0 0 Spurious interrupts
> > PMI: 20 774 10986 4227 Performance monitoring interrupts
> > <snip>
>
> Looks pretty useful!
>
> The lost vertical alignment of the counts is a problem though IMHO.
Agreed! It wasn't obvious to me at the time on how to keep that alignment
while only changing the first column. I can look at it again, if you are
ok with the small shift in the first column. Otherwise alternate ideas
are welcomed. :-)
Cheers,
Don
next prev parent reply other threads:[~2014-05-07 16:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 15:34 [PATCH 0/5 RESEND] x86, nmi: Various fixes and cleanups Don Zickus
2014-05-07 15:34 ` [PATCH 1/5] x86, nmi: Add new nmi type 'external' Don Zickus
2014-05-07 15:38 ` Ingo Molnar
2014-05-07 16:02 ` Don Zickus
2014-05-07 16:27 ` Ingo Molnar
2014-05-07 16:48 ` Don Zickus
2014-05-08 16:33 ` Don Zickus
2014-05-08 17:35 ` Ingo Molnar
2014-05-08 17:52 ` Don Zickus
2014-05-09 7:10 ` Ingo Molnar
2014-05-09 13:36 ` Don Zickus
2014-05-07 15:34 ` [PATCH 2/5] x86, nmi: Add boot line option 'panic_on_unrecovered_nmi' and 'panic_on_io_nmi' Don Zickus
2014-05-07 15:34 ` [PATCH 3/5] x86, nmi: Remove 'reason' value from unknown nmi output Don Zickus
2014-05-07 15:34 ` [PATCH 4/5] x86, nmi: Move default external NMI handler to its own routine Don Zickus
2014-05-07 15:34 ` [PATCH 5/5] x86, nmi: Add better NMI stats to /proc/interrupts and show handlers Don Zickus
2014-05-07 15:42 ` Ingo Molnar
2014-05-07 16:04 ` Don Zickus [this message]
2014-05-07 16:30 ` Ingo Molnar
2014-05-07 19:50 ` Elliott, Robert (Server Storage)
2014-05-08 1:28 ` Don Zickus
2014-05-08 6:04 ` Ingo Molnar
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=20140507160439.GR39568@redhat.com \
--to=dzickus@redhat.com \
--cc=ak@linux.intel.com \
--cc=fweisbec@gmail.com \
--cc=gong.chen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).