[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20121123141025.GG24690@rric.localhost>
Date: Fri, 23 Nov 2012 15:10:25 +0100
From: Robert Richter <rric@...nel.org>
To: Will Deacon <will.deacon@....com>
Cc: Maynard Johnson <maynardj@...ibm.com>,
"jgq516@...il.com" <jgq516@...il.com>,
"linux@....linux.org.uk" <linux@....linux.org.uk>,
"oprofile-list@...ts.sf.net" <oprofile-list@...ts.sf.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 1/1] ARM: oprofile: add A5/A7/A15 entries in op_perf_name
On 20.11.12 17:08:17, Will Deacon wrote:
> > The advantage of a solution where userland updates cpu_type is that we
> > never need to update the kernel anymore. This means, cpu detection can
> > be part of the tools.
>
> True, but the kernel-side perf code still needs updating to support the new
> CPU so I don't think you win much.
You also need perf support to use operf. If oprofile can update
cpu_type, the oprofile kernel interface would work for new hardware
without changes. We have support for both then, operf and opcontrol.
-Robert
--
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