From: Alex Ghiti <alex@ghiti.fr>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: corbet@lwn.net, Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, Arnd Bergmann <arnd@arndb.de>,
aryabinin@virtuozzo.com, glider@google.com, dvyukov@google.com,
linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
linux-arch@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/3] Move kernel mapping outside the linear mapping
Date: Sat, 13 Mar 2021 04:26:47 -0500 [thread overview]
Message-ID: <0bb85388-c4e1-523a-9bf3-0ccec6c4041e@ghiti.fr> (raw)
In-Reply-To: <mhng-cf5d29ec-e941-4579-8c42-2c11799a8f2f@penguin>
Hi Palmer,
Le 3/9/21 à 9:54 PM, Palmer Dabbelt a écrit :
> On Thu, 25 Feb 2021 00:04:50 PST (-0800), alex@ghiti.fr wrote:
>> I decided to split sv48 support in small series to ease the review.
>>
>> This patchset pushes the kernel mapping (modules and BPF too) to the last
>> 4GB of the 64bit address space, this allows to:
>> - implement relocatable kernel (that will come later in another
>> patchset) that requires to move the kernel mapping out of the linear
>> mapping to avoid to copy the kernel at a different physical address.
>> - have a single kernel that is not relocatable (and then that avoids the
>> performance penalty imposed by PIC kernel) for both sv39 and sv48.
>>
>> The first patch implements this behaviour, the second patch introduces a
>> documentation that describes the virtual address space layout of the
>> 64bit
>> kernel and the last patch is taken from my sv48 series where I simply
>> added
>> the dump of the modules/kernel/BPF mapping.
>>
>> I removed the Reviewed-by on the first patch since it changed enough from
>> last time and deserves a second look.
>>
>> Alexandre Ghiti (3):
>> riscv: Move kernel mapping outside of linear mapping
>> Documentation: riscv: Add documentation that describes the VM layout
>> riscv: Prepare ptdump for vm layout dynamic addresses
>>
>> Documentation/riscv/index.rst | 1 +
>> Documentation/riscv/vm-layout.rst | 61 ++++++++++++++++++++++
>> arch/riscv/boot/loader.lds.S | 3 +-
>> arch/riscv/include/asm/page.h | 18 ++++++-
>> arch/riscv/include/asm/pgtable.h | 37 +++++++++----
>> arch/riscv/include/asm/set_memory.h | 1 +
>> arch/riscv/kernel/head.S | 3 +-
>> arch/riscv/kernel/module.c | 6 +--
>> arch/riscv/kernel/setup.c | 3 ++
>> arch/riscv/kernel/vmlinux.lds.S | 3 +-
>> arch/riscv/mm/fault.c | 13 +++++
>> arch/riscv/mm/init.c | 81 +++++++++++++++++++++++------
>> arch/riscv/mm/kasan_init.c | 9 ++++
>> arch/riscv/mm/physaddr.c | 2 +-
>> arch/riscv/mm/ptdump.c | 67 +++++++++++++++++++-----
>> 15 files changed, 258 insertions(+), 50 deletions(-)
>> create mode 100644 Documentation/riscv/vm-layout.rst
>
> This generally looks good, but I'm getting a bunch of checkpatch
> warnings and some conflicts, do you mind fixing those up (and including
> your other kasan patch, as that's likely to conflict)?
I fixed a few checkpatch warnings and rebased on top of for-next but had
not conflicts.
I have just sent the v2.
Thanks,
Alex
next prev parent reply other threads:[~2021-03-13 9:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 8:04 [PATCH 0/3] Move kernel mapping outside the linear mapping Alexandre Ghiti
2021-02-25 8:04 ` [PATCH 1/3] riscv: Move kernel mapping outside of " Alexandre Ghiti
2021-02-25 8:04 ` [PATCH 2/3] Documentation: riscv: Add documentation that describes the VM layout Alexandre Ghiti
2021-02-25 10:34 ` David Hildenbrand
2021-02-25 11:56 ` Alex Ghiti
2021-03-10 11:42 ` Arnd Bergmann
2021-03-10 19:12 ` Alex Ghiti
2021-03-11 8:42 ` Arnd Bergmann
2021-03-13 8:23 ` Alex Ghiti
2021-03-13 22:34 ` Arnd Bergmann
2021-02-25 8:04 ` [PATCH 3/3] riscv: Prepare ptdump for vm layout dynamic addresses Alexandre Ghiti
2021-03-10 2:54 ` [PATCH 0/3] Move kernel mapping outside the linear mapping Palmer Dabbelt
2021-03-13 9:26 ` Alex Ghiti [this message]
2021-03-17 5:05 ` Palmer Dabbelt
2021-03-20 8:48 ` Alex Ghiti
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=0bb85388-c4e1-523a-9bf3-0ccec6c4041e@ghiti.fr \
--to=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=aryabinin@virtuozzo.com \
--cc=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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).