Date: Tue, 30 Jun 2009 13:57:32 +0200
From: Ingo Molnar <mingo@elte.hu>
To: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] perf_counter: tools: Make :u and :k exclude
	hypervisor
Message-ID: <20090630115732.GA7611@elte.hu>
References: <19016.41130.429944.316897@cargo.ozlabs.ibm.com> <20090629203443.GH31577@elte.hu> <19017.63611.674927.683004@cargo.ozlabs.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <19017.63611.674927.683004@cargo.ozlabs.ibm.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 884
Lines: 29


* Paul Mackerras <paulus@samba.org> wrote:

> Ingo Molnar writes:
> 
> > Hm, mind fixing the full range of problems with these flags 
> > please?
> 
> Sure, looking at it now.
> 
> One thing I'd like to do is add complete lists of hardware events 
> for each processor so that perf can tell you the full set of 
> things you can measure, and can let you ask for them without 
> having to know raw event codes. [...]

Excellent.

> [...] I know how to work out which processor we're running on for 
> powerpc; for x86 I assume cpuid or something similar is usable 
> from userspace, is it?

Yeah. /proc/cpuinfo can be read as well.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/