From: Nigel Stephens <nigel@mips.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: c-r4k.c cleanup
Date: Fri, 04 Feb 2005 14:39:07 +0000 [thread overview]
Message-ID: <4203890B.5030305@mips.com> (raw)
In-Reply-To: <20050204.231254.74753794.anemo@mba.ocn.ne.jp>
Atsushi Nemoto wrote:
>This code is wrong (should be "c->dcache.waysize > PAGE_SIZE") and
>unnecessary (done correctly in probe_pcache).
>
>diff -u -r1.96 c-r4k.c
>--- arch/mips/mm/c-r4k.c 7 Dec 2004 02:33:02 -0000 1.96
>+++ arch/mips/mm/c-r4k.c 4 Feb 2005 14:01:35 -0000
>@@ -1213,9 +1213,6 @@
> probe_pcache();
> setup_scache();
>
>- if (c->dcache.sets * c->dcache.ways > PAGE_SIZE)
>- c->dcache.flags |= MIPS_CACHE_ALIASES;
>-
> r4k_blast_dcache_page_setup();
> r4k_blast_dcache_page_indexed_setup();
> r4k_blast_dcache_setup();
>
>
>Also, some MIPS32/MIPS64 chip have physically indexed data cache so do
>no suffer from aliasing. CPU_20KC is one of them. Others?
>
>
The MIPS 24K family's caches are not physically indexed, but they do
have optional h/w assist to prevent aliases in certain cache
configurations. This optional feature is indicated by the read-only AR
(alias removed) flag being set - that's bit 16 in the CP0 Config7 register.
Nigel
next prev parent reply other threads:[~2005-02-04 14:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 14:12 c-r4k.c cleanup Atsushi Nemoto
2005-02-04 14:39 ` Nigel Stephens [this message]
2005-02-04 14:58 ` Ralf Baechle
2005-02-04 15:19 ` Dominic Sweetman
2005-02-04 15:45 ` Ralf Baechle
2005-02-04 15:53 ` Ralf Baechle
2005-02-04 17:51 ` David Daney
2005-02-04 17:49 ` Jun Sun
2005-02-07 10:24 ` Atsushi Nemoto
2005-02-07 12:32 ` Yoichi Yuasa
2005-02-07 14:04 ` Yoichi Yuasa
2005-02-07 12:36 ` Dominic Sweetman
2005-02-07 13:52 ` Dominic Sweetman
2005-02-07 21:49 ` Ralf Baechle
2005-02-07 21:36 ` Ralf Baechle
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=4203890B.5030305@mips.com \
--to=nigel@mips.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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