From: David Ahern <dsahern@gmail.com>
To: Stephane Eranian <eranian@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Gleb Natapov <gleb@redhat.com>, Avi Kivity <avi@redhat.com>
Subject: Re: perf, x86: only do lbr init if bts is available
Date: Thu, 24 May 2012 10:41:52 -0600 [thread overview]
Message-ID: <4FBE64D0.7040507@gmail.com> (raw)
In-Reply-To: <CABPqkBT7dKa3P2hk=_pismGdPHuseWMbCKhUzz1sQNDemb133A@mail.gmail.com>
On 5/24/12 10:35 AM, Stephane Eranian wrote:
> Well, no. There is no connection between BTS and LBR and you're creating one.
Ok. That was not clear to me from skimming the manual.
Then should it be tied to X86_FEATURE_DTES64?
diff --git a/arch/x86/kernel/cpu/perf_event_intel_lbr.c
b/arch/x86/kernel/cpu/perf_event_intel_lbr.c
index 520b426..1090ae6 100644
--- a/arch/x86/kernel/cpu/perf_event_intel_lbr.c
+++ b/arch/x86/kernel/cpu/perf_event_intel_lbr.c
@@ -640,6 +640,9 @@ void intel_pmu_lbr_init_core(void)
/* nehalem/westmere */
void intel_pmu_lbr_init_nhm(void)
{
+ if (!boot_cpu_has(X86_FEATURE_DTES64))
+ return;
+
x86_pmu.lbr_nr = 16;
x86_pmu.lbr_tos = MSR_LBR_TOS;
x86_pmu.lbr_from = MSR_LBR_NHM_FROM;
> Where is the wrmsr coming from? What we need to do is ensure that LBR is not
> touched if we don't actually use it.
e.g., intel_pmu_lbr_init_nhm sets up lbr_nr, lbr_from, lbr_to and from,
etc. Fhat I can tell intel_pmu_lbr_reset() gets invoked some where
during the VM boot; I haven't traced how/when yet.
David
next prev parent reply other threads:[~2012-05-24 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 16:19 perf, x86: only do lbr init if bts is available David Ahern
2012-05-24 16:35 ` Stephane Eranian
2012-05-24 16:41 ` David Ahern [this message]
2012-05-24 17:07 ` David Ahern
2012-05-24 17:11 ` Stephane Eranian
2012-05-25 22:49 ` Andi Kleen
2012-05-24 17:18 ` Peter Zijlstra
2012-05-24 17:21 ` 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=4FBE64D0.7040507@gmail.com \
--to=dsahern@gmail.com \
--cc=avi@redhat.com \
--cc=eranian@google.com \
--cc=gleb@redhat.com \
--cc=linux-kernel@vger.kernel.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