From: sashiko-bot@kernel.org
To: "Gary Guo" <gary@garyguo.net>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
dri-devel@lists.freedesktop.org, ojeda@kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v5 09/20] rust: io: use view types instead of addresses for `Io`
Date: Fri, 26 Jun 2026 14:55:47 +0000 [thread overview]
Message-ID: <20260626145547.BBE361F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260626-io_projection-v5-9-d0961471ae50@garyguo.net>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The abstraction methods `io_read` and `io_write` for `ConfigSpaceBackend` are missing the `#[inline]` annotation.
--
commit 4b02e1c6f87f5cb689ea18ffd09a2fb450c97ee7
Author: Gary Guo <gary@garyguo.net>
Subject: rust: io: use view types instead of addresses for Io
This commit introduces a new IoBackend trait to avoid monomorphization
duplication and defines operations on it using view types instead of
addresses. IoCapable implementations are moved to backends, and io_read
and io_write are made safe by relying on view invariants.
> diff --git a/rust/kernel/pci/io.rs b/rust/kernel/pci/io.rs
> index 89f4bb483a7f6..e67c1e3694fb8 100644
> --- a/rust/kernel/pci/io.rs
> +++ b/rust/kernel/pci/io.rs
[ ... ]
> @@ -112,25 +138,24 @@ unsafe fn io_write(self, value: $ty, address: usize) {
> /// Implements [`IoCapable`] on [`ConfigSpace`] for `$ty` using `$read_fn` and `$write_fn`.
> macro_rules! impl_config_space_io_capable {
> ($ty:ty, $read_fn:ident, $write_fn:ident) => {
> - impl<'a, T: ?Sized> IoCapable<$ty> for ConfigSpace<'a, T> {
> - unsafe fn io_read(self, address: usize) -> $ty {
> + impl IoCapable<$ty> for ConfigSpaceBackend {
> + fn io_read(view: ConfigSpace<'_, $ty>) -> $ty {
[Severity: Low]
this isn't a bug, but should this small forwarding function be annotated
with #[inline]? The Rust subsystem guidelines state that functions in
abstractions that are small or forwarding to a binding call should be
annotated with #[inline].
> + // CAST: The offset is cast to `i32` because the C functions expect a 32-bit
> + // signed offset parameter. PCI configuration space size is at most 4096 bytes,
> + // so the value always fits within `i32` without truncation or sign change.
> + let addr = view.ptr.addr() as i32;
> +
> let mut val: $ty = 0;
>
> // Return value from C function is ignored in infallible accessors.
> - let _ret =
> - // SAFETY: By the type invariant `self.pdev` is a valid address.
> - // CAST: The offset is cast to `i32` because the C functions expect a 32-bit
> - // signed offset parameter. PCI configuration space size is at most 4096 bytes,
> - // so the value always fits within `i32` without truncation or sign change.
> - unsafe { bindings::$read_fn(self.pdev.as_raw(), address as i32, &mut val) };
> -
> + // SAFETY: By the type invariant `pdev` is a valid address.
> + let _ = unsafe { bindings::$read_fn(view.pdev.as_raw(), addr, &mut val) };
> val
> }
>
> - unsafe fn io_write(self, value: $ty, address: usize) {
> + fn io_write(view: ConfigSpace<'_, $ty>, value: $ty) {
[Severity: Low]
this isn't a bug, but should this function also have the #[inline] annotation?
> + // CAST: The offset is cast to `i32` because the C functions expect a 32-bit
> + // signed offset parameter. PCI configuration space size is at most 4096 bytes,
> + // so the value always fits within `i32` without truncation or sign change.
> + let addr = view.ptr.addr() as i32;
> +
> // Return value from C function is ignored in infallible accessors.
> - let _ret =
> - // SAFETY: By the type invariant `self.pdev` is a valid address.
> - // CAST: The offset is cast to `i32` because the C functions expect a 32-bit
> - // signed offset parameter. PCI configuration space size is at most 4096 bytes,
> - // so the value always fits within `i32` without truncation or sign change.
> - unsafe { bindings::$write_fn(self.pdev.as_raw(), address as i32, value) };
> + // SAFETY: By the type invariant `pdev` is a valid address.
> + let _ = unsafe { bindings::$write_fn(view.pdev.as_raw(), addr, value) };
> }
> }
> };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260626-io_projection-v5-0-d0961471ae50@garyguo.net?part=9
next prev parent reply other threads:[~2026-06-26 14:55 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 14:45 [PATCH v5 00/20] rust: I/O type generalization and projection Gary Guo
2026-06-26 14:45 ` [PATCH v5 01/20] rust: io: add dynamically-sized `Region` type Gary Guo
2026-06-26 14:52 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 02/20] rust: io: add missing safety requirement in `IoCapable` methods Gary Guo
2026-06-26 15:00 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 03/20] rust: io: restrict untyped IO access and `register!` to `Region` Gary Guo
2026-06-26 15:03 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 04/20] rust: io: implement `Io` on reference types instead Gary Guo
2026-06-26 14:57 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 05/20] rust: io: generalize `MmioRaw` to pointer to arbitrary type Gary Guo
2026-06-26 15:02 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 06/20] rust: io: rename `Mmio` to `MmioOwned` Gary Guo
2026-06-26 14:56 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 07/20] rust: io: implement `Mmio` as view type Gary Guo
2026-06-26 15:01 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 08/20] rust: pci: io: make `ConfigSpace` a view Gary Guo
2026-06-26 14:53 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 09/20] rust: io: use view types instead of addresses for `Io` Gary Guo
2026-06-26 14:55 ` sashiko-bot [this message]
2026-06-26 14:45 ` [PATCH v5 10/20] pwm: th1520: remove unnecessary `deref` Gary Guo
2026-06-26 14:52 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 11/20] rust: io: remove `MmioOwned` Gary Guo
2026-06-26 14:53 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 12/20] rust: io: move `Io` methods to extension trait Gary Guo
2026-06-26 14:56 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 13/20] rust: io: add projection macro and methods Gary Guo
2026-06-26 15:00 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 14/20] rust: io: add I/O backend for system memory with volatile access Gary Guo
2026-06-26 14:57 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 15/20] rust: io: implement a view type for `Coherent` Gary Guo
2026-06-26 15:05 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 16/20] rust: io: add `read_val` and `write_val` functions on `Io` Gary Guo
2026-06-26 14:59 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 17/20] gpu: nova-core: use I/O projection for cleaner encapsulation Gary Guo
2026-06-26 15:06 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 18/20] rust: dma: drop `dma_read!` and `dma_write!` API Gary Guo
2026-06-26 15:12 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 19/20] rust: io: add copying methods Gary Guo
2026-06-26 15:02 ` sashiko-bot
2026-06-26 14:45 ` [PATCH v5 20/20] rust: io: implement `IoSysMap` Gary Guo
2026-06-26 14:59 ` sashiko-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=20260626145547.BBE361F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=acourbot@nvidia.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=linux-pci@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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