From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Geoff Levand <geoffrey.levand@am.sony.com>
Cc: linuxppc-dev@ozlabs.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 3/3] zImage: Cleanup and improve zImage entry point
Date: Tue, 20 Feb 2007 06:59:40 +1100 [thread overview]
Message-ID: <1171915180.18571.52.camel@localhost.localdomain> (raw)
In-Reply-To: <45D9BEC0.1060909@am.sony.com>
> I think the better idea is to make the generic bootwrapper code support
> SMP. I don't see any fundamental reason why it can't. The trouble here
> is that your BSS stack is really not a proper way, that's why it doesn't
> work.
>
> I'll put something together that provides generic (SMP) stack support
> for the bootwrapper. I'll be away the end of this week and next week,
> so I don't know when I'll be able to post it.
As I said earlier, I see no reason why the wrapper needs to provide a
stack for non-primary CPUs.
Ben.
next prev parent reply other threads:[~2007-02-19 19:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 6:24 [0/3] RFC: Cleanups and improvements to the zImage wrapper David Gibson
2007-02-16 6:27 ` [PATCH 2/3] zImage: Cleanup and improve prep_kernel() David Gibson
2007-02-18 1:22 ` Geoff Levand
2007-02-18 7:21 ` David Gibson
2007-02-16 6:27 ` [PATCH 1/3] zImage: Add more flexible gunzip convenience functions David Gibson
2007-02-16 6:27 ` [PATCH 3/3] zImage: Cleanup and improve zImage entry point David Gibson
2007-02-18 1:22 ` Geoff Levand
2007-02-18 7:23 ` David Gibson
2007-02-19 0:26 ` Paul Mackerras
2007-02-19 0:48 ` David Gibson
2007-02-19 15:14 ` Geoff Levand
2007-02-19 19:59 ` Benjamin Herrenschmidt [this message]
2007-02-19 19:57 ` Benjamin Herrenschmidt
2007-02-19 20:37 ` Geoff Levand
2007-02-19 20:50 ` Benjamin Herrenschmidt
2007-02-19 21:14 ` Geoff Levand
2007-02-16 16:47 ` [0/3] RFC: Cleanups and improvements to the zImage wrapper Geoff Levand
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=1171915180.18571.52.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=geoffrey.levand@am.sony.com \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).