All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Sandeep Kumar <sandeepksinha@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: PAE and PSE ??
Date: Mon, 23 Oct 2006 07:10:38 -0700	[thread overview]
Message-ID: <453CCD5E.6060303@zytor.com> (raw)
In-Reply-To: <200610231213.47232.rjw@sisk.pl>

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.

	-hpa

  reply	other threads:[~2006-10-23 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-22  6:29 PAE and PSE ?? 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 [this message]
2006-10-23 14:14         ` Rafael J. Wysocki

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=453CCD5E.6060303@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.