From: Greg KH <gregkh@linuxfoundation.org>
To: Danilo Krummrich <dakr@kernel.org>
Cc: rafael@kernel.org, ojeda@kernel.org, alex.gaynor@gmail.com,
boqun.feng@gmail.com, gary@garyguo.net, bjorn3_gh@protonmail.com,
benno.lossin@proton.me, a.hindborg@kernel.org,
aliceryhl@google.com, tmgross@umich.edu,
david.m.ertman@intel.com, ira.weiny@intel.com, leon@kernel.org,
kwilczynski@kernel.org, bhelgaas@google.com,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 4/8] rust: pci: use generic device drvdata accessors
Date: Tue, 1 Jul 2025 11:30:11 +0200 [thread overview]
Message-ID: <2025070142-scrambler-ramp-cd7e@gregkh> (raw)
In-Reply-To: <20250621195118.124245-5-dakr@kernel.org>
On Sat, Jun 21, 2025 at 09:43:30PM +0200, Danilo Krummrich wrote:
> Take advantage of the generic drvdata accessors of the generic Device
> type.
>
> While at it, use from_result() instead of match.
>
> Signed-off-by: Danilo Krummrich <dakr@kernel.org>
> ---
> rust/helpers/pci.c | 10 ----------
> rust/kernel/pci.rs | 31 ++++++++++++++-----------------
> 2 files changed, 14 insertions(+), 27 deletions(-)
>
> diff --git a/rust/helpers/pci.c b/rust/helpers/pci.c
> index cd0e6bf2cc4d..ef9cb38c81a6 100644
> --- a/rust/helpers/pci.c
> +++ b/rust/helpers/pci.c
> @@ -2,16 +2,6 @@
>
> #include <linux/pci.h>
>
> -void rust_helper_pci_set_drvdata(struct pci_dev *pdev, void *data)
> -{
> - pci_set_drvdata(pdev, data);
> -}
> -
> -void *rust_helper_pci_get_drvdata(struct pci_dev *pdev)
> -{
> - return pci_get_drvdata(pdev);
> -}
> -
> resource_size_t rust_helper_pci_resource_len(struct pci_dev *pdev, int bar)
> {
> return pci_resource_len(pdev, bar);
> diff --git a/rust/kernel/pci.rs b/rust/kernel/pci.rs
> index 8435f8132e38..064e74a90904 100644
> --- a/rust/kernel/pci.rs
> +++ b/rust/kernel/pci.rs
> @@ -10,11 +10,11 @@
> device_id::RawDeviceId,
> devres::Devres,
> driver,
> - error::{to_result, Result},
> + error::{from_result, to_result, Result},
> io::Io,
> io::IoRaw,
> str::CStr,
> - types::{ARef, ForeignOwnable, Opaque},
> + types::{ARef, Opaque},
> ThisModule,
> };
> use core::{
> @@ -66,35 +66,32 @@ extern "C" fn probe_callback(
> // `struct pci_dev`.
> //
> // INVARIANT: `pdev` is valid for the duration of `probe_callback()`.
> - let pdev = unsafe { &*pdev.cast::<Device<device::Core>>() };
> + let pdev = unsafe { &*pdev.cast::<Device<device::Internal>>() };
>
> // SAFETY: `DeviceId` is a `#[repr(transparent)` wrapper of `struct pci_device_id` and
> // does not add additional invariants, so it's safe to transmute.
> let id = unsafe { &*id.cast::<DeviceId>() };
> let info = T::ID_TABLE.info(id.index());
>
> - match T::probe(pdev, info) {
> - Ok(data) => {
> - // Let the `struct pci_dev` own a reference of the driver's private data.
> - // SAFETY: By the type invariant `pdev.as_raw` returns a valid pointer to a
> - // `struct pci_dev`.
> - unsafe { bindings::pci_set_drvdata(pdev.as_raw(), data.into_foreign() as _) };
> - }
> - Err(err) => return Error::to_errno(err),
> - }
> + from_result(|| {
> + let data = T::probe(pdev, info)?;
>
> - 0
> + pdev.as_ref().set_drvdata(data);
> + Ok(0)
> + })
> }
>
> extern "C" fn remove_callback(pdev: *mut bindings::pci_dev) {
> // SAFETY: The PCI bus only ever calls the remove callback with a valid pointer to a
> // `struct pci_dev`.
> - let ptr = unsafe { bindings::pci_get_drvdata(pdev) }.cast();
> + //
> + // INVARIANT: `pdev` is valid for the duration of `remove_callback()`.
> + let pdev = unsafe { &*pdev.cast::<Device<device::Internal>>() };
>
> // SAFETY: `remove_callback` is only ever called after a successful call to
> - // `probe_callback`, hence it's guaranteed that `ptr` points to a valid and initialized
> - // `KBox<T>` pointer created through `KBox::into_foreign`.
> - let _ = unsafe { KBox::<T>::from_foreign(ptr) };
> + // `probe_callback`, hence it's guaranteed that `Device::set_drvdata()` has been called
> + // and stored a `Pin<KBox<T>>`.
> + let _ = unsafe { pdev.as_ref().drvdata_obtain::<Pin<KBox<T>>>() };
> }
> }
>
> --
> 2.49.0
>
>
Overall, I like this, same for the other bus types. But again, can't it
be part of Core?
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-01 9:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-21 19:43 [PATCH 0/8] Device: generic accessors for drvdata + Driver::unbind() Danilo Krummrich
2025-06-21 19:43 ` [PATCH 1/8] rust: device: introduce device::Internal Danilo Krummrich
2025-07-01 9:26 ` Greg KH
2025-07-01 10:41 ` Danilo Krummrich
2025-07-01 12:32 ` Danilo Krummrich
2025-07-03 15:06 ` Greg KH
2025-06-21 19:43 ` [PATCH 2/8] rust: device: add drvdata accessors Danilo Krummrich
2025-07-01 9:27 ` Greg KH
2025-07-01 10:58 ` Danilo Krummrich
2025-07-01 13:12 ` Danilo Krummrich
2025-07-05 11:15 ` Benno Lossin
2025-07-05 15:06 ` Danilo Krummrich
2025-07-05 21:38 ` Benno Lossin
2025-07-07 7:46 ` Alexandre Courbot
2025-07-07 9:40 ` Danilo Krummrich
2025-06-21 19:43 ` [PATCH 3/8] rust: platform: use generic device " Danilo Krummrich
2025-06-21 19:43 ` [PATCH 4/8] rust: pci: " Danilo Krummrich
2025-07-01 9:30 ` Greg KH [this message]
2025-06-21 19:43 ` [PATCH 5/8] rust: auxiliary: " Danilo Krummrich
2025-06-21 19:43 ` [PATCH 6/8] rust: platform: implement Driver::unbind() Danilo Krummrich
2025-06-21 19:43 ` [PATCH 7/8] rust: pci: " Danilo Krummrich
2025-06-21 19:43 ` [PATCH 8/8] samples: rust: pci: reset pci-testdev in unbind() Danilo Krummrich
2025-07-01 9:25 ` [PATCH 0/8] Device: generic accessors for drvdata + Driver::unbind() Greg KH
2025-07-01 10:40 ` Danilo Krummrich
2025-07-07 7:18 ` Alexandre Courbot
2025-07-07 9:26 ` Danilo Krummrich
2025-07-08 22:25 ` Danilo Krummrich
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=2025070142-scrambler-ramp-cd7e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=david.m.ertman@intel.com \
--cc=gary@garyguo.net \
--cc=ira.weiny@intel.com \
--cc=kwilczynski@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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).