[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1276146811.2096.463.camel@ymzhang.sh.intel.com>
Date: Thu, 10 Jun 2010 13:13:31 +0800
From: "Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>
To: Avi Kivity <avi@...hat.com>
Cc: LKML <linux-kernel@...r.kernel.org>, kvm@...r.kernel.org,
Ingo Molnar <mingo@...e.hu>,
Fr??d??ric Weisbecker <fweisbec@...il.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Cyrill Gorcunov <gorcunov@...il.com>,
Lin Ming <ming.m.lin@...el.com>,
Sheng Yang <sheng@...ux.intel.com>,
Marcelo Tosatti <mtosatti@...hat.com>,
oerg Roedel <joro@...tes.org>,
Jes Sorensen <Jes.Sorensen@...hat.com>,
Gleb Natapov <gleb@...hat.com>,
Zachary Amsden <zamsden@...hat.com>, zhiteng.huang@...el.com,
tim.c.chen@...el.com, Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [RFC] para virt interface of perf to support kvm guest os
statistics collection in guest os
On Thu, 2010-06-10 at 06:06 +0300, Avi Kivity wrote:
> On 06/10/2010 05:21 AM, Zhang, Yanmin wrote:
> >
> >> I see. So put it in a union. Or perhaps not even in a union - what if
> >> a kvm guest is also acting as a kvm host?
> >>
> > My patch has consideration on it. I compiled kernel with host and guest support
> > at the same time. The accessing to perf_event->shadow is really under specific
> > scenarios, or they are just in specific functions. These functions are called
> > just bu host kernel , or just by guest kernel.
> >
>
> But a kernel can be both guest and host at the same time. Currently
> this only works on AMD, but there was some work to bring it to Intel as
> well.
Oh, this is a fancy VT feature. My patch doesn't support this mode.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists