From: "J.A. Magallon" <jamagallon@able.es>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: "J.A. Magallon" <jamagallon@able.es>,
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: Thu, 30 May 2002 01:06:44 +0200 [thread overview]
Message-ID: <20020529230644.GC3174@werewolf.able.es> (raw)
In-Reply-To: <20020529143544.GA2224@werewolf.able.es> <3CF53C03.5040301@mandrakesoft.com> <3CF53C34.2080300@mandrakesoft.com> <20020529224423.GA3174@werewolf.able.es> <3CF55C3D.6030008@mandrakesoft.com>
On 2002.05.30 Jeff Garzik wrote:
>
>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.
>
Grep on the tree showed this:
drivers/char/serial.c:
#if defined(__i386__) && (defined(CONFIG_M386) || defined(CONFIG_M486))
#define SERIAL_INLINE
#endif
include/asm-i386/processor.h:
/* Prefetch instructions for Pentium III and AMD Athlon */
#ifdef CONFIG_MPENTIUMIII
#define ARCH_HAS_PREFETCH
extern inline void prefetch(const void *x)
{
__asm__ __volatile__ ("prefetchnta (%0)" : : "r"(x));
}
#elif CONFIG_X86_USE_3DNOW
#define ARCH_HAS_PREFETCH
#define ARCH_HAS_PREFETCHW
#define ARCH_HAS_SPINLOCK_PREFETCH
More candidates for CONFIG_X86_xxxxx.
But these spawn over other architextures:
include/asm-alpha/processor.h:#define ARCH_HAS_PREFETCH
include/asm-ppc/processor.h:#define ARCH_HAS_PREFETCH
...
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.3 (Cooker) for i586
Linux werewolf 2.4.19-pre9-jam1 #1 SMP mié may 29 02:20:48 CEST 2002 i686
next prev parent reply other threads:[~2002-05-29 23:07 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
2002-05-29 23:06 ` J.A. Magallon [this message]
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=20020529230644.GC3174@werewolf.able.es \
--to=jamagallon@able.es \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@suse.de \
--cc=jgarzik@mandrakesoft.com \
--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