From: dave.martin@linaro.org (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: Single zImage and A15/LPAE
Date: Tue, 9 Oct 2012 15:17:36 +0100 [thread overview]
Message-ID: <20121009141736.GB2122@linaro.org> (raw)
In-Reply-To: <2043931.InXdkgrjkp@wuerfel>
On Tue, Oct 09, 2012 at 07:51:02AM +0000, Arnd Bergmann wrote:
> On Monday 08 October 2012 22:18:24 Nicolas Pitre wrote:
> > On Mon, 8 Oct 2012, Stephen Warren wrote:
> >
> > > I'm curious what the single-zImage story is for Cortex A15 CPUs with
> > > LPAE extensions; IIRC, LPAE entails a different page table format and so
> > > isn't going to co-exist in the same zImage as non-LPAE
> >
> > LPAE vs non LPAE is an even more invasive change than ARMv6+ vs pre
> > ARMv6 support. So no, I don't think we'll ever support LPAE and non
> > LPAE configs in the same kernel binary.
> >
> > > (although doesn't x86 support that now; I though separate
> > > LPAE/non-LPAE kernels went away there?)
> >
> > I don't think so. At least Ubuntu apparently still carries a PAE and
> > non PAE kernel packages. Fedora doesn't, probably because they decided
> > not to support non PAE capable machines anymore. We certainly cannot
> > make this choice on ARM yet.
>
> Fedora 18 still has both PAE and non-PAE kernels. I would really hope
> they could give up the PAE version in favor of a 64 bit kernel in
> the 32 bit distro, but it seems none of the big distros trust the
> compat code enough yet. On x86, the number of 32 bit machines still
> running with more than 3GB of RAM installed should be very marginal
> now, most people running the PAE kernel actually have 64 bit capable
> CPUs and have some legacy 32 bit applications that are easier to
> run with a 32 bit user space.
>
> Maybe we get to the same point on ARM in some 10 years, but for
> the forseeable future, Cortex-a15 machines with lots of RAM will
> be very real and we need to have separate kernels for those.
In the medium term we could work around this with a fat kernel in
principle (i.e., bundle a non-LPAE single kernel together with an LPAE
one and choose the right one at boot time). This can be solved outside
the kernel if necessary.
This is not great, but the general feeling seems to be that combining
LPAE and non-LPAE in the same kernel is just not going to be worth the
pain (either in code or runtime impacts).
For AArch64, we obviously have a different kernel binary anyway.
Cheers
---Dave
next prev parent reply other threads:[~2012-10-09 14:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 23:02 Single zImage and A15/LPAE Stephen Warren
2012-10-09 2:18 ` Nicolas Pitre
2012-10-09 7:51 ` Arnd Bergmann
2012-10-09 14:17 ` Dave Martin [this message]
2013-05-29 0:28 ` Kukjin Kim
2013-05-29 1:54 ` Nicolas Pitre
2013-05-29 2:02 ` Olof Johansson
2013-05-29 2:04 ` Olof Johansson
2013-05-29 13:01 ` Arnd Bergmann
2013-05-29 15:15 ` Catalin Marinas
2013-05-29 21:51 ` Arnd Bergmann
2013-05-30 16:56 ` Catalin Marinas
2013-07-16 4:01 ` Kukjin Kim
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=20121009141736.GB2122@linaro.org \
--to=dave.martin@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).