From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Eddy Raineri <eraineri@axiom-tx.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Quad SMP on G4
Date: Mon, 16 Apr 2001 19:01:58 +0200 [thread overview]
Message-ID: <20010416170158.17749@smtp.wanadoo.fr> (raw)
In-Reply-To: <000d01c0c68c$b65be250$3e03a8c0@dnaent.com>
>
>4) One more simple question. I'm unclear as to which 2_4 version I should
>pull from I have been using the linuxppc_2_4 kernel and not linus' is this
>correct? I'm trying to stay current on the PPC fixes for the 2_4 kernel. I
>am assuming that any fixes Linus makes to the kernel will be put into the
>linuxppc_2_4 version however any fixes made in general by the PPC group
>might not make it into the Linus version.
>
>I apologize if this is repeated. I'm trying desperately to find the
>resources necessary for me to stay informed but may have not found it yet.
>
The linuxppc_2_4 is the current kernel for PPC, yes. It contains the
latest PPC fixes and Linus patches are regulary merged in (it's currently
at 2.4.4pre3).
As far as you lock problem is concerned, I can't help you. All I can say
for now is that it workes well on other SMP machines like the Apple dual
G4, so this makes me think you might have a bus arbitration problem.
Also, do you have the kernel BAT mapped or did you remove that optim ?
I'm not too sure the hash table code is very safe to run without this.
I beleive that without the BAT mapping, the code & data that are
touched when the hash table lock is held should be locked in the TLB as
well to avoid deadlocks.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-16 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-16 15:48 Quad SMP on G4 Eddy Raineri
2001-04-16 17:01 ` Benjamin Herrenschmidt [this message]
2001-04-17 12:25 ` Gabriel Paubert
2001-04-17 13:16 ` Benjamin Herrenschmidt
[not found] <200104170459.XAA21609@lists.linuxppc.org>
2001-04-17 7:03 ` Peter Cordes
2001-04-17 14:23 ` Michel Lanners
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=20010416170158.17749@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=eraineri@axiom-tx.com \
--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).