On Tue, Oct 05, 2004 at 08:35:52PM +0100, Maciej W. Rozycki wrote: > Well, the nearby comment agrees with me. Is the handler misused or has > someone forgotten to fix the comment (yes, I do know of the R4700 and > R4640/R4650, with the former being almost identical to the R4600 and the > latters being unsupported due to lacking a TLB MMU)? The names R4000 and R4k are at times used to mean any R4000-ish processor. What that means in a particular context isn't always well defined. Even an oddball processor like the R8000 may be covered ... R5000 being the faster twin of the R4600 also uses it. Nevada only got it's own handler due some processor bug; upto it's workaround this class of processors also used the R4000 handler. With hazards.h the need for the nop-free version for the R10000 family went away also, so it moved over to the standard R4000 one. RM7000 was always using it and RM9000 having slightly different hazards than it's predecessors never had a good reason > is it worth the hassle? Or is the "plan" scheduled for around 2.8 or so? Given the experience with clear_user / copy_user going for the runtime generated handlers is relativly easy and can be done without alot of breakage so it's more a question of somebody doing it and I'll not try to stop any reasonable implementation. Ralf
