mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael T. Kloos" <michael@michaelkloos.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Work to remove kernel dependence on the M-extension
Date: Thu, 10 Mar 2022 23:54:24 -0500	[thread overview]
Message-ID: <e880a9421239e388ebce74f3cd41637886930f03.camel@michaelkloos.com> (raw)
In-Reply-To: <mhng-97bc7422-36da-436a-a326-1705ef6fcace@palmer-ri-x1c9>

Well at least I can take some satisfaction in that it seems that on my
2nd patch sent to the Linux kernel, I got it right the first time.  No
one has complained about problems with the code itself, just that they
don't want the feature.  I have also received no errors back from the
build bot.

For now, I will try to maintain this port on my own.  Thank you for the
consideration Palmer.

	Michael

On Thu, 2022-03-10 at 20:29 -0800, Palmer Dabbelt wrote:
> On Thu, 10 Mar 2022 05:37:27 PST (-0800), Michael@MichaelKloos.com wrote:
> > Is there something I can do that would help alleviate your concerns or
> > apprehension?
> 
> IMO this is one of those cases where having hardware is required.
> 
> I can understand the goal of providing a Linux port for the minimal 
> RISC-V compatible system, but IIUC the minimal RISC-V compatible system 
> is any object associated with a member of the RISC-V foundation that 
> said member attests is a RISC-V system.  There's really no way to 
> implement Linux on all such systems so we have to set the bar somewhere, 
> and bar is generally set at "more time will be spent using this than 
> maintaining it".  Systems without M have generally not met that bar, and 
> I don't see anything changing now.
> 
> If you have users then I'm happy to reconsider, the goal here is to make 
> real systems work.  That said: we've already got enough trouble trying 
> to make actual shipping hardware function correctly, we're all going to 
> lose our minds trying to chase around everything that could in theory be 
> a RISC-V system but doesn't actually exist.
> 
> > 
> > On 3/10/2022 8:22 AM, Michael T. Kloos wrote:
> > 
> > > Some other thoughts:
> > > It sounds like I am not the first person to want this feature and I
> > > probably won't be the last.  I created the change for my own reasons, the
> > > same as any other contributor.  I think we all know that I can not pull
> > > out some chart and say, "This many people want this and here is why."  I
> > > live in central Ohio and have been doing this as a hobby.  I don't even
> > > know anyone else who knows about systems and operating system development.
> > > If the justification that you are looking for is that I as some
> > > hypothetical developer at a major tech company is about to release a new
> > > RISC-V chip without M support but we want it to run Linux, I can not
> > > provide that answer.  It sounds a bit like some software or hardware,
> > > chicken or the egg anyway.  Trying to maintain my own fork if people
> > > start contributing patches with incompatible assembly scares me.
> > >      Michael



      reply	other threads:[~2022-03-11  4:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09  5:28 Michael T. Kloos
2022-03-09 10:02 ` Arnd Bergmann
2022-03-09 11:43   ` Michael T. Kloos
2022-03-09 11:47     ` Arnd Bergmann
2022-03-10  7:34   ` Palmer Dabbelt
2022-03-10  7:54     ` Arnd Bergmann
2022-03-10 17:09       ` Palmer Dabbelt
2022-04-02 10:18         ` Pavel Machek
2022-03-10  7:06 ` Christoph Hellwig
2022-03-10  7:34   ` Palmer Dabbelt
2022-03-10  8:04     ` Christoph Hellwig
2022-03-10  9:31     ` Michael T. Kloos
2022-03-10 13:22       ` Michael T. Kloos
2022-03-10 13:37         ` Michael T. Kloos
2022-03-11  4:29           ` Palmer Dabbelt
2022-03-11  4:54             ` Michael T. Kloos [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=e880a9421239e388ebce74f3cd41637886930f03.camel@michaelkloos.com \
    --to=michael@michaelkloos.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=arnd@arndb.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.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

all inboxes | Powered by JetHome®