From: Andrew Ballance <andrewjballance@gmail.com>
To: dakr@kernel.org, a.hindborg@kernel.org, airlied@gmail.com,
akpm@linux-foundation.org, alex.gaynor@gmail.com,
aliceryhl@google.com, andrewjballance@gmail.com,
andriy.shevchenko@linux.intel.com, arnd@arndb.de,
benno.lossin@proton.me, bhelgaas@google.com,
bjorn3_gh@protonmail.com, boqun.feng@gmail.com,
daniel.almeida@collabora.com, fujita.tomonori@gmail.com,
gary@garyguo.net, gregkh@linuxfoundation.org,
kwilczynski@kernel.org, me@kloenk.dev, ojeda@kernel.org,
raag.jadav@intel.com, rafael@kernel.org, simona@ffwll.ch,
tmgross@umich.edu
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, nouveau@lists.freedesktop.org,
rust-for-linux@vger.kernel.org
Subject: [PATCH v2 0/6] rust: add support for port io
Date: Wed, 14 May 2025 05:57:28 -0500 [thread overview]
Message-ID: <20250514105734.3898411-1-andrewjballance@gmail.com> (raw)
currently the rust `Io` type maps to the c read{b, w, l, q}/write{b, w, l, q}
functions and have no support for port io. this can be a problem for pci::Bar
because the pointer returned by pci_iomap can be either PIO or MMIO [0].
this patch series splits the `Io` type into `Io`, and `MMIo`. `Io` can be
used to access PIO or MMIO. `MMIo` can only access memory mapped IO but
might, depending on the arch, be faster than `Io`. and updates pci::Bar,
so that it is generic over Io and, a user can optionally give a compile
time hint about the type of io.
Link: https://docs.kernel.org/6.11/driver-api/pci/pci.html#c.pci_iomap [0]
changes in v2:
- remove `PortIo`
- typo fixes
- squash "fixup" patches so that patches will not introduce build fails
- move some changes across patches so that build will not fail
- changes macro define in rust/helpers/io.c to use full rust name
- specialize `io_backend` for the x86 case
- do not modify lib/iomap.c
- rebased on v6.15-rc6
Link to v1: https://lore.kernel.org/rust-for-linux/20250509031524.2604087-1-andrewjballance@gmail.com/
Andrew Ballance (3):
rust: io: add new Io type
rust: io: add from_raw_cookie functions
rust: pci: make Bar generic over Io
Fiona Behrens (3):
rust: helpers: io: use macro to generate io accessor functions
rust: io: make Io use IoAccess trait
rust: io: implement Debug for IoRaw and add some doctests
drivers/gpu/nova-core/driver.rs | 4 +-
drivers/gpu/nova-core/regs.rs | 1 +
rust/helpers/io.c | 112 ++----
rust/kernel/devres.rs | 4 +-
rust/kernel/io.rs | 645 +++++++++++++++++++++++---------
rust/kernel/pci.rs | 101 +++--
samples/rust/rust_driver_pci.rs | 6 +-
7 files changed, 595 insertions(+), 278 deletions(-)
base-commit: 82f2b0b97b36ee3fcddf0f0780a9a0825d52fec3
--
2.49.0
next reply other threads:[~2025-05-14 10:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 10:57 Andrew Ballance [this message]
2025-05-14 10:57 ` [PATCH v2 1/6] rust: helpers: io: use macro to generate io accessor functions Andrew Ballance
2025-05-14 10:57 ` [PATCH v2 2/6] rust: io: make Io use IoAccess trait Andrew Ballance
2025-05-14 10:57 ` [PATCH v2 3/6] rust: io: add new Io type Andrew Ballance
2025-05-14 10:57 ` [PATCH v2 4/6] rust: io: implement Debug for IoRaw and add some doctests Andrew Ballance
2025-05-14 10:57 ` [PATCH v2 5/6] rust: io: add from_raw_cookie functions Andrew Ballance
2025-05-14 10:57 ` [PATCH v2 6/6] rust: pci: make Bar generic over Io Andrew Ballance
2025-06-16 8:03 ` [PATCH v2 0/6] rust: add support for port io Alice Ryhl
2025-06-16 9:04 ` 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=20250514105734.3898411-1-andrewjballance@gmail.com \
--to=andrewjballance@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=benno.lossin@proton.me \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=me@kloenk.dev \
--cc=nouveau@lists.freedesktop.org \
--cc=ojeda@kernel.org \
--cc=raag.jadav@intel.com \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--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).