public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alice Ryhl <aliceryhl@google.com>
To: Zhi Wang <zhiw@nvidia.com>
Cc: rust-for-linux@vger.kernel.org, linux-pci@vger.kernel.org,
	 linux-kernel@vger.kernel.org, dakr@kernel.org,
	bhelgaas@google.com,  kwilczynski@kernel.org, ojeda@kernel.org,
	alex.gaynor@gmail.com,  boqun.feng@gmail.com, gary@garyguo.net,
	bjorn3_gh@protonmail.com,  lossin@kernel.org,
	a.hindborg@kernel.org, tmgross@umich.edu,
	 markus.probst@posteo.de, helgaas@kernel.org, cjia@nvidia.com,
	 smitra@nvidia.com, ankita@nvidia.com, aniketa@nvidia.com,
	 kwankhede@nvidia.com, targupta@nvidia.com, acourbot@nvidia.com,
	 joelagnelf@nvidia.com, jhubbard@nvidia.com, zhiwang@kernel.org
Subject: Re: [PATCH v6 RESEND 4/7] rust: io: factor common I/O helpers into Io trait
Date: Fri, 14 Nov 2025 12:58:31 +0000	[thread overview]
Message-ID: <aRcnd_nSflxnALQ9@google.com> (raw)
In-Reply-To: <20251110204119.18351-5-zhiw@nvidia.com>

On Mon, Nov 10, 2025 at 10:41:16PM +0200, Zhi Wang wrote:
> The previous Io<SIZE> type combined both the generic I/O access helpers
> and MMIO implementation details in a single struct.
> 
> To establish a cleaner layering between the I/O interface and its concrete
> backends, paving the way for supporting additional I/O mechanisms in the
> future, Io<SIZE> need to be factored.
> 
> Factor the common helpers into a new Io trait, and move the MMIO-specific
> logic into a dedicated Mmio<SIZE> type implementing that trait. Rename the
> IoRaw to MmioRaw and update the bus MMIO implementations to use MmioRaw.
> 
> No functional change intended.
> 
> Cc: Alexandre Courbot <acourbot@nvidia.com>
> Cc: Bjorn Helgaas <helgaas@kernel.org>
> Cc: Danilo Krummrich <dakr@kernel.org>
> Cc: John Hubbard <jhubbard@nvidia.com>
> Signed-off-by: Zhi Wang <zhiw@nvidia.com>

This defines three traits:

* Io
* IoInfallible: Io
* IoFallible: Io

This particular split says that there are going to be cases where we
implement IoInfallible only, cases where we implement IoFallible only,
and maybe cases where we implement both.

And the distiction between them is whether the bounds check is runtime
or compile-time.

But this doesn't make much sense to me. Surely any Io resource that can
provide compile-time checked io can also provide runtime-checked io, so
maybe IoFallible should extend IoInfallible?

And why are these separate traits at all? Why not support both
compile-time and runtime-checked IO always?

I noticed also that the trait does not have methods for 64-bit writes,
and that these are left as inherent methods on Mmio.

The traits that would make sense to me are these:

* Io
* Io64: Io

where Io provides everything the three traits you have now provides, and
Io64 provides the 64-bit operations. That way, everything needs to
support operations of various sizes with both compile-time and
runtime-checked bounds, but types may opt-in to providing 64-bit ops.

Thoughts?

Alice

  parent reply	other threads:[~2025-11-14 12:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-10 20:41 [PATCH v6 RESEND 0/7] rust: pci: add config space read/write support Zhi Wang
2025-11-10 20:41 ` [PATCH v6 RESEND 1/7] samples: rust: rust_driver_pci: use "kernel vertical" style for imports Zhi Wang
2025-11-10 20:41 ` [PATCH v6 RESEND 2/7] rust: devres: " Zhi Wang
2025-11-10 20:41 ` [PATCH v6 RESEND 3/7] rust: io: " Zhi Wang
2025-11-10 20:41 ` [PATCH v6 RESEND 4/7] rust: io: factor common I/O helpers into Io trait Zhi Wang
2025-11-13  7:36   ` Alexandre Courbot
2025-11-14 12:58   ` Alice Ryhl [this message]
2025-11-14 17:27     ` Zhi Wang
2025-11-14 18:53       ` Tamir Duberstein
2025-11-17 17:14         ` Zhi Wang
2025-11-14 20:31       ` Danilo Krummrich
2025-11-17 22:44     ` John Hubbard
2025-11-18 21:18       ` Danilo Krummrich
2025-11-18 23:43         ` John Hubbard
2025-11-10 20:41 ` [PATCH v6 RESEND 5/7] rust: io: factor out MMIO read/write macros Zhi Wang
2025-11-13  7:36   ` Alexandre Courbot
2025-11-14 16:06     ` Zhi Wang
2025-11-10 20:41 ` [PATCH v6 RESEND 6/7] rust: pci: add config space read/write support Zhi Wang
2025-11-13  7:56   ` Alexandre Courbot
2025-11-14 16:59     ` Zhi Wang
2025-11-14  0:20   ` Joel Fernandes
2025-11-17 20:28     ` Zhi Wang
2025-11-17 22:07     ` Danilo Krummrich
2025-11-10 20:41 ` [PATCH v6 RESNED 7/7] sample: rust: pci: add tests for config space routines Zhi Wang
2025-11-11  0:01 ` [PATCH v6 RESEND 0/7] rust: pci: add config space read/write support Joel Fernandes
2025-11-11  8:43   ` Zhi Wang

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=aRcnd_nSflxnALQ9@google.com \
    --to=aliceryhl@google.com \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aniketa@nvidia.com \
    --cc=ankita@nvidia.com \
    --cc=bhelgaas@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=cjia@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=helgaas@kernel.org \
    --cc=jhubbard@nvidia.com \
    --cc=joelagnelf@nvidia.com \
    --cc=kwankhede@nvidia.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=markus.probst@posteo.de \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=smitra@nvidia.com \
    --cc=targupta@nvidia.com \
    --cc=tmgross@umich.edu \
    --cc=zhiw@nvidia.com \
    --cc=zhiwang@kernel.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