From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Rust in the kernel
Date: Mon, 04 Jul 2022 14:57:38 +0200 [thread overview]
Message-ID: <878rp9c9x9.fsf@gnu.org> (raw)
In-Reply-To: <Yr3RYnthsOf4C6c1@jasmine.lan> (Leo Famulari's message of "Thu, 30 Jun 2022 12:37:54 -0400")
Hi!
Leo Famulari <leo@famulari.name> skribis:
> The effort to use the Rust programming language within the Linux kernel
> is progressing and may be realized in the next few months:
>
> https://lwn.net/SubscriberLink/899182/6c831b90eaee015e/
> https://www.memorysafety.org/blog/memory-safety-in-linux-kernel/
>
> Within Guix, we'll need to adapt our kernel build processes in order to
> support this.
>
> Although I help with updating and configuring the kernel builds, I won't
> be able to participate in the "Rust in the kernel" effort for Guix.
Understood…
> So, interested volunteers should begin organizing :)
Yup!
Now, concretely, how long will it take before key parts of the kernel
are written in Rust? Hopefully a long time, no? Per the article above,
it’s starting small, with Rust usage in well-defined locations.
This is not to say that we shouldn’t start organizing, but rather that
we still have a bit of time ahead.
(During that time, interested readers can also take a stab at improving
support for the Hurd, which relies on that revolutionary technology
called “address spaces” to ensure Memory Safety™ among other things!)
Ludo’.
next prev parent reply other threads:[~2022-07-04 12:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 16:37 Rust in the kernel Leo Famulari
2022-06-30 16:48 ` Leo Famulari
2022-07-04 12:57 ` Ludovic Courtès [this message]
2022-07-04 17:35 ` Akib Azmain Turja
2022-07-04 21:34 ` jbranso
2022-07-05 4:47 ` Akib Azmain Turja
2022-07-05 14:00 ` jbranso
2022-07-05 15:35 ` Akib Azmain Turja
2022-07-05 18:54 ` jbranso
2022-07-05 8:47 ` Akib Azmain Turja
2022-07-06 15:31 ` Ludovic Courtès
2022-07-06 16:25 ` Akib Azmain Turja
-- strict thread matches above, loose matches on Subject: below --
2022-07-05 18:29 Nathan Dehnel
2022-07-05 18:32 Nathan Dehnel
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rp9c9x9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).