From: Boqun Feng <boqun.feng@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
Borislav Petkov <bp@alien8.de>, Uros Bizjak <ubizjak@gmail.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Gary Guo <gary@garyguo.net>
Subject: Re: [GIT PULL] locking changes for v6.18
Date: Fri, 26 Sep 2025 08:55:14 -0700 [thread overview]
Message-ID: <aNa3YrzdrcXM0bhM@tardis.local> (raw)
In-Reply-To: <aNanBZ9VbIO2CO9x@gmail.com>
On Fri, Sep 26, 2025 at 04:45:25PM +0200, Ingo Molnar wrote:
> Linus,
>
Hi Ingo,
The commits in the pull request look good to me, however I find the
description has some problems.
> Please pull the latest locking/core Git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-core-2025-09-26
>
> # HEAD: 17d9f8eaa87d40a2ff66598875a43363e37a909b MAINTAINERS: update atomic infrastructure entry to include Rust
>
> Locking updates for v6.16 mostly include Rust runtime enhancements:
>
This should be v6.18, right?
> - Add initial support for generic LKMM atomic variables in Rust. (Boqun Feng)
> - Add the wrapper for `refcount_t` in Rust. (Gary Guo)
> - Make `data` in `Lock` structurally pinned. (Daniel Almeida)
This part is not in the pull request. I had two pull requests to tip
tree this cycle:
* For atomics: https://lore.kernel.org/rust-for-linux/20250905044141.77868-1-boqun.feng@gmail.com/
* For locking: https://lore.kernel.org/rust-for-linux/20250919091241.32138-1-boqun.feng@gmail.com/
The second one contains the part you mentioned above, but it's never
been merged into tip tree, so it doesn't exist in tag
locking-core-2025-09-26.
Regards,
Boqun
> - Add a new reviewer, Gary Guo.
>
> Thanks,
>
> Ingo
>
> ------------------>
> Boqun Feng (9):
> rust: Introduce atomic API helpers
> rust: sync: Add basic atomic operation mapping framework
> rust: sync: atomic: Add ordering annotation types
> rust: sync: atomic: Add generic atomics
> rust: sync: atomic: Add atomic {cmp,}xchg operations
> rust: sync: atomic: Add the framework of arithmetic operations
> rust: sync: atomic: Add Atomic<u{32,64}>
> rust: sync: atomic: Add Atomic<{usize,isize}>
> rust: sync: Add memory barriers
>
> Gary Guo (5):
> rust: implement `kernel::sync::Refcount`
> rust: make `Arc::into_unique_or_drop` associated function
> rust: convert `Arc` to use `Refcount`
> rust: block: convert `block::mq` to use `Refcount`
> MAINTAINERS: update atomic infrastructure entry to include Rust
>
>
> MAINTAINERS | 6 +-
> rust/helpers/atomic.c | 1040 +++++++++++++++++++++++++++++
> rust/helpers/barrier.c | 18 +
> rust/helpers/helpers.c | 2 +
> rust/helpers/refcount.c | 10 +
> rust/kernel/block/mq/operations.rs | 7 +-
> rust/kernel/block/mq/request.rs | 73 +-
> rust/kernel/sync.rs | 4 +
> rust/kernel/sync/arc.rs | 55 +-
> rust/kernel/sync/atomic.rs | 551 +++++++++++++++
> rust/kernel/sync/atomic/internal.rs | 265 ++++++++
> rust/kernel/sync/atomic/ordering.rs | 104 +++
> rust/kernel/sync/atomic/predefine.rs | 169 +++++
> rust/kernel/sync/barrier.rs | 61 ++
> rust/kernel/sync/refcount.rs | 113 ++++
> scripts/atomic/gen-atomics.sh | 1 +
> scripts/atomic/gen-rust-atomic-helpers.sh | 67 ++
> 17 files changed, 2454 insertions(+), 92 deletions(-)
> create mode 100644 rust/helpers/atomic.c
> create mode 100644 rust/helpers/barrier.c
> create mode 100644 rust/kernel/sync/atomic.rs
> create mode 100644 rust/kernel/sync/atomic/internal.rs
> create mode 100644 rust/kernel/sync/atomic/ordering.rs
> create mode 100644 rust/kernel/sync/atomic/predefine.rs
> create mode 100644 rust/kernel/sync/barrier.rs
> create mode 100644 rust/kernel/sync/refcount.rs
> create mode 100755 scripts/atomic/gen-rust-atomic-helpers.sh
next prev parent reply other threads:[~2025-09-26 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 14:45 [GIT PULL] locking changes for v6.18 Ingo Molnar
2025-09-26 15:55 ` Boqun Feng [this message]
2025-09-30 21:03 ` pr-tracker-bot
2025-12-01 8:53 ` [GIT PULL] locking updates for v6.19 Ingo Molnar
2025-12-02 5:54 ` pr-tracker-bot
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=aNa3YrzdrcXM0bhM@tardis.local \
--to=boqun.feng@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=ubizjak@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.