From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: sched_clock: allow sched_clock to be selected at runtime
Date: Fri, 02 Sep 2011 13:56:03 +0100 [thread overview]
Message-ID: <4E60D263.60702@arm.com> (raw)
In-Reply-To: <20110902124945.GX3548@atomide.com>
Hi Tony,
On 02/09/11 13:49, Tony Lindgren wrote:
> * Marc Zyngier <marc.zyngier@arm.com> [110830 16:29]:
>> 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).
>>
>> Tested on 11MPCore, OMAP4 and Tegra.
>
> Great, seems to boot just fine with printk_time :)
>
> I gave it a quick boot test on omap16xx, 2420, 3430,
> 3630 and 4430:
>
> Tested-by: Tony Lindgren <tony@atomide.com>
Thanks for testing!.
M.
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2011-09-02 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 13:56 [PATCH v3] ARM: sched_clock: allow sched_clock to be selected at runtime Marc Zyngier
2011-09-02 12:49 ` Tony Lindgren
2011-09-02 12:56 ` Marc Zyngier [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=4E60D263.60702@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.