[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <450499D3.5010903@goop.org>
Date: Sun, 10 Sep 2006 16:03:47 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Andrew Morton <akpm@...l.org>
CC: Ingo Molnar <mingo@...e.hu>, Andi Kleen <ak@...e.de>,
Laurent Riffard <laurent.riffard@...e.fr>,
Arjan van de Ven <arjan@...radead.org>,
Kernel development list <linux-kernel@...r.kernel.org>,
Jeremy Fitzhardinge <jeremy@...source.com>
Subject: Re: 2.6.18-rc6-mm1: GPF loop on early boot
Andrew Morton wrote:
> I must say that having an unreliable early-current is going to be quite a
> pita for evermore. Things like mcount-based tricks and
> basic-block-profiling-based tricks, for example.
>
> Is it really going to be too messy to fake up some statically-defined gdt
> which points at init_task, install that before we call any C at all?
That's on my TODO list - make %gs set correctly before hitting C code,
and get rid of all the early_* stuff. I had already encountered a
PDA-related oops with lockdep enabled, and addressed it.
It's pretty easy to solve in general for the boot CPU, but its a bit
more tricky to handle for secondary CPUs.
Laurent, could you resend your original oops? It doesn't seem to have
appeared on lkml.
In the meantime, I'll work on a proper fix for this.
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists