From: Arjan van de Ven <arjan@infradead.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ingo Molnar <mingo@elte.hu>,
x86@kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jan Beulich <jbeulich@novell.com>,
Stable Kernel <stable@kernel.org>
Subject: Re: [PATCH] x86: set PAE PHYSICAL_MASK_SHIFT to match 64-bit
Date: Thu, 5 Jun 2008 21:45:36 -0700 [thread overview]
Message-ID: <20080605214536.0e289ebb@infradead.org> (raw)
In-Reply-To: <4848046A.5060006@goop.org>
On Thu, 05 Jun 2008 16:21:14 +0100
Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> When a 64-bit x86 processor runs in 32-bit PAE mode, a pte can
> potentially have the same number of physical address bits as the
> 64-bit host ("Enhanced Legacy PAE Paging").
>
the problem on 32 bit is that if you have that much ram, you run out of
lowmem FAST.... so you have bigger problems.
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-06-06 4:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 15:21 [PATCH] x86: set PAE PHYSICAL_MASK_SHIFT to match 64-bit Jeremy Fitzhardinge
2008-06-05 15:34 ` Jan Beulich
2008-06-05 15:42 ` Jeremy Fitzhardinge
2008-06-05 16:45 ` H. Peter Anvin
2008-06-05 21:14 ` Jeremy Fitzhardinge
2008-06-07 18:35 ` H. Peter Anvin
2008-06-06 9:21 ` [PATCH UPDATED] x86: set PAE PHYSICAL_MASK_SHIFT to 44 bits Jeremy Fitzhardinge
2008-06-06 9:58 ` Jan Beulich
2008-06-06 13:15 ` Andi Kleen
2008-06-06 13:50 ` Jeremy Fitzhardinge
2008-06-10 10:31 ` Ingo Molnar
2008-06-10 13:06 ` Jeremy Fitzhardinge
2008-06-13 7:24 ` Ingo Molnar
2008-06-06 1:40 ` [PATCH] x86: set PAE PHYSICAL_MASK_SHIFT to match 64-bit Andi Kleen
2008-06-06 7:14 ` Jan Beulich
2008-06-06 7:59 ` Jeremy Fitzhardinge
2008-06-06 8:14 ` Jan Beulich
2008-06-06 8:15 ` Jeremy Fitzhardinge
2008-06-07 18:39 ` H. Peter Anvin
2008-06-06 4:45 ` Arjan van de Ven [this message]
2008-06-06 8:08 ` Jeremy Fitzhardinge
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=20080605214536.0e289ebb@infradead.org \
--to=arjan@infradead.org \
--cc=jbeulich@novell.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@kernel.org \
--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