linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Charlie Jenkins <charlie@rivosinc.com>
To: Conor Dooley <conor@kernel.org>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
	"Paul Walmsley" <paul.walmsley@sifive.com>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	"Eric Biederman" <ebiederm@xmission.com>,
	"Kees Cook" <keescook@chromium.org>,
	"Shuah Khan" <shuah@kernel.org>,
	"Alexandre Ghiti" <alexghiti@rivosinc.com>,
	"Björn Töpel" <bjorn@rivosinc.com>,
	"Conor Dooley" <conor.dooley@microchip.com>,
	"Greentime Hu" <greentime.hu@sifive.com>,
	"Zong Li" <zong.li@sifive.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Guo Ren" <guoren@kernel.org>,
	"Andrew Jones" <ajones@ventanamicro.com>,
	"Sergey Matyukevich" <sergey.matyukevich@syntacore.com>,
	"David Hildenbrand" <david@redhat.com>,
	"Mayuresh Chitale" <mchitale@ventanamicro.com>,
	"Qinglin Pan" <panqinglin2020@iscas.ac.cn>,
	"Anshuman Khandual" <anshuman.khandual@arm.com>,
	"Huacai Chen" <chenhuacai@kernel.org>,
	"Brian Cain" <bcain@quicinc.com>,
	"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Stafford Horne" <shorne@gmail.com>,
	"Kefeng Wang" <wangkefeng.wang@huawei.com>,
	"Anup Patel" <anup@brainfault.org>,
	"Sunil V L" <sunilvl@ventanamicro.com>,
	"Evan Green" <evan@rivosinc.com>,
	"Guillaume Tucker" <guillaume.tucker@collabora.com>,
	"Mark Brown" <broonie@kernel.org>,
	"Nick Desaulniers" <ndesaulniers@google.com>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	"open list:RISC-V ARCHITECTURE" <linux-riscv@lists.infradead.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	"open list:EXEC & BINFMT API" <linux-mm@kvack.org>,
	"open list:KERNEL SELFTEST FRAMEWORK"
	<linux-kselftest@vger.kernel.org>,
	"Atish Kumar Patra" <atishp@rivosinc.com>
Subject: Re: [PATCH 0/2] Restrict address space for sv39,sv48,sv57
Date: Tue, 27 Jun 2023 14:07:08 -0700	[thread overview]
Message-ID: <CA+7dDtL=bNCSWOTet8NLqOaceaNKQaPaw-cKEFbW2gh6wFeb7g@mail.gmail.com> (raw)
In-Reply-To: <CA+7dDtKARX35pcgdKopuM6c8oj+TKLRhXcF0+d4MZE51V7Bifg@mail.gmail.com>

I see it in patchwork here:
https://patchwork.kernel.org/project/linux-mm/cover/20230626183611.40479-1-charlie@rivosinc.com/.

On Tue, Jun 27, 2023 at 1:44 PM Charles Jenkins <charlie@rivosinc.com> wrote:
>
> I talked to Atish, he's not sure what's going on here either. I am going
> to add him to the CC list.
>
> On Tue, Jun 27, 2023 at 11:24 AM Conor Dooley <conor@kernel.org> wrote:
>
> > Hey Charlie,
> >
> > On Mon, Jun 26, 2023 at 11:36:02AM -0700, Charlie Jenkins wrote:
> > > Make sv39 the default address space for mmap as some applications
> > > currently depend on this assumption. The RISC-V specification enforces
> > > that bits outside of the virtual address range are not used, so
> > > restricting the size of the default address space as such should be
> > > temporary. A hint address passed to mmap will cause the largest address
> > > space that fits entirely into the hint to be used. If the hint is less
> > > than or equal to 1<<38, a 39-bit address will be used. After an address
> > > space is completely full, the next smallest address space will be used.
> > >
> > > Documentation is also added to the RISC-V virtual memory section to
> > explain
> > > these changes.
> >
> > I don't know what went wrong here, but this never ended up in patchwork
> > for some reason, although it has appeared on lore. That seems to be via
> > the docs mailing list, rather than linux-riscv. Could you speak to Atish
> > and see if he knows what went wrong?
> >
> > Cheers,
> > Conor.
> >
> > >
> > > Charlie Jenkins (2):
> > >   RISC-V: mm: Restrict address space for sv39,sv48,sv57
> > >   RISC-V: mm: Update documentation and include test
> > >
> > >  Documentation/riscv/vm-layout.rst             | 20 ++++++++
> > >  arch/riscv/include/asm/elf.h                  |  2 +-
> > >  arch/riscv/include/asm/pgtable.h              | 21 ++++++--
> > >  arch/riscv/include/asm/processor.h            | 41 +++++++++++++---
> > >  tools/testing/selftests/riscv/Makefile        |  2 +-
> > >  tools/testing/selftests/riscv/mm/Makefile     | 22 +++++++++
> > >  .../selftests/riscv/mm/testcases/mmap.c       | 49 +++++++++++++++++++
> > >  7 files changed, 144 insertions(+), 13 deletions(-)
> > >  create mode 100644 tools/testing/selftests/riscv/mm/Makefile
> > >  create mode 100644 tools/testing/selftests/riscv/mm/testcases/mmap.c
> > >
> > >
> > > base-commit: eef509789cecdce895020682192d32e8bac790e8
> > > --
> > > 2.34.1
> > >
> >


      reply	other threads:[~2023-06-27 21:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 18:36 Charlie Jenkins
2023-06-26 18:36 ` [PATCH 1/2] RISC-V: mm: " Charlie Jenkins
2023-06-26 18:36 ` [PATCH 2/2] RISC-V: mm: Update documentation and include test Charlie Jenkins
2023-06-27 18:24 ` [PATCH 0/2] Restrict address space for sv39,sv48,sv57 Conor Dooley
2023-06-27 20:44   ` Charles Jenkins
2023-06-27 21:07     ` Charlie Jenkins [this message]

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='CA+7dDtL=bNCSWOTet8NLqOaceaNKQaPaw-cKEFbW2gh6wFeb7g@mail.gmail.com' \
    --to=charlie@rivosinc.com \
    --cc=ajones@ventanamicro.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexghiti@rivosinc.com \
    --cc=anshuman.khandual@arm.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=atishp@rivosinc.com \
    --cc=bcain@quicinc.com \
    --cc=bjorn@rivosinc.com \
    --cc=broonie@kernel.org \
    --cc=chenhuacai@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=corbet@lwn.net \
    --cc=david@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=evan@rivosinc.com \
    --cc=geert@linux-m68k.org \
    --cc=greentime.hu@sifive.com \
    --cc=guillaume.tucker@collabora.com \
    --cc=guoren@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mchitale@ventanamicro.com \
    --cc=ndesaulniers@google.com \
    --cc=palmer@dabbelt.com \
    --cc=panqinglin2020@iscas.ac.cn \
    --cc=paul.walmsley@sifive.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=sergey.matyukevich@syntacore.com \
    --cc=shorne@gmail.com \
    --cc=shuah@kernel.org \
    --cc=sunilvl@ventanamicro.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=zong.li@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