All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Lyude Paul" <lyude@redhat.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v5 2/5] drm/nouveau/gsp/r535: Add support for MEMSYS_GET_STATIC_CONFIG
Date: Thu, 17 Sep 2026 17:11:36 +0000	[thread overview]
Message-ID: <20260917171137.00C9C1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260917170042.440276-3-lyude@redhat.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] nouveau: missing r535_gsp_get_static_memsys_info() call in r535 init
--

commit ea59a1e02ca1ca9ba089fd374c676d4e85191d91
Author: Lyude Paul <lyude@redhat.com>

drm/nouveau/gsp/r535: Add support for MEMSYS_GET_STATIC_CONFIG

This commit introduces support for MEMSYS_GET_STATIC_CONFIG to fetch memory
management characteristics from the GSP during driver load. It implements the
fetching logic and wires it up for the r570 initialization path.

[ ... ]

> diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/r570/gsp.c b/drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/r570/gsp.c
> index dfda6b0b910a2..dff2081ed764f 100644
> --- a/drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/r570/gsp.c
> +++ b/drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/r570/gsp.c
> @@ -138,6 +138,14 @@ r570_gsp_get_static_info(struct nvkm_gsp *gsp)
>  		}
>  	}
>  
> +	ret = r535_gsp_get_static_memsys_info(gsp);
> +	if (ret) {
> +		nvkm_error(&gsp->subdev, "Retrieving static memsys info failed\n");
> +		return ret;
> +	}
> +	nvkm_debug(&gsp->subdev, "memsys: Use raw mode for comptag allocations? %s\n",
> +		   str_yes_no(gsp->memsys.use_raw_mode_comptagline_alloc));
> +
>  	return 0;
>  }

[Severity: Medium]
Since the commit title explicitly claims to add support for r535, does
r535_gsp_get_static_info() in 
drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/r535/gsp.c 
also need to call r535_gsp_get_static_memsys_info()?

Right now, it appears the initialization is only performed in the r570 path.
When loading the nouveau driver on a GPU that uses the r535 GSP firmware,
this leaves gsp->memsys.use_raw_mode_comptagline_alloc uninitialized (false).

Could this create a mismatch and leave internal state incorrectly initialized 
for r535 hardware?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260917170042.440276-1-lyude@redhat.com?part=2

  reply	other threads:[~2026-09-17 17:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 16:58 [PATCH v5 0/5] drm/nouveau/gsp/r570: Follow OpenRM's runtime PM process more closely Lyude Paul
2026-09-17 16:58 ` Lyude Paul
2026-09-17 16:58 ` [PATCH v5 1/5] drm/nouveau/gsp/r570: Add support for INTERNAL_GCX_ENTRY_PREREQUISITE Lyude Paul
2026-09-17 16:58   ` Lyude Paul
2026-09-17 17:38   ` sashiko-bot
2026-09-17 16:58 ` [PATCH v5 2/5] drm/nouveau/gsp/r535: Add support for MEMSYS_GET_STATIC_CONFIG Lyude Paul
2026-09-17 16:58   ` Lyude Paul
2026-09-17 17:11   ` sashiko-bot [this message]
2026-09-17 16:58 ` [PATCH v5 3/5] drm/nouveau/gsp/r570: Add comp mode workaround from issue #3172217 Lyude Paul
2026-09-17 16:58   ` Lyude Paul
2026-09-17 16:58 ` [PATCH v5 4/5] drm/nouveau/gsp/r570: Start saving comptag backing stores Lyude Paul
2026-09-17 16:58   ` Lyude Paul
2026-09-17 16:58 ` [PATCH v5 5/5] drm/nouveau/gsp/r570: Enable Gcoff in fbsr again Lyude Paul
2026-09-17 16:58   ` Lyude Paul

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=20260917171137.00C9C1F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lyude@redhat.com \
    --cc=sashiko-reviews@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.