Re: [PATCH] 2.6 workaround for Athlon/Opteron prefetch errata

[Bill Davidsen]

On Mon, 15 Sep 2003, Adrian Bunk wrote:

> On Mon, Sep 15, 2003 at 07:32:49AM +0100, John Bradford wrote:
> >...
> > It should be possible, and straightforward, to compile a kernel which:
> > 
> > 1. Supports, (I.E. has workarounds for), any combination of CPUs.
> >    E.G. a kernel which supports 386s, and Athlons _only_ would not
> >    need the F00F bug workaround.  Currently '386' kernels include it,
> >    because '386' means 'support 386 and above processors'.
> > 
> > 2. Has compiler optimisations for one particular CPU.
> >    E.G. the 386 and Athlon supporting kernel above could have
> >    alignment optimised for either 386 or Athlon.
> >...
> 
> That's the point where even I consider such a system to be too complex.

How does it strike you to have these:
 - compile support for any CPU which doesn't break the target
   (including slow it in some serious way)
 - drop support for any CPU except the target

It seems to me that this is what the vendors want (as general as possible)
and the size limited users want (small is beautiful).

Fitting the code to this model could be done gradually and hopefully with
some macros to prevent too much ugly ifdef code.

-- 
bill davidsen <davidsen@xxxxxxx>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/