From: Dave Jones <davej@suse.de>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
"J.A. Magallon" <jamagallon@able.es>,
Lista Linux-Kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] intel-x86 model config cleanup
Date: Thu, 30 May 2002 13:09:47 +0200 [thread overview]
Message-ID: <20020530130947.J26821@suse.de> (raw)
In-Reply-To: <20020530021159.B26821@suse.de> <200205300243.g4U2hIZ369399@saturn.cs.uml.edu>
On Wed, May 29, 2002 at 10:43:18PM -0400, Albert D. Cahalan wrote:
> No, it's like this:
> I want one kernel. I have a Pentium-MMX and a Pentium Pro.
> I don't need support for a 386, 486, Athlon, or Xeon.
>
> It's also like this:
>
> We have a lab full of Athlon and Pentium III boxes.
> There's not a Pentium 4 in sight, and no Pentium II
> either. It's too much work to manage multiple kernels;
> every box must boot from the same disk image.
Ok, I think I see what you're getting at. Instead of a multi-list
giving one result, you'd like to tick every box that kernel is
going run on, and have it spit out CONFIG_Mxxx for each of those
processors.
It's doable, and it keeps things like vendor kernels possible
(they just select all CPUs), it's probably quite a bit of work
though.
The trickiest bit is getting the Makefile right to choose
the lowest-chosen-denominator in the list for its gcc options, and that's
probably not that hard, just a few extra ifdefs in an already ifdef heavy area.
Other than that, dealing with the cases like "this cpu has TSC" "this
doesn't" and "this has this bug" "this doesn't have this bug" need to be
done too, but thats again, just a few more ifdefs away..
Dave.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-05-30 11:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 14:35 [PATCH] intel-x86 model config cleanup J.A. Magallon
2002-05-29 20:37 ` Jeff Garzik
2002-05-29 20:38 ` Jeff Garzik
2002-05-29 22:05 ` Albert D. Cahalan
2002-05-30 0:11 ` Dave Jones
2002-05-30 2:43 ` Albert D. Cahalan
2002-05-30 4:34 ` Jeff Garzik
2002-05-30 11:09 ` Dave Jones [this message]
2002-05-29 22:44 ` J.A. Magallon
2002-05-29 22:54 ` Jeff Garzik
2002-05-29 23:06 ` J.A. Magallon
2002-05-29 23:12 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020530130947.J26821@suse.de \
--to=davej@suse.de \
--cc=acahalan@cs.uml.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jamagallon@able.es \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox