From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vince@deater.net>
Cc: junk@eslaf.co.uk, alan@lxorguk.ukuu.org.uk,
Ingo Molnar <mingo@kernel.org>,
Stephane Eranian <eranian@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf,x86,p6: Add userspace RDPMC quirk for P6
Date: Wed, 5 Feb 2014 20:55:06 +0100 [thread overview]
Message-ID: <20140205195506.GN2936@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1402051435540.16859@pianoman.cluster.toy>
On Wed, Feb 05, 2014 at 02:37:29PM -0500, Vince Weaver wrote:
> On Wed, 5 Feb 2014, Vince Weaver wrote:
>
> > Has someone actually hit this bug? People used PAPI/perfctr on these
> > machines for years, and it uses rdpmc by default so I would think it would
> > show up if it were an issue. I should check the perfctr code to see if it
> > had some sort of check.
>
> I can verify the perfctr code does have a case for PPRO errata 26, but it
> only disables things on pentium pros with stepping less than 9.
The doc said 0xB1, right? Should we keep it at that? Its not like
there's a lot of PPro machines left out there, so better safe than
sorry.
> It also disables rdpmc on original Pentiums due to errata 74 but I don't
> think we have to worry about that one.
We don't have a Family 5 driver, so no.
next prev parent reply other threads:[~2014-02-05 19:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 10:27 [PATCH] perf,x86,p6: Add userspace RDPMC quirk for P6 Peter Zijlstra
2014-02-05 19:16 ` Vince Weaver
2014-02-05 19:20 ` Peter Zijlstra
2014-02-05 19:29 ` Vince Weaver
2014-02-05 19:37 ` Vince Weaver
2014-02-05 19:55 ` Peter Zijlstra [this message]
2014-02-05 20:04 ` Vince Weaver
2014-02-05 20:20 ` Peter Zijlstra
2014-02-05 19:53 ` Peter Zijlstra
2014-02-05 19:48 ` Peter Zijlstra
2014-02-06 19:41 ` Mark Davies
2014-02-06 20:38 ` Peter Zijlstra
2014-02-06 22:15 ` Mark Davies
2014-02-07 7:52 ` 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=20140205195506.GN2936@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=eranian@google.com \
--cc=junk@eslaf.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=vince@deater.net \
/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