From: Benjamin Herrenschmidt <bh40@calva.net>
To: <guillaume.laures@noos.fr>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: progress on l2cr
Date: Tue, 18 Jul 2000 10:03:55 +0200 [thread overview]
Message-ID: <20000718080355.26687@mailhost.mipsys.com> (raw)
In-Reply-To: <3973882B.1C9A581E@noos.fr>
>
>
>Here are two patches against current stable tree, the first,
>l2cr-display-gom.diff, fixes the ouput of "cat /proc/sys/kernel.l2cr"
>according to M Lanners' patch for G3, and according to the Motorola 7400
>Users' Manual.
>Tested on G4, but not G3 yet. It should be clean and harmful anyway.
>
>The second, l2cr-cmdline-gom.diff, is a try to enable "l2cr=xx" kernel
>command line option.
>All is fine if you don't put the option, and hangs at boot with
>something like this: l2cr=0xb5100000.
>Since when I tried to kill calls to __set_L2CR in ppc_setup_l2cr()
>commenting the following two lines:
> _set_L2CR(0); /* disable cache */
> _set_L2CR(val); /* enable it */
>it stills hangs at the same point, I guess the way I call
>ppc_setup_l2cr() is wrong. I couldn't find documentation on this, but I
>figured out reading init/main.c that doing this would be sufficient,
>tell me were I'm wrong :
Try my current rsync tree. I merged in some new code from PowerLogix in
the _set_L2CR() function that work around a few CPU erratas and increase
a few things.
You'll notice that when calling _set_L2CR(x) with x!=0, I always OR x
with the invalidate bit to force an invalidation. It's not necessary to
wait for the invaldation to complete inside the ppc_htab.c code however
since it's done inside the _set_L2CR() function in misc.S
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-18 8:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-17 22:26 progress on l2cr Guillaume Laurès
2000-07-18 6:54 ` Guillaume Laurès
2000-07-18 8:03 ` Benjamin Herrenschmidt [this message]
2000-07-22 1:38 ` Giuliano Pochini
2000-07-22 20:13 ` Benjamin Herrenschmidt
2000-08-01 0:18 ` Giuliano Pochini
2000-07-31 18:42 ` Benjamin Herrenschmidt
2000-08-06 3:25 ` Giuliano Pochini
2000-08-06 9:33 ` Timothy A. Seufert
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=20000718080355.26687@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=guillaume.laures@noos.fr \
--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).