From: "Eliot Courtney" <ecourtney@nvidia.com>
To: "Timur Tabi" <ttabi@nvidia.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"John Hubbard" <jhubbard@nvidia.com>,
"Eliot Courtney" <ecourtney@nvidia.com>,
<nova-gpu@lists.linux.dev>
Subject: Re: [PATCH 2/5] gpu: nova-core: merge LibosParams into GspFwHeapParams
Date: Wed, 11 Nov 2026 15:30:24 +0900 [thread overview]
Message-ID: <DMS64VZKSLOP.2RCSK9BCHD47C@nvidia.com> (raw)
In-Reply-To: <20261110231053.1352163-3-ttabi@nvidia.com>
On Wed Nov 11, 2026 at 8:10 AM JST, Timur Tabi wrote:
> LibosParams and GspFwHeapParams are two types used to hold data and/or
> methods for calculating the heap sides that GSP-RM needs for booting.
> Although they technically represent distinct parts of the equations,
> they are always used together.
>
> A future change to this code will introduce runtime calculations based
> on values extracted from the GSP-RM, replacing the compile-time
> constants currently used. Merging the two types in this commit keeps
> the current functionality while providing a foundation that simplifies
> future changes.
>
> For the same reason, the LIBOSx constants are replaced with variables.
>
> Signed-off-by: Timur Tabi <ttabi@nvidia.com>
> ---
The direction of this series looks good to me, but I think there's some
unnecessary churn from moving the functions from LibosParams now, rather
than switching over after adding the TLV values to GspFwHeapParams. What
about doing essentially patch #1 then patch #3 (which doesn't need the
zero dummy vals if #2 is removed) of this series, then a patch each for
switching over
- non-wpr heap + pmu reserved size (+drop hal functions)
- vGPU stuff
- WPR2 heap size
I tried this locally and it seems to remove a bunch of the churn.
WDYT?
next prev parent reply other threads:[~2026-11-11 6:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 23:10 [PATCH 0/5] Transition nova-core to use TLV variables for heap sizes Timur Tabi
2026-11-10 23:10 ` [PATCH 1/5] gpu: nova-core: add Tlv.get_u64 Timur Tabi
2026-11-11 0:20 ` John Hubbard
2026-11-11 2:59 ` Timur Tabi
2026-11-11 3:45 ` John Hubbard
2026-11-11 5:21 ` Eliot Courtney
2026-11-11 5:27 ` Eliot Courtney
2026-11-10 23:10 ` [PATCH 2/5] gpu: nova-core: merge LibosParams into GspFwHeapParams Timur Tabi
2026-11-11 6:30 ` Eliot Courtney [this message]
2026-11-10 23:10 ` [PATCH 3/5] gpu: nova-core: read GSP heap variables from TLV Timur Tabi
2026-11-10 23:10 ` [PATCH 4/5] gpu: nova-core: use the TLV heap sizes Timur Tabi
2026-11-10 23:10 ` [PATCH 5/5] gpu: nova-core: remove heap size related HAL functions Timur Tabi
2026-11-10 23:21 ` [PATCH 0/5] Transition nova-core to use TLV variables for heap sizes Timur Tabi
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=DMS64VZKSLOP.2RCSK9BCHD47C@nvidia.com \
--to=ecourtney@nvidia.com \
--cc=acourbot@nvidia.com \
--cc=dakr@kernel.org \
--cc=jhubbard@nvidia.com \
--cc=nova-gpu@lists.linux.dev \
--cc=ttabi@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 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.