linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Avi Kivity <avi@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
	kvm@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Fr??d??ric Weisbecker <fweisbec@gmail.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Cyrill Gorcunov <gorcunov@gmail.com>,
	Lin Ming <ming.m.lin@intel.com>,
	Sheng Yang <sheng@linux.intel.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	oerg Roedel <joro@8bytes.org>, Gleb Natapov <gleb@redhat.com>,
	Zachary Amsden <zamsden@redhat.com>,
	zhiteng.huang@intel.com, tim.c.chen@intel.com
Subject: Re: [PATCH V2 1/5] ara virt interface of perf to support kvm guest os statistics collection in guest os
Date: Tue, 22 Jun 2010 17:29:03 +0800	[thread overview]
Message-ID: <1277198943.2096.724.camel@ymzhang.sh.intel.com> (raw)
In-Reply-To: <4C206D8B.4080105@redhat.com>

On Tue, 2010-06-22 at 10:00 +0200, Jes Sorensen wrote:
> On 06/22/10 09:55, Peter Zijlstra wrote:
> > On Tue, 2010-06-22 at 15:47 +0800, Zhang, Yanmin wrote:
> >> Besides the para virt perf interface, I'm also considering the direct exposition
> >> of PMU hardware to guest os. 
> > 
> > NAK NAK NAK NAK, we've been over that, its not going to happen, full
> > stop!
> > 
> > Use MSR read/write traps and host perf to emulate the hardware. In some
> > cases we could allow the reads without trap but that's a later
> > optimization.
> 
> I believe whats meant here is a PMU compatible interface which is
> partially emulated. Not a handover of the PMU.
Right. We need capture all write to PMU MSR and allows guest os to read MSR directly.

Yanmin


  reply	other threads:[~2010-06-22  9:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21  9:31 [PATCH V2 1/5] ara virt interface of perf to support kvm guest os statistics collection in guest os Zhang, Yanmin
2010-06-21 11:45 ` Avi Kivity
2010-06-22  1:49   ` Zhang, Yanmin
2010-06-22  7:14     ` Jes Sorensen
2010-06-22  7:47       ` Zhang, Yanmin
2010-06-22  7:55         ` Peter Zijlstra
2010-06-22  8:00           ` Jes Sorensen
2010-06-22  9:29             ` Zhang, Yanmin [this message]
2010-06-22  9:31               ` Peter Zijlstra
2010-06-22  9:39                 ` Jes Sorensen
2010-06-22  9:46                   ` Peter Zijlstra
2010-06-22  9:53                     ` Avi Kivity
2010-06-22 10:02                       ` Peter Zijlstra
2010-06-22 10:06                         ` Avi Kivity
2010-06-22 10:10                           ` Peter Zijlstra
2010-06-22 11:01                             ` Avi Kivity
2010-06-22  7:58         ` Jes Sorensen
2010-06-23  1:13           ` Zhang, Yanmin
2010-06-23  8:15             ` Jes Sorensen
2010-06-22  8:59     ` Avi Kivity

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=1277198943.2096.724.camel@ymzhang.sh.intel.com \
    --to=yanmin_zhang@linux.intel.com \
    --cc=Jes.Sorensen@redhat.com \
    --cc=acme@redhat.com \
    --cc=avi@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=gleb@redhat.com \
    --cc=gorcunov@gmail.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=mingo@elte.hu \
    --cc=mtosatti@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sheng@linux.intel.com \
    --cc=tim.c.chen@intel.com \
    --cc=zamsden@redhat.com \
    --cc=zhiteng.huang@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;
as well as URLs for NNTP newsgroup(s).