From: Paul Mackerras <paulus@cs.anu.edu.au>
To: hozer@drgw.net
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: kswapd and SMP still broke on 2.2.0-pre9
Date: Sat, 23 Jan 1999 13:59:03 +1100 [thread overview]
Message-ID: <199901230259.NAA17964@tango.anu.edu.au> (raw)
In-Reply-To: <Pine.LNX.4.04.9901221336410.12144-100000@narn.local.drgw.net> (message from Troy Benjegerdes on Fri, 22 Jan 1999 13:44:25 -0600 (CST))
Troy Benjegerdes <hozer@drgw.net> wrote:
> kswapd is still dieing on boot with SMP enabled (and this time the second
> processor is actually active)
>
> Does this indicate something is wrong with SMP and the MM code, or that
> some PPC-specific part needs fixing? I've tried to keep up on
> linux-kernel, but it's a little overwhelming ;)
The SMP stuff in Linux/PPC currently only supports the Apple MP
architecture (I think they call it "powersurge"). Your MTX board
probably has entirely different ways of coordinating the CPUs. Have
you looked at arch/ppc/kernel/smp.c? I think that's where you'd have
to start changing things.
Paul.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-01-23 2:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-22 19:44 kswapd and SMP still broke on 2.2.0-pre9 Troy Benjegerdes
1999-01-23 2:59 ` Paul Mackerras [this message]
1999-01-23 5:54 ` Troy Benjegerdes
1999-01-23 9:05 ` Ryan Nielsen
1999-01-23 18:25 ` Cort Dougan
1999-01-23 23:25 ` Paul Mackerras
1999-01-24 7:02 ` Ryan Nielsen
1999-01-24 21:30 ` Troy Benjegerdes
1999-01-26 2:09 ` Cort Dougan
1999-01-26 6:02 ` 2.2.0 SMP kswapd okay, but rpciod crashes Troy Benjegerdes
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=199901230259.NAA17964@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=hozer@drgw.net \
--cc=linuxppc-dev@lists.linuxppc.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).