From: Anup Patel <Anup.Patel@wdc.com>
To: Palmer Dabbelt <palmer@sifive.com>, Albert Ou <aou@eecs.berkeley.edu>
Cc: Anup Patel <Anup.Patel@wdc.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mike Rapoport <rppt@linux.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
Atish Patra <Atish.Patra@wdc.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: [PATCH v5 0/2] Two-stagged initial page table setup
Date: Fri, 7 Jun 2019 06:01:24 +0000 [thread overview]
Message-ID: <20190607060049.29257-1-anup.patel@wdc.com> (raw)
This patchset implements two-stagged initial page table setup using fixmap
to avoid mapping non-existent RAM and also reduce high_memory consumed by
initial page tables.
The patchset is based on Linux-5.2-rc3 and tested on SiFive Unleashed board
and QEMU virt machine.
These patches can be found in riscv_setup_vm_v5 branch of
https//github.com/avpatel/linux.git
Changes since v4:
- Added dtb_early_va which points to DTB for early parsing
Changes since v3:
- Changed patch series subject.
- Dropped PATCH1 because it's already merged
- Dropped PATCH3 because trampoline page table handles a corner case
for 32bit systems where load address range overlaps kernel virtual
address range
- Revamped PATCH for 4K aligned booting into two-stagged initial page
table setup
Changes since v2:
- Dropped PATCH2 because we have separate fix for Linux-5.1-rcX
- Moved PATCH5 to PATCH2
- Moved PATCH4 to PATCH3
- The "Booting kernel from any 4KB aligned address" is now PATCH4
Changes since v1:
- Add kconfig option BOOT_PAGE_ALIGNED to enable 4KB aligned booting
- Improved initial page table setup code to select best/biggest
possible mapping size based on load address alignment
- Added PATCH4 to remove redundant trampoline page table
- Added PATCH5 to fix memory reservation in setup_bootmem()
Anup Patel (2):
RISC-V: Fix memory reservation in setup_bootmem()
RISC-V: Setup initial page tables in two stages
arch/riscv/include/asm/fixmap.h | 5 +
arch/riscv/include/asm/pgtable-64.h | 5 +
arch/riscv/include/asm/pgtable.h | 8 +
arch/riscv/kernel/head.S | 17 +-
arch/riscv/kernel/setup.c | 6 +-
arch/riscv/mm/init.c | 331 ++++++++++++++++++++++------
6 files changed, 292 insertions(+), 80 deletions(-)
--
2.17.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2019-06-07 6:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 6:01 Anup Patel [this message]
2019-06-07 6:01 ` [PATCH v5 1/2] RISC-V: Fix memory reservation in setup_bootmem() Anup Patel
2019-06-28 20:59 ` Paul Walmsley
2019-06-07 6:01 ` [PATCH v5 2/2] RISC-V: Setup initial page tables in two stages Anup Patel
2019-07-11 0:05 ` Paul Walmsley
2019-08-15 18:57 ` Alistair Francis
2019-08-15 19:07 ` David Abdurachmanov
2019-08-15 20:25 ` Alistair Francis
2019-08-15 20:29 ` Paul Walmsley
2019-08-15 21:32 ` Alistair Francis
2019-08-16 1:05 ` Anup Patel
2019-06-22 4:13 ` [PATCH v5 0/2] Two-stagged initial page table setup Anup Patel
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=20190607060049.29257-1-anup.patel@wdc.com \
--to=anup.patel@wdc.com \
--cc=Atish.Patra@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=rppt@linux.ibm.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).