From: Alice Ryhl <aliceryhl@google.com>
To: Timur Tabi <ttabi@nvidia.com>
Cc: Gary Guo <gary@garyguo.net>, Danilo Krummrich <dakr@kernel.org>,
rust-for-linux@vger.kernel.org,
John Hubbard <jhubbard@nvidia.com>,
Joel Fernandes <joelagnelf@nvidia.com>,
Alexandre Courbot <acourbot@nvidia.com>,
Lyude Paul <lyude@redhat.com>,
nouveau@lists.freedesktop.org
Subject: Re: [PATCH v3 1/9] rust: pci: add PCI device name method
Date: Thu, 18 Dec 2025 08:05:36 +0000 [thread overview]
Message-ID: <aUO10KftOHuOwDeP@google.com> (raw)
In-Reply-To: <20251218013910.459045-2-ttabi@nvidia.com>
On Wed, Dec 17, 2025 at 07:39:02PM -0600, Timur Tabi wrote:
> Add a name() method to the PCI `Device` type, which returns a CStr
> that contains the device name, typically the BDF address.
>
> Signed-off-by: Timur Tabi <ttabi@nvidia.com>
> ---
> rust/kernel/pci.rs | 37 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 37 insertions(+)
>
> diff --git a/rust/kernel/pci.rs b/rust/kernel/pci.rs
> index 82e128431f08..125fb39f4316 100644
> --- a/rust/kernel/pci.rs
> +++ b/rust/kernel/pci.rs
> @@ -427,6 +427,43 @@ pub fn pci_class(&self) -> Class {
> // SAFETY: `self.as_raw` is a valid pointer to a `struct pci_dev`.
> Class::from_raw(unsafe { (*self.as_raw()).class })
> }
> +
> + /// Returns the PCI device name.
> + ///
> + /// This returns the device name in the format "DDDD:BB:DD.F" where:
> + /// - DDDD is the PCI domain (4 hex digits)
> + /// - BB is the bus number (2 hex digits)
> + /// - DD is the device number (2 hex digits)
> + /// - F is the function number (1 hex digit)
> + ///
> + /// # Examples
> + ///
> + /// ```
> + /// # use kernel::{c_str, debugfs::Dir, device::Core, pci, prelude::*};
> + /// fn create_debugfs(pdev: &pci::Device<Core>) -> Result {
> + /// let dir = Dir::new(pdev.name());
> + /// Ok(())
> + /// }
> + /// ```
> + #[inline]
> + pub fn name(&self) -> &CStr {
> + // SAFETY: By its type invariant `self.as_raw` is always a valid pointer to a
> + // `struct pci_dev`, which contains a `struct device dev` member.
> + unsafe {
What's the actual unsafe operation in this block? We generally try to
limit the scope of unsafe as much as possible.
Alice
> + let pci_dev = self.as_raw();
> + let dev = &raw const (*pci_dev).dev;
> +
> + // If init_name is set, use it; otherwise use the kobject name
> + let init_name = (*dev).init_name;
> + let name_ptr = if !init_name.is_null() {
> + init_name
> + } else {
> + (*dev).kobj.name
> + };
> +
> + CStr::from_char_ptr(name_ptr)
> + }
> + }
> }
>
> impl Device<device::Core> {
> --
> 2.52.0
>
next prev parent reply other threads:[~2025-12-18 8:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 1:39 [PATCH v3 0/9] gpu: nova-core: expose the logging buffers via debugfs Timur Tabi
2025-12-18 1:39 ` [PATCH v3 1/9] rust: pci: add PCI device name method Timur Tabi
2025-12-18 8:05 ` Alice Ryhl [this message]
2025-12-18 8:55 ` Danilo Krummrich
2025-12-18 10:09 ` Miguel Ojeda
2025-12-18 1:39 ` [PATCH v3 2/9] rust: debugfs: add lookup contructor Timur Tabi
2025-12-18 9:40 ` Danilo Krummrich
2025-12-18 18:00 ` Matthew Maurer
2025-12-18 1:39 ` [PATCH v3 3/9] rust: debugfs: add Dir::empty() for no-op directory handle Timur Tabi
2025-12-18 1:39 ` [PATCH v3 4/9] rust: debugfs: fix Dir::scope() to not borrow self for returned lifetime Timur Tabi
2025-12-18 17:55 ` Matthew Maurer
2025-12-18 1:39 ` [PATCH v3 5/9] gpu: nova-core: Replace module_pci_driver! with explicit module init Timur Tabi
2025-12-18 9:01 ` Danilo Krummrich
2025-12-18 1:39 ` [PATCH v3 6/9] gpu: nova-core: create debugfs root when driver loads Timur Tabi
2025-12-18 10:10 ` Danilo Krummrich
2025-12-18 1:39 ` [PATCH v3 7/9] gpu: nova-core: implement BinaryWriter for LogBuffer Timur Tabi
2025-12-18 10:18 ` Danilo Krummrich
2025-12-18 11:14 ` Alexandre Courbot
2025-12-18 1:39 ` [PATCH v3 8/9] gpu: nova-core: use pin projection in method boot() Timur Tabi
2025-12-18 1:39 ` [PATCH v3 9/9] gpu: nova-core: create GSP-RM logging buffers debugfs entries Timur Tabi
2025-12-21 10:05 ` kernel test robot
2025-12-18 8:07 ` [PATCH v3 0/9] gpu: nova-core: expose the logging buffers via debugfs Alice Ryhl
2025-12-18 8:44 ` 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=aUO10KftOHuOwDeP@google.com \
--to=aliceryhl@google.com \
--cc=acourbot@nvidia.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=joelagnelf@nvidia.com \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=ttabi@nvidia.com \
/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).