lkml.org 
[lkml]   [2006]   [Dec]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    Date
    From
    Subject[PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options
    > > I'd be happy to know how to enable it.
    >
    > CONFIG_HIGHMEM64G=y

    This is not at all obvious from arch/i386/Kconfig. Maybe we should
    fix this?

    - Ted

    Add an explanation that HIGHMEM64G is needed in order to get support
    for the NX feature.

    Remove an (incorrect) assertion that NOHIGHMEM is right for more
    users, since most systems are coming with at least 1G of memory these
    days, and even some laptops have up 4G of memory.

    Finally, although the explanation of the 1G/3G split is correct, it is
    not relevant to the NOHIGHMEM/HIGHMEM4G/HIGHMEM64G discussion, since
    the each process will always see 3GB of virtual memory. It also might
    be something else depending on the setting of CONFIG_VMSPLIT_*.

    Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
    ---
    arch/i386/Kconfig | 17 ++++++++---------
    1 files changed, 8 insertions(+), 9 deletions(-)

    diff --git a/arch/i386/Kconfig b/arch/i386/Kconfig
    index 8ff1c6f..4b8f156 100644
    --- a/arch/i386/Kconfig
    +++ b/arch/i386/Kconfig
    @@ -457,22 +457,21 @@ config NOHIGHMEM
    "high memory".

    If you are compiling a kernel which will never run on a machine with
    - more than 1 Gigabyte total physical RAM, answer "off" here (default
    - choice and suitable for most users). This will result in a "3GB/1GB"
    - split: 3GB are mapped so that each process sees a 3GB virtual memory
    - space and the remaining part of the 4GB virtual memory space is used
    - by the kernel to permanently map as much physical memory as
    - possible.
    + more than 1 Gigabyte total physical RAM, answer "off" here.

    If the machine has between 1 and 4 Gigabytes physical RAM, then
    answer "4GB" here.

    If more than 4 Gigabytes is used then answer "64GB" here. This
    selection turns Intel PAE (Physical Address Extension) mode on.
    - PAE implements 3-level paging on IA32 processors. PAE is fully
    + PAE implements 3-level paging on IA32 processors. PAE is fully
    supported by Linux, PAE mode is implemented on all recent Intel
    - processors (Pentium Pro and better). NOTE: If you say "64GB" here,
    - then the kernel will not boot on CPUs that don't support PAE!
    + processors (Pentium Pro and better). PAE support is also needed
    + if you wish to enable NX support, to make your system more secure by
    + enabling non-executable stacks.
    +
    + NOTE: If you say "64GB" here, then the kernel will not boot
    + on CPUs that don't support PAE!

    The actual amount of total physical memory will either be
    auto detected or can be forced by using a kernel command line option
    --
    1.4.1
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-12-14 16:23    [W:3.198 / U:0.016 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site