From: Brian Waite <waite@skycomputers.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Disable cache on 74xx
Date: Thu, 20 Feb 2003 09:09:50 -0500 [thread overview]
Message-ID: <200302200909.50420.waite@skycomputers.com> (raw)
In-Reply-To: <1045749699.18487.7532.camel@hermes.chez-thomas.org>
Gary,
Thanks for the clarification. I appreciate the real life experiences. This is
exactly why I said "in the User Manual". I was hoping you would come back
with the exact answer you provided. :) I'll keep my eyes open.
Thanks
Brian
On Thursday 20 February 2003 9:01 am, Gary Thomas wrote:
> On Thu, 2003-02-20 at 06:55, Brian Waite wrote:
> > According to The User's Manual, the data cache instructions become no-ops
> > if the data cache is disabled.
>
> There are "User Manuals" and then there is "Real Life". My
> experience has been that trying to execute these instructions
> with the cache disabled was treated like an invalid instruction
> (hence causing a trap). Maybe this isn't always true with all
> PowerPC processors, but I was just pointing out that you might
> run into trouble with it.
>
> > Thanks
> > Brian
> >
> > On Wednesday 19 February 2003 5:48 pm, Gary Thomas wrote:
> > > On Wed, 2003-02-19 at 14:07, Benjamin Herrenschmidt wrote:
> > > > On Wed, 2003-02-19 at 21:52, Brian Waite wrote:
> > > > > Hi all,
> > > > > I am trying to hunt down a memory controller configuration problem
> > > > > and I have been asked to disable all caching so as to remove it
> > > > > from the equation. I can easl disable L2 but when I start ucking
> > > > > with the WIMG bits to set cache inhibit, The kernel panics with
> > > > > stack overflows. Does anyone know where or what I have to set to
> > > > > disable caching?
> > > >
> > > > Hrm... set L2 and L3 off, then hack HID0 to disable L1 ?
> > >
> > > There are other problems with this. With the caches disabled
> > > (via HID0) all data cache instructions (like DCBF) will fail.
> > > There are some of these in the kernel itself, but beware that
> > > GLIBC has it's own set.
> > >
> > > ... totally disabling the data CACHE with Linux is non-trivial.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-02-20 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 20:52 Disable cache on 74xx Brian Waite
2003-02-19 21:07 ` Benjamin Herrenschmidt
2003-02-19 22:48 ` Gary Thomas
2003-02-20 13:55 ` Brian Waite
2003-02-20 14:01 ` Gary Thomas
2003-02-20 14:09 ` Geert Uytterhoeven
2003-02-20 15:23 ` Dan Malek
2003-02-20 15:47 ` Brian Waite
2003-02-20 15:54 ` Gary Thomas
2003-02-20 15:55 ` Benjamin Herrenschmidt
2003-02-20 16:14 ` Dan Malek
2003-02-20 16:51 ` Mark A. Greer
2003-02-20 14:09 ` Brian Waite [this message]
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=200302200909.50420.waite@skycomputers.com \
--to=waite@skycomputers.com \
--cc=benh@kernel.crashing.org \
--cc=gary@mlbassoc.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).