kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: "Roedel, Joerg" <Joerg.Roedel@amd.com>
Cc: Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 3/3] perf, tools: Add support for guest/host-only profiling
Date: Tue, 10 May 2011 18:09:46 +0200	[thread overview]
Message-ID: <1305043786.2914.115.camel@laptop> (raw)
In-Reply-To: <20110510154652.GF30996@amd.com>

On Tue, 2011-05-10 at 17:46 +0200, Roedel, Joerg wrote:
> 
> I intended to re-use the exlude_hv bit originally, but then I looked
> into how this bit is used. On PPC it looks like this bit is set when
> Linux itself runs as a guest to exclude the hypervisor code being
> profiled. The meaning here is different (beacause Linux itself is the
> hypervisor) and I wanted to avoid different semantics for this bit
> across architectures. So I introduces seperate bits.
> The exclude_hv bit can be used when we have some kind of perf-ctr
> support for KVM guests. 

Ah, I didn't mean it like that, yes HV is strictly something different
(and you understood its purpose well, its when the 'host' is a guest
itself). What I was wondering about is if we want HV to be included in
the Guest/Host exclusion mask or not.

Then again, I guess that'll change behaviour in non-obvious ways, so
better not do that.


  reply	other threads:[~2011-05-10 16:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 14:35 [RFC][PATCH 0/3] perf support for amd guest/host-only bits Joerg Roedel
2011-05-10 14:35 ` [PATCH 1/3] perf, core: Introduce attrs to count in either host or guest mode Joerg Roedel
2011-05-10 14:45   ` Peter Zijlstra
2011-05-10 14:59     ` Roedel, Joerg
2011-05-10 15:18       ` Peter Zijlstra
2011-05-10 15:38         ` Roedel, Joerg
2011-05-10 16:07           ` Peter Zijlstra
2011-05-10 16:25             ` Roedel, Joerg
2011-05-11 11:44   ` Avi Kivity
2011-05-11 11:45     ` Avi Kivity
2011-05-11 13:49       ` Peter Zijlstra
2011-05-11 13:52         ` Avi Kivity
2011-05-11 14:02           ` Ingo Molnar
2011-05-10 14:35 ` [PATCH 2/3] perf, x86: Use GO/HO bits in perf-ctr Joerg Roedel
2011-05-10 14:48   ` Peter Zijlstra
2011-05-10 15:04     ` Roedel, Joerg
2011-05-11 12:58       ` Avi Kivity
2011-05-12  9:21         ` Joerg Roedel
2011-05-10 14:35 ` [PATCH 3/3] perf, tools: Add support for guest/host-only profiling Joerg Roedel
2011-05-10 14:50   ` Peter Zijlstra
2011-05-10 15:08     ` Roedel, Joerg
2011-05-10 15:25       ` Peter Zijlstra
2011-05-10 15:46         ` Roedel, Joerg
2011-05-10 16:09           ` Peter Zijlstra [this message]
2011-05-10 15:21 ` [RFC][PATCH 0/3] perf support for amd guest/host-only bits Ingo Molnar
2011-05-10 15:50   ` Roedel, Joerg
2011-05-10 20:41     ` Ingo Molnar
2011-05-11  8:57       ` Joerg Roedel

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=1305043786.2914.115.camel@laptop \
    --to=a.p.zijlstra@chello.nl \
    --cc=Joerg.Roedel@amd.com \
    --cc=acme@ghostprotocols.net \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.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 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).