linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Val Henson <val@nmt.edu>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Highmem on PPC?
Date: Tue, 5 Feb 2002 11:56:18 -0700	[thread overview]
Message-ID: <20020205115618.D6834@boardwalk> (raw)
In-Reply-To: <20020205125256.16831@mailhost.mipsys.com>; from benh@kernel.crashing.org on Tue, Feb 05, 2002 at 01:52:56PM +0100


On Tue, Feb 05, 2002 at 01:52:56PM +0100, benh@kernel.crashing.org wrote:
>
> >What's the current state of highmem on the G4?  Does it work, not
> >work, kinda work, only work on UP... ?
> >
> >I hope to have a dual 7450 G4 with 1 GB RAM within a week, at which
> >point I'll be able to work on highmem seriously.
>
> It's supposed to work. However, I'm having reports of dual 7450 with
> 1G or 1.5G of RAM locking up, I haven't been able to track those down.
>
> Is this an Apple machine ? The 7450 has a bug that prevents use on
> SMP with HW hash table walk. Apple is supposed to implement a HW
> workaround for this on their machines, but if it's not an Apple machine,
> then you may have to implement software TLB load.

The dual 7450 is an apple machine.  I also have one of our beta
boards, a dual 7410 with 1 GB RAM, and we're planning on having a dual
7450 with 1 GB RAM just as soon as we get the chips.

What's your philosophy about highmem?  We map all lowmem with BATs on
SMP in order to avoid trashing SRR0/SRR1 according to your new comment
in entry.S, but it also mentions "other cpus" without saying which cpu
you're talking about. :) How are you avoiding recursive TLB faults on
the highmem pages themselves?  What cpus did you have in mind when you
wrote the SMP stuff?

I'm currently getting hard crashes on the dual 7410 with highmem.  Not
even the SMI starts xmon.  I'm not sure that it's a software bug,
which is why I'm getting the dual 7450.

-VAL

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

  reply	other threads:[~2002-02-05 18:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05  1:32 Highmem on PPC? Val Henson
2002-02-05 12:52 ` benh
2002-02-05 18:56   ` Val Henson [this message]
2002-02-05 19:33     ` Benjamin Herrenschmidt
2002-02-05 19:42       ` Val Henson
2002-02-05 19:47         ` Benjamin Herrenschmidt
2002-02-07 12:27       ` Christopher Murtagh
2002-02-07 21:43       ` Val Henson
2002-02-07 21:51         ` Benjamin Herrenschmidt
2002-02-07 21:56           ` Val Henson
2002-02-07 21:59             ` Benjamin Herrenschmidt
2002-02-07 21:53         ` Mark A. Greer
2002-02-07 21:58           ` Val Henson
2002-02-07 23:09             ` Mark A. Greer
2002-02-08  3:02         ` Tom Rini
2002-02-08  6:05         ` Christopher Murtagh
2002-02-08  6:25           ` Val Henson
2002-02-08 17:36       ` Val Henson

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=20020205115618.D6834@boardwalk \
    --to=val@nmt.edu \
    --cc=benh@kernel.crashing.org \
    --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).