From: "Gary Guo" <gary@garyguo.net>
To: "John Hubbard" <jhubbard@nvidia.com>,
"Danilo Krummrich" <dakr@kernel.org>
Cc: "Alexandre Courbot" <acourbot@nvidia.com>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"Timur Tabi" <ttabi@nvidia.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Edwin Peer" <epeer@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>,
nouveau@lists.freedesktop.org, rust-for-linux@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 01/31] gpu: nova-core: print FB sizes, along with ranges
Date: Tue, 13 Jan 2026 13:28:14 +0000 [thread overview]
Message-ID: <DFNHWA9PXH5X.5HWPO3GQPX6R@garyguo.net> (raw)
In-Reply-To: <20251203055923.1247681-2-jhubbard@nvidia.com>
On Wed Dec 3, 2025 at 5:58 AM GMT, John Hubbard wrote:
> For convenience of the reader: now you can directly see the sizes of
> each range. It is suprising just how much this helps.
>
> Sample output (using an Ampere GA104):
>
> NovaCore 0000:e1:00.0: FbLayout {
> fb: 0x0..0x3ff800000 (16376 MB),
> vga_workspace: 0x3ff700000..0x3ff800000 (1 MB),
> frts: 0x3ff600000..0x3ff700000 (1 MB),
> boot: 0x3ff5fa000..0x3ff600000 (0 MB),
> elf: 0x3fb960000..0x3ff5f9000 (60 MB),
> wpr2_heap: 0x3f3900000..0x3fb900000 (128 MB),
> wpr2: 0x3f3800000..0x3ff700000 (191 MB),
> heap: 0x3f3700000..0x3f3800000 (1 MB),
> vf_partition_count: 0x0,
> }
>
> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
> ---
> drivers/gpu/nova-core/fb.rs | 66 +++++++++++++++++++++++++++----------
> 1 file changed, 49 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/gpu/nova-core/fb.rs b/drivers/gpu/nova-core/fb.rs
> index 3c9cf151786c..333e952400e6 100644
> --- a/drivers/gpu/nova-core/fb.rs
> +++ b/drivers/gpu/nova-core/fb.rs
> @@ -1,9 +1,13 @@
> // SPDX-License-Identifier: GPL-2.0
>
> -use core::ops::Range;
> +use core::ops::{
> + Deref,
> + Range, //
> +};
>
> use kernel::{
> device,
> + fmt,
> prelude::*,
> ptr::{
> Alignable,
> @@ -94,26 +98,54 @@ pub(crate) fn unregister(&self, bar: &Bar0) {
> }
> }
>
> +pub(crate) struct FbRange(Range<u64>);
How useful do you think this is in general? Would it make sense to have a
dedicated PhysAddrRange type in kernel crate that provides this feature?
> +
> +impl From<Range<u64>> for FbRange {
> + fn from(range: Range<u64>) -> Self {
> + Self(range)
> + }
> +}
> +
> +impl Deref for FbRange {
> + type Target = Range<u64>;
> +
> + fn deref(&self) -> &Self::Target {
> + &self.0
> + }
> +}
> +
> +impl fmt::Debug for FbRange {
> + fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
If you want to make this more generic, you can gate the size printing on
`f.alternate()`. So if people use `{:?}` to print a compact form of `FbLayout`,
they get just the range, and if they use `{:#?}` then they also get the sizes.
> + let size_mb = (self.0.end - self.0.start) >> 20;
> + f.write_fmt(fmt!(
> + "{:#x}..{:#x} ({} MB)",
I would either just use IEC prefix "MiB", or alternatively use the coreutils
convention and use "M" to represent MiB.
Best,
Gary
> + self.0.start,
> + self.0.end,
> + size_mb
> + ))
> + }
> +}
> +
> /// Layout of the GPU framebuffer memory.
> ///
> /// Contains ranges of GPU memory reserved for a given purpose during the GSP boot process.
> #[derive(Debug)]
> pub(crate) struct FbLayout {
> /// Range of the framebuffer. Starts at `0`.
> - pub(crate) fb: Range<u64>,
> + pub(crate) fb: FbRange,
> /// VGA workspace, small area of reserved memory at the end of the framebuffer.
> - pub(crate) vga_workspace: Range<u64>,
> + pub(crate) vga_workspace: FbRange,
> /// FRTS range.
> - pub(crate) frts: Range<u64>,
> + pub(crate) frts: FbRange,
> /// Memory area containing the GSP bootloader image.
> - pub(crate) boot: Range<u64>,
> + pub(crate) boot: FbRange,
> /// Memory area containing the GSP firmware image.
> - pub(crate) elf: Range<u64>,
> + pub(crate) elf: FbRange,
> /// WPR2 heap.
> - pub(crate) wpr2_heap: Range<u64>,
> + pub(crate) wpr2_heap: FbRange,
> /// WPR2 region range, starting with an instance of `GspFwWprMeta`.
> - pub(crate) wpr2: Range<u64>,
> - pub(crate) heap: Range<u64>,
> + pub(crate) wpr2: FbRange,
> + pub(crate) heap: FbRange,
> pub(crate) vf_partition_count: u8,
> }
>
> @@ -125,7 +157,7 @@ pub(crate) fn new(chipset: Chipset, bar: &Bar0, gsp_fw: &GspFirmware) -> Result<
> let fb = {
> let fb_size = hal.vidmem_size(bar);
>
> - 0..fb_size
> + FbRange(0..fb_size)
> };
>
> let vga_workspace = {
> @@ -152,7 +184,7 @@ pub(crate) fn new(chipset: Chipset, bar: &Bar0, gsp_fw: &GspFirmware) -> Result<
> }
> };
>
> - vga_base..fb.end
> + FbRange(vga_base..fb.end)
> };
>
> let frts = {
> @@ -160,7 +192,7 @@ pub(crate) fn new(chipset: Chipset, bar: &Bar0, gsp_fw: &GspFirmware) -> Result<
> const FRTS_SIZE: u64 = usize_as_u64(SZ_1M);
> let frts_base = vga_workspace.start.align_down(FRTS_DOWN_ALIGN) - FRTS_SIZE;
>
> - frts_base..frts_base + FRTS_SIZE
> + FbRange(frts_base..frts_base + FRTS_SIZE)
> };
>
> let boot = {
> @@ -168,7 +200,7 @@ pub(crate) fn new(chipset: Chipset, bar: &Bar0, gsp_fw: &GspFirmware) -> Result<
> let bootloader_size = u64::from_safe_cast(gsp_fw.bootloader.ucode.size());
> let bootloader_base = (frts.start - bootloader_size).align_down(BOOTLOADER_DOWN_ALIGN);
>
> - bootloader_base..bootloader_base + bootloader_size
> + FbRange(bootloader_base..bootloader_base + bootloader_size)
> };
>
> let elf = {
> @@ -176,7 +208,7 @@ pub(crate) fn new(chipset: Chipset, bar: &Bar0, gsp_fw: &GspFirmware) -> Result<
> let elf_size = u64::from_safe_cast(gsp_fw.size);
> let elf_addr = (boot.start - elf_size).align_down(ELF_DOWN_ALIGN);
>
> - elf_addr..elf_addr + elf_size
> + FbRange(elf_addr..elf_addr + elf_size)
> };
>
> let wpr2_heap = {
> @@ -185,7 +217,7 @@ pub(crate) fn new(chipset: Chipset, bar: &Bar0, gsp_fw: &GspFirmware) -> Result<
> gsp::LibosParams::from_chipset(chipset).wpr_heap_size(chipset, fb.end);
> let wpr2_heap_addr = (elf.start - wpr2_heap_size).align_down(WPR2_HEAP_DOWN_ALIGN);
>
> - wpr2_heap_addr..(elf.start).align_down(WPR2_HEAP_DOWN_ALIGN)
> + FbRange(wpr2_heap_addr..(elf.start).align_down(WPR2_HEAP_DOWN_ALIGN))
> };
>
> let wpr2 = {
> @@ -193,13 +225,13 @@ pub(crate) fn new(chipset: Chipset, bar: &Bar0, gsp_fw: &GspFirmware) -> Result<
> let wpr2_addr = (wpr2_heap.start - u64::from_safe_cast(size_of::<gsp::GspFwWprMeta>()))
> .align_down(WPR2_DOWN_ALIGN);
>
> - wpr2_addr..frts.end
> + FbRange(wpr2_addr..frts.end)
> };
>
> let heap = {
> const HEAP_SIZE: u64 = usize_as_u64(SZ_1M);
>
> - wpr2.start - HEAP_SIZE..wpr2.start
> + FbRange(wpr2.start - HEAP_SIZE..wpr2.start)
> };
>
> Ok(Self {
next prev parent reply other threads:[~2026-01-13 13:28 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 5:58 [PATCH 00/31] gpu: nova-core: firmware: Hopper/Blackwell support John Hubbard
2025-12-03 5:58 ` [PATCH 01/31] gpu: nova-core: print FB sizes, along with ranges John Hubbard
2025-12-03 19:35 ` Timur Tabi
2025-12-04 7:27 ` John Hubbard
2026-01-13 13:28 ` Gary Guo [this message]
2026-01-13 13:42 ` Miguel Ojeda
2026-01-14 2:23 ` John Hubbard
2026-01-23 3:09 ` John Hubbard
2026-01-23 18:04 ` Gary Guo
2025-12-03 5:58 ` [PATCH 02/31] gpu: nova-core: add FbRange.len() and use it in boot.rs John Hubbard
2026-01-13 13:29 ` Gary Guo
2025-12-03 5:58 ` [PATCH 03/31] gpu: nova-core: Hopper/Blackwell: basic GPU identification John Hubbard
2025-12-03 5:58 ` [PATCH 04/31] nova-core: factor .fwsignature* selection into a new get_gsp_sigs_section() John Hubbard
2026-01-13 13:33 ` Gary Guo
2026-01-14 2:24 ` John Hubbard
2025-12-03 5:58 ` [PATCH 05/31] gpu: nova-core: use GPU Architecture to simplify HAL selections John Hubbard
2025-12-03 19:38 ` Timur Tabi
2025-12-04 7:28 ` John Hubbard
2025-12-03 5:58 ` [PATCH 06/31] gpu: nova-core: apply the one "use" item per line policy to commands.rs John Hubbard
2026-01-13 13:35 ` Gary Guo
2025-12-03 5:58 ` [PATCH 07/31] gpu: nova-core: set DMA mask width based on GPU architecture John Hubbard
2026-01-13 13:43 ` Gary Guo
2026-01-14 3:03 ` John Hubbard
2025-12-03 5:59 ` [PATCH 08/31] gpu: nova-core: move firmware image parsing code to firmware.rs John Hubbard
2026-01-13 13:44 ` Gary Guo
2025-12-03 5:59 ` [PATCH 09/31] gpu: nova-core: factor out a section_name_eq() function John Hubbard
2026-01-13 13:57 ` Gary Guo
2026-01-14 3:18 ` John Hubbard
2026-01-14 14:40 ` Gary Guo
2025-12-03 5:59 ` [PATCH 10/31] gpu: nova-core: don't assume 64-bit firmware images John Hubbard
2025-12-03 5:59 ` [PATCH 11/31] gpu: nova-core: add support for 32-bit " John Hubbard
2025-12-03 5:59 ` [PATCH 12/31] gpu: nova-core: add auto-detection of 32-bit, 64-bit " John Hubbard
2025-12-03 5:59 ` [PATCH 13/31] gpu: nova-core: Hopper/Blackwell: add FMC firmware image, in support of FSP John Hubbard
2025-12-03 5:59 ` [PATCH 14/31] gpu: nova-core: Hopper/Blackwell: add FSP falcon engine stub John Hubbard
2025-12-03 5:59 ` [PATCH 15/31] gpu: nova-core: Hopper/Blackwell: add FSP falcon EMEM operations John Hubbard
2025-12-03 6:04 ` Timur Tabi
2025-12-03 6:07 ` John Hubbard
2026-01-21 16:06 ` Gary Guo
2026-01-21 16:17 ` Miguel Ojeda
2026-01-23 23:48 ` John Hubbard
2025-12-03 5:59 ` [PATCH 16/31] gpu: nova-core: Hopper/Blackwell: add FSP message infrastructure John Hubbard
2025-12-05 16:47 ` Joel Fernandes
2026-01-03 2:15 ` John Hubbard
2025-12-03 5:59 ` [PATCH 17/31] gpu: nova-core: Hopper/Blackwell: calculate reserved FB heap size John Hubbard
2025-12-03 20:48 ` Timur Tabi
2025-12-04 7:34 ` John Hubbard
2026-01-21 16:10 ` Gary Guo
2026-01-23 23:56 ` John Hubbard
2025-12-03 5:59 ` [PATCH 18/31] gpu: nova-core: Hopper/Blackwell: add needs_large_reserved_mem() John Hubbard
2025-12-03 20:51 ` Timur Tabi
2025-12-04 7:36 ` John Hubbard
2025-12-03 5:59 ` [PATCH 19/31] gpu: nova-core: Hopper/Blackwell: add FSP secure boot completion waiting John Hubbard
2025-12-03 5:59 ` [PATCH 20/31] gpu: nova-core: Hopper/Blackwell: add FSP message structures John Hubbard
2025-12-03 5:59 ` [PATCH 21/31] gpu: nova-core: Hopper/Blackwell: add FMC signature extraction John Hubbard
2025-12-03 15:45 ` Joel Fernandes
2025-12-04 7:55 ` John Hubbard
2026-01-21 16:15 ` Gary Guo
2026-01-24 0:45 ` John Hubbard
2025-12-03 5:59 ` [PATCH 22/31] gpu: nova-core: Hopper/Blackwell: add FSP send/receive messaging John Hubbard
2025-12-03 5:59 ` [PATCH 23/31] gpu: nova-core: Hopper/Blackwell: add FSP Chain of Trust boot John Hubbard
2025-12-05 17:15 ` Joel Fernandes
2025-12-08 6:00 ` John Hubbard
2025-12-06 21:36 ` Joel Fernandes
2025-12-08 6:09 ` John Hubbard
2025-12-03 5:59 ` [PATCH 24/31] gpu: nova-core: Hopper/Blackwell: larger non-WPR heap John Hubbard
2026-01-21 16:18 ` Gary Guo
2026-01-24 1:50 ` John Hubbard
2025-12-03 5:59 ` [PATCH 25/31] gpu: nova-core: Hopper/Blackwell: larger WPR2 (GSP) heap John Hubbard
2025-12-03 5:59 ` [PATCH 26/31] gpu: nova-core: refactor SEC2 booter loading into run_booter() helper John Hubbard
2025-12-03 20:53 ` Timur Tabi
2025-12-04 7:37 ` John Hubbard
2025-12-03 5:59 ` [PATCH 27/31] gpu: nova-core: Hopper/Blackwell: skip GFW boot waiting John Hubbard
2025-12-03 5:59 ` [PATCH 28/31] gpu: nova-core: Hopper/Blackwell: add GSP lockdown release polling John Hubbard
2025-12-03 20:59 ` Timur Tabi
2025-12-04 7:49 ` John Hubbard
2026-01-21 16:20 ` Gary Guo
2026-01-24 1:10 ` John Hubbard
2025-12-03 5:59 ` [PATCH 29/31] gpu: nova-core: Hopper/Blackwell: add FSP Chain of Trust boot path John Hubbard
2026-01-21 16:35 ` Gary Guo
2026-01-24 1:38 ` John Hubbard
2026-01-24 1:42 ` John Hubbard
2026-01-26 13:08 ` Gary Guo
2026-01-26 19:53 ` John Hubbard
2025-12-03 5:59 ` [PATCH 30/31] gpu: nova-core: Hopper/Blackwell: new location for PCI config mirror John Hubbard
2025-12-03 5:59 ` [PATCH 31/31] gpu: nova-core: clarify the GPU firmware boot steps 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=DFNHWA9PXH5X.5HWPO3GQPX6R@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--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=epeer@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.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