From: Brian Gerst <bgerst@didntduck.org>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Use of CONFIG_M686
Date: Mon, 27 May 2002 18:38:01 -0400 [thread overview]
Message-ID: <3CF2B549.6020803@didntduck.org> (raw)
In-Reply-To: <20020527222253.GG1848@werewolf.able.es>
J.A. Magallon wrote:
> 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
>
>
I fixed that in 2.5 by introducing CONFIG_X86_F00F_BUG.
http://marc.theaimsgroup.com/?l=linux-kernel&m=101416800017102&w=4
--
Brian Gerst
prev parent reply other threads:[~2002-05-27 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 22:22 Use of CONFIG_M686 J.A. Magallon
2002-05-27 22:29 ` J.A. Magallon
2002-05-28 0:05 ` Alan Cox
2002-05-29 14:25 ` Dave Jones
2002-05-27 22:38 ` Brian Gerst [this message]
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=3CF2B549.6020803@didntduck.org \
--to=bgerst@didntduck.org \
--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