From: Tsutomu OWA <tsutomu.owa@toshiba.co.jp>
To: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, tglx@linutronix.de
Subject: Re: [patch 5/5] powerpc 2.6.21-rt1] fix clocksource_timebase.shift value
Date: Mon, 14 May 2007 17:23:17 +0900 [thread overview]
Message-ID: <yyilkfr95l6.wl@toshiba.co.jp> (raw)
In-Reply-To: <yyisl9z97hg.wl@toshiba.co.jp>
Calculate clocksource_timebase.shift from tb_ticks_per_jiffy to get an
accurate translation, though I don't understand why current version of
clocksource_timebase.shift could be constant...
Signed-off-by: Tsutomu OWA <tsutomu.owa@toshiba.co.jp>
-- owa
--- linux-2.6.21-rt1/arch/powerpc/kernel/time.c 2007-05-09 18:05:57.000000000 +0900
+++ rt/arch/powerpc/kernel/time.c 2007-05-09 18:06:24.000000000 +0900
@@ -945,6 +945,9 @@ static int __init init_timebase_clocksou
if (__USE_RTC())
return -ENODEV;
+#ifdef CONFIG_PPC64
+ clocksource_timebase.shift = tb_ticks_per_jiffy / 1000000;
+#endif
clocksource_timebase.mult = clocksource_hz2mult(tb_ticks_per_sec,
clocksource_timebase.shift);
return clocksource_register(&clocksource_timebase);
prev parent reply other threads:[~2007-05-14 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 7:42 [patch 0/5] powerpc 2.6.21-rt1] latency trace support for powerpc Tsutomu OWA
2007-05-14 8:15 ` [patch 1/5] powerpc 2.6.21-rt1: add mcount() and _mcount() Tsutomu OWA
2007-05-14 8:16 ` [patch 2/5] powerpc 2.6.21-rt1: dummy functions and export _mcount to compile Tsutomu OWA
2007-05-14 8:17 ` [patch 3/5] powerpc 2.6.21-rt1: mark raw_local_irq_restore() and timebase_read() as notrace Tsutomu OWA
2007-05-14 8:19 ` [patch 4/5] powerpc 2.6.21-rt1: rename mcount variable in xmon to xmon_mcount Tsutomu OWA
2007-05-14 8:23 ` Tsutomu OWA [this message]
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=yyilkfr95l6.wl@toshiba.co.jp \
--to=tsutomu.owa@toshiba.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--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