From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Tom Rini <trini@kernel.crashing.org>
Subject: Re: problem with cache flush routine for G5?
Date: Thu, 04 Mar 2004 19:37:07 -0500 [thread overview]
Message-ID: <4047CBB3.9050608@nortelnetworks.com> (raw)
In-Reply-To: 1078444268.5698.27.camel@gaston
Benjamin Herrenschmidt wrote:
> First of all, why do you need to flush the cache at all ?
In-house OS emulator. For some reason it wants to be able to flush the
cache. I don't know why.
> 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.
>
> The kernel proper definitely doesn't contain such a routine.
It did in 2.4, and we added a syscall to export it to userspace. Now
I'm supposed to figure out what to do for 2.6, and it appears that the
kernel version is gone and the one in boot is screwed.
The only remaining ppc version of flush_data_cache is used by
flush_instruction_cache in arc/ppc/boot/common/util.S
There is also another version of flush_instruction_cache implemented in
arch/ppc/kernel/misc.S.
Here are the suspicious instances of flush_instruction_cache in
arch/ppc/boot:
boot/prep/head.S: bl flush_instruction_cache
boot/common/util.S:_GLOBAL(flush_instruction_cache)
boot/simple/relocate.S: b flush_instruction_cache
boot/simple/relocate.S: b flush_instruction_cache
boot/simple/misc-embedded.c: flush_instruction_cache();
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2004-03-05 0:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 21:06 problem with cache flush routine for G5? Chris Friesen
2004-03-04 23:51 ` Benjamin Herrenschmidt
2004-03-04 23:57 ` Tom Rini
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 [this message]
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=4047CBB3.9050608@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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