From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Mark Lord <lkml@rtr.ca>,
Andi Kleen <ak@suse.de>
Subject: Re: divorce CONFIG_X86_PAE from CONFIG_HIGHMEM64G
Date: Thu, 7 Jun 2007 20:06:29 -0700 [thread overview]
Message-ID: <20070608030629.GW6909@holomorphy.com> (raw)
In-Reply-To: <20070607194156.d4aacf4c.akpm@linux-foundation.org>
On Thu, 7 Jun 2007 19:35:51 -0700 William Lee Irwin III <wli@holomorphy.com> wrote:
>> PAE is useful for more than supporting more than 4GB RAM. It supports
>> expanded swapspace and NX executable protections. Some users may want
>> NX or expanded swapspace support without the overhead or instability
>> of highmem. For these reasons, the following patch divorces
>> CONFIG_X86_PAE from CONFIG_HIGHMEM64G.
On Thu, Jun 07, 2007 at 07:41:56PM -0700, Andrew Morton wrote:
> Do (CONFIG_X86_PAE && !CONFIG_HIGHMEM64G) and (!CONFIG_X86_PAE && CONFIG_HIGHMEM64G)
> kernels actually work? I wouldn't be surprised if there are places where we used
> the incorrect one.
!CONFIG_X86_PAE && CONFIG_HIGHMEM64G doesn't make sense and is not allowed
by this patch. CONFIG_X86_PAE && !CONFIG_HIGHMEM64G works here.
-- wli
next prev parent reply other threads:[~2007-06-08 3:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 2:35 divorce CONFIG_X86_PAE from CONFIG_HIGHMEM64G William Lee Irwin III
2007-06-08 2:41 ` Andrew Morton
2007-06-08 3:06 ` William Lee Irwin III [this message]
2007-06-08 3:38 ` H. Peter Anvin
2007-06-08 3:41 ` William Lee Irwin III
2007-06-08 3:44 ` H. Peter Anvin
2007-06-08 3:51 ` William Lee Irwin III
2007-06-11 23:52 ` Adrian Bunk
2007-06-12 0:00 ` William Lee Irwin III
2007-06-12 1:12 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2007-06-08 8:07 Mikael Pettersson
2007-06-08 14:47 ` William Lee Irwin III
2007-06-12 8:37 linux
2007-06-13 7:26 Bodo Eggert
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=20070608030629.GW6909@holomorphy.com \
--to=wli@holomorphy.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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