From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Colin King <colin.king@canonical.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Disable 4MB page tables for Atom, work around errata AAE44
Date: Mon, 12 Apr 2010 07:37:22 -0700 [thread overview]
Message-ID: <4BC33022.3000608@zytor.com> (raw)
In-Reply-To: <87633xayk4.fsf@basil.nowhere.org>
On 04/12/2010 01:02 AM, Andi Kleen wrote:
> Colin King <colin.king@canonical.com> writes:
>>
>> +static void __init check_atom(void)
>> +{
>> +
>> + /*
>> + * Disable 4MB page tables to work around Intel errata AAE44 for
>> + * Atom. We cannot guarantee stopping undefined processor behaviour
>> + * when two pageing structure translations differ with respect to
>> + * page frame sizes. Hence, for Atoms we disable the PSE.
>> + */
>> + if (boot_cpu_data.x86_model == 0x1c) {
>
> Perhaps someone else pointed that out already, but you obviously
> need to check for x86_vendor == X86_VENDOR_INTEL and x86_family == 6 too,
> otherwise you'll get false positives.
>
> Besides such workarounds are normally in arch/x86/kernel/cpu/intel.c.
> bugs.c is really obsolete.
>
Much more than that, the constraint is clearly not strict enough. I'm
currently trying to work out internally what the actual constraint
should be (it's a bit of a documentation hole at the moment.)
-hpa
next prev parent reply other threads:[~2010-04-12 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 15:20 [PATCH] x86: Disable 4MB page tables for Atom, work around errata AAE44 Colin King
2010-03-31 22:35 ` Jeremy Fitzhardinge
2010-04-12 8:02 ` Andi Kleen
2010-04-12 14:37 ` H. Peter Anvin [this message]
2010-05-01 21:37 ` Yuhong Bao
2010-04-23 23:52 ` [tip:x86/urgent] x86: Disable large pages on CPUs with Atom erratum AAE44 tip-bot for H. Peter Anvin
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=4BC33022.3000608@zytor.com \
--to=hpa@zytor.com \
--cc=andi@firstfloor.org \
--cc=colin.king@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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