From: Bodo Eggert <7eggert@gmx.de>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org, Adrian Bunk <bunk@stusta.de>
Subject: Re: divorce CONFIG_X86_PAE from CONFIG_HIGHMEM64G
Date: Wed, 13 Jun 2007 09:26:30 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0706130809240.2702@be1.lrz> (raw)
Since your (William) patch will change the kconfig files my proposed patch
would change, could you please add those changes?
I hand-updated the patch below as recommended by the original discussion
on LKML. It won't aply as-is because of that (and because of your changes).
--- 2.6.21/arch/i386/Kconfig.ori 2007-06-06 13:41:09.000000000 +0200
+++ 2.6.21/arch/i386/Kconfig 2007-06-06 14:07:40.000000000 +0200
@@ -495,8 +495,8 @@ config NOHIGHMEM
bool "off"
depends on !X86_NUMAQ
---help---
- Linux can use up to 64 Gigabytes of physical memory on x86 systems.
- However, the address space of 32-bit x86 processors is only 4
+ Linux can use up to 64 Gigabytes of physical address space on x86
+ systems. However, the address space of 32-bit x86 processors is only 4
Gigabytes large. That means that, if you have a large amount of
physical memory, not all of it can be "permanently mapped" by the
kernel. The physical memory that's not permanently mapped is called
@@ -510,8 +510,15 @@ config NOHIGHMEM
by the kernel to permanently map as much physical memory as
possible.
- If the machine has between 1 and 4 Gigabytes physical RAM, then
+
+ If the machine has between 1 and about 3 Gigabytes physical RAM,
+ then
answer "4GB" here.
+
+ The PCI address space will usually take 512 MB or 1 GB of address
+ space. This address space is unavailable to RAM, but depending on the
+ chipset (and BIOS settings), memory overlapping the PCI address space
+ may be mapped beyond the 4 GB limit and be available using "64GB".
+
If more than 4 Gigabytes is used then answer "64GB" here. This
selection turns Intel PAE (Physical Address Extension) mode on.
@@ -520,6 +527,10 @@ config NOHIGHMEM
processors (Pentium Pro and better). NOTE: If you say "64GB" here,
then the kernel will not boot on CPUs that don't support PAE!
+ An additional benefit of the 64GB-Mode is the availability of the
+ no-execute-pageflag, which can be used to prevent some attacks from
+ injecting malicious code into applications.
+
The actual amount of total physical memory will either be
auto detected or can be forced by using a kernel command line option
such as "mem=256M". (Try "man bootparam" or see the documentation of
@@ -532,14 +543,14 @@ config HIGHMEM4G
bool "4GB"
depends on !X86_NUMAQ
help
- Select this if you have a 32-bit processor and between 1 and 4
+ Select this if you have a 32-bit processor and between 1 and 3
gigabytes of physical RAM.
config HIGHMEM64G
- bool "64GB"
+ bool "64GB (enables no-execute memory protection if available)"
depends on X86_CMPXCHG64
help
- Select this if you have a 32-bit processor and more than 4
+ Select this if you have a 32-bit processor and more than 3
gigabytes of physical RAM.
endchoice
--
RAM DISK is not an installation procedure!
next reply other threads:[~2007-06-13 7:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 7:26 Bodo Eggert [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-12 8:37 linux
2007-06-08 8:07 Mikael Pettersson
2007-06-08 14:47 ` William Lee Irwin III
2007-06-08 2:35 William Lee Irwin III
2007-06-08 2:41 ` Andrew Morton
2007-06-08 3:06 ` William Lee Irwin III
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
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=Pine.LNX.4.58.0706130809240.2702@be1.lrz \
--to=7eggert@gmx.de \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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
all inboxes | Powered by JetHome®