From: Zi Yan <ziy@nvidia.com>
To: Xu Lu <luxu.kernel@bytedance.com>
Cc: paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, ardb@kernel.org, anup@brainfault.org,
atishp@atishpatra.org, xieyongji@bytedance.com,
lihangjing@bytedance.com, punit.agrawal@bytedance.com,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Linux MM <linux-mm@kvack.org>
Subject: Re: [RFC PATCH v2 00/21] riscv: Introduce 64K base page
Date: Thu, 05 Dec 2024 21:00:23 -0500 [thread overview]
Message-ID: <F94D21C0-8189-404A-B796-BB3C6620AB89@nvidia.com> (raw)
In-Reply-To: <20241205103729.14798-1-luxu.kernel@bytedance.com>
On 5 Dec 2024, at 5:37, Xu Lu wrote:
> This patch series attempts to break through the limitation of MMU and
> supports larger base page on RISC-V, which only supports 4K page size
> now. The key idea is to always manage and allocate memory at a
> granularity of 64K and use SVNAPOT to accelerate address translation.
> This is the second version and the detailed introduction can be found
> in [1].
>
> Changes from v1:
> - Rebase on v6.12.
>
> - Adjust the page table entry shift to reduce page table memory usage.
> For example, in SV39, the traditional va behaves as:
>
> ----------------------------------------------
> | pgd index | pmd index | pte index | offset |
> ----------------------------------------------
> | 38 30 | 29 21 | 20 12 | 11 0 |
> ----------------------------------------------
>
> When we choose 64K as basic software page, va now behaves as:
>
> ----------------------------------------------
> | pgd index | pmd index | pte index | offset |
> ----------------------------------------------
> | 38 34 | 33 25 | 24 16 | 15 0 |
> ----------------------------------------------
>
> - Fix some bugs in v1.
>
> Thanks in advance for comments.
>
> [1] https://lwn.net/Articles/952722/
This looks very interesting. Can you cc me and linux-mm@kvack.org
in the future? Thanks.
Have you thought about doing it for ARM64 4KB as well? ARM64’s contig PTE
should have similar effect of RISC-V’s SVNAPOT, right?
>
> Xu Lu (21):
> riscv: mm: Distinguish hardware base page and software base page
> riscv: mm: Configure satp with hw page pfn
> riscv: mm: Reimplement page table entry structures
> riscv: mm: Reimplement page table entry constructor function
> riscv: mm: Reimplement conversion functions between page table entry
> riscv: mm: Avoid pte constructor during pte conversion
> riscv: mm: Reimplement page table entry get function
> riscv: mm: Reimplement page table entry atomic get function
> riscv: mm: Replace READ_ONCE with atomic pte get function
> riscv: mm: Reimplement PTE A/D bit check function
> riscv: mm: Reimplement mk_huge_pte function
> riscv: mm: Reimplement tlb flush function
> riscv: mm: Adjust PGDIR/P4D/PUD/PMD_SHIFT
> riscv: mm: Only apply svnapot region bigger than software page
> riscv: mm: Adjust FIX_BTMAPS_SLOTS for variable PAGE_SIZE
> riscv: mm: Adjust FIX_FDT_SIZE for variable PMD_SIZE
> riscv: mm: Apply Svnapot for base page mapping if possible
> riscv: Kconfig: Introduce 64K page size
> riscv: Kconfig: Adjust mmap rnd bits for 64K Page
> riscv: mm: Adjust address space layout and init page table for 64K
> Page
> riscv: mm: Update EXEC_PAGESIZE for 64K Page
>
> arch/riscv/Kconfig | 34 +-
> arch/riscv/include/asm/fixmap.h | 3 +-
> arch/riscv/include/asm/hugetlb.h | 5 +
> arch/riscv/include/asm/page.h | 56 ++-
> arch/riscv/include/asm/pgtable-32.h | 12 +-
> arch/riscv/include/asm/pgtable-64.h | 128 ++++--
> arch/riscv/include/asm/pgtable-bits.h | 3 +-
> arch/riscv/include/asm/pgtable.h | 564 +++++++++++++++++++++++---
> arch/riscv/include/asm/tlbflush.h | 26 +-
> arch/riscv/include/uapi/asm/param.h | 24 ++
> arch/riscv/kernel/head.S | 4 +-
> arch/riscv/kernel/hibernate.c | 21 +-
> arch/riscv/mm/context.c | 7 +-
> arch/riscv/mm/fault.c | 15 +-
> arch/riscv/mm/hugetlbpage.c | 30 +-
> arch/riscv/mm/init.c | 45 +-
> arch/riscv/mm/kasan_init.c | 7 +-
> arch/riscv/mm/pgtable.c | 111 ++++-
> arch/riscv/mm/tlbflush.c | 31 +-
> arch/s390/include/asm/hugetlb.h | 2 +-
> include/asm-generic/hugetlb.h | 5 +-
> include/linux/pgtable.h | 21 +
> kernel/events/core.c | 6 +-
> mm/debug_vm_pgtable.c | 6 +-
> mm/gup.c | 10 +-
> mm/hmm.c | 2 +-
> mm/hugetlb.c | 4 +-
> mm/mapping_dirty_helpers.c | 2 +-
> mm/memory.c | 4 +-
> mm/mprotect.c | 2 +-
> mm/ptdump.c | 8 +-
> mm/sparse-vmemmap.c | 2 +-
> mm/vmscan.c | 2 +-
> 33 files changed, 1029 insertions(+), 173 deletions(-)
> create mode 100644 arch/riscv/include/uapi/asm/param.h
>
> --
> 2.20.1
Best Regards,
Yan, Zi
next parent reply other threads:[~2024-12-06 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241205103729.14798-1-luxu.kernel@bytedance.com>
2024-12-06 2:00 ` Zi Yan [this message]
2024-12-06 2:41 ` [External] " Xu Lu
2024-12-06 10:13 ` David Hildenbrand
2024-12-06 13:42 ` [External] " Xu Lu
2024-12-06 18:48 ` Pedro Falcato
2024-12-07 8:03 ` Xu Lu
2024-12-07 22:02 ` Yu Zhao
2024-12-09 3:36 ` Xu Lu
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=F94D21C0-8189-404A-B796-BB3C6620AB89@nvidia.com \
--to=ziy@nvidia.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=atishp@atishpatra.org \
--cc=lihangjing@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luxu.kernel@bytedance.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=punit.agrawal@bytedance.com \
--cc=xieyongji@bytedance.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