From: "H. Peter Anvin" <hpa@zytor.com>
To: lkml@morethan.org
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
the arch/x86 maintainers <x86@kernel.org>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [Bug Fix]: Do 32-bit table calculations in pre-processor
Date: Fri, 03 Jul 2009 17:11:32 -0700 [thread overview]
Message-ID: <4A4E9E34.2030103@zytor.com> (raw)
In-Reply-To: <200907031905.55258.lkml@morethan.org>
Michael S. Zick wrote:
> On Fri July 3 2009, H. Peter Anvin wrote:
>> Michael S. Zick wrote:
>>>> The CPUID flags, in particular the pse flag.
>>>>
>>> I haven't touch anything that would have changed that -
>>> so this should be representative (the *&^*% datasheet says yes to pse also)
>>>
>> Actually, come to think of it, we don't generate PSE page tables
>> initially -- we only later go in and reclaim the page tables if we
>> switch to PSE (and $DEITY knows if we're doing it correctly...)
>>
>
> I am of that age range where senility has to be considered, but not this time:
>
> "Via C7-M Datasheet", May 2008 (supposed to be most recent) -
>
> page 22 - section 2.3.7 - Table 2-14 "CR4 Bits"
> "<5> PAE: Enables address extensions; C7-M:<r>"
> <quote>An "r" means that this bit is reserved. It appears as a 0 when read,
> and a GP exception is signaled if an attemp is made to write a 1 to this bit.</quote>
>
> Same document -
> page 16 - section 2.3.2 - Table 2-3 "CPUID Feature Flag Values (EAX=1)"
> <EDX:6> PAE: Physical address extensions; C7:<1>
Especially since I was talking about PSE and not PAE.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-07-04 0:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 18:14 Michael S. Zick
2009-07-03 18:27 ` Andi Kleen
2009-07-03 18:38 ` Michael S. Zick
2009-07-03 19:08 ` Jeremy Fitzhardinge
2009-07-03 19:13 ` Michael S. Zick
2009-07-03 19:30 ` Jeremy Fitzhardinge
2009-07-03 20:03 ` Michael S. Zick
2009-07-03 18:56 ` Jeremy Fitzhardinge
2009-07-03 18:57 ` Jeremy Fitzhardinge
2009-07-03 19:03 ` Michael S. Zick
2009-07-03 19:11 ` Jeremy Fitzhardinge
2009-07-03 19:18 ` H. Peter Anvin
2009-07-03 19:46 ` Michael S. Zick
2009-07-03 20:00 ` H. Peter Anvin
2009-07-03 19:14 ` H. Peter Anvin
2009-07-03 19:41 ` Michael S. Zick
2009-07-03 19:48 ` H. Peter Anvin
2009-07-03 20:38 ` Michael S. Zick
2009-07-03 20:40 ` H. Peter Anvin
2009-07-03 21:02 ` Michael S. Zick
2009-07-03 22:33 ` H. Peter Anvin
2009-07-04 0:05 ` Michael S. Zick
2009-07-04 0:11 ` H. Peter Anvin [this message]
2009-07-03 22:01 ` Michael S. Zick
2009-07-04 13:23 ` Michael S. Zick
2009-07-03 19:33 ` Jeremy Fitzhardinge
2009-07-03 20:07 ` Yinghai Lu
2009-07-03 20:08 ` Yinghai Lu
2009-07-03 20:48 ` Michael S. Zick
2009-07-03 20:45 ` Michael S. Zick
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=4A4E9E34.2030103@zytor.com \
--to=hpa@zytor.com \
--cc=ak@linux.intel.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@morethan.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®