From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Shrink sched_clock some more
Date: Tue, 01 Nov 2011 14:29:00 +0000 [thread overview]
Message-ID: <4EB0022C.7080109@arm.com> (raw)
In-Reply-To: <4EAAF5AE.6090300@codeaurora.org>
On 28/10/11 19:34, Stephen Boyd wrote:
> On 09/23/11 01:52, Marc Zyngier wrote:
>> On 22/09/11 16:36, Russell King - ARM Linux wrote:
>>> ... by getting rid of the fixed-constant optimization, and moving the
>>> update code into arch/arm/kernel/sched_clock.c.
>>>
>>> Platforms now only have to supply a function to read the sched_clock
>>> register, and some basic information such as the number of significant
>>> bits and the tick rate.
>> This looks similar to a patch I posted a while ago:
>> http://patchwork.ozlabs.org/patch/112318/
>>
>>
>
> Can we get one of these two patches merged next merge window? I'd like
> to add sched_clock support to MSM and building on top of this patch is
> easier than the other way around.
I'm happy either way. The only problem I can see with Russell's patch is
the lack of support for platforms that do not actually implement a
sched_clock_read() function.
I've worked around this by having a default jiffy based read function,
but there is probably other, better solutions.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2011-11-01 14:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 15:36 [RFC] Shrink sched_clock some more Russell King - ARM Linux
2011-09-22 18:16 ` Nicolas Pitre
2011-09-23 6:22 ` Kyungmin Park
2011-09-23 20:44 ` Russell King - ARM Linux
2011-09-23 8:52 ` Marc Zyngier
2011-10-28 18:34 ` Stephen Boyd
2011-10-28 22:50 ` Nicolas Pitre
2011-11-01 14:29 ` Marc Zyngier [this message]
2011-11-08 0:13 ` Kyungmin Park
2011-09-28 8:59 ` Linus Walleij
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=4EB0022C.7080109@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).