From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: linux-mips@linux-mips.org
Subject: Re: [patch] R4k cache code synchronization
Date: Fri, 10 Jan 2003 14:03:26 +0100 [thread overview]
Message-ID: <20030110140326.B7699@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1030110131859.23678B-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Fri, Jan 10, 2003 at 01:37:12PM +0100
On Fri, Jan 10, 2003 at 01:37:12PM +0100, Maciej W. Rozycki wrote:
> I can't see any need for flush_cache_l1() and flush_cache_l2(). I'd like
> to remove them. A single flush_cache_all() seems sufficient for our
> needs. Any objections?
The reason for the existance of flush_cache_l1 and flush_cache_l2 is the
Origin. An empty flush_cache_all() is sufficient on the Origin because
it's R10000 processor doesn't suffer from cache aliases. During bootup
we have to flush all caches or the cache coherence logic will send crazy
exceptions at us. For all other occasions just a flush of the primary
caches is sufficient which is why there is flush_cache_l1.
So I think we want to wrap things a bit nicer but basically we have to
keep those cacheops for the sake of the Origin.
Ralf
next prev parent reply other threads:[~2003-01-10 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 12:37 [patch] R4k cache code synchronization Maciej W. Rozycki
2003-01-10 13:03 ` Ralf Baechle [this message]
2003-01-10 13:30 ` Maciej W. Rozycki
2003-01-10 13:36 ` Juan Quintela
2003-01-10 13:33 ` Juan Quintela
2003-01-10 13:33 ` Maciej W. Rozycki
2003-01-10 13:51 ` Juan Quintela
2003-01-10 14:02 ` Maciej W. Rozycki
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=20030110140326.B7699@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.