linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Timothy A. Seufert" <tas@mindspring.com>,
	Christopher Murtagh <christopher.murtagh@mcgill.ca>,
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: SMP/HIGHMEM/7450 status ?
Date: Thu, 6 Jun 2002 21:46:36 +0200	[thread overview]
Message-ID: <20020606194636.7979@smtp.wanadoo.fr> (raw)
In-Reply-To: <a05111b00b92567b867f3@[10.0.0.42]>


>Apple did hold off on dual 7450 until rev 2.1 came out and fixed some
>of the nastier SMP errata, so presumably they at least thought there
>were no SMP showstoppers left in rev 2.1.  As far as I can tell they
>are pretty stable under OS X.

There is an SMP showstopper with HW hashtable walk, but Apple
claims to have a HW workaround.

>Linux is probably just missing some deep magic needed for working
>around one or more of the errata that do still apply to rev 2.1.  The
>trouble is figuring out exactly what's wrong... it can be VERY
>difficult to understand all the ramifications of a CPU bug
>(particularly a SMP related bug) until you use a bus analyzer to
>snapshot bus traffic during a crash, or probe CPU registers via JTAG
>after it has crashed, etc.

Especially since you don't have the connector on the motherboard
to put such a tool, and since I don't even have physical access
to any of these machines.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-06-06 19:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-06 15:51 SMP/HIGHMEM/7450 status ? Christopher Murtagh
2002-06-06  5:37 ` benh
2002-06-06 16:29   ` Christopher Murtagh
2002-06-06  6:08     ` benh
2002-06-06 17:09       ` Christopher Murtagh
2002-06-06 17:45         ` benh
2002-06-06 19:40           ` Christopher Murtagh
2002-06-07  8:23           ` Geert Uytterhoeven
2002-06-06 19:51         ` Timothy A. Seufert
2002-06-06 19:46           ` Benjamin Herrenschmidt [this message]
2002-06-08 23:10       ` Christopher Murtagh
2002-06-09  0:41         ` Dan Burcaw
2002-06-06 16:05 ` Kevin B. Hendricks

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=20020606194636.7979@smtp.wanadoo.fr \
    --to=benh@kernel.crashing.org \
    --cc=christopher.murtagh@mcgill.ca \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=tas@mindspring.com \
    /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).