linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Charles Lohr <lohr85@gmail.com>
To: Conor Dooley <conor@kernel.org>
Cc: "Clément Léger" <cleger@rivosinc.com>,
	"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 11:00:41 -0800	[thread overview]
Message-ID: <CAGu26P_v9FjYq9Bncvfd-dBhdHQevvN3HpO1nqjA2hYFCpG7hg@mail.gmail.com> (raw)
In-Reply-To: <20240226-pajamas-okay-51e16426b0f5@spud>

WOAH! Please DO NOT deprecate NOMMU. I use the NOMMU build constantly
and NOMMU Linux on RISC-V is the avenue used by many FPGA soft cores
for Linux, as well as some limited systems.

I get new copies of the kernel when there are releases and test them
frequently to make sure everything is still working as expected.

For us we just don't care about XIP. I mean if someone did push it
through to fruition, I'd also test and use it, but I urge you please
do not deprecate this.  While it's sometimes needed a bit of a
creative build to get everything working, I've never needed to patch
anything in the kernel beyond patching in a custom console for serial
output.

I am happy to discuss the possibility of me and or one of the other
RISC-V soft (FPGA) core people stepping up to try to be more active,
but so far we've just been very well serviced by the current NOMMU
Linux setup.

Charles


On Mon, Feb 26, 2024 at 8:03 AM Conor Dooley <conor@kernel.org> wrote:
>
> 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.
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv

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

  reply	other threads:[~2024-02-26 19:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 14:06 [PATCH] riscv: deprecate CONFIG_MMU=n Clément Léger
2024-02-26 14:57 ` Damien Le Moal
2024-02-26 14:59   ` Clément Léger
2024-02-26 15:01     ` Damien Le Moal
2024-02-26 15:14 ` Samuel Holland
2024-02-26 15:25   ` Clément Léger
2024-02-26 16:02     ` Conor Dooley
2024-02-26 19:00       ` Charles Lohr [this message]
2024-02-26 21:29         ` Conor Dooley
2024-02-27  9:11         ` Clément Léger
2024-02-27 16:38           ` Palmer Dabbelt
2024-03-14 12:46             ` Jisheng Zhang
2024-03-14 13:02               ` Jisheng Zhang
2024-03-25 16:59                 ` Jisheng Zhang
2024-03-26 20:25                   ` Charles Lohr
2024-03-27  1:14                     ` Jisheng Zhang
2024-03-27  1:34                       ` Charles Lohr
2024-03-27  3:40                         ` Jisheng Zhang

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=CAGu26P_v9FjYq9Bncvfd-dBhdHQevvN3HpO1nqjA2hYFCpG7hg@mail.gmail.com \
    --to=lohr85@gmail.com \
    --cc=ajones@ventanamicro.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=atishp@rivosinc.com \
    --cc=bjorn@rivosinc.com \
    --cc=cleger@rivosinc.com \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=samuel.holland@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).