From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Sandeep Kumar <sandeepksinha@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: PAE and PSE ??
Date: Mon, 23 Oct 2006 16:14:05 +0200 [thread overview]
Message-ID: <200610231614.05716.rjw@sisk.pl> (raw)
In-Reply-To: <453CCD5E.6060303@zytor.com>
On Monday, 23 October 2006 16:10, H. Peter Anvin wrote:
> Rafael J. Wysocki wrote:
> >
> > Well, "AMD64 Architecture Programmer’s Manual" says the following:
> >
> > The choice of 2 Mbyte or 4 Mbyte as the large physical-page size
> > depends on the value of CR4.PSE and CR4.PAE, as follows:
> > - If physical-address extensions are enabled (CR4.PAE=1), the
> > large physical-page size is 2 Mbytes, regardless of the value
> > of CR4.PSE.
> > - If physical-address extensions are disabled (CR4.PAE=0)
> > and CR4.PSE=1, the large physical-page size is 4 Mbytes.
> > - If both CR4.PAE=0 and CR4.PSE=0, the only available page
> > size is 4 Kbytes.
> >
>
> That would be a retroactive redef on the part of AMD; it probably makes
> sense for x86-64 if someone thinks that is may drop support for 4 MB
> pages at some point in the distant future. Still, I'm not sure Intel
> would agree with the definition as stated, although I haven't looked in
> the docs.
>
> This is all extremely theoretical, since there has never been a chip
> with PAE=1 and PSE=0, and I wouldn't expect one to appear any time soon.
Agreed.
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
prev parent reply other threads:[~2006-10-23 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 6:29 Sandeep Kumar
2006-10-22 10:15 ` Rafael J. Wysocki
2006-10-22 23:37 ` H. Peter Anvin
2006-10-23 10:13 ` Rafael J. Wysocki
2006-10-23 14:10 ` H. Peter Anvin
2006-10-23 14:14 ` Rafael J. Wysocki [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=200610231614.05716.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeepksinha@gmail.com \
/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
Powered by JetHome