From: Joel Fernandes <joelagnelf@nvidia.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: 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, aliceryhl@google.com, tmgross@umich.edu,
rust-for-linux@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] rust: pci: implement TryInto<IrqRequest<'a>> for IrqVector<'a>
Date: Thu, 16 Oct 2025 18:24:20 -0400 [thread overview]
Message-ID: <20251016222420.GA1480061@joelbox2> (raw)
In-Reply-To: <20251015182118.106604-2-dakr@kernel.org>
On Wed, Oct 15, 2025 at 08:14:29PM +0200, Danilo Krummrich wrote:
> Implement TryInto<IrqRequest<'a>> for IrqVector<'a> to directly convert
> a pci::IrqVector into a generic IrqRequest, instead of taking the
> indirection via an unrelated pci::Device method.
>
> Signed-off-by: Danilo Krummrich <dakr@kernel.org>
> ---
> rust/kernel/pci.rs | 38 ++++++++++++++++++--------------------
> 1 file changed, 18 insertions(+), 20 deletions(-)
>
> diff --git a/rust/kernel/pci.rs b/rust/kernel/pci.rs
> index d91ec9f008ae..c6b750047b2e 100644
> --- a/rust/kernel/pci.rs
> +++ b/rust/kernel/pci.rs
> @@ -596,6 +596,20 @@ fn index(&self) -> u32 {
> }
> }
>
> +impl<'a> TryInto<IrqRequest<'a>> for IrqVector<'a> {
> + type Error = Error;
> +
> + fn try_into(self) -> Result<IrqRequest<'a>> {
> + // SAFETY: `self.as_raw` returns a valid pointer to a `struct pci_dev`.
> + let irq = unsafe { bindings::pci_irq_vector(self.dev.as_raw(), self.index()) };
> + if irq < 0 {
> + return Err(crate::error::Error::from_errno(irq));
> + }
> + // SAFETY: `irq` is guaranteed to be a valid IRQ number for `&self`.
> + Ok(unsafe { IrqRequest::new(self.dev.as_ref(), irq as u32) })
> + }
> +}A
Nice change, looks good to me but I do feel it is odd to 'convert' an
IrqVector directly into a IrqRequest using TryInto (one is a device-relative
vector index and the other holds the notion of an IRQ request).
Instead, we should convert IrqVector into something like LinuxIrqNumber
(using TryInto) because we're converting one number to another, and then pass
that to a separate function to create the IrqRequest. Or we can do both in a
vector.make_request() function (which is basically this patch but not using
TryInto).
Actually even my original code had this oddity:
The function irq_vector should have been called irq_request or something but
instead was:
pub fn irq_vector(&self, vector: IrqVector<'_>) -> Result<IrqRequest<'_>>
I think we can incrementally improve this though, so LGTM.
Reviewed-by: Joel Fernandes <joelagnelf@nvidia.com>
thanks,
- Joel
> +
> /// Represents an IRQ vector allocation for a PCI device.
> ///
> /// This type ensures that IRQ vectors are properly allocated and freed by
> @@ -675,31 +689,15 @@ pub fn iomap_region<'a>(
> self.iomap_region_sized::<0>(bar, name)
> }
>
> - /// Returns an [`IrqRequest`] for the given IRQ vector.
> - pub fn irq_vector(&self, vector: IrqVector<'_>) -> Result<IrqRequest<'_>> {
> - // Verify that the vector belongs to this device.
> - if !core::ptr::eq(vector.dev.as_raw(), self.as_raw()) {
> - return Err(EINVAL);
> - }
> -
> - // SAFETY: `self.as_raw` returns a valid pointer to a `struct pci_dev`.
> - let irq = unsafe { crate::bindings::pci_irq_vector(self.as_raw(), vector.index()) };
> - if irq < 0 {
> - return Err(crate::error::Error::from_errno(irq));
> - }
> - // SAFETY: `irq` is guaranteed to be a valid IRQ number for `&self`.
> - Ok(unsafe { IrqRequest::new(self.as_ref(), irq as u32) })
> - }
> -
> /// Returns a [`kernel::irq::Registration`] for the given IRQ vector.
> pub fn request_irq<'a, T: crate::irq::Handler + 'static>(
> &'a self,
> - vector: IrqVector<'_>,
> + vector: IrqVector<'a>,
> flags: irq::Flags,
> name: &'static CStr,
> handler: impl PinInit<T, Error> + 'a,
> ) -> Result<impl PinInit<irq::Registration<T>, Error> + 'a> {
> - let request = self.irq_vector(vector)?;
> + let request = vector.try_into()?;
>
> Ok(irq::Registration::<T>::new(request, flags, name, handler))
> }
> @@ -707,12 +705,12 @@ pub fn request_irq<'a, T: crate::irq::Handler + 'static>(
> /// Returns a [`kernel::irq::ThreadedRegistration`] for the given IRQ vector.
> pub fn request_threaded_irq<'a, T: crate::irq::ThreadedHandler + 'static>(
> &'a self,
> - vector: IrqVector<'_>,
> + vector: IrqVector<'a>,
> flags: irq::Flags,
> name: &'static CStr,
> handler: impl PinInit<T, Error> + 'a,
> ) -> Result<impl PinInit<irq::ThreadedRegistration<T>, Error> + 'a> {
> - let request = self.irq_vector(vector)?;
> + let request = vector.try_into()?;
>
> Ok(irq::ThreadedRegistration::<T>::new(
> request, flags, name, handler,
> --
> 2.51.0
>
next prev parent reply other threads:[~2025-10-16 22:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 18:14 [PATCH 0/3] Rust PCI housekeeping Danilo Krummrich
2025-10-15 18:14 ` [PATCH 1/3] rust: pci: implement TryInto<IrqRequest<'a>> for IrqVector<'a> Danilo Krummrich
2025-10-16 15:01 ` Alice Ryhl
2025-10-16 17:04 ` Danilo Krummrich
2025-10-16 22:24 ` Joel Fernandes [this message]
2025-10-16 22:57 ` Danilo Krummrich
2025-10-16 23:02 ` Joel Fernandes
2025-10-15 18:14 ` [PATCH 2/3] rust: pci: move I/O infrastructure to separate file Danilo Krummrich
2025-10-15 22:58 ` Bjorn Helgaas
2025-10-16 12:34 ` Danilo Krummrich
2025-10-16 15:52 ` Bjorn Helgaas
2025-10-16 18:54 ` Miguel Ojeda
2025-10-15 18:14 ` [PATCH 3/3] rust: pci: move IRQ " Danilo Krummrich
2025-10-15 23:02 ` Bjorn Helgaas
2025-10-20 11:39 ` [PATCH 0/3] Rust PCI housekeeping 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=20251016222420.GA1480061@joelbox2 \
--to=joelagnelf@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@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).