Re: [PATCH] riscv: deprecate CONFIG_MMU=n

From: Conor Dooley <conor@kernel.org>
To: "Clément Léger" <cleger@rivosinc.com>
Cc: "Samuel Holland" <samuel.holland@sifive.com>,
	"Paul Walmsley" <paul.walmsley@sifive.com>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	"Conor Dooley" <conor.dooley@microchip.com>,
	"Andrew Jones" <ajones@ventanamicro.com>,
	"Damien Le Moal" <dlemoal@kernel.org>,
	"Björn Töpel" <bjorn@rivosinc.com>,
	"Atish Patra" <atishp@rivosinc.com>
Subject: Re: [PATCH] riscv: deprecate CONFIG_MMU=n
Date: Mon, 26 Feb 2024 16:02:44 +0000	[thread overview]
Message-ID: <20240226-pajamas-okay-51e16426b0f5@spud> (raw)
In-Reply-To: <ea356036-5a0b-47ea-aafb-f9813cc6ec9b@rivosinc.com>

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

On Mon, Feb 26, 2024 at 04:25:24PM +0100, Clément Léger wrote:
> I guess I could also mark XIP as deprecated. 

I'm not so sure, people recently added XIP support to QEMU (and sent
kernel fixes in December). XIP is also not nearly as much of a problem
to support, there's far less that it does differently, the main barrier
was the inability to test it which is no longer the case.
That said, XIP is gonna kill itself off I feel as it does not support
runtime patching and therefore is extremely limited on extensions, given
we use alternatives for all of that (although I suppose if someone has a
usecase they could make nasty macros worse and implement a compiletime
switch in the alternatives too).

Cheers,
Conor.

[-- 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