Re: About Celeron processor memory barrier problem

From: The Doctor What (docwhat@gerf.org)
Date: Mon Dec 25 2000 - 02:19:15 EST

Next message: Linus Torvalds: "Re: innd mmap bug in 2.4.0-test12"
Previous message: Joe deBlaquiere: "sysmips call and glibc atomic set"
In reply to: Linus Torvalds: "Re: About Celeron processor memory barrier problem"
Next in thread: Alan Cox: "Re: About Celeron processor memory barrier problem"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

* Linus Torvalds (torvalds@transmeta.com) [001224 16:27]:
> 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.

Good Lord, YES! And while we're at it, how about a:
"Build into kernel every module for hardware I have..."

That'd make a 'make config' one line....

(I'll go back to dreaming)

Ciao!

-- Excusing bad programming is a shooting offence, no matter _what_ the circumstances. -- Linus Torvalds (linux-kernel mailing list)

The Doctor What: Not that 'who' guy http://docwhat.gerf.org/ docwhat@gerf.org KF6VNC - 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/

Next message: Linus Torvalds: "Re: innd mmap bug in 2.4.0-test12"
Previous message: Joe deBlaquiere: "sysmips call and glibc atomic set"
In reply to: Linus Torvalds: "Re: About Celeron processor memory barrier problem"
Next in thread: Alan Cox: "Re: About Celeron processor memory barrier problem"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Dec 31 2000 - 21:00:08 EST