From: Andreas Hindborg <a.hindborg@kernel.org>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Tamir Duberstein" <tamird@gmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Matthew Wilcox" <willy@infradead.org>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Rust xarray for v6.16
Date: Tue, 06 May 2025 13:05:13 +0200 [thread overview]
Message-ID: <87jz6uq9sm.fsf@kernel.org> (raw)
Hi Miguel,
Please pull these changes to enable access to the xarray data structure
from rust.
The following changes since commit 9c32cda43eb78f78c73aee4aa344b777714e259b:
Linux 6.15-rc3 (2025-04-20 13:43:47 -0700)
are available in the Git repository at:
https://github.com/rust-for-linux/linux.git tags/rust-xarray-for-v6.16
for you to fetch changes up to fa616196fbea12462107774fb6a1908c95f71cf0:
MAINTAINERS: add entry for Rust XArray API (2025-05-01 11:37:59 +0200)
Best regards,
Andreas Hindborg
----------------------------------------------------------------
Rust xarray API for v6.16
Introduce Rust support for the `xarray` data structure:
- Add a rust abstraction for the `xarray` data structure. This abstraction
allows rust code to leverage the `xarray` to store types that implement
`ForeignOwnable`. This support is a dependency for memory backing feature of
the rust null block driver, which is waiting to be merged.
- Set up an entry in MAINTAINERS for the xarray rust support. Patches will go
to the new rust xarray tree and then via the rust subsystem tree for now.
`kernel` crate:
- Allow `ForeignOwnable` to carry information about the pointed-to type. This
helps asserting alignment requirements for the pointer passed to the foreign
language.
----------------------------------------------------------------
Tamir Duberstein (3):
rust: types: add `ForeignOwnable::PointedTo`
rust: xarray: Add an abstraction for XArray
MAINTAINERS: add entry for Rust XArray API
MAINTAINERS | 11 ++
rust/bindings/bindings_helper.h | 6 +
rust/helpers/helpers.c | 1 +
rust/helpers/xarray.c | 28 ++++
rust/kernel/alloc/kbox.rs | 38 +++---
rust/kernel/lib.rs | 1 +
rust/kernel/miscdevice.rs | 10 +-
rust/kernel/pci.rs | 2 +-
rust/kernel/platform.rs | 2 +-
rust/kernel/sync/arc.rs | 21 +--
rust/kernel/types.rs | 46 ++++---
rust/kernel/xarray.rs | 275 ++++++++++++++++++++++++++++++++++++++++
12 files changed, 392 insertions(+), 49 deletions(-)
create mode 100644 rust/helpers/xarray.c
create mode 100644 rust/kernel/xarray.rs
next reply other threads:[~2025-05-06 11:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 11:05 Andreas Hindborg [this message]
2025-05-18 20:48 ` [GIT PULL] Rust xarray for v6.16 Miguel Ojeda
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=87jz6uq9sm.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
--cc=tmgross@umich.edu \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).