From: Boqun Feng <boqun.feng@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: stern@rowland.harvard.edu, parri.andrea@gmail.com,
will@kernel.org, peterz@infradead.org, npiggin@gmail.com,
dhowells@redhat.com, j.alglave@ucl.ac.uk, luc.maranget@inria.fr,
akiyks@gmail.com, dlustig@nvidia.com, joel@joelfernandes.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: Another possible use for LKMM, or a subset (strengthening) thereof
Date: Tue, 19 Oct 2021 10:28:04 +0800 [thread overview]
Message-ID: <YW4tNHz42/EbAdHM@boqun-archlinux> (raw)
In-Reply-To: <20211019000729.GY880162@paulmck-ThinkPad-P17-Gen-1>
On Mon, Oct 18, 2021 at 05:07:29PM -0700, Paul E. McKenney wrote:
> On Tue, Oct 19, 2021 at 07:56:35AM +0800, Boqun Feng wrote:
> > Hi Paul,
> >
> > On Mon, Oct 18, 2021 at 03:53:13PM -0700, Paul E. McKenney wrote:
> > > On Thu, Oct 07, 2021 at 01:56:21PM -0700, Paul E. McKenney wrote:
> > > > Hello!
> > > >
> > > > On the perhaps unlikely chance that this is new news of interest...
> > > >
> > > > I have finally prototyped the full "So You Want to Rust the Linux
> > > > Kernel?" series (as in marked "under construction").
> > > >
> > > > https://paulmck.livejournal.com/62436.html
> > >
> > > And this blog series is now proclaimed to be feature complete.
> > >
> > > Recommendations (both short- and long-term) may be found in the last post,
> > > "TL;DR: Memory-Model Recommendations for Rusting the Linux Kernel",
> > > at https://paulmck.livejournal.com/65341.html.
> >
> > Thanks for putting this together! For the short-term recommendations, I
> > think one practical goal would be having the equivalent (or stronger)
> > litmus tests in Rust for the ones in tools/memory-model/litmus-tests.
> > The translation of litmus tests may be trivial, but it at least ensure
> > us that Rust can support the existing patterns widely used in Linux
> > kernel. Of course, the Rust litmus tests don't have to be able to run
> > with herd, we just need some code snippest to check our understanding of
> > Rust memory model. ;-)
>
> It would be very helpful for klitmus to be able to check Rust-code memory
> ordering, now that you mention it! This would be useful (for example)
> to test the Rust wrappers on weakly ordered systems, such as ARM's.
>
Right.
> > Besides, it's interesting to how things react with each if one function
> > in the litmus test is in Rust and the other is in C ;-) Maybe this is a
> > long-term goal.
> >
> > Thoughts?
>
> These issues are quite important. How do you feel that they should be
> tracked?
>
Yep, it's already in my list. I created a small repo to track all issues
I know about LKMM for Rust:
https://github.com/fbq/lkmm-for-rust
It's still under construction, but I put the litmus test thing in that
list.
Regards,
Boqun
> Thanx, Paul
next prev parent reply other threads:[~2021-10-19 2:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 20:56 Another possible use for LKMM, or a subset (strengthening) thereof Paul E. McKenney
2021-10-18 22:53 ` Paul E. McKenney
2021-10-18 23:56 ` Boqun Feng
2021-10-19 0:07 ` Paul E. McKenney
2021-10-19 2:28 ` Boqun Feng [this message]
2021-10-19 3:50 ` Paul E. McKenney
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=YW4tNHz42/EbAdHM@boqun-archlinux \
--to=boqun.feng@gmail.com \
--cc=akiyks@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will@kernel.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