linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Sheng Yang <sheng@linux.intel.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	Marcelo Tosatti <mtosatti@redhat.com>,
	oerg Roedel <joro@8bytes.org>,
	Jes Sorensen <Jes.Sorensen@redhat.com>,
	Gleb Natapov <gleb@redhat.com>,
	Zachary Amsden <zamsden@redhat.com>,
	zhiteng.huang@intel.com, tim.c.chen@intel.com,
	Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: Re: [PATCH V5 1/3] perf & kvm: Enhance perf to collect KVM guest os statistics from host side
Date: Mon, 19 Apr 2010 11:59:46 +0300	[thread overview]
Message-ID: <4BCC1B82.5050000@redhat.com> (raw)
In-Reply-To: <1271667323.2078.611.camel@ymzhang.sh.intel.com>

On 04/19/2010 11:55 AM, Zhang, Yanmin wrote:
> On Mon, 2010-04-19 at 11:37 +0300, Avi Kivity wrote:
>    
>> On 04/19/2010 08:32 AM, Zhang, Yanmin wrote:
>>      
>>> Below patch introduces perf_guest_info_callbacks and related register/unregister
>>> functions. Add more PERF_RECORD_MISC_XXX bits meaning guest kernel and guest user
>>> space.
>>>
>>>        
>> This doesn't apply against upstream.
>>      
> What does upstream mean here? The vanilla 2.6.34-rc4?
>    

Yes, sorry for being unclear.

>>    What branch was this generated
>> against?
>>
>>      
> It's against the latest tip/master. I checked out to 19b26586090 as the latest
> tip/master has some updates on perf.
>    

I don't want to merge tip/master... does tip/perf/core contain the 
needed updates?

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-04-19  9:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19  5:32 [PATCH V5 1/3] perf & kvm: Enhance perf to collect KVM guest os statistics from host side Zhang, Yanmin
2010-04-19  8:37 ` Avi Kivity
2010-04-19  8:55   ` Zhang, Yanmin
2010-04-19  8:59     ` Avi Kivity [this message]
2010-04-19  9:09       ` Avi Kivity
2010-04-19  9:22       ` Zhang, Yanmin
2010-04-19 10:00         ` Avi Kivity
2010-04-19 18:11 ` Ingo Molnar
2010-04-20  2:13   ` Zhang, Yanmin
2010-04-20  6:06     ` Ingo Molnar
2010-04-20  6:09       ` Ingo Molnar
2010-04-20  6:21         ` Zhang, Yanmin
2010-04-20 17:54     ` [tip:perf/core] perf & kvm: Clean up some of the guest profiling callback API details tip-bot for Zhang, Yanmin
2010-04-22 10:27 ` [PATCH V5 1/3] perf & kvm: Enhance perf to collect KVM guest os statistics from host side Liu Yu-B13201
2010-04-23 10:50   ` Avi Kivity
2010-04-26  6:11     ` Zhang, Yanmin

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=4BCC1B82.5050000@redhat.com \
    --to=avi@redhat.com \
    --cc=Jes.Sorensen@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@infradead.org \
    --cc=gleb@redhat.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mtosatti@redhat.com \
    --cc=sheng@linux.intel.com \
    --cc=tim.c.chen@intel.com \
    --cc=yanmin_zhang@linux.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).