mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benno Lossin <y86-dev@protonmail.com>
To: Alice Ryhl <alice@ryhl.io>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@lists.linux.dev, "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>
Subject: Re: [PATCH v3 05/13] rust: init: add initialization macros
Date: Thu, 30 Mar 2023 15:38:54 +0000	[thread overview]
Message-ID: <226e4772-0e10-6593-7cfe-e1e290a0216c@protonmail.com> (raw)
In-Reply-To: <f9f1d67f-5c89-d508-d582-528273b635db@ryhl.io>

On 30.03.23 16:21, Alice Ryhl wrote:
> On 3/30/23 00:33, y86-dev@protonmail.com wrote:
>> From: Benno Lossin <y86-dev@protonmail.com>
>>
>> Add the following initializer macros:
>> - `#[pin_data]` to annotate structurally pinned fields of structs,
>>     needed for `pin_init!` and `try_pin_init!` to select the correct
>>     initializer of fields.
>> - `pin_init!` create a pin-initializer for a struct with the
>>     `Infallible` error type.
>> - `try_pin_init!` create a pin-initializer for a struct with a custom
>>     error type (`kernel::error::Error` is the default).
>> - `init!` create an in-place-initializer for a struct with the
>>     `Infallible` error type.
>> - `try_init!` create an in-place-initializer for a struct with a custom
>>     error type (`kernel::error::Error` is the default).
>>
>> Also add their needed internal helper traits and structs.
>>
>> Co-developed-by: Gary Guo <gary@garyguo.net>
>> Signed-off-by: Gary Guo <gary@garyguo.net>
>> Signed-off-by: Benno Lossin <y86-dev@protonmail.com>
>
> Reviewed-by: Alice Ryhl <aliceryhl@google.com>
>
>> +/// ```rust
>> +/// # #![allow(clippy::disallowed_names, clippy::new_ret_no_self)]
>> +/// # use kernel::{init, pin_init, prelude::*, init::*};
>> +/// # use core::pin::Pin;
>> +/// # #[pin_data]
>> +/// # struct Foo {
>> +/// #     a: usize,
>> +/// #     b: Bar,
>> +/// # }
>> +/// # #[pin_data]
>> +/// # struct Bar {
>> +/// #     x: u32,
>> +/// # }
>> +///
>> +/// impl Foo {
>> +///     fn new() -> impl PinInit<Self> {
>
> I would remove the empty line above `impl Foo` so that the example
> doesn't start with an empty line when rendered.

Sure.

>
>> +/// # Syntax
>> +///
>> +/// As already mentioned in the examples above, inside of `pin_init!` a `struct` initializer with
>> +/// the following modifications is expected:
>> +/// - Fields that you want to initialize in-place have to use `<-` instead of `:`.
>> +/// - In front of the initializer you can write `&this in` to have access to a [`NonNull<Self>`]
>> +///   pointer named `this` inside of the initializer.
>> +///
>> +/// For instance:
>> +///
>> +/// ```rust
>> +/// # use kernel::pin_init;
>> +/// # use macros::pin_data;
>> +/// # use core::{ptr::addr_of_mut, marker::PhantomPinned};
>> +/// #[pin_data]
>> +/// struct Buf {
>> +///     ptr: *mut u8,
>
> I'd add a comment on the `ptr` field saying "points at `buf`".

Sure.

>
>> +/// impl BigBuf {
>> +///     fn new() -> impl PinInit<Self, Error> {
>> +///         try_pin_init!(Self {
>> +///             big: {
>> +///                 let zero = Box::try_new_zeroed()?;
>> +///                 unsafe { zero.assume_init() }
>> +///             },
>
> Is there a reason for not using `Box::init(kernel::init::zeroed())?` here?

No, this was probably designed prior to `zeroed`, will change it.

--
Cheers,
Benno


  reply	other threads:[~2023-03-30 15:39 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 22:32 [PATCH v3 00/13] Rust pin-init API for pinned initialization of structs y86-dev
2023-03-29 22:32 ` [PATCH v3 01/13] rust: macros: add `quote!` macro y86-dev
2023-03-30 11:42   ` Andreas Hindborg
2023-03-30 12:01     ` Andreas Hindborg
2023-03-30 13:11     ` Gary Guo
2023-03-30 13:33   ` Alice Ryhl
2023-03-31 10:43   ` Andreas Hindborg
2023-03-29 22:32 ` [PATCH v3 02/13] rust: sync: add `assume_init` to `UniqueArc` y86-dev
2023-03-30  4:13   ` Wedson Almeida Filho
2023-03-30 12:18   ` Andreas Hindborg
2023-03-30 13:33   ` Alice Ryhl
2023-03-29 22:33 ` [PATCH v3 03/13] rust: types: add `Opaque::raw_get` y86-dev
2023-03-30 10:49   ` Gary Guo
2023-03-30 12:32   ` Andreas Hindborg
2023-03-30 13:33   ` Alice Ryhl
2023-03-29 22:33 ` [PATCH v3 04/13] rust: add pin-init API core y86-dev
2023-03-30 13:05   ` Andreas Hindborg
2023-03-30 15:46     ` Benno Lossin
2023-03-31  8:16       ` Andreas Hindborg
2023-03-30 13:17   ` Alice Ryhl
2023-03-30 13:33   ` Alice Ryhl
2023-03-30 14:16     ` Andreas Hindborg
2023-03-30 15:37       ` Benno Lossin
2023-03-30 15:36     ` Benno Lossin
2023-03-31 12:00   ` Andreas Hindborg
2023-03-29 22:33 ` [PATCH v3 05/13] rust: init: add initialization macros y86-dev
2023-03-30 14:21   ` Alice Ryhl
2023-03-30 15:38     ` Benno Lossin [this message]
2023-03-31 12:02   ` Andreas Hindborg
2023-03-29 22:33 ` [PATCH v3 06/13] rust: init/sync: add `InPlaceInit` trait to pin-initialize smart pointers y86-dev
2023-03-30 10:58   ` Gary Guo
2023-03-30 13:39   ` Andreas Hindborg
2023-03-30 14:37   ` Alice Ryhl
2023-03-30 15:28     ` Benno Lossin
2023-03-30 20:24       ` Alice Ryhl
2023-03-29 22:33 ` [PATCH v3 07/13] rust: init: add `PinnedDrop` trait and macros y86-dev
2023-03-30 11:01   ` Gary Guo
2023-03-30 15:41     ` Benno Lossin
2023-03-30 14:45   ` Alice Ryhl
2023-03-31 12:31   ` Andreas Hindborg
2023-03-29 22:33 ` [PATCH v3 08/13] rust: init: add `stack_pin_init!` macro y86-dev
2023-03-30 11:06   ` Gary Guo
2023-03-30 15:07     ` Alice Ryhl
2023-03-30 15:00   ` Alice Ryhl
2023-03-30 15:19     ` Benno Lossin
2023-03-30 20:28       ` Alice Ryhl
2023-03-31 12:43   ` Andreas Hindborg

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=226e4772-0e10-6593-7cfe-e1e290a0216c@protonmail.com \
    --to=y86-dev@protonmail.com \
    --cc=alex.gaynor@gmail.com \
    --cc=alice@ryhl.io \
    --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

all inboxes | Powered by JetHome®