From: John Hubbard <jhubbard@nvidia.com>
To: Alexandre Courbot <acourbot@nvidia.com>,
Dave Airlie via B4 Relay <devnull+airlied.redhat.com@kernel.org>
Cc: airlied@redhat.com, Danilo Krummrich <dakr@kernel.org>,
David Airlie <airlied@gmail.com>,
nova-gpu@lists.linux.dev, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] gpu: nova-core: make pramin/buddy optional
Date: Fri, 30 Oct 2026 14:30:12 -0700 [thread overview]
Message-ID: <26dee420-ed28-47e1-808a-531bdfbb03ef@nvidia.com> (raw)
In-Reply-To: <DMHV8ZWTAEVB.YC2XG5BHNBN4@nvidia.com>
On 10/29/26 8:51 PM, Alexandre Courbot wrote:
> On Mon Oct 26, 2026 at 1:24 PM JST, Dave Airlie via B4 Relay wrote:
>> From: Dave Airlie <airlied@redhat.com>
...
>> pub(crate) struct GpuMm<'gpu> {
>> - buddy: GpuBuddy,
>> - pramin: pramin::Pramin<'gpu>,
>> + buddy: Option<GpuBuddy>,
>> + pramin: Option<pramin::Pramin<'gpu>>,
>> tlb: Pin<KBox<Tlb<'gpu>>>,
>> }
>>
>> @@ -85,28 +85,28 @@ impl<'gpu> GpuMm<'gpu> {
>> pub(crate) fn new(
>> bar: Bar0<'gpu>,
>> chipset: Chipset,
>> - buddy_params: GpuBuddyParams,
>> - total_fb_end: VramAddress,
>> + buddy_params: Option<GpuBuddyParams>,
>> + total_fb_end: Option<VramAddress>,
>
> This is related to the comment made by Sashiko, but in which cases are
> we expecting `total_fb_end` to be `None` here? Is this the same set of
> systems for which `buddy_params` will be `None`? If so both arguments
> should be merged into a new type to remove the ability to represent
> invalid state where one is `Some` and the other is `None`.
Neither, because the decision has to happen before GSP boot: on a
zero-FB chip the kernel-side RM sends GSP-RM a system-memory heap in the
boot arguments. The static info comes back after that.
Open RM makes it a per-chip HAL constant. See "bGpuArchIsZeroFb".
thanks,
--
John Hubbard
next prev parent reply other threads:[~2026-10-30 21:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 4:24 [PATCH] gpu: nova-core: make pramin/buddy optional Dave Airlie via B4 Relay
2026-10-26 6:58 ` sashiko-bot
2026-10-26 18:50 ` Danilo Krummrich
2026-10-30 3:51 ` Alexandre Courbot
2026-10-30 6:18 ` David Airlie
2026-10-30 11:28 ` Alexandre Courbot
2026-10-30 7:54 ` Eliot Courtney
2026-10-30 21:30 ` John Hubbard [this message]
2026-10-30 7:57 ` Eliot Courtney
2026-10-30 11:23 ` Alexandre Courbot
2026-10-30 21:42 ` John Hubbard
2026-10-30 21:34 ` John Hubbard
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=26dee420-ed28-47e1-808a-531bdfbb03ef@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dakr@kernel.org \
--cc=devnull+airlied.redhat.com@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=nova-gpu@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