From: y86-dev@protonmail.com
To: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Alice Ryhl" <alice@ryhl.io>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev, Benno Lossin <y86-dev@protonmail.com>,
Andreas Hindborg <a.hindborg@samsung.com>,
Alice Ryhl <aliceryhl@google.com>
Subject: [PATCH v4 05/15] rust: types: add `Opaque::raw_get`
Date: Fri, 31 Mar 2023 21:52:46 +0000 [thread overview]
Message-ID: <20230331215053.585759-6-y86-dev@protonmail.com> (raw)
In-Reply-To: <20230331215053.585759-1-y86-dev@protonmail.com>
From: Benno Lossin <y86-dev@protonmail.com>
This function mirrors `UnsafeCell::raw_get`. It avoids creating a
reference and allows solely using raw pointers.
The `pin-init` API will be using this, since uninitialized memory
requires raw pointers.
Signed-off-by: Benno Lossin <y86-dev@protonmail.com>
Reviewed-by: Gary Guo <gary@garyguo.net>
Reviewed-by: Andreas Hindborg <a.hindborg@samsung.com>
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
---
rust/kernel/types.rs | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/rust/kernel/types.rs b/rust/kernel/types.rs
index 9d0fdbc55843..ff2b2fac951d 100644
--- a/rust/kernel/types.rs
+++ b/rust/kernel/types.rs
@@ -238,6 +238,14 @@ impl<T> Opaque<T> {
pub fn get(&self) -> *mut T {
UnsafeCell::raw_get(self.0.as_ptr())
}
+
+ /// Gets the value behind `this`.
+ ///
+ /// This function is useful to get access to the value without creating intermediate
+ /// references.
+ pub const fn raw_get(this: *const Self) -> *mut T {
+ UnsafeCell::raw_get(this.cast::<UnsafeCell<T>>())
+ }
}
/// A sum type that always holds either a value of type `L` or `R`.
--
2.39.2
next prev parent reply other threads:[~2023-03-31 21:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 21:51 [PATCH v4 00/15] Rust pin-init API for pinned initialization of structs y86-dev
2023-03-31 21:51 ` [PATCH v4 01/15] rust: enable the `pin_macro` feature y86-dev
2023-03-31 21:52 ` Boqun Feng
2023-03-31 22:23 ` Boqun Feng
2023-03-31 21:51 ` [PATCH v4 02/15] rust: macros: add `quote!` macro y86-dev
2023-04-03 8:36 ` Andreas Hindborg
2023-03-31 21:52 ` [PATCH v4 03/15] rust: sync: change error type of constructor functions y86-dev
2023-04-03 8:41 ` Andreas Hindborg
2023-03-31 21:52 ` [PATCH v4 04/15] rust: sync: add `assume_init` to `UniqueArc` y86-dev
2023-03-31 21:52 ` y86-dev [this message]
2023-03-31 21:52 ` [PATCH v4 06/15] rust: add pin-init API core y86-dev
2023-04-01 5:24 ` Wedson Almeida Filho
2023-04-01 7:43 ` Benno Lossin
2023-03-31 21:53 ` [PATCH v4 07/15] rust: init: add initialization macros y86-dev
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=20230331215053.585759-6-y86-dev@protonmail.com \
--to=y86-dev@protonmail.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=alice@ryhl.io \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
/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).