Messages in this thread | | | Date | Sun, 24 Dec 2000 18:38:56 -0800 | From | Tim Wright <> | Subject | Re: About Celeron processor memory barrier problem |
| |
On Sun, Dec 24, 2000 at 02:25:54PM -0800, Linus Torvalds wrote: > > Indeed. Some of the issues end up just becoming compiler flags, which > means that anything that uses C is "tainted" by the processor choice. And > happily there isn't all that much non-C in the kernel any more. > > One thing we _could_ potentially do is to simplify the CPU selection a > bit, and make it a two-stage process. Basically have a > > bool "Optimize for current CPU" CONFIG_CPU_CURRENT > > which most people who just want to get the best kernel would use. Less > confusion that way. > > Linus
Makes sense. Are you thinking along the lines of parsing /proc/cpuinfo to work out what is there, or did you have something else in mind ?
Regards,
Tim
-- Tim Wright - timw@splhi.com or timw@aracnet.com or twright@us.ibm.com IBM Linux Technology Center, Beaverton, Oregon "Nobody ever said I was charming, they said "Rimmer, you're a git!"" RD VI - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |