From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: test for PMU feature on v7 (v2 with typo fix)
Date: Fri, 30 Mar 2012 18:04:01 +0100 [thread overview]
Message-ID: <20120330170401.GD11451@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1203281005110.24151@xanadu.home>
Hi Nicolas,
On Wed, Mar 28, 2012 at 03:17:29PM +0100, Nicolas Pitre wrote:
> On Mon, 26 Mar 2012, Will Deacon wrote:
>
> > Now, if everything was device-tree based then we could simply use a
> > different binding for each CPU but since we support perf on non-DT
> > platforms, probing the CPU type is the best solution. I would like to avoid
> > the probing code if we are initialised from DT, but I've not got round to it
> > yet (this would be useful for big.LITTLE).
>
> Still... my opinion is that we should try to autodetect as much as
> possible and avoid overstuffing the DT with content that can otherwise
> be run-time probed. OK to use DT to override the probe for corner
> cases, but IMHO the probe should be the default method of
> initialization. The rational is that we want to spread knowledge about
> part of the system and have it confined into respective drivers and
> subsystems for easier maintenance. If the guy who has to maintain the
> dts has to know all the details for everything then that won't scale and
> the risk for discrepancies is increased.
I agree that probing is preferable where possible but, since the PMUs are
banked, we cannot reliably probe them on big.LITTLE platforms. I guess if
there were some infrastructure for probing on the remote cluster, I could
use that, but it seems like DT would be easier.
Will
next prev parent reply other threads:[~2012-03-30 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F590411.9060201@arm.com>
2012-03-23 0:32 ` [PATCH] ARM: test for PMU feature on v7 Rusty Russell
2012-03-23 0:34 ` [PATCH] ARM: test for PMU feature on v7 (v2 with typo fix) Rusty Russell
2012-03-23 9:53 ` Will Deacon
2012-03-23 23:17 ` Rusty Russell
2012-03-26 9:40 ` Will Deacon
2012-03-26 9:50 ` [Android-virt] " Peter Maydell
2012-03-26 15:15 ` Will Deacon
2012-03-28 6:09 ` Rusty Russell
2012-03-28 14:17 ` Nicolas Pitre
2012-03-30 17:04 ` Will Deacon [this message]
2012-03-30 17:40 ` Nicolas Pitre
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=20120330170401.GD11451@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--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).