public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "John Hubbard" <jhubbard@nvidia.com>,
	"Joel Fernandes" <joelagnelf@nvidia.com>,
	"Danilo Krummrich" <dakr@kernel.org>
Cc: "Alexandre Courbot" <acourbot@nvidia.com>,
	"Timur Tabi" <ttabi@nvidia.com>,
	"Alistair Popple" <apopple@nvidia.com>,
	"Edwin Peer" <epeer@nvidia.com>, "Zhi Wang" <zhiw@nvidia.com>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	nouveau@lists.freedesktop.org, rust-for-linux@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Nouveau <nouveau-bounces@lists.freedesktop.org>
Subject: Re: [PATCH v7 4/4] gpu: nova-core: add boot42 support for next-gen GPUs
Date: Fri, 14 Nov 2025 10:21:58 +0900	[thread overview]
Message-ID: <DE80VIWX6W4T.3GFVGHVWZGGEP@nvidia.com> (raw)
In-Reply-To: <4b3badf1-e3ec-47a9-b90f-5f13234afd5c@nvidia.com>

On Fri Nov 14, 2025 at 5:16 AM JST, John Hubbard wrote:
> On 11/13/25 11:59 AM, Joel Fernandes wrote:
>> Hi John,
>> 
> ...
>>> -        Spec::try_from(boot0)
>>> +        if boot0.is_older_than_fermi() {
>>> +            return Err(ENOTSUPP);
>>> +        }
>>> +
>>> +        Spec::try_from(regs::NV_PMC_BOOT_42::read(bar))
>> 
>> There is an inconsistency in error return here, if NV04 through NV50, it returns
>> -ENOTSUPP. For Fermi through Volta, it will read boot42 but will return -ENODEV
>> because `Spec::try_from()` -> `boot42.chipset()` with return -ENODEV. I am Ok
>> with either error return, but it would be good to make it consistent.
>> 
>
> Yes, good catch. It should be -ENOTSUPP for sure.
>
>> There also does not seem to be a diagnostic if the chipset is not supported. It
>> would be good diagnostic that the chipset did not match, right now it will
>> return -ENODEV, which could mean the device does not exist. -ENOTSUPP is better
>> though but an actual dmesg error message would be nice.
>
> Yes. The "not supported" case would happen in two situations:
>
> a) Someone found a pre-Fermi GPU to use for (probably) display, and they
> also have a Turing+ GPU in the same system (!), and they have both Nouveau
> and Nova drivers available.
>
> Here, it's not really an error situation. If this actually works, then
> Nova not supporting the older GPU is just expected operation.
>
> But these older GPUs are not even really directly supported, so this
> is a fringe case anyway.
>
> b) A newer GPU is installed, and Nova does not yet support it. Here,
> an error message is OK, because Nova is eventually (soon) going to 
> support that GPU.
>
> So I think that means an error message is reasonable here.
>
>> 
>> With these,
>> 
>> Reviewed-by: Joel Fernandes <joelagnelf@nvidia.com>
>> 
>
> Thanks for the review!
>
> Alex, I think I'd better re-spin and re-test, in order to safely collect
> the various small fixes from you and Joel. I can do that today.

Agreed, that will limit the risk of me not capturing everything
properly. Thanks!

  reply	other threads:[~2025-11-14  1:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12  4:29 [PATCH v7 0/4] gpu: nova: add boot42 support for next-gen GPUs John Hubbard
2025-11-12  4:29 ` [PATCH v7 1/4] gpu: nova-core: implement Display for Spec John Hubbard
2025-11-12  4:29 ` [PATCH v7 2/4] gpu: nova-core: prepare Spec and Revision types for boot0/boot42 John Hubbard
2025-11-13 20:00   ` Joel Fernandes
2025-11-13 20:17     ` John Hubbard
2025-11-12  4:29 ` [PATCH v7 3/4] gpu: nova-core: make Architecture behave as a u8 type John Hubbard
2025-11-12  4:30 ` [PATCH v7 4/4] gpu: nova-core: add boot42 support for next-gen GPUs John Hubbard
2025-11-13  8:03   ` Alexandre Courbot
2025-11-13 18:38     ` John Hubbard
2025-11-14  1:54     ` John Hubbard
2025-11-14  2:34       ` Alexandre Courbot
2025-11-13 19:59   ` Joel Fernandes
2025-11-13 20:16     ` John Hubbard
2025-11-14  1:21       ` Alexandre Courbot [this message]
2025-11-13 20:02 ` [PATCH v7 0/4] gpu: nova: " Joel Fernandes

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=DE80VIWX6W4T.3GFVGHVWZGGEP@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=a.hindborg@kernel.org \
    --cc=airlied@gmail.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=apopple@nvidia.com \
    --cc=bhelgaas@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=epeer@nvidia.com \
    --cc=gary@garyguo.net \
    --cc=jhubbard@nvidia.com \
    --cc=joelagnelf@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=nouveau-bounces@lists.freedesktop.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tmgross@umich.edu \
    --cc=ttabi@nvidia.com \
    --cc=zhiw@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