[Top] [All Lists]

Re: [PATCH]: c-r4k.c 4/7 flush_cache_mm cleanup

To: Ralf Baechle <>
Subject: Re: [PATCH]: c-r4k.c 4/7 flush_cache_mm cleanup
From: Juan Quintela <>
Date: Fri, 28 Mar 2003 20:33:22 +0100
Cc: "Maciej W. Rozycki" <>, mipslist <>
In-reply-to: <> (Ralf Baechle's message of "Fri, 28 Mar 2003 19:59:53 +0100")
Original-recipient: rfc822;
References: <m2smt89ut8.fsf@neno.mitica> <> <>
User-agent: Gnus/5.090015 (Oort Gnus v0.15) Emacs/21.2.93
>>>>> "ralf" == Ralf Baechle <> writes:

ralf> 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.

ralf> Now that the problem is mentioned on the list lemme elaborate a bit.  The
ralf> problem mentioned only affects R4000SC and R4400SC processors.
ralf> Flush_cache_mm is only used when a mm is either copied on fork or when
ralf> it's finally destroyed.  Because the S-cache is is physically indexed
ralf> and the P-cache is refilled from the S-cache if data should be still in
ralf> there we don't need to flush the S-cache ever for any of the mm's
ralf> cacheflushing functions.  So the observation that things are only
ralf> working properly if we do flush the S-cache also suggest we're either
ralf> having a bug elsewhere in the cache code or we're hitting a hardware
ralf> problem.

Ok, will took a look at that (casually my I2 has an R4400SC), but I
still think that patch can be applied.  It has the same behaviour than
actual code.  And it is a cleanup.  When we found the bug, we can do a

on that function.

Later, Juan.

In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

<Prev in Thread] Current Thread [Next in Thread>