[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120328085732.GV22197@one.firstfloor.org>
Date: Wed, 28 Mar 2012 10:57:32 +0200
From: Andi Kleen <andi@...stfloor.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: "Yan, Zheng" <zheng.z.yan@...el.com>, a.p.zijlstra@...llo.nl,
mingo@...e.hu, andi@...stfloor.org, eranian@...gle.com,
linux-kernel@...r.kernel.org, ming.m.lin@...el.com
Subject: Re: [RFC PATCH 0/5] perf: Intel uncore pmu counting support
On Wed, Mar 28, 2012 at 08:49:28AM +0200, Ingo Molnar wrote:
>
> * Yan, Zheng <zheng.z.yan@...el.com> wrote:
>
> > Hi, all
> >
> > Here is the RFC patches to add uncore counting support for Nehalem,
> > Sandy Bridge and Sandy Bridge-EP, applied on top of current tip.
> > The code is based on Lin Ming's old patches.
> >
> > You can use 'perf stat' to access to the uncore pmu. For example:
> > perf stat -a -C 0 -e 'uncore_nhm/config=0xffff/' sleep 1
>
> My main complaint is that that's not user friendly *AT ALL*.
>
> You need to make this useful to mere mortals: go through the
> SDM, categorize interesting looking events, look at how it can
The main problem is that we don't know currently what events are
really useful. People need to play around with the raw events
first to find that out. But to do that really already need some
in tree support because out of tree is too painful to use: it's
a chicken and egg problem.
> be expressed via tooling, add a generic event where appropriate,
> provide examples, actually *USE* it to improve the kernel or an
Yes it needs to be used, exactly.
To do that need the base line driver be available first, so that
this experience can be gained.
The only way to satisfy your request now would be to put in
some unproven events as generic events, probably not a good idea.
-Andi
--
ak@...ux.intel.com -- Speaking for myself only.
--
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