From: sashiko-bot@kernel.org
To: "Alexandre Courbot" <acourbot@nvidia.com>
Cc: dri-devel@lists.freedesktop.org,
"Danilo Krummrich" <dakr@kernel.org>,
ojeda@kernel.org
Subject: Re: [PATCH v4 10/13] gpu: nova-core: avoid repeated calls to pci::Device::as_ref
Date: Mon, 29 Jun 2026 14:17:13 +0000 [thread overview]
Message-ID: <20260629141714.36F7D1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260629-nova-bootcontext-v4-10-5539d8469590@nvidia.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The refactoring to use a local `Device` reference misses several `dev_dbg!` macro invocations in `Gpu::new`, leaving the task incomplete and the code inconsistent.
--
commit 5b411de251c3e77848e5e58356562796a1fb83fe
Author: Alexandre Courbot <acourbot@nvidia.com>
gpu: nova-core: avoid repeated calls to pci::Device::as_ref
Add a local Device reference created from the pci::Device in the
Gpu constructor to avoid repeatedly calling as_ref.
> diff --git a/drivers/gpu/nova-core/gpu.rs b/drivers/gpu/nova-core/gpu.rs
> index c04706b60ba80..663e61d0c023b 100644
> --- a/drivers/gpu/nova-core/gpu.rs
> +++ b/drivers/gpu/nova-core/gpu.rs
[ ... ]
> @@ -372,8 +374,8 @@ pub(crate) fn new(
> // Obtain and display basic GPU information.
> let info = gsp_resources.gsp.get_static_info(bar)?;
> match info.gpu_name() {
> - Ok(name) => dev_info!(pdev, "GPU name: {}\n", name),
> - Err(e) => dev_warn!(pdev, "GPU name unavailable: {:?}\n", e),
> + Ok(name) => dev_info!(dev, "GPU name: {}\n", name),
> + Err(e) => dev_warn!(dev, "GPU name unavailable: {:?}\n", e),
> }
>
> if !info.usable_fb_regions.is_empty() {
> dev_dbg!(pdev, "Usable FB regions:\n");
> for region in &info.usable_fb_regions {
> dev_dbg!(pdev, " - {:#x?}\n", region);
> }
>
> dev_dbg!(
> pdev,
> "Total usable VRAM: {} MiB\n",
> info.usable_fb_regions.iter().fold(0u64, |res, region| res
> .saturating_add(region.end - region.start))
> / u64::SZ_1M
> );
[Severity: Low]
This isn't a bug, but should these remaining dev_dbg!() macros also be updated
to use dev instead of pdev? Leaving them as pdev continues to implicitly
invoke .as_ref(), which this patch is trying to avoid.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260629-nova-bootcontext-v4-0-5539d8469590@nvidia.com?part=10
next prev parent reply other threads:[~2026-06-29 14:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 14:09 [PATCH v4 00/13] gpu: nova-core: consolidate and streamline GSP boot process Alexandre Courbot
2026-06-29 14:09 ` [PATCH v4 01/13] gpu: nova-core: gsp: sequencer: use GspBootContext Alexandre Courbot
2026-06-29 14:22 ` sashiko-bot
2026-06-29 14:09 ` [PATCH v4 02/13] gpu: nova-core: gsp: sequencer: do not store sequence into GspSequencer Alexandre Courbot
2026-06-29 14:19 ` sashiko-bot
2026-06-29 14:09 ` [PATCH v4 03/13] gpu: nova-core: gsp: replace BootUnloadGuard with local handlers Alexandre Courbot
2026-06-29 14:21 ` sashiko-bot
2026-07-01 2:54 ` Eliot Courtney
2026-07-06 10:00 ` Alexandre Courbot
2026-06-29 14:09 ` [PATCH v4 04/13] gpu: nova-core: gsp: pass GspBootContext to unload methods Alexandre Courbot
2026-07-01 3:57 ` Eliot Courtney
2026-06-29 14:09 ` [PATCH v4 05/13] gpu: nova-core: gsp: centralize missing unload bundle warnings Alexandre Courbot
2026-06-29 14:20 ` sashiko-bot
2026-07-01 4:06 ` Eliot Courtney
2026-06-29 14:09 ` [PATCH v4 06/13] gpu: nova-core: gsp: fold TU102 unload bundle construction into HAL method Alexandre Courbot
2026-07-01 4:15 ` Eliot Courtney
2026-06-29 14:09 ` [PATCH v4 07/13] gpu: nova-core: gsp: turn FWSEC execution " Alexandre Courbot
2026-07-01 4:16 ` Eliot Courtney
2026-06-29 14:09 ` [PATCH v4 08/13] gpu: nova-core: gsp: make use of FWSEC bootloader a property of the TU102 HAL Alexandre Courbot
2026-06-29 14:09 ` [PATCH v4 09/13] gpu: nova-core: introduce GspBootMethod Alexandre Courbot
2026-07-02 2:28 ` Eliot Courtney
2026-06-29 14:09 ` [PATCH v4 10/13] gpu: nova-core: avoid repeated calls to pci::Device::as_ref Alexandre Courbot
2026-06-29 14:17 ` sashiko-bot [this message]
2026-07-01 6:38 ` Eliot Courtney
2026-06-29 14:09 ` [PATCH v4 11/13] gpu: nova-core: gsp: pass GspBootContext mutably Alexandre Courbot
2026-07-01 6:40 ` Eliot Courtney
2026-06-29 14:09 ` [PATCH v4 12/13] gpu: nova-core: gsp: separate context and GPU lifetimes in GspBootContext Alexandre Courbot
2026-06-29 14:22 ` sashiko-bot
2026-07-01 6:52 ` Eliot Courtney
2026-06-29 14:09 ` [PATCH v4 13/13] gpu: nova-core: store Fsp instance in Gpu Alexandre Courbot
2026-06-29 14:27 ` sashiko-bot
2026-07-01 6:46 ` Eliot Courtney
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=20260629141714.36F7D1F000E9@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