From: Andi Kleen <andi@firstfloor.org>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: Alexey Dobriyan <adobriyan@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] A simple way to determine if the kernel needs HIGHMEM64G to be able to use all the installed memory
Date: Sun, 08 Mar 2009 21:20:49 +0100 [thread overview]
Message-ID: <87r617ojfi.fsf@firstfloor.org> (raw)
In-Reply-To: <49B2CE44.4060305@pardus.org.tr> (Ozan Çağlayan's message of "Sat, 07 Mar 2009 21:43:00 +0200")
Ozan Çağlayan <ozan@pardus.org.tr> writes:
>
> So, the PAE enabled kernel should be installed by distribution installers or
> package management systems if the processor honors the PAE bit. Because PAE
> is an extension mechanism for 32bit processors, AFAIK it has some overhead.
> So enabling it if the user doesn't have a memory size >=4GB would not make
> much sense if a proper noexecute (NX) support is not intended.
The general recommendation is to always use PAE when the machine
is NX capable. Or at least use it by default.
> Fedora installer parses /proc/iomem to see if any address listed is bigger than
> 0x100000000h. I checked it on a machine having 4GB of memory, and it failed.
Newer kernels have the memmap in /sys/firmware/memmap to export the memory
map. If anything is in there >4GB you need PAE.
But there's also the problem that a few systems have MMIO mappings above 4GB.
If you're lucky they are in the memmap too, but sometimes they are not.
For those you also always need PAE. The only way to check for that
would be to load all drivers and then check /proc/iomem or walk
the PCI resources (in /sys/bus/pci). That would be still not 100% fool
proof, but probably as good as you can get.
-Andi
next prev parent reply other threads:[~2009-03-08 20:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 11:04 [RFC] A simple way to determine if the kernel needs HIGHMEM64G to be able to use all the installed memory Ozan Çağlayan
2009-03-07 19:30 ` Alexey Dobriyan
2009-03-07 19:43 ` Ozan Çağlayan
2009-03-08 20:20 ` Andi Kleen [this message]
2009-03-09 13:42 ` [PATCH] x86: suggest running a 64bit kernel on LM capable machines with plenty memory Peter Zijlstra
2009-03-09 19:15 ` Andi Kleen
2009-03-10 9:37 ` Peter Zijlstra
2009-03-10 12:50 ` Andi Kleen
2009-03-10 13:21 ` Arjan van de Ven
2009-03-11 12:01 ` Peter Zijlstra
2009-03-11 12:38 ` Andi Kleen
2009-03-11 11:47 ` Ingo Molnar
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=87r617ojfi.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ozan@pardus.org.tr \
/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