From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 0/3] 64bit friendly generic sched_clock
Date: Wed, 5 Jun 2013 16:54:42 -0700 [thread overview]
Message-ID: <1370476485-468-1-git-send-email-sboyd@codeaurora.org> (raw)
Ok here's the second take at 64 bit support in generic sched_clock.
This assumes that the previous three patches in the v2 of this
series have been applied.
I've also noticed that we probably need to update the mult/shift
calculation similar to how clocksources are done. Should we
just copy/paste the maxsec calculation code here or do something
else?
Stephen Boyd (3):
sched_clock: Add support for >32 bit sched_clock
ARM: arch_timer: Move to generic sched_clock framework
arm64: Move to generic sched_clock infrastructure
arch/arm/kernel/arch_timer.c | 14 ++------------
arch/arm64/Kconfig | 1 +
arch/arm64/kernel/time.c | 11 ++---------
include/linux/sched_clock.h | 3 +--
kernel/time/sched_clock.c | 46 ++++++++++++++++++++++++++------------------
5 files changed, 33 insertions(+), 42 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next reply other threads:[~2013-06-05 23:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 23:54 Stephen Boyd [this message]
2013-06-05 23:54 ` [PATCHv3 1/3] sched_clock: Add support for >32 bit sched_clock Stephen Boyd
2013-06-06 0:38 ` John Stultz
2013-06-06 1:43 ` Stephen Boyd
2013-06-05 23:54 ` [PATCHv3 2/3] ARM: arch_timer: Move to generic sched_clock framework Stephen Boyd
2013-06-05 23:54 ` [PATCHv3 3/3] arm64: Move to generic sched_clock infrastructure Stephen Boyd
2013-06-12 18:51 ` Christopher Covington
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=1370476485-468-1-git-send-email-sboyd@codeaurora.org \
--to=sboyd@codeaurora.org \
--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).