From: linus.walleij@stericsson.com (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] RFC: nomadik: expand timesource to 63 bits
Date: Fri, 12 Nov 2010 11:37:45 +0100 [thread overview]
Message-ID: <4CDD18F9.5090005@stericsson.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1011121130350.2900@localhost6.localdomain6>
Thomas Gleixner wrote:
> On Fri, 12 Nov 2010, Linus Walleij wrote:
>> Uwe Kleine-K?nig wrote:
>>
>>> Instead of implementing sched_clock for each architecture seperatly,
>>> wouldn't it be nice to have a generic sched_clock that uses the
>>> architecture's clocksource? I tried to implement that some time ago,
>>> but tglx shoot it down because of locking problems.
>> I was and still am a big fan of this approach, I am willing to help
>> testing it if you want to dust off this patch set...
>
> sched_clock is not necessarily the same as the current clocksource.
IIRC Uwe:s approach was that if and only if you would want to use
the clocksource for sched_clock() you provide a special flag on
the clocksource, and it will be attempted to be used for sched_clock().
Incidentally the dual use of a single free-running timer as both
single clocksource and sched_clock() baseline seem to creep up in
a lot of embedded platforms...
Yours,
Linus Walleij
next prev parent reply other threads:[~2010-11-12 10:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 9:05 [PATCH] RFC: nomadik: expand timesource to 63 bits Linus Walleij
2010-11-11 10:16 ` Thomas Gleixner
2010-11-11 10:31 ` Linus Walleij
2010-11-11 11:05 ` Thomas Gleixner
2010-11-11 18:31 ` Nicolas Pitre
2010-11-11 19:00 ` Thomas Gleixner
2010-11-11 19:19 ` Nicolas Pitre
2010-11-11 21:33 ` john stultz
2010-11-12 9:43 ` Linus Walleij
2010-11-12 9:57 ` Uwe Kleine-König
2010-11-12 10:08 ` Linus Walleij
2010-11-12 10:31 ` Thomas Gleixner
2010-11-12 10:37 ` Linus Walleij [this message]
2010-11-12 11:08 ` Thomas Gleixner
2010-11-12 19:18 ` Nicolas Pitre
2010-11-12 20:22 ` john stultz
2010-11-12 19:15 ` Nicolas Pitre
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=4CDD18F9.5090005@stericsson.com \
--to=linus.walleij@stericsson.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