From: Don Zickus <dzickus@redhat.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
peterz@infradead.org, robert.richter@amd.com,
andi@firstfloor.org, ming.m.lin@intel.com, eranian@google.com,
ying.huang@intel.com, mathieu.desnoyers@efficios.com,
acme@redhat.com
Subject: Re: [RFC] x86, perf: high volume of events produces a flood of unknown NMIs
Date: Wed, 20 Apr 2011 15:12:31 -0400 [thread overview]
Message-ID: <20110420191231.GB31724@redhat.com> (raw)
In-Reply-To: <4DAF2A57.1010804@gmail.com>
On Wed, Apr 20, 2011 at 10:47:51PM +0400, Cyrill Gorcunov wrote:
> > Or perhaps we don't care about this because in the end perf can't even
> > capture the data without spitting out a CPU Overload message.
> >
> > Thoughts?
> >
>
> Hi Don, just a thought -- since pmi masks lvtpc we could read it and check if it's
> masked or no, though I fear it is quite time consuming operation in compare with
> frames :( (hmm, intel spec mentions only p4 and xeon as masking lvtpc)
Been there, tried that. It seems to be masked a large majority of the
time, even when the NMIs don't appear to be back-to-back.
Cheers,
Don
next prev parent reply other threads:[~2011-04-20 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 18:26 [RFC] x86, perf: high volume of events produces a flood of unknown NMIs Don Zickus
2011-04-20 18:47 ` Cyrill Gorcunov
2011-04-20 18:59 ` Cyrill Gorcunov
2011-04-20 19:12 ` Don Zickus [this message]
2011-04-20 19:26 ` Stephane Eranian
2011-04-20 21:01 ` Don Zickus
2011-04-21 13:28 ` Don Zickus
2011-04-21 13:40 ` Stephane Eranian
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=20110420191231.GB31724@redhat.com \
--to=dzickus@redhat.com \
--cc=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.