public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: x86@kernel.org, Andi Kleen <andi@firstfloor.org>,
	Robert Richter <robert.richter@amd.com>,
	ying.huang@intel.com, LKML <linux-kernel@vger.kernel.org>,
	jason.wessel@windriver.com
Subject: Re: [RFC][PATCH 6/6] x86, nmi: print out NMI stats in /proc/interrupts
Date: Mon, 22 Aug 2011 11:28:39 -0400	[thread overview]
Message-ID: <20110822152839.GE2067@redhat.com> (raw)
In-Reply-To: <1314023262.24275.38.camel@twins>

On Mon, Aug 22, 2011 at 04:27:42PM +0200, Peter Zijlstra wrote:
> On Fri, 2011-08-19 at 16:37 -0400, Don Zickus wrote:
> > NMI:       4161       4155        158       4194   Non-maskable interrupts
> > SWA:          0          0          0          0   Unknown NMIs swallowed
> >   0:       4161       4155        158       4194   NMI  PMI, arch_bt
> > UNK:          0          0          0          0   NMI
> > EXT:          0          0          0          0   NMI 
> 
> Yeah, not too pretty.. I would have expected something like:
> 
> NMI:
>  PMI:
>  uv:
>  arch_bt:
>  ...
>  swallowed:
>  unknown:

Yeah, I kinda wanted to do that originally, but wasn't sure what the rules
were for the output structure of that file.  I even toyed with the idea of
creating a /proc/nmi file to do that too, but thought that it might confuse
people.

> 
> But then, I'm sure some people would complain to that as I'm pretty sure
> it'll break stuff parsing /proc/interrupts

That's why I just posted my half-ass patch to see if it was

- useful info
- gather ideas on the best way to present it

Cheers,
Don


      reply	other threads:[~2011-08-22 15:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19 20:37 [RFC][PATCH 0/6] x86, nmi: new NMI handling routines Don Zickus
2011-08-19 20:37 ` [RFC][PATCH 1/6] x86, nmi: split out nmi from traps.c Don Zickus
2011-08-19 20:37 ` [RFC][PATCH 2/6] x86, nmi: create new NMI handler routines Don Zickus
2011-08-22 14:13   ` Peter Zijlstra
2011-08-22 15:21     ` Don Zickus
2011-08-22 15:26       ` Peter Zijlstra
2011-08-22 15:41         ` Don Zickus
2011-08-22 15:31       ` Peter Zijlstra
2011-08-22 14:16   ` Peter Zijlstra
2011-08-22 15:23     ` Don Zickus
2011-08-23 14:14     ` Don Zickus
2011-08-23 14:17       ` Peter Zijlstra
2011-08-24 17:04   ` Paul E. McKenney
2011-08-24 17:44     ` Don Zickus
2011-08-24 17:51       ` Peter Zijlstra
2011-08-24 18:16         ` Don Zickus
2011-08-24 18:19           ` Peter Zijlstra
2011-08-24 19:16             ` Paul E. McKenney
2011-08-19 20:37 ` [RFC][PATCH 3/6] x86, nmi: wire up NMI handlers to new routines Don Zickus
2011-08-19 20:37 ` [RFC][PATCH 4/6] x86, nmi: add in logic to handle multiple events and unknown NMIs Don Zickus
2011-08-22 14:22   ` Peter Zijlstra
2011-08-22 15:25     ` Don Zickus
2011-08-19 20:37 ` [RFC][PATCH 5/6] x86, nmi: track NMI usage stats Don Zickus
2011-08-19 20:37 ` [RFC][PATCH 6/6] x86, nmi: print out NMI stats in /proc/interrupts Don Zickus
2011-08-22 14:27   ` Peter Zijlstra
2011-08-22 15:28     ` Don Zickus [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=20110822152839.GE2067@redhat.com \
    --to=dzickus@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=robert.richter@amd.com \
    --cc=x86@kernel.org \
    --cc=ying.huang@intel.com \
    /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