From: Don Zickus <dzickus@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: Robert Richter <robert.richter@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@elte.hu" <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 4/4] [x86] perf: fix accidentally ack'ing a second event on intel perf counter
Date: Thu, 2 Sep 2010 10:19:00 -0400 [thread overview]
Message-ID: <20100902141900.GG4879@redhat.com> (raw)
In-Reply-To: <AANLkTikOaCL8FqQuUQsYPxm19WZOdarp8AMAugN0mnqQ@mail.gmail.com>
On Thu, Sep 02, 2010 at 10:13:19AM +0200, Stephane Eranian wrote:
> Robert,
>
> Do you have the test program you used to test this?
> I believe the NHM hack does not solve the problem, it
> just makes it harder to appear.
Could be.
>
> I suspect the real issue is that the GLOBAL_STATUS
> bitmask cannot be trusted. I'd like to verify this.
>
> Has the problem appear only on Nehalem or also on
> Westmere?
I was able to duplicate on
Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz
Intel(R) Xeon(R) CPU X5560 @ 2.80GHz
with just running 'perf top' for about 60 seconds.
You would need the first three patches to expose the problem.
Reading the code, it seemed like the perf counters should be disabled and
this patch should be unecessary, but after playing around with the code
for a few hours, I came up with this patch to trap the issue.
I read through the cpu errata and could not find anything related but I
might have missed something.
I am willing to help test if you have a more targeted patch.
Cheers,
Don
next prev parent reply other threads:[~2010-09-02 14:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 13:04 [PATCH 4/4] [x86] perf: fix accidentally ack'ing a second event on intel perf counter Stephane Eranian
2010-09-01 14:57 ` Robert Richter
2010-09-02 8:13 ` Stephane Eranian
2010-09-02 13:11 ` Robert Richter
2010-09-02 14:19 ` Don Zickus [this message]
2010-09-02 14:39 ` Stephane Eranian
2010-09-02 15:47 ` Don Zickus
2010-09-02 16:18 ` Stephane Eranian
2010-09-03 8:33 ` Peter Zijlstra
2010-09-03 11:02 ` Stephane Eranian
2010-09-03 11:11 ` Peter Zijlstra
2010-09-03 11:52 ` Stephane Eranian
2010-09-03 14:03 ` Don Zickus
2010-09-03 14:28 ` Stephane Eranian
-- strict thread matches above, loose matches on Subject: below --
2010-09-01 2:56 [PATCH 0/4] nmi perf fixes Don Zickus
2010-09-01 2:56 ` [PATCH 4/4] [x86] perf: fix accidentally ack'ing a second event on intel perf counter Don Zickus
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=20100902141900.GG4879@redhat.com \
--to=dzickus@redhat.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.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