From: Chris Metcalf <cmetcalf@tilera.com>
To: John Stultz <john.stultz@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, John Stultz <johnstul@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 6/6] clocksource: tile: convert to use clocksource_register_hz
Date: Wed, 1 Jun 2011 12:18:13 -0400 [thread overview]
Message-ID: <4DE66645.6020406@tilera.com> (raw)
In-Reply-To: <1306913570-9445-7-git-send-email-john.stultz@linaro.org>
On 6/1/2011 3:32 AM, John Stultz wrote:
> From: John Stultz <johnstul@us.ibm.com>
>
> Convert tile to use clocksource_register_hz.
>
> Untested. Help from maintainers would be appreciated.
>
> CC: Chris Metcalf <cmetcalf@tilera.com>
This patch boots up fine on tile. It provides a shift count of 31, with a
mult value in the billions. This does mean that clocksource_cyc2ns() will
only be able to give correct timer conversions for up to about 9 seconds.
Is this believed to be adequate for all the uses the cycle counter is put
to? I can run our normal regression tests, but I'd like to get a
high-level sanity check from the clocksource folks.
The original shift of 22 was put in by commit
749dc6f252b57d5cb9c1f4c1c4aafe4c92a28207 back in August.
> CC: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: John Stultz <johnstul@us.ibm.com>
> ---
> arch/tile/kernel/time.c | 5 +----
> 1 files changed, 1 insertions(+), 4 deletions(-)
>
> diff --git a/arch/tile/kernel/time.c b/arch/tile/kernel/time.c
> index c4be58c..f6f50f2a 100644
> --- a/arch/tile/kernel/time.c
> +++ b/arch/tile/kernel/time.c
> @@ -78,7 +78,6 @@ static struct clocksource cycle_counter_cs = {
> .rating = 300,
> .read = clocksource_get_cycles,
> .mask = CLOCKSOURCE_MASK(64),
> - .shift = 22, /* typical value, e.g. x86 tsc uses this */
> .flags = CLOCK_SOURCE_IS_CONTINUOUS,
> };
>
> @@ -91,8 +90,6 @@ void __init setup_clock(void)
> cycles_per_sec = hv_sysconf(HV_SYSCONF_CPU_SPEED);
> sched_clock_mult =
> clocksource_hz2mult(cycles_per_sec, SCHED_CLOCK_SHIFT);
> - cycle_counter_cs.mult =
> - clocksource_hz2mult(cycles_per_sec, cycle_counter_cs.shift);
> }
>
> void __init calibrate_delay(void)
> @@ -107,7 +104,7 @@ void __init calibrate_delay(void)
> void __init time_init(void)
> {
> /* Initialize and register the clock source. */
> - clocksource_register(&cycle_counter_cs);
> + clocksource_register_hz(&cycle_counter_cs, cycles_per_sec);
>
> /* Start up the tile-timer interrupt source on the boot cpu. */
> setup_tile_timer();
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2011-06-01 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 7:32 [PATCH 0/6] clocksource_register_hz/khz cleanups John Stultz
2011-06-01 7:32 ` [PATCH 1/6] clocksource: Convert tcb_clksrc to use clocksource_register_hz/khz John Stultz
2011-06-01 7:32 ` [PATCH 2/6] clocksource: parisc: convert to clocksource_register_hz/khz John Stultz
2011-06-01 7:32 ` [PATCH 3/6] clocksource: um: " John Stultz
2011-06-01 7:32 ` [PATCH 4/6] clocksource: xtensa: " John Stultz
2011-06-01 7:32 ` [PATCH 5/6] clocksource: cris: convert to clocksource_register_khz John Stultz
2011-06-01 7:32 ` [PATCH 6/6] clocksource: tile: convert to use clocksource_register_hz John Stultz
2011-06-01 16:18 ` Chris Metcalf [this message]
2011-06-01 17:55 ` john stultz
2011-06-03 21:27 ` Chris Metcalf
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=4DE66645.6020406@tilera.com \
--to=cmetcalf@tilera.com \
--cc=john.stultz@linaro.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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