Re: [PATCH 0/2] Restrict address space for sv39,sv48,sv57

From: Conor Dooley <conor@kernel.org>
To: Charles Jenkins <charlie@rivosinc.com>
Cc: "Paul Walmsley" <paul.walmsley@sifive.com>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	"Björn Töpel" <bjorn@rivosinc.com>,
	"Conor Dooley" <conor.dooley@microchip.com>,
	"Anup Patel" <anup@brainfault.org>,
	"Evan Green" <evan@rivosinc.com>,
	linux-riscv@lists.infradead.org,
	"Atish Kumar Patra" <atishp@rivosinc.com>,
	"Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
Subject: Re: [PATCH 0/2] Restrict address space for sv39,sv48,sv57
Date: Tue, 27 Jun 2023 22:11:59 +0100	[thread overview]
Message-ID: <20230627-paddle-chatter-257a9885722a@spud> (raw)
In-Reply-To: <20230627-john-spree-0f82769618c5@spud>

[-- Attachment #1.1: Type: text/plain, Size: 2137 bytes --]

On Tue, Jun 27, 2023 at 10:10:06PM +0100, Conor Dooley wrote:
> On Tue, Jun 27, 2023 at 01:44:18PM -0700, Charles Jenkins wrote:
> 
> - all the random CCs

And without ballsing up Konstantin's address....

> 
> > On Tue, Jun 27, 2023 at 11:24 AM Conor Dooley <conor@kernel.org> wrote:
> > > 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?
> 
> > I talked to Atish, he's not sure what's going on here either. I am going
> > to add him to the CC list.
> 
> Atish is the one with admin for the list, I figured he'd be able to tell
> if it got bounced properly. If it got bounced correctly, but didn't
> arrive in patchwork then I don't know.
> 
> Usually when a bunch of lists are CCed, multiple entries show up on
> lore, afair. In this case, a bunch of lists were CCed, but only the one
> via linux-doc appeared on lore.
> 
> Konstantin, any ideas?
> 
> Cheers,
> Conor.
> 

> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv