From: Tom Rini <trini@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Chris Friesen <cfriesen@nortelnetworks.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: problem with cache flush routine for G5?
Date: Thu, 4 Mar 2004 16:57:54 -0700 [thread overview]
Message-ID: <20040304235754.GK26065@smtp.west.cox.net> (raw)
In-Reply-To: <1078444268.5698.27.camel@gaston>
On Fri, Mar 05, 2004 at 10:51:08AM +1100, Benjamin Herrenschmidt wrote:
> On Fri, 2004-03-05 at 08:06, Chris Friesen wrote:
> > We're running into issues with the "flush_data_cache" routine on the G5.
> >
> > For the G5, the L1 dcache is 32K and the L2 cache is 512K. At 128
> > bytes/cacheline, that's 256 and 4096 cachelines, respectively.
> >
> > In the existing tree, NUM_CACHE_LINES is set to 128*8, or 1024. Is this
> > an oversight or am I missing something?
> >
> > Also, I'm curious why the dcbf instruction is not used for this.
>
> First of all, why do you need to flush the cache at all ?
>
> If you are talking about the cache flush in the 32 bits bootloaders,
> then yes, this seem to be broken, you should ask Tom Rini who
> maintain these things.
... unless this is a 'G5' that's not in a pmac, it's not my code, and
the openfirmware bootloaders don't, IIRC, do any cache stuff.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-03-04 23:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 21:06 Chris Friesen
2004-03-04 23:51 ` Benjamin Herrenschmidt
2004-03-04 23:57 ` Tom Rini [this message]
2004-03-05 0:04 ` Benjamin Herrenschmidt
2004-03-05 0:44 ` Chris Friesen
2004-03-05 15:15 ` Tom Rini
2004-03-05 23:51 ` Benjamin Herrenschmidt
2004-03-05 0:37 ` Chris Friesen
2004-03-05 2:10 ` Benjamin Herrenschmidt
2004-03-05 5:39 ` Chris Friesen
2004-03-05 5:46 ` Benjamin Herrenschmidt
2004-03-05 17:21 ` Chris Friesen
2004-03-05 23:53 ` Benjamin Herrenschmidt
2004-03-06 1:34 ` Segher Boessenkool
2004-03-06 2:31 ` Anton Blanchard
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=20040304235754.GK26065@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=benh@kernel.crashing.org \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®