From: John Hubbard <jhubbard@nvidia.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: Vladislav Zaharov <vladazaharova2018@gmail.com>,
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 v6 0/3] gpu: nova-core: retain the GSP-RM log buffers
Date: Fri, 6 Nov 2026 17:40:44 -0800 [thread overview]
Message-ID: <af634f12-02d9-483d-a17d-31d3f6024981@nvidia.com> (raw)
In-Reply-To: <DMOLFAB4UNSV.1A99UVEZAI527@kernel.org>
On 11/6/26 5:38 PM, Danilo Krummrich wrote:
> On Sat Nov 7, 2026 at 1:39 AM CET, John Hubbard wrote:
>> Specifically, (as you mention above), I had to add "retained/" to the
>> directory path in order to retrieve the logs. That is awkward, because
>> that means that if I ask for gsp_keep_logs=1, now I have to know/remember
>> that they are in:
>>
>> /sys/kernel/debug/nova-core/retained/<BDF>/
>>
>> instead of:
>>
>> /sys/kernel/debug/nova-core/<BDF>
>>
>> We should try hard to avoid such complications, especially given that
>> debugging is often done when one has a thousand other complicated things
>> going on at the same time, late at night, too.
>
> It doesn't bother me too much, but I think the concern is fair.
>
> The retained directory keeps a clear separation between live buffers and
> retained buffers, but I don't think that's a strong reason to keep it.
>
> In nouveau we don't have that separation either, but nouveau also keeps the
> retained buffers until module unload. I.e. after the first retention nouveau
> never exposes new buffers (including the live ones) unless you reload the
> module. This works, but can be rather unexpected when e.g. doing multiple
> rebinds via sysfs.
>
> Rebinding via sysfs can be especially useful in multi-GPU setups, where you
> don't want to unbind all GPUs by unloading the module.
>
> So, getting rid of retained/ is fine, but let's not follow what nouveau does.
> Instead, let's make the same files point to the live buffers when the device is
> bound and otherwise let them point at the retained buffers.
This sounds right and proper, yes. :)
thanks,
--
John Hubbard
prev parent reply other threads:[~2026-11-07 1:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 15:45 Vladislav Zaharov
2026-10-14 15:45 ` [PATCH v6 1/3] gpu: nova-core: move the debugfs root into the module data Vladislav Zaharov
2026-11-07 1:23 ` Alexandre Courbot
2026-10-14 15:45 ` [PATCH v6 2/3] gpu: nova-core: gsp: retain the GSP-RM log buffers after unbind Vladislav Zaharov
2026-11-07 1:26 ` Alexandre Courbot
2026-10-14 15:45 ` [PATCH v6 3/3] Documentation: nova: remove completed GSP log buffer task Vladislav Zaharov
2026-11-06 20:51 ` [PATCH v6 0/3] gpu: nova-core: retain the GSP-RM log buffers Timur Tabi
2026-11-06 22:52 ` Danilo Krummrich
2026-11-06 23:15 ` John Hubbard
2026-11-06 23:08 ` Alexandre Courbot
2026-11-06 23:15 ` Alexandre Courbot
2026-11-07 0:39 ` John Hubbard
2026-11-07 1:38 ` Danilo Krummrich
2026-11-07 1:40 ` 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=af634f12-02d9-483d-a17d-31d3f6024981@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®