All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yan, Zheng" <zheng.z.yan@linux.intel.com>
To: Avi Kivity <avi@redhat.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	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: Mon, 20 Aug 2012 13:30:04 +0800	[thread overview]
Message-ID: <5031CB5C.7040405@linux.intel.com> (raw)
In-Reply-To: <5030B82C.5000106@redhat.com>

On 08/19/2012 05:55 PM, Avi Kivity wrote:
> On 08/17/2012 09:56 AM, Peter Zijlstra wrote:
>> On Fri, 2012-08-17 at 09:40 +0800, Yan, Zheng wrote:
>>>
>>> Peter, do I need to submit a patch disables uncore on virtualized CPU?
>>>
>> 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/.
> 
>>
>> If you're willing to have a go at that, please do so. If you're not sure
>> how to do the KVM part, I'm sure Avi and/or Gleb can help you out.
> 
> Certainly, please see kvm_pmu_get_msr() and kvm_pmu_set_msr().
> 
> The approach is that if an msr write can be emulated correctly (for
> example, it disables a counter) then we let it proceed; if it cannot be
> emulated correctly (for example it enables a counter that we cannot
> emulate), then we ignore it, but print out a message that tells the user
> that we're faking something that may cause the guest to malfunction.
> 
> 

Anyone knows how to detect if the kernel is running on virtualized CPU?

Regards
Yan, Zheng

  parent reply	other threads:[~2012-08-20  5:30 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 [this message]
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
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=5031CB5C.7040405@linux.intel.com \
    --to=zheng.z.yan@linux.intel.com \
    --cc=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 \
    /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.