dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <ttabi@nvidia.com>
To: "mhenning@darkrefraction.com" <mhenning@darkrefraction.com>
Cc: "kherbst@redhat.com" <kherbst@redhat.com>,
	"martin.peres@free.fr" <martin.peres@free.fr>,
	"faith.ekstrand@collabora.com" <faith.ekstrand@collabora.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
	"dakr@kernel.org" <dakr@kernel.org>,
	"lyude@redhat.com" <lyude@redhat.com>,
	Ben Skeggs <bskeggs@nvidia.com>
Subject: Re: [PATCH 2/2] drm/nouveau: Remove nvkm_gsp_fwif.enable
Date: Tue, 24 Jun 2025 19:13:37 +0000	[thread overview]
Message-ID: <127e866b4bb4fd3a77e1cbfc5b709bcb2533c744.camel@nvidia.com> (raw)
In-Reply-To: <CAAgWFh05pj_9rk7Wcx24tFWR2sgMZH4WtBsm3hYrqM3svwniOQ@mail.gmail.com>

On Tue, 2025-06-24 at 15:01 -0400, M Henning wrote:
> We did no such error checking before this series (in fact, most of
> these options have almost no error checking). Are you saying you want
> to see this added in this patch series?

You have a good point, but I think your change, in effect, necessitates my request.  Previously, the
default was no GSP-RM unless needed.  Now it's yes GSP-RM, and the concept of "need" has been
removed.  So there's no indication any more that some GPUs need GSP-RM and some do not.

So to address that, I think it makes sense to add a warning if someone tries disable GSP-RM on a GPU
that is not supported in that configuration.

Now, whether or not we should ignore NvGspRm=0 on Ada+ is up for debate.  If I understand the code
correctly, today (and still with your patches), Ada+ would fail to boot.  I can't say whether or not
that's a good idea.  But I think a warning should be printed either way.

  reply	other threads:[~2025-06-24 19:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23 22:04 [PATCH 0/2] drm/nouveau: Remove DRM_NOUVEAU_GSP_DEFAULT config Mel Henning
2025-06-23 22:04 ` [PATCH 1/2] " Mel Henning
2025-06-23 22:04 ` [PATCH 2/2] drm/nouveau: Remove nvkm_gsp_fwif.enable Mel Henning
2025-06-24 17:28   ` Timur Tabi
2025-06-24 19:01     ` M Henning
2025-06-24 19:13       ` Timur Tabi [this message]
2025-06-26 17:15         ` M Henning
2025-07-14  3:19           ` Ben Skeggs
2025-07-14 16:04             ` M Henning
2025-07-14 21:25               ` Ben Skeggs

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=127e866b4bb4fd3a77e1cbfc5b709bcb2533c744.camel@nvidia.com \
    --to=ttabi@nvidia.com \
    --cc=bskeggs@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=faith.ekstrand@collabora.com \
    --cc=kherbst@redhat.com \
    --cc=lyude@redhat.com \
    --cc=martin.peres@free.fr \
    --cc=mhenning@darkrefraction.com \
    --cc=nouveau@lists.freedesktop.org \
    /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;
as well as URLs for NNTP newsgroup(s).