public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	davej@suse.de
Subject: Re: [PATCH] intel-x86 model config cleanup
Date: Wed, 29 May 2002 18:54:53 -0400	[thread overview]
Message-ID: <3CF55C3D.6030008@mandrakesoft.com> (raw)
In-Reply-To: <20020529143544.GA2224@werewolf.able.es> <3CF53C03.5040301@mandrakesoft.com> <3CF53C34.2080300@mandrakesoft.com> <20020529224423.GA3174@werewolf.able.es>

J.A. Magallon wrote:

>  
>
>Then for each model you would define its generic CONFIG_M<arch>, and
>the specific features not contained in the generic. And then define
>the rest of features based on generic.
>The CONFIG_M<arch> would serve as a flag for 'this cpu has all features
>of a generic xxx'.
>
>Or if you are worried about namespace pollution these could be named
>CONFIG_CPU_VENDOR_, CONFIG_CPU_, CONFIG_CPU_M.
>  
>


Your division of categories (snipped from above quoted) seems ok.

The basic thing to remember is that "generic_foo" or "cpu_intel_foo" 
options should very rarely, if ever, appear in the config.in or sources. 
 We simply want to use the generic or cpu-specific user selection to 
determine (a) compiler flags, (b) CONFIG_xxx symbols for specific CPU 
features and optimizations, [like CONFIG_X86_F00F_BUG] and maybe (c) 
enable and disable CPU-specific drivers.  (c) will be a special case, 
since very few drivers should require a specific CPU type... but some 
drivers simply don't work on 386.

    Jeff




  reply	other threads:[~2002-05-29 22:56 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
2002-05-29 22:44     ` J.A. Magallon
2002-05-29 22:54       ` Jeff Garzik [this message]
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=3CF55C3D.6030008@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davej@suse.de \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    /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