From: steve.capper@arm.com (Steve Capper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Map larger kernels at early init
Date: Fri, 17 Nov 2017 11:41:41 +0000 [thread overview]
Message-ID: <20171117114143.26577-1-steve.capper@arm.com> (raw)
The early pagetable creation code assumes that a single pgd, pud, pmd
and pte are sufficient to map the kernel text for MMU bringup. For 16KB
granules this is, unfortunately, rarely the case. Some kernels may be too
big even for a 64KB granule employing this scheme.
This patch series addresses the problem in two steps: 1) re-order the
reserved_ttbr0 to allow its address computation to be independent of
swapper_pg_dir size, 2) re-write the early pgtable code to allow for
multiple page table entries at each level.
Steve Capper (2):
arm64: Re-order reserved_ttbr0 in linker script
arm64: Extend early page table code to allow for larger kernels
arch/arm64/include/asm/asm-uaccess.h | 6 +-
arch/arm64/include/asm/kernel-pgtable.h | 20 ++++-
arch/arm64/include/asm/pgtable.h | 2 +-
arch/arm64/include/asm/uaccess.h | 2 +-
arch/arm64/kernel/head.S | 148 +++++++++++++++++++++++---------
arch/arm64/kernel/vmlinux.lds.S | 6 +-
arch/arm64/mm/mmu.c | 3 +-
7 files changed, 137 insertions(+), 50 deletions(-)
--
2.11.0
next reply other threads:[~2017-11-17 11:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 11:41 Steve Capper [this message]
2017-11-17 11:41 ` [PATCH 1/2] arm64: Re-order reserved_ttbr0 in linker script Steve Capper
2017-11-20 16:25 ` Mark Rutland
2017-11-21 11:15 ` Steve Capper
2017-11-17 11:41 ` [PATCH 2/2] arm64: Extend early page table code to allow for larger kernels Steve Capper
2017-11-20 17:00 ` Mark Rutland
2017-11-21 11:13 ` Steve Capper
2017-11-21 13:14 ` Steve Capper
2017-11-21 13:24 ` Ard Biesheuvel
2017-11-21 16:14 ` Steve Capper
2017-11-21 16:43 ` Ard Biesheuvel
2017-11-17 12:06 ` [PATCH 0/2] Map larger kernels at early init Ard Biesheuvel
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=20171117114143.26577-1-steve.capper@arm.com \
--to=steve.capper@arm.com \
--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).