From: rric@kernel.org (Robert Richter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: oprofile: add A5/A7/A15 entries in op_perf_name
Date: Fri, 23 Nov 2012 15:10:25 +0100 [thread overview]
Message-ID: <20121123141025.GG24690@rric.localhost> (raw)
In-Reply-To: <20121120170817.GG27765@mudshark.cambridge.arm.com>
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
prev parent reply other threads:[~2012-11-23 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 10:43 [PATCH 1/1] ARM: oprofile: add A5/A7/A15 entries in op_perf_name jgq516 at gmail.com
2012-11-05 11:31 ` Will Deacon
2012-11-20 12:17 ` Robert Richter
2012-11-20 15:57 ` Will Deacon
2012-11-20 16:31 ` Robert Richter
2012-11-20 16:55 ` Will Deacon
2012-11-20 17:06 ` Robert Richter
2012-11-20 17:08 ` Will Deacon
2012-11-23 14:10 ` Robert Richter [this message]
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=20121123141025.GG24690@rric.localhost \
--to=rric@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).