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 11:07:30 -0600 [thread overview]
Message-ID: <4FBE6AD2.6050501@gmail.com> (raw)
In-Reply-To: <4FBE64D0.7040507@gmail.com>
On 5/24/12 10:41 AM, David Ahern wrote:
> On 5/24/12 10:35 AM, Stephane Eranian wrote:
>> 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.
[ 0.012998] [<c04220ca>] intel_pmu_lbr_reset+0x2a/0xa0
[ 0.012998] [<c0423beb>] intel_pmu_cpu_starting+0x3b/0x100
[ 0.012998] [<c0424bd0>] ? allocate_shared_regs+0x20/0x50
[ 0.012998] [<c0932714>] x86_pmu_notifier+0xb3/0xc0
[ 0.012998] [<c0bed54c>] init_hw_perf_events+0x42c/0x456
[ 0.012998] [<c0403034>] do_one_initcall+0x34/0x170
[ 0.012998] [<c0bf2388>] ? native_smp_prepare_cpus+0x2b7/0x2f2
[ 0.012998] [<c0bed120>] ? check_bugs+0xf9/0xf9
[ 0.012998] [<c0be4833>] kernel_init+0x77/0x1a4
[ 0.012998] [<c0be47bc>] ? start_kernel+0x36d/0x36d
[ 0.012998] [<c094af7e>] kernel_thread_helper+0x6/0x10
next prev parent reply other threads:[~2012-05-24 17:07 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
2012-05-24 17:07 ` David Ahern [this message]
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=4FBE6AD2.6050501@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 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.