From: khc@pm.waw.pl (Krzysztof Halasa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] ARM: sched_clock: allow sched_clock to be selected at runtime
Date: Tue, 13 Dec 2011 14:22:34 +0100 [thread overview]
Message-ID: <m3y5ugip2d.fsf@intrepid.localdomain> (raw)
In-Reply-To: <1323444833-10587-1-git-send-email-marc.zyngier@arm.com> (Marc Zyngier's message of "Fri, 9 Dec 2011 15:33:53 +0000")
Marc Zyngier <marc.zyngier@arm.com> writes:
> 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.
> If the platform doesn't provide a read(), the code falls back
> to the jiffy counter (just like the default sched_clock).
>
> 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.
The IXP4xx part looks good to me,
Acked-By: Krzysztof Halasa <khc@pm.waw.pl>
--
Krzysztof Halasa
next prev parent reply other threads:[~2011-12-13 13:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 15:33 [PATCH v4] ARM: sched_clock: allow sched_clock to be selected at runtime Marc Zyngier
2011-12-09 22:43 ` Nicolas Pitre
2011-12-12 3:57 ` Rob Herring
2011-12-12 17:05 ` Marc Zyngier
2011-12-13 0:46 ` Tony Lindgren
2011-12-13 0:50 ` Tony Lindgren
2011-12-13 1:33 ` Kyungmin Park
2011-12-13 18:58 ` Marc Zyngier
2011-12-13 21:16 ` Russell King - ARM Linux
2011-12-14 22:07 ` Tony Lindgren
2011-12-15 10:47 ` Marc Zyngier
2011-12-13 13:22 ` Krzysztof Halasa [this message]
2011-12-15 1:22 ` Shawn Guo
2011-12-15 1:56 ` Kukjin Kim
2011-12-15 11:04 ` 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=m3y5ugip2d.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--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).