From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "John Hubbard" <jhubbard@nvidia.com>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
"Timur Tabi" <ttabi@nvidia.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Eliot Courtney" <ecourtney@nvidia.com>,
"Zhi Wang" <zhiw@nvidia.com>, "David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
nova-gpu@lists.linux.dev, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] gpu: nova-core: extract radix3 page table into its own module
Date: Tue, 22 Sep 2026 22:23:27 +0900 [thread overview]
Message-ID: <DLLVLWJRODXZ.1WPWHMSMWJLJK@nvidia.com> (raw)
In-Reply-To: <20260913195413.742143-2-jhubbard@nvidia.com>
On Mon Sep 14, 2026 at 4:54 AM JST, John Hubbard wrote:
> In order to boot the GSP, nova-core loads the GSP firmware image into
> system memory, and the GPU copies it into the framebuffer, the GPU's own
> memory. The GPU finds the GSP firmware image's pages via "radix3", a
> three-level page table of 4 KiB pages that the driver builds. Today the
> table exists as fields within the GSP firmware wrapper, which is fine
> because there is only one radix3 consumer.
>
> The upcoming r000 series[1], however, introduces a second radix3 caller:
> the ucodes firmware image. That is because the GSP has been changed, so
> that it automatically fetches the subset of ucodes that it requires,
> thus reducing the size of the GSP image. This is a helpful change for
> the firmware situation overall, but it will require nova-core to load
> and provide ucodes, in much the same way that it was loading and
> providing the GSP firmware image.
>
> Therefore, split out radix3 into its own module.
This patch does a multitude of renames and comment updates as it moves
code around, which makes it difficult to review with `--color-moved`.
`--color-moved` is a really nice git option that applies a different
color to lines that have just moved instead of having changed; on a
patch like this one I expect to see mostly the "this has moved" color,
which allows me to confirm that no undesirable side-effect has taken
place.
But unfortunately the mix of move and changes turns the `--color-moved`
augmented diff into a Christmas tree of moves mixed with code changes,
defeating its purpose.
So in order to be able to review properly I had to split this patch into
the mechanical move, plus two patches on top to handle the rename and
comments updates.
This makes the first patch's mechanical move easy to confirm using
`--color-moved`, and as a bonus the other changes also become easily
reviewable on top of that.
Anyway, all this to say that this series is merged with a couple of
extra commits (and some removed comments kept as they were useful imho).
Please check the end result of this patch with `--color-moved` to see
what I mean, and let's make sure to keep code moves and changes
separated from now on to make reviews easier.
next prev parent reply other threads:[~2026-09-22 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 19:54 [PATCH 0/3] radix3 and ELF cleanup, pre-r000 John Hubbard
2026-09-13 19:54 ` [PATCH 1/3] gpu: nova-core: extract radix3 page table into its own module John Hubbard
2026-09-13 20:36 ` Gary Guo
2026-09-13 20:56 ` John Hubbard
2026-09-14 0:44 ` Alexandre Courbot
2026-09-22 13:23 ` Alexandre Courbot [this message]
2026-09-13 19:54 ` [PATCH 2/3] gpu: nova-core: zero-pad radix3 page table levels to page boundary John Hubbard
2026-09-13 19:54 ` [PATCH 3/3] gpu: nova-core: rename the FbRanges elf field to fw_image 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=DLLVLWJRODXZ.1WPWHMSMWJLJK@nvidia.com \
--to=acourbot@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=airlied@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=ecourtney@nvidia.com \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=simona@ffwll.ch \
--cc=tmgross@umich.edu \
--cc=ttabi@nvidia.com \
--cc=zhiw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®