From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: 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: Sat, 07 Mar 2009 21:43:00 +0200 [thread overview]
Message-ID: <49B2CE44.4060305@pardus.org.tr> (raw)
In-Reply-To: <20090307193026.GA2165@x200.localdomain>
Alexey Dobriyan wrote:
> On Sat, Mar 07, 2009 at 01:04:38PM +0200, Ozan Çağlayan wrote:
>>
>> I'm quite dumb about the internal structures of the kernel but, wouldn't it
>> be possible to create a simple read-only sysfs object like kexec_loaded
>> that will contain "1" when the kernel needs HIGHMEM64G to see all of the memory
>> and "0" when it doesn't?
>
> Why do you need a file? If kernel says to enable HIGHMEM64G, enable it.
It's not for me. We're not able to ship HIGHMEM64G enabled kernel packages with
distributions because it breaks some processors not having PAE flag.
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.
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.
If the linux kernel is able to drop such an advisory message into the log buffer,
it would be very easy to implement a read-only sysfs object. dmesg parsing
is another hacky, dirty solution to the problem that I would not prefer at all.
Regards,
--
Ozan Çağlayan
<ozan_at_pardus.org.tr>
next prev parent reply other threads:[~2009-03-07 19:45 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 [this message]
2009-03-08 20:20 ` Andi Kleen
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=49B2CE44.4060305@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=adobriyan@gmail.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