From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Robert Johnson <rjohnson@sierraphotonics.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: PowerPC PPC32 CONFIG_HIGHMEM dependency question
Date: Tue, 18 Mar 2014 11:54:38 +0100 [thread overview]
Message-ID: <20140318105438.GA10448@linutronix.de> (raw)
In-Reply-To: <d23eabd04d35481db8b483f9630341fd@SPIEXCHMAIL01.sierraphotonics.com>
* Robert Johnson | 2014-03-17 17:41:25 [+0000]:
>I am using an embedded single board computer (SBC) that has a Freescale P2020 processor. The vendor board support package (BSP) for this product currently uses a 3.0.4 Linux kernel. In looking through the RT patch for various Linux kernel versions even up through 3.12.13-rt21, I see that CONFIG_HIGHMEM is not allowed if CONFIG_PREEMPT_RT_FULL is selected (see arch/powerpc/Kconfig).
>
>The result for my SBC is that if I enable CONFIG_PREEMPT_RT_FULL in the kernel, I am then only able to access 1GB of RAM instead of the 4GB that is resident.
For 2 GiB you could move the memory mapping to something like 1.5GiB
userland, 2.GiB kernel and the remaining 500MiB for virtual.
>Is there any way to get CONFIG_PREEMPT_RT_FULL to work with CONFIG_HIGHMEM?
Yes. The trick is to look either at the ARM code or at the x86 code and
do something similar for powerpc.
>If I want to use CONFIG_HIGHMEM, should I consider the use of CONFIG_PREEMPT_RTB which does not appear to have a dependency?
You could CONFIG_PREEMPT_RT_BASE with CONFIG_HIGHMEM, yes. But then
don't complain about your latency which will be higher compared to
_FULL. Again: CONFIG_PREEMPT_RT_BASE is only debugging option.
Sebastian
next prev parent reply other threads:[~2014-03-18 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 17:41 PowerPC PPC32 CONFIG_HIGHMEM dependency question Robert Johnson
2014-03-18 10:54 ` Sebastian Andrzej Siewior [this message]
2014-03-21 15:12 ` Robert Johnson
2014-03-21 20:02 ` Sebastian Andrzej Siewior
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=20140318105438.GA10448@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=rjohnson@sierraphotonics.com \
/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;
as well as URLs for NNTP newsgroup(s).