From: Peter Allworth <linsol@zeta.org.au>
To: Jesper Skov <jskov@redhat.com>
Cc: duncanp@research.canon.com.au,
linuxppc-embedded@lists.linuxppc.org,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Low memory problems in 8xx Linux
Date: Thu, 10 Feb 2000 10:26:30 +1100 [thread overview]
Message-ID: <38A1F7A6.F7DD8ED4@zeta.org.au> (raw)
In-Reply-To: 14497.10437.498606.647038@thinktwice.zoftcorp.dk
Jesper Skov wrote:
<snip>
> I read the patch and think I understand what's going on, but I don't
> see where the GUARDED bits comes in. Maybe I'm missing some subtlety
> from other patches (cllf?) and should not use the code at all. I'd
> better back it out.
>
> Jesper
>
Apologies for being vague. I have a head-cold and my brain seems to be
on vacation. :(
The guarded flag doesn't appear in the patch but in
cllf-2.2.13/arch/ppc/kernel/head.S
(from Dan's distribution for the Classic Lite Low Fat board)
near where the head.S-patch is applied.
Somewhere in the DataStoreTLBMiss routine, I think, you'll see the comment:
/* Insert the Guarded flag into the TWC from the Linux PTE.
<snip>
*/
This is one of the areas where cllf-2.2.13 differs from mpc8xx-2.2.13.
HTH,
PeterA.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-09 23:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-31 15:02 Low memory problems in 8xx Linux Marcus Sundberg
2000-02-01 2:51 ` Peter Allworth
2000-02-01 18:08 ` Marcus Sundberg
2000-02-01 19:47 ` Dan Malek
2000-02-01 23:30 ` Peter Allworth
2000-02-01 23:59 ` Dan Malek
2000-02-01 23:54 ` duncanp
2000-02-02 0:25 ` Peter Allworth
2000-02-08 10:01 ` Jesper Skov
2000-02-09 0:00 ` Peter Allworth
2000-02-09 8:43 ` Jesper Skov
2000-02-09 23:26 ` Peter Allworth [this message]
2000-02-09 1:11 ` more " Peter Allworth
2000-02-09 5:52 ` Dan Malek
2000-02-09 8:40 ` Jesper Skov
2000-03-22 15:43 ` Residual data Claude Robitaille
2000-03-23 10:36 ` Gabriel Paubert
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=38A1F7A6.F7DD8ED4@zeta.org.au \
--to=linsol@zeta.org.au \
--cc=duncanp@research.canon.com.au \
--cc=jskov@redhat.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-embedded@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).