From: William Lee Irwin III <wli@holomorphy.com>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc2-mm2
Date: Wed, 22 Sep 2004 23:01:22 -0700 [thread overview]
Message-ID: <20040923060122.GC9106@holomorphy.com> (raw)
In-Reply-To: <41526341.8070902@bigpond.net.au>
William Lee Irwin III wrote:
>> Something's a tad off here. Should be easy enough to fix up.
[...]
>> TPC: <sched_clock+0xc/0x40>
On Thu, Sep 23, 2004 at 03:46:41PM +1000, Peter Williams wrote:
> This looks the problem of sched_clock() being called before it's ready
> (that we experienced with 2.6.9-rc2 on IA32 systems) only this time it's
> fatal :-(
> A quick workaround for this would be to initialize idle->sched_timestamp
> in init_idle() and current->sched_timestamp in sched_init() to the
> INITIAL_JIFFIES converted to nanoseconds instead of using sched_clock().
> Another solution would be to set them to a value much greater than the
> nanosecond equivalent of INITIAL_JIFFIES (e.g. 1ULL << 63) and let the
> code that handles the non monotonic behaviour of sched_clock() sort it
> out later.
Well, I posted a quick hack to get it to tolerate being called so early.
Might be better if I statically initialized the thing to a dummy driver
so only the indirect call remains at runtime. e.g.:
-- wli
Index: mm2-2.6.9-rc2/arch/sparc64/kernel/time.c
===================================================================
--- mm2-2.6.9-rc2.orig/arch/sparc64/kernel/time.c 2004-09-22 21:33:03.000000000 -0700
+++ mm2-2.6.9-rc2/arch/sparc64/kernel/time.c 2004-09-22 22:59:35.980157226 -0700
@@ -64,7 +64,16 @@
static int set_rtc_mmss(unsigned long);
-struct sparc64_tick_ops *tick_ops;
+static __init unsigned long dummy_get_tick(void)
+{
+ return 0;
+}
+
+static __initdata struct sparc64_tick_ops dummy_tick_ops = {
+ .get_tick = dummy_get_tick,
+};
+
+struct sparc64_tick_ops *tick_ops = &dummy_tick_ops;
#define TICK_PRIV_BIT (1UL << 63)
next prev parent reply other threads:[~2004-09-23 6:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 20:12 2.6.9-rc2-mm2 Andrew Morton
2004-09-22 20:48 ` 2.6.9-rc2-mm2 Jesse Barnes
2004-09-22 20:54 ` 2.6.9-rc2-mm2 Andrew Morton
2004-09-22 21:05 ` 2.6.9-rc2-mm2 Jesse Barnes
2004-09-22 20:55 ` 2.6.9-rc2-mm2 William Lee Irwin III
2004-09-22 20:59 ` 2.6.9-rc2-mm2 Jesse Barnes
2004-09-22 21:04 ` 2.6.9-rc2-mm2 Andrew Morton
2004-09-22 21:10 ` 2.6.9-rc2-mm2 Jesse Barnes
2004-09-22 21:02 ` 2.6.9-rc2-mm2 Stefan Seyfried
2004-09-22 22:27 ` 2.6.9-rc2-mm2 Peter Williams
2004-09-23 1:47 ` 2.6.9-rc2-mm2 Nuno Ferreira
2004-09-23 2:03 ` 2.6.9-rc2-mm2 Andrew Morton
2004-09-23 2:58 ` 2.6.9-rc2-mm2 Herbert Xu
2004-09-23 9:29 ` 2.6.9-rc2-mm2 Nuno Ferreira
2004-09-23 3:00 ` 2.6.9-rc2-mm2 Nick Piggin
2004-09-23 5:07 ` 2.6.9-rc2-mm2 William Lee Irwin III
2004-09-23 5:27 ` 2.6.9-rc2-mm2 William Lee Irwin III
2004-09-23 5:46 ` 2.6.9-rc2-mm2 Peter Williams
2004-09-23 6:01 ` William Lee Irwin III [this message]
2004-09-23 13:15 ` 2.6.9-rc2-mm2 Vladimir Saveliev
2004-09-23 15:51 ` 2.6.9-rc2-mm2 (disable repacker) Mike Houston
2004-09-23 16:48 ` 2.6.9-rc2-mm2 William Lee Irwin III
2004-09-23 17:59 ` 2.6.9-rc2-mm2 Akinobu Mita
2004-09-24 0:53 ` 2.6.9-rc2-mm2 [u] Martin Schlemmer [c]
2004-10-02 7:44 ` 2.6.9-rc2-mm2 Jaakko Hyvätti
2004-10-02 7:49 ` 2.6.9-rc2-mm2 Andrew Morton
2004-10-02 18:21 ` 2.6.9-rc2-mm2 Jaakko Hyvätti
2004-10-08 11:24 ` 2.6.9-rc2-mm2 William Lee Irwin III
[not found] <747804697@toto.iv>
2004-09-23 0:39 ` 2.6.9-rc2-mm2 Peter Chubb
2004-09-23 0:43 ` 2.6.9-rc2-mm2 Jesse Barnes
2004-09-23 6:23 ` 2.6.9-rc2-mm2 Andrew Morton
2004-09-23 6:23 ` 2.6.9-rc2-mm2 Andrew Morton
2004-09-23 16:10 ` 2.6.9-rc2-mm2 Luck, Tony
2004-09-23 16:10 ` 2.6.9-rc2-mm2 Luck, Tony
2004-09-23 18:31 ` 2.6.9-rc2-mm2 Andrew Morton
2004-09-23 18:31 ` 2.6.9-rc2-mm2 Andrew Morton
2004-09-23 0:49 ` 2.6.9-rc2-mm2 Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-09-24 6:27 2.6.9-rc2-mm2 Tim Krieglstein
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=20040923060122.GC9106@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pwil3058@bigpond.net.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.