From: Andrew Morton <akpm@linux-foundation.org>
To: Ben Hutchings <bhutchings@solarflare.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH][RFC] Add default CPU topology information
Date: Fri, 18 Apr 2008 00:32:17 -0700 [thread overview]
Message-ID: <20080418003217.94e25f2f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080418001024.7377c52d.akpm@linux-foundation.org>
On Fri, 18 Apr 2008 00:10:24 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> On Mon, 31 Mar 2008 12:44:13 +0100 Ben Hutchings <bhutchings@solarflare.com> wrote:
>
> > Not all architectures and configurations define CPU topology information.
> > This can result in an empty topology directory in sysfs, and requires
> > in-kernel users to protect all uses with #ifdef - see
> > <http://marc.info/?l=linux-netdev&m=120639033904472&w=2>.
> >
> > The documentation of CPU topology specifies what the defaults should be
> > if only partial information is available from the hardware. So we can
> > provide these defaults as a fallback.
> >
> > This patch:
> >
> > - Adds default definitions of the 4 topology macros to
> > include/asm-generic/topology.h.
> > - Changes include/asm-*/topology.h to include <asm-generic/topology.h>
> > unconditionally.
> > - Changes drivers/base/topology.c to use the topology macros unconditionally
> > and to cope with definitions that aren't lvalues.
> > - Updates documentation accordingly.
>
> I get a huuuuuuuge crash early in boot on the t61p dual x86_64 laptop.
> Before netconsole has started and it has no serial port, so all I have is a
> partially-scrolled-off jpg, sorry.
>
> I'll drop the patch.
>
> http://userweb.kernel.org/~akpm/p4175278.jpg
> http://userweb.kernel.org/~akpm/config-t61p.txt
> http://userweb.kernel.org/~akpm/dmesg-t61p.txt
>
>
> If I didn't have all that wrong crap on the stack we'd have a full
> trace here. I have CONFIG_FRAME_POINTER=y, but that doesn't seem to
> have helped.
>
ooh, I just discovered kstack=. That should be hoisted up to core kernel
then pushed out to other architectures, not hidden in x86_64 code.
But first I guess it should be make to work - it fails miserably, because
only one of our seventy fix stack-dumping functions actually looks at it.
This:
--- a/arch/x86/kernel/traps_64.c~a
+++ a/arch/x86/kernel/traps_64.c
@@ -426,7 +426,7 @@ _show_stack(struct task_struct *tsk, str
printk(" %016lx", *stack++);
touch_nmi_watchdog();
}
- show_trace(tsk, regs, sp, bp);
+// show_trace(tsk, regs, sp, bp);
}
void show_stack(struct task_struct *tsk, unsigned long * sp)
works heaps better.
Here's the rest of your oops: http://userweb.kernel.org/~akpm/p4175279.jpg
I'd be suspecting startup ordering problems - maybe the page allocator
isn't ready yet.
otoh, it _should_ be ready by the time we run init_sched_domains().
next prev parent reply other threads:[~2008-04-18 7:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 11:44 [PATCH][RFC] Add default CPU topology information Ben Hutchings
2008-03-31 12:35 ` Ingo Molnar
2008-04-15 19:42 ` Andrew Morton
2008-04-16 12:51 ` Ingo Molnar
2008-04-16 19:07 ` Andrew Morton
2008-04-18 6:45 ` Andrew Morton
2008-04-18 12:10 ` Ben Hutchings
2008-04-18 7:10 ` Andrew Morton
2008-04-18 7:32 ` Andrew Morton [this message]
2008-04-18 12:24 ` Ben Hutchings
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=20080418003217.94e25f2f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=bhutchings@solarflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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