dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Alexandre Courbot" <acourbot@nvidia.com>
Cc: "Alexandre Courbot" <acourbot@nvidia.com>,
	ojeda@kernel.org, dri-devel@lists.freedesktop.org,
	"Danilo Krummrich" <dakr@kernel.org>
Subject: Re: [PATCH v5 12/13] gpu: nova-core: gsp: separate context and GPU lifetimes in GspBootContext
Date: Tue, 07 Jul 2026 09:02:26 +0000	[thread overview]
Message-ID: <20260707090227.61B361F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260707-nova-bootcontext-v5-12-ecad9346387f@nvidia.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The GspSequencer struct was not updated with separate context and GPU lifetimes, leaving it vulnerable to the exact covariance issue this commit aims to fix.
--

--- Patch [12]: [PATCH v5 12/13] gpu: nova-core: gsp: separate context and GPU lifetimes in GspBootContext ---
commit 25c80f140498d9178aab39d3a011facb7416a203
Author: Alexandre Courbot <acourbot@nvidia.com>

gpu: nova-core: gsp: separate context and GPU lifetimes in GspBootContext

This commit splits the lifetimes in GspBootContext into separate context and
GPU lifetimes to allow mutable references to GPU subdevices. This distinction
prepares the context for holding mutable borrows of Falcon instances.

> diff --git a/drivers/gpu/nova-core/gsp/sequencer.rs b/drivers/gpu/nova-core/gsp/sequencer.rs
> index ddce32cc4e308..422a74f9ecbd5 100644
> --- a/drivers/gpu/nova-core/gsp/sequencer.rs
> +++ b/drivers/gpu/nova-core/gsp/sequencer.rs
[ ... ]
> @@ -335,7 +335,7 @@ fn next(&mut self) -> Option<Self::Item> {
>  impl<'a> GspSequencer<'a> {

[Severity: Low]
Should GspSequencer also be updated to use separate 'ctx and 'gpu lifetimes?

The commit splits lifetimes in GspBootContext because holding mutable
references to GPU subdevices requires invariant lifetimes. However, the
GspSequencer struct definition still uses a single lifetime for its Falcon
references:

pub(crate) struct GspSequencer<'a> {
    bar: Bar0<'a>,
    sec2_falcon: &'a Falcon<'a, Sec2>,
    gsp_falcon: &'a Falcon<'a, Gsp>,
    ...

Will this cause similar compilation errors for GspSequencer when the Falcon
references are eventually made mutable?

>      pub(crate) fn run(
>          cmdq: &Cmdq,
> -        ctx: &'a GspBootContext<'_>,
> +        ctx: &'a GspBootContext<'_, '_>,
>          libos_dma_handle: u64,
>          bootloader_app_version: u32,
>      ) -> Result {

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260707-nova-bootcontext-v5-0-ecad9346387f@nvidia.com?part=12

  reply	other threads:[~2026-07-07  9:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07  7:21 [PATCH v5 00/13] gpu: nova-core: consolidate and streamline GSP boot process Alexandre Courbot
2026-07-07  7:21 ` [PATCH v5 01/13] gpu: nova-core: gsp: sequencer: use GspBootContext Alexandre Courbot
2026-07-07  7:21 ` [PATCH v5 02/13] gpu: nova-core: gsp: sequencer: do not store sequence into GspSequencer Alexandre Courbot
2026-07-07  7:58   ` sashiko-bot
2026-07-07  7:21 ` [PATCH v5 03/13] gpu: nova-core: gsp: replace BootUnloadGuard with local handlers Alexandre Courbot
2026-07-07  8:04   ` Eliot Courtney
2026-07-07 12:56     ` Alexandre Courbot
2026-07-07 13:34       ` Eliot Courtney
2026-07-07  8:10   ` sashiko-bot
2026-07-07  7:21 ` [PATCH v5 04/13] gpu: nova-core: gsp: pass GspBootContext to unload methods Alexandre Courbot
2026-07-07  7:21 ` [PATCH v5 05/13] gpu: nova-core: gsp: centralize missing unload bundle warnings Alexandre Courbot
2026-07-07  8:30   ` sashiko-bot
2026-07-07  7:21 ` [PATCH v5 06/13] gpu: nova-core: gsp: fold TU102 unload bundle construction into HAL method Alexandre Courbot
2026-07-07  7:21 ` [PATCH v5 07/13] gpu: nova-core: gsp: turn FWSEC execution " Alexandre Courbot
2026-07-07  7:21 ` [PATCH v5 08/13] gpu: nova-core: gsp: make use of FWSEC bootloader a property of the TU102 HAL Alexandre Courbot
2026-07-07  7:42   ` Eliot Courtney
2026-07-07  7:21 ` [PATCH v5 09/13] gpu: nova-core: move GSP firmware files decision to GSP HAL Alexandre Courbot
2026-07-07  7:49   ` Alexandre Courbot
2026-07-07 13:08     ` Eliot Courtney
2026-07-07  7:21 ` [PATCH v5 10/13] gpu: nova-core: avoid repeated calls to pci::Device::as_ref Alexandre Courbot
2026-07-07  7:21 ` [PATCH v5 11/13] gpu: nova-core: gsp: pass GspBootContext mutably Alexandre Courbot
2026-07-07  7:21 ` [PATCH v5 12/13] gpu: nova-core: gsp: separate context and GPU lifetimes in GspBootContext Alexandre Courbot
2026-07-07  9:02   ` sashiko-bot [this message]
2026-07-07  7:21 ` [PATCH v5 13/13] gpu: nova-core: store Fsp instance in Gpu Alexandre Courbot

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=20260707090227.61B361F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ojeda@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox