mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Vladislav Zaharov <vladazaharova2018@gmail.com>, dakr@kernel.org
Cc: acourbot@nvidia.com, aliceryhl@google.com, ttabi@nvidia.com,
	gary@garyguo.net, nova-gpu@lists.linux.dev,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH v8 0/4] gpu: nova-core: retain the GSP-RM log buffers
Date: Sat, 14 Nov 2026 18:37:07 -0800	[thread overview]
Message-ID: <4166acdf-fdde-44e5-b052-7eb059296f36@nvidia.com> (raw)
In-Reply-To: <20261114044304.245684-1-vladazaharova2018@gmail.com>

On 11/13/26 8:43 PM, Vladislav Zaharov wrote:
> The GSP-RM log buffers are exposed through debugfs, but they go away
> when the GPU is unbound, including when probe() fails, which is when
> they are most useful.
> 
> Patch 1 moves the debugfs root into the module data, which also fixes
> the root being leaked when the driver registration fails. Patch 2 moves
> the log buffer code into its own file. Patch 3 adds a gsp_keep_logs
> module parameter that keeps a copy of the buffers after unbind. Patch 4
> drops the completed item from todo.rst.
> 
> Changes since v7:
>  - patch 3: check only gsp_keep_logs, not CONFIG_DEBUG_FS, drop the
>    reserve() before replacing the copies, add RetainedLogs::push() and
>    mark retained_logs() #[inline] (Danilo)
>  - collect Alexandre's Reviewed-by for patches 1 and 2

Hi Vlad,

This is working nicely for me, the logs stay in the same place and
I can retrieve them even when I inject an error in the driver to
fail the probe:

root@redforge:/sys/kernel/debug/nova-core# dmesg -t |grep nova-core|grep failed
nova-core 0000:c1:00.0: probe with driver nova-core failed with error -22
nova-core 0000:c2:00.0: probe with driver nova-core failed with error -22
nova-core 0000:01:00.0: probe with driver nova-core failed with error -22
root@redforge:/sys/kernel/debug/nova-core# tree
.
├── 0000:01:00.0
│   ├── loginit
│   ├── logintr
│   └── logrm
├── 0000:c1:00.0
│   ├── loginit
│   └── logrm
└── 0000:c2:00.0
    ├── loginit
    ├── logintr
    └── logrm


So for the series,

Tested-by: John Hubbard <jhubbard@nvidia.com>


thanks,
-- 
John Hubbard

> 
> The code and the commit messages were drafted with an LLM coding
> assistant and reviewed by me. Each patch builds on its own, and the
> series was tested again on a GB203: the copies are kept after unbind
> and after a failed probe, replaced by the live buffers on the next
> bind, and nothing is kept without gsp_keep_logs.
> 
> v7: https://lore.kernel.org/nova-gpu/20261113075317.934264-1-vladazaharova2018@gmail.com/
> 
> Vladislav Zaharov (4):
>   gpu: nova-core: move the debugfs root into the module data
>   gpu: nova-core: gsp: move the log buffers into their own file
>   gpu: nova-core: gsp: retain the GSP-RM log buffers after unbind
>   Documentation: nova: remove completed GSP log buffer task
> 
>  Documentation/gpu/nova/core/todo.rst   |  12 --
>  drivers/gpu/nova-core/debugfs.rs       |  45 ++++++
>  drivers/gpu/nova-core/gsp.rs           | 100 +++---------
>  drivers/gpu/nova-core/gsp/logbuffer.rs | 205 +++++++++++++++++++++++++
>  drivers/gpu/nova-core/nova_core.rs     |  68 +++++---
>  5 files changed, 313 insertions(+), 117 deletions(-)
>  create mode 100644 drivers/gpu/nova-core/debugfs.rs
>  create mode 100644 drivers/gpu/nova-core/gsp/logbuffer.rs
> 
> 
> base-commit: 0ff9e5b9ff6736c37593cd7db89f4593ec4f8e86



      parent reply	other threads:[~2026-11-15  2:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-14  4:43 Vladislav Zaharov
2026-11-14  4:43 ` [PATCH v8 1/4] gpu: nova-core: move the debugfs root into the module data Vladislav Zaharov
2026-11-14  4:43 ` [PATCH v8 2/4] gpu: nova-core: gsp: move the log buffers into their own file Vladislav Zaharov
2026-11-14  4:43 ` [PATCH v8 3/4] gpu: nova-core: gsp: retain the GSP-RM log buffers after unbind Vladislav Zaharov
2026-11-14  4:43 ` [PATCH v8 4/4] Documentation: nova: remove completed GSP log buffer task Vladislav Zaharov
2026-11-15  2:37 ` John Hubbard [this message]

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=4166acdf-fdde-44e5-b052-7eb059296f36@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=acourbot@nvidia.com \
    --cc=aliceryhl@google.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gary@garyguo.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nova-gpu@lists.linux.dev \
    --cc=ttabi@nvidia.com \
    --cc=vladazaharova2018@gmail.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

all inboxes | Powered by JetHome®