In any case, note that the cache descriptor structures
defined by MIPS Technologies for the Linux 2.2 kernels
(coming one of these days to 2.3) allow for the cache
geometry to be fully described and specified, either
as a simple table copy based on the PrID, or as a
combination of table data and dynamic probing.
From: Jun Sun <email@example.com>
To: Dominic Sweetman <firstname.lastname@example.org>
Cc: email@example.com <firstname.lastname@example.org>; email@example.com
<firstname.lastname@example.org>; email@example.com <firstname.lastname@example.org>
Date: Saturday, July 01, 2000 3:29 AM
Subject: Re: R5000 support (specifically two-way set-associative cache...)
>> o "index" operations just go first through one set, then the other.
>> So long as initialisation routines are applied to each possible
>> index in turn, both sets get initialised.
>> o "hit" operations "just work".
>> So long as initialisation is done carefully (basic rule: perform one
>> stage to the whole cache before going on to the next), run-time cache
>> maintenance can and should be done with "hit" instructions, and you
>> don't need to worry whether the CPU is direct mapped, 2- or 4-way set
>> (it's all explained in my book, "See MIPS Run", of course...)
>> Even with the Vr5432 you only have to know the difference when first
>> setting up the CPU.
>Not exactly - the current Linux/MIPS implementation uese index
>operations to flush cache.
>As a result flush_all_cache() does not really flush all cache.
>> Dominic Sweetman
>> Algorithmics Ltd