From: Charlie Jenkins <charlie@rivosinc.com>
To: Jessica Clarke <jrtc27@jrtc27.com>
Cc: Alexandre Ghiti <alexghiti@rivosinc.com>,
Atish Patra <atishp@rivosinc.com>,
Conor Dooley <conor@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@rivosinc.com>,
Albert Ou <aou@eecs.berkeley.edu>,
bjorn@rivosinc.com, Anup Patel <anup@brainfault.org>,
Evan Green <evan@rivosinc.com>,
linux-riscv <linux-riscv@lists.infradead.org>,
konstantin@linuxfoundation.org, linux-doc@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/2] RISC-V: mm: Restrict address space for sv39,sv48,sv57
Date: Tue, 27 Jun 2023 16:38:58 -0700 [thread overview]
Message-ID: <ZJtzEn9Yut3nPuw8@ghost> (raw)
In-Reply-To: <473F7474-D7AA-4C9F-95A3-320F1741EC50@jrtc27.com>
Yes it is small to have a default of 38-bits of userspace. I would be
interesting in the opinions of other people on whether it would be
acceptable to have the default be sv48 and require applications that
prefer fewer bits to specify so with the given mmap hinting.
next prev parent reply other threads:[~2023-06-27 23:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 22:21 [PATCH 0/2] Make SV39 the default address space Charlie Jenkins
2023-06-27 22:21 ` [PATCH 1/2] RISC-V: mm: Restrict address space for sv39,sv48,sv57 Charlie Jenkins
2023-06-27 22:32 ` Jessica Clarke
2023-06-27 23:36 ` Palmer Dabbelt
2023-06-28 7:44 ` Nick Kossifidis
2023-06-27 23:38 ` Charlie Jenkins [this message]
2023-06-28 12:34 ` Anup Patel
2023-06-29 1:38 ` Charlie Jenkins
2023-06-27 22:21 ` [PATCH 2/2] RISC-V: mm: Update documentation and include test Charlie Jenkins
2023-06-28 10:18 ` Muhammad Usama Anjum
-- strict thread matches above, loose matches on Subject: below --
2023-06-26 18:36 [PATCH 0/2] Restrict address space for sv39,sv48,sv57 Charlie Jenkins
2023-06-26 18:36 ` [PATCH 1/2] RISC-V: mm: " Charlie Jenkins
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=ZJtzEn9Yut3nPuw8@ghost \
--to=charlie@rivosinc.com \
--cc=alexghiti@rivosinc.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=bjorn@rivosinc.com \
--cc=conor@kernel.org \
--cc=evan@rivosinc.com \
--cc=jrtc27@jrtc27.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@rivosinc.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