From: Josh Triplett <josh@joshtriplett.org>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
alex.gaynor@gmail.com, Greg KH <gregkh@linuxfoundation.org>,
geofft@ldpreload.com, jbaublitz@redhat.com,
Masahiro Yamada <masahiroy@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
keescook@chromium.org
Subject: Re: Linux kernel in-tree Rust support
Date: Fri, 10 Jul 2020 15:59:34 -0700 [thread overview]
Message-ID: <20200710225934.GA16881@localhost> (raw)
In-Reply-To: <20200710125022.alry7wkymalmv3ge@wittgenstein>
On Fri, Jul 10, 2020 at 02:50:22PM +0200, Christian Brauner wrote:
> On Fri, Jul 10, 2020 at 08:28:03AM +0200, Greg KH wrote:
> > On Thu, Jul 09, 2020 at 11:41:47AM -0700, Nick Desaulniers wrote:
> > > Hello folks,
> > > I'm working on putting together an LLVM "Micro Conference" for the
> > > upcoming Linux Plumbers Conf
> > > (https://www.linuxplumbersconf.org/event/7/page/47-attend). It's not
> > > solidified yet, but I would really like to run a session on support
> > > for Rust "in tree." I suspect we could cover technical aspects of
> > > what that might look like (I have a prototype of that, was trivial to
> > > wire up KBuild support), but also a larger question of "should we do
> > > this?" or "how might we place limits on where this can be used?"
> > >
> > > Question to folks explicitly in To:, are you planning on attending plumbers?
> > >
> > > If so, would this be an interesting topic that you'd participate in?
> >
> > Yes, I'll be there.
>
> We actually had this dicussion a while back and there were some more
> people interested in this. I'd be interested to attend this and I've
> spoken with Kees and a few others about this topic at last Plumbers (I
> think Greg might have been around for this informal discussion as well.
> But I might be imagining things.).
I was around for one of the informal conversations with Greg and Kees
and others.
As I recall, Greg's biggest condition for initial introduction of this
was to do the same kind of "turn this Kconfig option on and turn an
option under it off" trick that LTO uses, so that neither "make
allnoconfig" nor "make allyesconfig" would require Rust until we've had
plenty of time to experiment with it. And that seems entirely
reasonable to me too.
- Josh
next prev parent reply other threads:[~2020-07-10 22:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 18:41 Linux kernel in-tree Rust support Nick Desaulniers
2020-07-09 20:52 ` Miguel Ojeda
2020-07-10 5:36 ` Josh Triplett
2020-07-10 6:28 ` Greg KH
2020-07-10 12:50 ` Christian Brauner
2020-07-10 16:10 ` Kees Cook
[not found] ` <CAFRnB2WNo45J8h3-ncopLKENvcO0rf7J3xsy_eRKwFSpDD-5sQ@mail.gmail.com>
2020-07-10 23:05 ` Kees Cook
2020-07-10 22:59 ` Josh Triplett [this message]
2020-07-10 23:54 ` Linus Torvalds
2020-07-11 21:03 ` Josh Triplett
2020-07-28 20:40 ` Pavel Machek
2020-07-29 6:34 ` Josh Triplett
2020-12-17 21:45 ` Pavel Machek
2020-12-18 3:31 ` Miguel Ojeda
2020-07-11 17:13 ` Geoffrey Thomas
2020-07-12 12:31 ` Adrian Bunk
2020-07-12 19:39 ` Josh Triplett
2020-07-12 20:33 ` Linus Torvalds
2020-07-12 20:45 ` Adrian Bunk
2020-07-14 8:27 ` David Laight
2020-07-16 13:06 ` Arnd Bergmann
2020-07-16 23:12 ` Josh Triplett
2020-07-19 18:19 ` Adrian Bunk
2020-07-20 14:46 ` David Laight
2020-08-23 21:02 ` Adrian Bunk
2020-08-23 21:54 ` Geoffrey Thomas
2020-07-13 18:11 ` Eric W. Biederman
2020-07-13 21:33 ` Josh Triplett
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=20200710225934.GA16881@localhost \
--to=josh@joshtriplett.org \
--cc=alex.gaynor@gmail.com \
--cc=christian.brauner@ubuntu.com \
--cc=clang-built-linux@googlegroups.com \
--cc=geofft@ldpreload.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbaublitz@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ndesaulniers@google.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
/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