From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Timur Tabi" <ttabi@nvidia.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Danilo Krummrich" <dakr@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Gary Guo" <gary@garyguo.net>, <mmaurer@google.com>,
"John Hubbard" <jhubbard@nvidia.com>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"Eliot Courtney" <ecourtney@nvidia.com>,
<rust-for-linux@vger.kernel.org>
Subject: Re: [PATCH v10 5/6] gpu: nova-core: create debugfs root in module init
Date: Thu, 19 Mar 2026 11:26:25 +0900 [thread overview]
Message-ID: <DH6EIYXIPMNX.2VBWKCBK75H08@nvidia.com> (raw)
In-Reply-To: <20260317235403.1094713-6-ttabi@nvidia.com>
On Wed Mar 18, 2026 at 8:54 AM JST, Timur Tabi wrote:
> Create the 'nova_core' root debugfs entry when the driver loads.
>
> Normally, non-const global variables need to be protected by a
> mutex. Instead, we use unsafe code, as we know the entry is never
> modified after the driver is loaded. This solves the lifetime
> issue of the mutex guard, which would otherwise have required the
> use of `pin_init_scope`.
>
> Signed-off-by: Timur Tabi <ttabi@nvidia.com>
> Reviewed-by: Gary Guo <gary@garyguo.net>
> Tested-by: John Hubbard <jhubbard@nvidia.com>
> Tested-by: Eliot Courtney <ecourtney@nvidia.com>
> ---
Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
With a few nitty nits below.
> drivers/gpu/nova-core/nova_core.rs | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/drivers/gpu/nova-core/nova_core.rs b/drivers/gpu/nova-core/nova_core.rs
> index 0114a59825aa..b7e6c6274aa8 100644
> --- a/drivers/gpu/nova-core/nova_core.rs
> +++ b/drivers/gpu/nova-core/nova_core.rs
> @@ -3,6 +3,7 @@
> //! Nova Core GPU Driver
>
> use kernel::{
> + debugfs,
> driver::Registration,
> pci,
> prelude::*,
> @@ -27,16 +28,40 @@
>
> pub(crate) const MODULE_NAME: &core::ffi::CStr = <LocalModule as kernel::ModuleMetadata>::NAME;
>
> +// FIXME: Move this into per-module data once that exists
I'd change this to do `TODO:` for easier discovery.
> +static mut DEBUGFS_ROOT: Option<debugfs::Dir> = None;
> +
> +/// Guard that clears DEBUGFS_ROOT when dropped.
Item names need `` quotes.
> +struct DebugfsRootGuard;
> +
> +impl Drop for DebugfsRootGuard {
> + fn drop(&mut self) {
> + // SAFETY: This guard is dropped after _driver (due to field order),
> + // so the driver is unregistered and no probe() can be running.
Here as well (even if it's not a doccomment).
> + unsafe { DEBUGFS_ROOT = None };
> + }
> +}
> +
> #[pin_data]
> struct NovaCoreModule {
> + // Fields are dropped in declaration order, so _driver is dropped first,
> + // then _debugfs_guard clears DEBUGFS_ROOT.
And here.
next prev parent reply other threads:[~2026-03-19 2:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 23:53 [PATCH v10 0/6] gpu: nova-core: expose the logging buffers via debugfs Timur Tabi
2026-03-17 23:53 ` [PATCH v10 1/6] rust: device: add device name method Timur Tabi
2026-03-17 23:53 ` [PATCH v10 2/6] rust: uaccess: add write_dma() for copying from DMA buffers to userspace Timur Tabi
2026-03-17 23:54 ` [PATCH v10 3/6] rust: dma: implement BinaryWriter for CoherentAllocation<u8> Timur Tabi
2026-03-17 23:54 ` [PATCH v10 4/6] gpu: nova-core: Replace module_pci_driver! with explicit module init Timur Tabi
2026-03-19 2:24 ` Alexandre Courbot
2026-03-17 23:54 ` [PATCH v10 5/6] gpu: nova-core: create debugfs root in " Timur Tabi
2026-03-19 2:26 ` Alexandre Courbot [this message]
2026-03-17 23:54 ` [PATCH v10 6/6] gpu: nova-core: create GSP-RM logging buffers debugfs entries Timur Tabi
2026-03-19 1:11 ` John Hubbard
2026-03-19 2:28 ` [PATCH v10 0/6] gpu: nova-core: expose the logging buffers via debugfs Alexandre Courbot
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=DH6EIYXIPMNX.2VBWKCBK75H08@nvidia.com \
--to=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=ecourtney@nvidia.com \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=joelagnelf@nvidia.com \
--cc=mmaurer@google.com \
--cc=ojeda@kernel.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