From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Juan Quintela <quintela@mandrakesoft.com>,
mipslist <linux-mips@linux-mips.org>
Subject: Re: [PATCH]: c-r4k.c 4/7 flush_cache_mm cleanup
Date: Fri, 28 Mar 2003 19:59:53 +0100 [thread overview]
Message-ID: <20030328195953.A17890@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1030328175039.26178B-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Fri, Mar 28, 2003 at 06:51:57PM +0100
On Fri, Mar 28, 2003 at 06:51:57PM +0100, Maciej W. Rozycki wrote:
> > flush_cache_mm can use __flush_cache_all.
>
> Wrong, it should use r4k_flush_pcache_all() unconditionally, but I'm told
> such a setup triggers a bug somewhere, that needs to be tracked down
> before committing that change to the CVS.
Now that the problem is mentioned on the list lemme elaborate a bit. The
problem mentioned only affects R4000SC and R4400SC processors.
Flush_cache_mm is only used when a mm is either copied on fork or when
it's finally destroyed. Because the S-cache is is physically indexed
and the P-cache is refilled from the S-cache if data should be still in
there we don't need to flush the S-cache ever for any of the mm's
cacheflushing functions. So the observation that things are only
working properly if we do flush the S-cache also suggest we're either
having a bug elsewhere in the cache code or we're hitting a hardware
problem.
Ralf
next prev parent reply other threads:[~2003-03-28 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 0:52 [PATCH]: c-r4k.c 4/7 flush_cache_mm cleanup Juan Quintela
2003-03-28 17:51 ` Maciej W. Rozycki
2003-03-28 18:59 ` Ralf Baechle [this message]
2003-03-28 19:33 ` Juan Quintela
2003-03-29 14:41 ` Juan Quintela
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=20030328195953.A17890@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
--cc=quintela@mandrakesoft.com \
/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