From: Florian Boelstler <euphoria@arcor.de>
To: linux-rt-users@vger.kernel.org
Subject: Re: 2.6.26.8-rt16 powerpc and mem=...
Date: Wed, 18 Feb 2009 12:48:39 +0100 [thread overview]
Message-ID: <gngsin$50r$1@ger.gmane.org> (raw)
In-Reply-To: <gnet5c$7k2$1@ger.gmane.org>
Hi,
I did some further tests in the meanwhile.
If the memory is reduced to 256M with mem=256M Linux does not make use
of highmem, since memory can be completely mapped using a single CAM entry.
(Kernel output: Memory CAM mapping: CAM0=256Mb, CAM1=0Mb, CAM2=0Mb
residual: 0Mb)
In that case the initrd is successfully mounted at all times up to now.
When I was starting to play with mem=... on vanilla kernels I was told
[1] that it should be trivial to allow more than three levels of CAM
mappings. May be this is an intermediate solution.
Florian
[1] http://ozlabs.org/pipermail/linuxppc-embedded/2008-June/030638.html
next prev parent reply other threads:[~2009-02-18 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 17:46 2.6.26.8-rt16 powerpc and mem= Florian Boelstler
2009-02-17 17:54 ` Florian Boelstler
2009-02-18 11:48 ` Florian Boelstler [this message]
2009-02-18 16:13 ` Florian Boelstler
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='gngsin$50r$1@ger.gmane.org' \
--to=euphoria@arcor.de \
--cc=linux-rt-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.