public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Avi Kivity <avi@redhat.com>
Cc: "Yan, Zheng" <zheng.z.yan@linux.intel.com>,
	Pekka Enberg <penberg@kernel.org>,
	Sasha Levin <levinsasha928@gmail.com>,
	Asias He <asias.hejun@gmail.com>,
	Cyrill Gorcunov <gorcunov@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	KVM General <kvm@vger.kernel.org>, Gleb Natapov <gleb@redhat.com>
Subject: Re: perf uncore & lkvm woes
Date: Tue, 21 Aug 2012 12:35:25 +0200	[thread overview]
Message-ID: <1345545325.23018.98.camel@twins> (raw)
In-Reply-To: <50334827.6010906@redhat.com>

On Tue, 2012-08-21 at 11:34 +0300, Avi Kivity wrote:
> On 08/21/2012 10:11 AM, Peter Zijlstra wrote:
> > On Sun, 2012-08-19 at 12:55 +0300, Avi Kivity wrote:
> >> > I think Avi prefers the method where KVM 'fakes' the MSRs and we have to
> >> > detect if the MSRs actually work or not.
> >> 
> >> s/we have/we don't have/. 
> > 
> > So for the 'normal' PMU we actually do check to see if the MSRs are
> > being faked and bail if they are.
> 
> That was because earlier versions of kvm did not virtualize the pmu.
> 
> The approaches are not mutually exclusive.  We can check in the guest,
> and fake it in the host.

This is actually what I proposed.

> The problem with faking it in the host is if someone actually relies on
> the pmu for something, not just instrumentation.  We do that for the
> watchdog, but I don't see it happening with the uncore pmu.

Agreed, although from a usability POV its nicer to refuse the
device/events than to pretend it works while it doesn't.

Anyway, for now I've taken Zheng Yan's cpu_has_hypervisor patch, we can
always revisit this.

  reply	other threads:[~2012-08-21 10:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16  7:01 perf uncore & lkvm woes Pekka Enberg
2012-08-16  7:07 ` Cyrill Gorcunov
2012-08-16  7:16   ` Cyrill Gorcunov
2012-08-16  7:16   ` Pekka Enberg
2012-08-16  7:19 ` Peter Zijlstra
2012-08-16  7:38   ` Yan, Zheng
2012-08-16  7:41     ` Pekka Enberg
2012-08-16  7:46       ` Cyrill Gorcunov
2012-08-16  8:45         ` Avi Kivity
2012-08-16  9:06           ` Cyrill Gorcunov
2012-08-16  9:23             ` Pekka Enberg
2012-08-16  8:40       ` Avi Kivity
2012-08-16 11:06         ` Avi Kivity
2012-08-16 11:17           ` Peter Zijlstra
2012-08-16 11:25             ` Avi Kivity
2012-08-17  1:40               ` Yan, Zheng
2012-08-17  6:56                 ` Peter Zijlstra
2012-08-19  9:55                   ` Avi Kivity
2012-08-20  4:15                     ` Yan, Zheng
2012-08-20  8:49                       ` Avi Kivity
2012-08-21  1:11                         ` Yan, Zheng
2012-08-21  8:32                           ` Avi Kivity
2012-08-21  9:07                             ` Yan, Zheng
2012-08-20  5:30                     ` Yan, Zheng
2012-08-20  8:48                       ` Avi Kivity
2012-08-21  7:11                     ` Peter Zijlstra
2012-08-21  8:34                       ` Avi Kivity
2012-08-21 10:35                         ` Peter Zijlstra [this message]
2012-08-22  8:53                           ` Avi Kivity
2012-08-16 14:28             ` David Ahern

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=1345545325.23018.98.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=asias.hejun@gmail.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=gorcunov@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --cc=mingo@elte.hu \
    --cc=penberg@kernel.org \
    --cc=zheng.z.yan@linux.intel.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