From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: Reading twd_base at run-time
Date: Wed, 01 Apr 2015 14:14:44 +0100 [thread overview]
Message-ID: <551BEF44.8020808@arm.com> (raw)
In-Reply-To: <551BEC33.1090702@free.fr>
On 01/04/15 14:01, Mason wrote:
> On 01/04/2015 14:28, Marc Zyngier wrote:
>
>> It is worth mentioning that PERIPH_BASE is *not* an architected
>> register, so an implementation is perfectly allowed not to implement it.
>> Even on Cortex A9, a UP implementation will report PERIPH_BASE as zero.
>> It is still likely to have a TWD though.
>
> It is interesting that you would mention TWD and UP implementations,
> because "config HAVE_ARM_TWD" depends on SMP, as I mentioned in a
> separate thread ("Dropping "depends on SMP" for HAVE_ARM_TWD").
>
> Would it make sense to drop the dependency?
>
> I have a single-core Cortex A9 MPcore system where I want to use
> the local timers. If it's too much trouble changing the build
> options, I suppose I can just run an SMP kernel?
There used to be a time where the TWD was completely tied to the SMP
code, but I think we now deal with per-cpu timers in a way similar to
the global timers (more or less...).
Worth trying, and see what breaks. On the other hand, SMP on UP should
give you the same result.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-04-01 13:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 16:16 Reading twd_base at run-time Mason
2015-03-27 16:35 ` Marc Zyngier
2015-03-27 20:33 ` Mason
2015-03-27 20:53 ` Russell King - ARM Linux
2015-04-01 12:07 ` Mason
2015-04-01 12:12 ` Russell King - ARM Linux
2015-04-01 12:47 ` Mason
2015-04-01 12:28 ` Marc Zyngier
2015-04-01 12:47 ` Mason
2015-04-01 13:01 ` Mason
2015-04-01 13:14 ` Marc Zyngier [this message]
2015-04-01 14:39 ` Mason
2015-04-01 14:56 ` Marc Zyngier
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=551BEF44.8020808@arm.com \
--to=marc.zyngier@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).