NVIDIA GPU driver infrastructure
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Danilo Krummrich <dakr@kernel.org>,
	Alexandre Courbot <acourbot@nvidia.com>
Cc: aliceryhl@google.com, gary@garyguo.net, nova-gpu@lists.linux.dev,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] gpu: nova-core: use a single try_pin_init!() block in probe()
Date: Tue, 29 Sep 2026 13:31:25 -0700	[thread overview]
Message-ID: <51dccdd0-eb85-4572-be62-6ca39038cbdf@nvidia.com> (raw)
In-Reply-To: <DLQZW9ZSEQF8.EFP3CFEMUABB@kernel.org>

On 9/28/26 6:48 AM, Danilo Krummrich wrote:
> On Mon Sep 28, 2026 at 2:23 AM CEST, Alexandre Courbot wrote:
>>> +        dev_dbg!(pdev, "Probe Nova Core GPU driver.\n");
>>
>> Don't you want to put this in the `_:` block below, so it printed at the
>> actual initialization time instead of the time the initializer is created?
> 
> No, because the :_ block below will become the PCI device enable guard soon. We
> could put it in a separate :_ block, but that seemed odd to me.
> 
> In any case, we probably should drop this dev_dbg!() entirely, as its value is
> quite limited.

I missed this comment until just now, when I went to test with the final
merged patch, and the "Probe..." debug print for each GPU was missing.

I really would like this restored. This is a high value thing to
print, because it acts as kind of a bookend, showing the beginning of
trying to boot up.

In fact, we even have some local scripts that look for it (not that
that matters, but just to indicate how we think about its usefulness).

I can post a trivial patch to restore it, if desired.

thanks,
-- 
John Hubbard


  reply	other threads:[~2026-09-29 20:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27 14:44 [PATCH] gpu: nova-core: use a single try_pin_init!() block in probe() Danilo Krummrich
2026-09-28  0:23 ` Alexandre Courbot
2026-09-28 13:48   ` Danilo Krummrich
2026-09-29 20:31     ` John Hubbard [this message]
2026-09-29 20:43       ` Danilo Krummrich
2026-09-28  4:17 ` Eliot Courtney
2026-09-28 11:36 ` Gary Guo
2026-09-28 12:00   ` Danilo Krummrich
2026-09-28 12:10     ` Gary Guo
2026-09-28 12:15       ` Danilo Krummrich
2026-09-28 13:53         ` Gary Guo
2026-09-28 13:56           ` Danilo Krummrich
2026-09-29 19:12 ` 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=51dccdd0-eb85-4572-be62-6ca39038cbdf@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=nova-gpu@lists.linux.dev \
    /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