mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: <linux-kernel@vger.kernel.org>
Subject: [PATCH] i386: stand-alone CONFIG_PAE
Date: Tue, 08 Nov 2005 17:55:43 +0100	[thread overview]
Message-ID: <4370E69F.76F0.0078.0@novell.com> (raw)
In-Reply-To: <4370AEE1.76F0.0078.0@novell.com>

[-- Attachment #1: Type: text/plain, Size: 342 bytes --]

Separate the config option for PAE from that for high memory beyond
4G, allowing configurations with non-execute protection without any
(potential) other overhead coming from HIGHMEM64G.
Also appropriately qualify both options depending on configured
minimum processor type.

From: Jan Beulich <jbeulich@novell.com>

(actual patch attached)


[-- Attachment #2: linux-2.6.14-i386-pae.patch --]
[-- Type: application/octet-stream, Size: 1058 bytes --]

Separate the config option for PAE from that for high memory beyond
4G, allowing configurations with non-execute protection without any
(potential) other overhead coming from HIGHMEM64G.
Also appropriately qualify both options depending on configured
minimum processor type.

From: Jan Beulich <jbeulich@novell.com>

--- 2.6.14/arch/i386/Kconfig	2005-10-28 02:02:08.000000000 +0200
+++ 2.6.14-i386-pae/arch/i386/Kconfig	2005-11-04 16:19:32.000000000 +0100
@@ -739,7 +739,7 @@ config HIGHMEM4G
 	  gigabytes of physical RAM.
 
 config HIGHMEM64G
-	bool "64GB"
+	bool "64GB" if !M386 && !M486 && !M586
 	help
 	  Select this if you have a 32-bit processor and more than 4
 	  gigabytes of physical RAM.
@@ -752,9 +752,11 @@ config HIGHMEM
 	default y
 
 config X86_PAE
-	bool
-	depends on HIGHMEM64G
-	default y
+	bool "PAE" if !HIGHMEM64G && !M386 && !M486 && !M586
+	default HIGHMEM64G
+	help
+	  Select this if you want the no-execute MMU functionality despite
+	  your system not having more than 4 gigabytes of RAM.
 
 # Common NUMA Features
 config NUMA

  parent reply	other threads:[~2005-11-08 16:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08 12:57 [PATCH] i386: export genapic again Jan Beulich
2005-11-08 13:08 ` Arjan van de Ven
2005-11-08 13:22   ` Jan Beulich
2005-11-08 13:29 ` Adrian Bunk
2005-11-08 14:17   ` Jan Beulich
2005-11-08 16:52 ` [PATCH] i386: make trap information available to die handlers Jan Beulich
2005-11-08 16:59   ` Randy.Dunlap
2005-11-08 17:08     ` Jan Beulich
2005-11-08 17:13       ` Randy.Dunlap
2005-11-09  8:20         ` Jan Beulich
2005-11-10 12:21           ` Pavel Machek
2005-11-08 20:58       ` Richard Knutsson
2005-11-08 16:52 ` [PATCH] i386: int3 adjustment Jan Beulich
2005-11-09  8:37   ` [PATCH 1/2] i386: double fault adjustment - introduce THREAD_ORDER Jan Beulich
2005-11-09  8:38     ` [PATCH 2/2] i386: double fault adjustment Jan Beulich
2005-11-08 16:54 ` [PATCH] i386: NMI <-> debugging handler adjustments Jan Beulich
2005-11-08 16:55 ` [PATCH] i386: handle NMI case in IPI sending Jan Beulich
2005-11-08 16:55 ` Jan Beulich [this message]
2005-11-08 17:02   ` [PATCH] i386: stand-alone CONFIG_PAE Adrian Bunk
2005-11-08 17:10     ` Jan Beulich
2005-11-08 16:57 ` [PATCH] i386: adjust page fault handling Jan Beulich
2005-11-08 21:22 ` [PATCH] i386: export genapic again Randy.Dunlap
2005-11-09  8:18   ` Jan Beulich

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=4370E69F.76F0.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=linux-kernel@vger.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

Powered by JetHome