From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: Andi Kleen <andi@firstfloor.org>, "mingo@elte.hu" <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf, x86: Add workaround for MEM_*_RETIRED errata BV98
Date: Thu, 2 May 2013 09:32:53 +0200 [thread overview]
Message-ID: <20130502073252.GG7521@dyad.programming.kicks-ass.net> (raw)
In-Reply-To: <CABPqkBS7FxoT1fioe_VdBMcLAdZtfwRiMmSMocSY5TB3QAyPQQ@mail.gmail.com>
On Wed, May 01, 2013 at 09:21:55PM +0200, Stephane Eranian wrote:
> On Wed, May 1, 2013 at 9:13 PM, Andi Kleen <andi@firstfloor.org> wrote:
> >> Unfortunately, Andi's patch fails to correct the problem though
> >> it is the right approach. As he said, the problem is unfortunately
> >
> > perf stat -a / record -a / top will work.
> >
> But it does not for perf stat -a. Look at my example, run it on your machine.
Since nobody seems interested in explaining the exact nature of the hardware
failure I think the best thing we can do is simply blacklist these events.
Broken hardware is broken after all -- we should jump through too many hoops
pretending its not.
next prev parent reply other threads:[~2013-05-02 7:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 18:45 Andi Kleen
2013-05-01 9:07 ` Peter Zijlstra
2013-05-01 9:56 ` Andi Kleen
2013-05-01 10:10 ` Ingo Molnar
2013-05-01 11:12 ` Peter Zijlstra
2013-05-01 18:13 ` Stephane Eranian
2013-05-01 19:13 ` Andi Kleen
2013-05-01 19:21 ` Stephane Eranian
2013-05-02 7:32 ` Peter Zijlstra [this message]
2013-05-06 17:41 ` Stephane Eranian
2013-05-06 19:00 ` Peter Zijlstra
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=20130502073252.GG7521@dyad.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®