From: Mike Galbraith <efault@gmx.de>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Paul Mackerras <paulus@samba.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perfcounters: IRQ and NMI support on AMD CPUs
Date: Fri, 06 Mar 2009 07:51:40 +0100 [thread overview]
Message-ID: <1236322300.6263.1.camel@marge.simson.net> (raw)
In-Reply-To: <1236321473.6030.8.camel@marge.simson.net>
On Fri, 2009-03-06 at 07:37 +0100, Mike Galbraith wrote:
> On Fri, 2009-03-06 at 01:31 +0530, Jaswinder Singh Rajput wrote:
> > On Thu, 2009-03-05 at 20:41 +0100, Ingo Molnar wrote:
> > > * Peter Zijlstra <peterz@infradead.org> wrote:
> > >
> > > > On Fri, 2009-03-06 at 00:26 +0530, Jaswinder Singh Rajput wrote:
> > > >
> > > > > But kerneltop is still not working and I am not getting any NMI Interrupts.
> > > >
> > > > Does the below work for you?
> > > >
> > > > The BKGD suggests its 48 for all existing machines (it
> > > > certainly is for mine).
> > >
> > > Yeah, this did the trick on AMD/Barcelona!
> > >
> >
> > Nice.
> >
> > but on my AMD box I got interrupts and NMI for some time:
> >
> > NMI: 100 1108209 Non-maskable interrupts
> > LOC: 213 192815 Local timer interrupts
> > CNT: 100 1108206 Performance counter interrupts
> > RES: 21132 20397 Rescheduling interrupts
> >
> > but kerneltop does not show anything, it only shows # irqs/sec for some
> > time and then irqs also become 0.
>
> Hm. Kerneltop on my Q6600 has ceased to function with n 1 as well, but
> n 0 still works. Zero NMIs.
>
> Perfstat has also gone south.
> perfstat: perfstat.c:423: main: Assertion `res == sizeof(single_count)' failed.
Ah, my woes are gonna be 2743a5b0fa6f309da904f2190a9cc25deee34dbd.
Never mind.
-Mike
next prev parent reply other threads:[~2009-03-06 6:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 17:20 [PATCH] perfcounters: IRQ and NMI support on AMD CPUs Peter Zijlstra
2009-03-05 17:25 ` Ingo Molnar
2009-03-05 17:27 ` [tip:perfcounters/core] " Peter Zijlstra
2009-03-12 1:44 ` Robert Richter
2009-03-12 9:12 ` Peter Zijlstra
2009-03-05 18:32 ` [PATCH] " Jaswinder Singh Rajput
2009-03-05 18:45 ` Peter Zijlstra
2009-03-05 18:56 ` Jaswinder Singh Rajput
2009-03-05 19:07 ` Peter Zijlstra
2009-03-05 19:37 ` Jaswinder Singh Rajput
2009-03-05 19:34 ` Peter Zijlstra
2009-03-05 19:41 ` Ingo Molnar
2009-03-05 20:01 ` Jaswinder Singh Rajput
2009-03-06 6:37 ` Mike Galbraith
2009-03-06 6:51 ` Mike Galbraith [this message]
2009-03-06 7:11 ` Mike Galbraith
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=1236322300.6263.1.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.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