From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM: sched_clock: allow sched_clock to be selected at runtime
Date: Wed, 10 Aug 2011 09:28:02 +0100 [thread overview]
Message-ID: <4E424112.10804@arm.com> (raw)
In-Reply-To: <CAMPhdO8qCXrPN7ASo=Fhm+BQJN11NRy=kNPv8ySHMbd24df3Rw@mail.gmail.com>
On 09/08/11 22:28, Eric Miao wrote:
> On Wed, Aug 10, 2011 at 5:20 AM, Rob Herring <robherring2@gmail.com> wrote:
>> On 08/09/2011 12:13 PM, Marc Zyngier wrote:
>>> sched_clock() is yet another blocker on the road to the single
>>> image. This patch implements an idea by Russell King:
>>>
>>> http://www.spinics.net/lists/linux-omap/msg49561.html
>>>
>>> Instead of asking the platform to implement both sched_clock()
>>> itself and the rollover callback, simply register a read()
>>> function, and let the ARM code care about sched_clock() itself,
>>> the conversion to ns and the rollover. sched_clock() uses
>>> this read() function as an indirection to the platform code.
>>>
>>> This allow some simplifications and possibly some footprint gain
>>> when multiple platforms are compiled in. Among the drawbacks,
>>> the removal of the *_fixed_sched_clock optimization which could
>>> negatively impact some platforms (sa1100, tegra, versatile
>>> and omap).
>>
>> There are similar patchsets that move sched_clock into clocksource code.
>> That seems like a cleaner approach to me.
>>
>> http://thread.gmane.org/gmane.linux.kernel/844872
>>
>> http://www.spinics.net/lists/arm-kernel/msg122716.html
>
> +1, yeah would be better for clocksource to handle that if possible.
I'd be all for that, and I've waited a long time (April?) before posting
that patch, hoping that a consensus would emerge on the clocksourse
patches.
So far, nothing.
We need a solution to this problem. I really don't care which patch gets
merged, so if someone thinks they can get the clocksource patches
further, then by all mean, please do it.
Cheers,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2011-08-10 8:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 17:13 [RFC PATCH] ARM: sched_clock: allow sched_clock to be selected at runtime Marc Zyngier
2011-08-09 20:54 ` Linus Walleij
2011-08-09 21:20 ` Rob Herring
2011-08-09 21:28 ` Eric Miao
2011-08-09 21:33 ` Russell King - ARM Linux
2011-08-10 8:28 ` Marc Zyngier [this message]
2011-08-10 8:52 ` Russell King - ARM Linux
2011-08-10 8:59 ` Marc Zyngier
2011-08-10 7:13 ` Linus Walleij
2011-08-10 11:49 ` Jamie Iles
2011-08-10 14:16 ` Marc Zyngier
2011-08-11 8:25 ` Russell King - ARM Linux
2011-08-11 8:49 ` Jamie Iles
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=4E424112.10804@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).