public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: David Ahern <dsahern@gmail.com>
Cc: Stephane Eranian <eranian@google.com>,
	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 19:18:36 +0200	[thread overview]
Message-ID: <1337879916.9698.69.camel@twins> (raw)
In-Reply-To: <4FBE5FA6.5050802@gmail.com>

On Thu, 2012-05-24 at 10:19 -0600, David Ahern wrote:
> KVM recently added support for a version 2 PMU. When passing -cpu host 
> as the CPU model for the guest we get an abnormal configuration from 
> perf's perspective in that the guest identifies the processor as a 
> Westmere or Nehalem (etc):
> 
> [    0.013998] Performance Events: Westmere events, Intel PMU driver.
> 
> 
> but yet the processor does not have the debug store mechanisms 
> (X86_FEATURE_DTES64 is not set) meaning there is no PEBS or BTS.
> 
> Right now the LBR init functions are run based on processor model which 
> leads to attempts to write to LBR MSRs generating messages like:

Right, as Stephane already noted, LBR is not an CPUID enumerated
feature, hence the only thing you can do is go by model. So if you set
qemu -cpu host but fail to implement all the architectural MSRs that go
with that model you get to keep the pieces.

Not really our problem.

  parent reply	other threads:[~2012-05-24 17:18 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
2012-05-24 17:11     ` Stephane Eranian
2012-05-25 22:49       ` Andi Kleen
2012-05-24 17:18 ` Peter Zijlstra [this message]
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=1337879916.9698.69.camel@twins \
    --to=peterz@infradead.org \
    --cc=avi@redhat.com \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=gleb@redhat.com \
    --cc=linux-kernel@vger.kernel.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