From: John Hubbard <jhubbard@nvidia.com>
To: Timur Tabi <ttabi@nvidia.com>, Gary Guo <gary@garyguo.net>,
Alice Ryhl <aliceryhl@google.com>,
mmaurer@google.com, Danilo Krummrich <dakr@kernel.org>,
Alexandre Courbot <acourbot@nvidia.com>,
Joel Fernandes <joelagnelf@nvidia.com>,
rust-for-linux@vger.kernel.org, nouveau@lists.freedesktop.org
Subject: Re: [PATCH v8 0/7] gpu: nova-core: expose the logging buffers via debugfs
Date: Tue, 10 Mar 2026 15:20:27 -0700 [thread overview]
Message-ID: <ac9783ca-ffe4-431c-95d3-3c221d17c8db@nvidia.com> (raw)
In-Reply-To: <20260310220000.1897166-1-ttabi@nvidia.com>
On 3/10/26 2:59 PM, Timur Tabi wrote:
> GSP-RM writes its printf message to "logging buffers", which are blocks
> memory allocated by the driver. The messages are encoded, so exposing
> the buffers as debugfs entries allows the buffers to be extracted and
> decoded by a special application.
I'll give this series a quick re-test and if it continues to work
well, a tested-by tag at least.
>
> When the driver loads, a /sys/kernel/debug/nova_core root entry is
> created. To do this, the normal module_pci_driver! macro call is
> replaced with an explicit initialization function, as this allows
> that debugfs entry to be created once for all GPUs.
>
> Then in each GPU's initialization, a subdirectory based on the PCI
> BDF name is created, and the logging buffer entries are created under
> that.
>
> Note: the debugfs entry has a file size of 0, because debugfs defaults
> a 0 size and the Rust abstractions do not adjust it for the same of
> the object. Nouveau makes this adjustment manually in the driver.
>
> Changes since v7:
> 1. Fixed rustfmt complaints
> 2. Marked write_raw() as unsafe
> 3. rebased onto drm-rust-next
>
> Timur Tabi (7):
> rust: device: add device name method
> rust: uaccess: add write_dma() for copying from DMA buffers to
> userspace
> rust: dma: implement BinaryWriter for CoherentAllocation<u8>
> gpu: nova-core: Replace module_pci_driver! with explicit module init
> gpu: nova-core: use pin projection in method boot()
> gpu: nova-core: create debugfs root in module init
> gpu: nova-core: create GSP-RM logging buffers debugfs entries
>
> drivers/gpu/nova-core/gsp.rs | 49 ++++++++++++++---
> drivers/gpu/nova-core/gsp/boot.rs | 14 ++---
> drivers/gpu/nova-core/nova_core.rs | 50 +++++++++++++++++-
> rust/helpers/device.c | 5 ++
> rust/kernel/device.rs | 10 ++++
> rust/kernel/dma.rs | 36 ++++++++++++-
> rust/kernel/uaccess.rs | 84 ++++++++++++++++++++++++++----
> 7 files changed, 221 insertions(+), 27 deletions(-)
>
>
> base-commit: a544873ce0575b2fd8285a1364d3e09929d9a3ba
thanks,
--
John Hubbard
next prev parent reply other threads:[~2026-03-10 22:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 21:59 [PATCH v8 0/7] gpu: nova-core: expose the logging buffers via debugfs Timur Tabi
2026-03-10 21:59 ` [PATCH v8 1/7] rust: device: add device name method Timur Tabi
2026-03-10 22:05 ` Alice Ryhl
2026-03-13 2:10 ` Alexandre Courbot
2026-03-10 21:59 ` [PATCH v8 2/7] rust: uaccess: add write_dma() for copying from DMA buffers to userspace Timur Tabi
2026-03-11 5:48 ` kernel test robot
2026-03-13 2:11 ` Alexandre Courbot
2026-03-10 21:59 ` [PATCH v8 3/7] rust: dma: implement BinaryWriter for CoherentAllocation<u8> Timur Tabi
2026-03-13 2:11 ` Alexandre Courbot
2026-03-14 2:05 ` Timur Tabi
2026-03-15 5:11 ` Alexandre Courbot
2026-03-15 18:57 ` Timur Tabi
2026-03-16 3:44 ` Alexandre Courbot
2026-03-10 21:59 ` [PATCH v8 4/7] gpu: nova-core: Replace module_pci_driver! with explicit module init Timur Tabi
2026-03-10 21:59 ` [PATCH v8 5/7] gpu: nova-core: use pin projection in method boot() Timur Tabi
2026-03-13 2:13 ` Alexandre Courbot
2026-03-14 2:20 ` Timur Tabi
2026-03-10 21:59 ` [PATCH v8 6/7] gpu: nova-core: create debugfs root in module init Timur Tabi
2026-03-10 22:00 ` [PATCH v8 7/7] gpu: nova-core: create GSP-RM logging buffers debugfs entries Timur Tabi
2026-03-10 22:20 ` John Hubbard [this message]
2026-03-12 3:50 ` [PATCH v8 0/7] gpu: nova-core: expose the logging buffers via debugfs John Hubbard
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=ac9783ca-ffe4-431c-95d3-3c221d17c8db@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=joelagnelf@nvidia.com \
--cc=mmaurer@google.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