[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101006155026.GT13563@erda.amd.com>
Date: Wed, 6 Oct 2010 17:50:26 +0200
From: Robert Richter <robert.richter@....com>
To: Paul Mundt <lethal@...ux-sh.org>
CC: Peter Zijlstra <peterz@...radead.org>,
Matt Fleming <matt@...sole-pimps.org>,
Will Deacon <will.deacon@....com>,
Russell King <linux@....linux.org.uk>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-sh@...r.kernel.org" <linux-sh@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>,
Frederic Weisbecker <fweisbec@...il.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Deng-Cheng Zhu <dengcheng.zhu@...il.com>,
Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [PATCH 2/7] perf: New helper function for pmu name
On 06.10.10 09:30:41, Paul Mundt wrote:
> On Wed, Oct 06, 2010 at 03:18:25PM +0200, Robert Richter wrote:
> > So, I am also fine with implementing a generic perf_pmu_name() for sh
> > and then derive the oprofile cpu_type string from it in the oprofile
> > code.
> >
> Again, this is unacceptable.
Paul,
maybe I misunderstood you, but isn't this you preferred solution? We
make perf_pmu_name() part of the generic i/f and then derive the
oprofile name from the pmu name provided by perf.
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
--
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