rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Geert Stappers <stappers@stappers.nl>
Cc: rust-for-linux <rust-for-linux@vger.kernel.org>
Subject: Re: real driver
Date: Thu, 8 Jul 2021 08:25:19 +0200	[thread overview]
Message-ID: <YOaaT59+zoewYhG3@kroah.com> (raw)
In-Reply-To: <20210707191836.nhqciiclpy4ghmj5@gpm.stappers.nl>

On Wed, Jul 07, 2021 at 09:18:36PM +0200, Geert Stappers wrote:
> In-Reply-To: <YOXB7FRqldZik2Xn@kroah.com>
> Previous-Subject: Re: [PATCH 00/17] Rust support
> 
> On Wed, Jul 07, 2021 at 05:02:04PM +0200, Greg Kroah-Hartman wrote:
> > On Wed, Jul 07, 2021 at 03:07:50PM +0100, Wedson Almeida Filho wrote:
> > > > Last I looked at this thing, it was not
> > > > feature-complete compared to the in-kernel binder code, has that been
> > > > resolved and the needed filesystem changes added?
> > > 
> > > It is not feature-complete in comparison to the C one just yet, it is missing a
> > > few things but not for any fundamental reason -- we were mostly focusing on the
> > > kernel crate and tests.
> > 
> > I love it how you call "binderfs is missing" a "few things" :)
> > 
> > > Miguel's point is that it does implement the vast majority of binder features
> > > and is non-trivial, so it could be used as evidence that useful kernel drivers
> > > can be built with Rust; not just "transpiled" from C, but written with the Rust
> > > safety guarantees.
> > 
> > As Christoph said, and I and others have said before, binder is in no
> > way shape or form anything that resembles any sort of "driver" at all.
> > It is a crazy IPC mechanism that is tacked onto the side of the kernel.
> > Not to say that it doesn't have its usages, but the interactions between
> > binder and the rest of the kernel are very small and specific.
> > Something that almost no one else will ever write again.
> > 
> > Please work on a real driver to help prove, or disprove, that this all
> > is going to be able to work properly.  There are huge unanswered
> > questions that need to be resolved that you will run into when you do
> > such a thing.
> 
> Suggesting virtual null modem drivers.

That is not a "real" driver that has to deal with hardware as well as
the core kernel apis at the same time.

virtual drivers are simpler in that they only have to handle "one half"
of the problem, not the whole thing, which is what a "real" driver has
to do.

thanks,

greg k-h

      reply	other threads:[~2021-07-08  6:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-07 19:18 real driver Geert Stappers
2021-07-08  6:25 ` Greg KH [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=YOaaT59+zoewYhG3@kroah.com \
    --to=greg@kroah.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=stappers@stappers.nl \
    /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).