From: "J.A. Magallon" <jamagallon@able.es>
To: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Use of CONFIG_M686
Date: Tue, 28 May 2002 00:22:53 +0200 [thread overview]
Message-ID: <20020527222253.GG1848@werewolf.able.es> (raw)
Hi all...
Grepping through the sources or the kernel in search of CONFIG_M686
occurences, there are some places where it looks like that flag is
used as 'Anything bigger than a Pentium'. Now kernel has configs
for PIII, P4, probably PII.
It is the f00f bug handling. Files:
arch/i386/kernel/traps.c:
#ifndef CONFIG_M686 <=================== which also passes if PII, P4...
void __init trap_init_f00f_bug(void)
...
arch/i386/kernel/setup.c:
static void __init init_intel(struct cpuinfo_x86 *c)
{
#ifndef CONFIG_M686 <=================== again
static int f00f_workaround_enabled = 0;
...
So thats why I asked if we could use a CONFIG_MPENTIUMPRO, and make
CONFIG_M686 a generic flag that is also defined for anything bigger
than a Pentium (that looks like the current usage).
So:
Pentium -> M586
PPro -> MPENTIUMPRO M686
PII -> MPENTIUMII M686
PIII -> MPENTIUMIII M686
P4 -> MPENTIUM4 M686
--
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-pre8-jam4 #2 SMP dom may 26 11:20:42 CEST 2002 i686
next reply other threads:[~2002-05-27 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 22:22 J.A. Magallon [this message]
2002-05-27 22:29 ` Use of CONFIG_M686 J.A. Magallon
2002-05-28 0:05 ` Alan Cox
2002-05-29 14:25 ` Dave Jones
2002-05-27 22:38 ` Brian Gerst
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=20020527222253.GG1848@werewolf.able.es \
--to=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