[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110822152839.GE2067@redhat.com>
Date: Mon, 22 Aug 2011 11:28:39 -0400
From: Don Zickus <dzickus@...hat.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: x86@...nel.org, Andi Kleen <andi@...stfloor.org>,
Robert Richter <robert.richter@....com>, ying.huang@...el.com,
LKML <linux-kernel@...r.kernel.org>, jason.wessel@...driver.com
Subject: Re: [RFC][PATCH 6/6] x86, nmi: print out NMI stats in
/proc/interrupts
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists