gpu: nova-core: firmware: Hopper/Blackwell support
Subsystems (4)
v9 cover gpu: nova-core: firmware: Hopper/Blackwell support
This is based on today's drm-rust-next. A git branch is here:
https://github.com/johnhubbard/linux/tree/nova-core-blackwell-v9
It's been re-tested on Turing and Blackwell:
NovaCore 0000:e1:00.0: GPU name: NVIDIA GeForce GTX 1650
NovaCore 0000:01:00.0: GPU name: NVIDIA RTX PRO 6000 Blackwell Max-Q
Workstation EditionChanges in v9:
* Rebased onto today's drm-rust-next.
* Split Architecture::Blackwell into BlackwellGB10x and BlackwellGB20x, after Gary Guo and Sashiko pointed out that GB10x and GB20x are distinct enough to warrant separate architecture variants. This surfaced several bugs where all Blackwell chips were incorrectly treated as a single group:
* Fixed the FSP boot completion register address for GB10x. GB10x
uses the same address as Hopper (0x000200bc), not the GB20x
address (0x00ad00bc).
* Made the FSP secure boot timeout architecture-dependent. GB20x
now gets 5000ms while Hopper and GB10x keep 4000ms. * Removed chipset-level match arms that were working around the single-variant design in fb/hal.rs, firmware/gsp.rs, and regs.rs.
* Simplified find_gsp_sigs_section() to return &'static str instead of Option<&'static str>, since the Architecture enum is now exhaustive and every variant has a known signature section name.
* Moved dma_set_mask_and_coherent from probe() into Gpu::new(), with the unsafe block narrowed to just that call. Gpu::new() now takes pci::Device<device::Core> instead of device::Bound to support this.
* Dropped the local chipset variable in Gpu::new() and accessed spec.chipset() directly, since Spec is now Copy.
* Changed Spec::chipset() to take self instead of &self, since Spec is Copy.
* Removed the unnecessary Tu102/Gh100 consts in gpu/hal.rs and used the unit structs directly.
* Kept a hold on the Firmware object in FspFirmware instead of copying the FMC ELF into a KVec<u8>.
* Moved the dev_info formatting fix and the GFW_BOOT comment removal out of the Copy/Clone patch and into the patches that actually touch those lines.
* Added Reviewed-by tags from Gary Guo and Alice Ryhl.
Changes in v8:
* Added Clone/Copy derives to Spec and Revision. Removed the unnecessary pin_init_scope wrapping in Gpu::new() that the lack of Copy had forced. Added a Spec::chipset() accessor.
* Removed implementation-detail sentence from the
Architecture::dma_mask() doccomment.
* Simplified the GPU HAL to two variants (Tu102, Gh100) instead of four. Renamed "Fsp" to "Gh100" to follow the HAL naming convention. Removed the spurious GA100 special case. Moved the GFW_BOOT wait into the HAL method itself instead of returning a bool.
* Increased the GFW_BOOT wait timeout from 4 seconds to 30 seconds, after Joel found that a different Blackwell SKU required extra time.
* Removed stray Cc lines from each patch.
* Fixed rustfmt issues in gsp/fw.rs and gsp/boot.rs reported by the kernel test robot against v7 patches 27 and 31.
Changes in v7:
* Rebased onto Alexandre Courbot's rust register!() series in drm-rust-next, including the related generic I/O accessor and IoCapable changes.
* Rebased onto drm-rust-next (v7.0-rc4 based).
* Dropped the v6 patches that are already in drm-rust-next: the aux-device fix, the pdev helper macro patch, and the one-item-per-line use cleanup.
* Reworked the GPU init pieces per review. DMA mask setup now stays in driver probe, with the mask width selected by GPU architecture, and the GFW boot policy now lives in a dedicated GPU HAL.
* Reworked firmware image parsing per review around a single ElfFormat trait with associated header types. Also added support for both ELF32 and ELF64 images, with automatic format detection.
* Reworked the MCTP/NVDM protocol code to use bitfield! and typed accessors, removing the open-coded bit handling.
* Reworked the FSP messaging part of the series so that the message structures are introduced in the first patches that use them, instead of as a standalone dead-code-only patch. Also changed fmc_full to use KVec<u8> from the start.
* Split the WPR heap overflow handling out into a separate prep patch. That patch makes management_overhead() and wpr_heap_size() fallible, uses checked arithmetic, and leaves the larger WPR2 heap patch with only the Hopper and Blackwell sizing changes.
* Added a code comment documenting the Hopper and Blackwell PCI config mirror base change.
Changes in v6:
* Rebased onto drm-rust-next (v7.0-rc1 based).
* Dropped the first two patches from v5 (aux device fix and pdev macros), which have since been merged independently.
* const_align_up(): reworked per review from Gary Guo, Miguel Ojeda, and Danilo Krummrich: now returns Option<usize> instead of panicking, takes an Alignment argument instead of a const generic, and no longer needs the inline_const feature addition in scripts/Makefile.build.
* The rust/sizes and SZ_*_U64 patches from v5 are no longer included. I plan to post those as a separate series that depends on this one.
Changes in v5:
* Rebased onto linux.git master.
* Split MCTP protocol into its own module and file.
* Many Rust-based improvements: more use of types, especially. Also used Result and Option more.
* Lots of cleanup of comments and print output and error handling.
* Added const_align_up() to rust/ and used it in nova-core. This required enabling a Rust feature: inline_const, as recommended by Miguel Ojeda.
* Refactoring various things, such as Gpu::new() to own Spec creation, and several more such things.
* Fixed three Delta::ZERO busy-polls (patches 21, 24, 31) to use non-zero sleep intervals (after just realizing that it was a bad choice to have zero in there).
* Reduced GH100/GB100 HAL duplication. Made FSP_PKEY_SIZE/FSP_SIG_SIZE consistent across patches. Replaced fragile architecture checks with chipset.arch(). Renamed LIBOS_BLACKWELL.
* Narrowed the scope of some of the #![expect(dead_code)] cases, although that really only matters within the series, not once it is fully applied.
John Hubbard (31):
gpu: nova-core: Hopper/Blackwell: basic GPU identification
gpu: nova-core: factor .fwsignature* selection into a new
find_gsp_sigs_section()
gpu: nova-core: use GPU Architecture to simplify HAL selections
gpu: nova-core: add Copy/Clone to Spec and Revision, add chipset()
accessor
gpu: nova-core: set DMA mask width based on GPU architecture
gpu: nova-core: Hopper/Blackwell: skip GFW boot waiting
gpu: nova-core: move firmware image parsing code to firmware.rs
gpu: nova-core: factor out an elf_str() function
gpu: nova-core: don't assume 64-bit firmware images
gpu: nova-core: add support for 32-bit firmware images
gpu: nova-core: add auto-detection of 32-bit, 64-bit firmware images
gpu: nova-core: Hopper/Blackwell: add FMC firmware image, in support
of FSP
gpu: nova-core: Hopper/Blackwell: add FSP falcon engine stub
gpu: nova-core: Hopper/Blackwell: add FSP falcon EMEM operations
gpu: nova-core: Hopper/Blackwell: add FSP message infrastructure
rust: ptr: add const_align_up()
gpu: nova-core: Hopper/Blackwell: calculate reserved FB heap size
gpu: nova-core: add MCTP/NVDM protocol types for firmware
communication
gpu: nova-core: Hopper/Blackwell: add FSP secure boot completion
waiting
gpu: nova-core: Hopper/Blackwell: add FMC signature extraction
gpu: nova-core: Hopper/Blackwell: add FSP send/receive messaging
gpu: nova-core: Hopper/Blackwell: add FspCotVersion type
gpu: nova-core: Hopper/Blackwell: larger non-WPR heap
gpu: nova-core: Hopper/Blackwell: add FSP Chain of Trust boot
gpu: nova-core: Blackwell: use correct sysmem flush registers
gpu: nova-core: make WPR heap sizing fallible
gpu: nova-core: Hopper/Blackwell: larger WPR2 (GSP) heap
gpu: nova-core: refactor SEC2 booter loading into
BooterFirmware::run()
gpu: nova-core: Hopper/Blackwell: add GSP lockdown release polling
gpu: nova-core: Hopper/Blackwell: new location for PCI config mirror
gpu: nova-core: Hopper/Blackwell: integrate FSP boot path into boot()
drivers/gpu/nova-core/driver.rs | 24 +- drivers/gpu/nova-core/falcon.rs | 1 + drivers/gpu/nova-core/falcon/fsp.rs | 220 ++++++++++ drivers/gpu/nova-core/falcon/hal.rs | 21 +- drivers/gpu/nova-core/fb.rs | 26 +- drivers/gpu/nova-core/fb/hal.rs | 36 +- drivers/gpu/nova-core/fb/hal/ga102.rs | 2 +- drivers/gpu/nova-core/fb/hal/gb100.rs | 75 ++++ drivers/gpu/nova-core/fb/hal/gb202.rs | 62 +++ drivers/gpu/nova-core/fb/hal/gh100.rs | 38 ++ drivers/gpu/nova-core/firmware.rs | 204 +++++++++ drivers/gpu/nova-core/firmware/booter.rs | 30 ++ drivers/gpu/nova-core/firmware/fsp.rs | 44 ++ drivers/gpu/nova-core/firmware/gsp.rs | 126 ++---- drivers/gpu/nova-core/fsp.rs | 530 +++++++++++++++++++++++ drivers/gpu/nova-core/gpu.rs | 87 +++- drivers/gpu/nova-core/gpu/hal.rs | 41 ++ drivers/gpu/nova-core/gsp/boot.rs | 292 ++++++++++--- drivers/gpu/nova-core/gsp/commands.rs | 8 +- drivers/gpu/nova-core/gsp/fw.rs | 85 +++- drivers/gpu/nova-core/gsp/fw/commands.rs | 22 +- drivers/gpu/nova-core/mctp.rs | 119 +++++ drivers/gpu/nova-core/nova_core.rs | 2 + drivers/gpu/nova-core/regs.rs | 96 ++++ rust/kernel/ptr.rs | 24 + 25 files changed, 1976 insertions(+), 239 deletions(-) create mode 100644 drivers/gpu/nova-core/falcon/fsp.rs create mode 100644 drivers/gpu/nova-core/fb/hal/gb100.rs create mode 100644 drivers/gpu/nova-core/fb/hal/gb202.rs create mode 100644 drivers/gpu/nova-core/fb/hal/gh100.rs create mode 100644 drivers/gpu/nova-core/firmware/fsp.rs create mode 100644 drivers/gpu/nova-core/fsp.rs create mode 100644 drivers/gpu/nova-core/gpu/hal.rs create mode 100644 drivers/gpu/nova-core/mctp.rs
base-commit: dff8302ca1d0e773c90dbeeb05e759f995c95482
Signature · 1 line
2.53.0
PATCH v9 1/31 gpu: nova-core: Hopper/Blackwell: basic GPU identification
Hopper (GH100) and Blackwell identification, including ELF .fwsignature_* items.
--- drivers/gpu/nova-core/falcon/hal.rs | 3 ++- drivers/gpu/nova-core/fb/hal.rs | 5 ++--- drivers/gpu/nova-core/firmware/gsp.rs | 6 ++++-- drivers/gpu/nova-core/gpu.rs | 21 +++++++++++++++++++++ 4 files changed, 29 insertions(+), 6 deletions(-)
drivers/gpu/nova-core/falcon/hal.rs +2 -1
@@ -80,7 +80,8 @@ pub(super) fn falcon_hal<E: FalconEngine + 'static>( TU102 | TU104 | TU106 | TU116 | TU117 => {KBox ::new (tu102::Tu102 ::<E >::new (),GFP_KERNEL )?as KBox <dyn FalconHal <E >> } - GA102 | GA103 | GA104 | GA106 | GA107 | AD102 | AD103 | AD104 | AD106 | AD107 => { + GA102 | GA103 | GA104 | GA106 | GA107 | AD102 | AD103 | AD104 | AD106 | AD107 | GH100 + | GB100 | GB102 | GB202 | GB203 | GB205 | GB206 | GB207 => {KBox ::new (ga102::Ga102 ::<E >::new (),GFP_KERNEL )?as KBox <dyn FalconHal <E >> } _ => return Err(ENOTSUPP),
drivers/gpu/nova-core/fb/hal.rs +2 -3
@@ -34,8 +34,7 @@ pub(super) fn fb_hal(chipset: Chipset) -> &'static dyn FbHal {match chipset {TU102 |TU104 |TU106 |TU117 |TU116 => tu102::TU102_HAL ,GA100 => ga100::GA100_HAL , -GA102 |GA103 |GA104 |GA106 |GA107 |AD102 |AD103 |AD104 |AD106 |AD107 => { - ga102::GA102_HAL - } +GA102 |GA103 |GA104 |GA106 |GA107 |AD102 |AD103 |AD104 |AD106 |AD107 |GH100 + |GB100 |GB102 |GB202 |GB203 |GB205 |GB206 |GB207 => ga102::GA102_HAL , } }
drivers/gpu/nova-core/firmware/gsp.rs +4 -2
@@ -213,8 +213,7 @@ pub(crate) fn new<'a>( signatures: { let sigs_section = match chipset.arch() {Architecture ::Turing -if matches! (chipset,Chipset ::TU116 |Chipset ::TU117 ) => - { +if matches! (chipset,Chipset ::TU116 |Chipset ::TU117 ) => {".fwsignature_tu11x" }Architecture ::Turing =>".fwsignature_tu10x" ,
@@ -222,6 +221,9 @@ pub(crate) fn new<'a>( Architecture::Ampere if chipset == Chipset::GA100 => ".fwsignature_tu10x", Architecture::Ampere => ".fwsignature_ga10x", Architecture::Ada => ".fwsignature_ad10x", + Architecture::Hopper => ".fwsignature_gh10x", + Architecture::BlackwellGB10x => ".fwsignature_gb10x", + Architecture::BlackwellGB20x => ".fwsignature_gb20x", }; elf::elf64_section(firmware.data(), sigs_section)
drivers/gpu/nova-core/gpu.rs +21 -0
@@ -83,12 +83,22 @@ fn try_from(value: u32) -> Result<Self, Self::Error> { GA104 = 0x174, GA106 = 0x176, GA107 = 0x177, +// Hopper + GH100 = 0x180,// Ada AD102 = 0x192, AD103 = 0x193, AD104 = 0x194, AD106 = 0x196, AD107 = 0x197, +// Blackwell + GB100 = 0x1a0, + GB102 = 0x1a2, + GB202 = 0x1b2, + GB203 = 0x1b3, + GB205 = 0x1b5, + GB206 = 0x1b6, + GB207 = 0x1b7, });impl Chipset {
@@ -100,9 +110,14 @@ pub(crate) const fn arch(self) -> Architecture { Self::GA100 | Self::GA102 | Self::GA103 | Self::GA104 | Self::GA106 | Self::GA107 => { Architecture::Ampere } + Self::GH100 => Architecture::Hopper, Self::AD102 | Self::AD103 | Self::AD104 | Self::AD106 | Self::AD107 => { Architecture::Ada } + Self::GB100 | Self::GB102 => Architecture::BlackwellGB10x, + Self::GB202 | Self::GB203 | Self::GB205 | Self::GB206 | Self::GB207 => { +Architecture ::BlackwellGB20x + } } }
@@ -139,7 +154,10 @@ pub(crate) enum Architecture {#[default] Turing = 0x16, Ampere = 0x17, + Hopper = 0x18, Ada = 0x19, + BlackwellGB10x = 0x1a, + BlackwellGB20x = 0x1b, }impl TryFrom <u8 >for Architecture {
@@ -149,7 +167,10 @@ fn try_from(value: u8) -> Result<Self> {match value {0x16 =>Ok (Self ::Turing ),0x17 =>Ok (Self ::Ampere ), +0x18 =>Ok (Self ::Hopper ),0x19 =>Ok (Self ::Ada ), +0x1a =>Ok (Self ::BlackwellGB10x ), +0x1b =>Ok (Self ::BlackwellGB20x ), _ =>Err (ENODEV ), } }
Signature · 1 line
2.53.0
PATCH v9 2/31 gpu: nova-core: factor .fwsignature* selection into a new find_gsp_sigs_section()
In reply to John HubbardKeep Gsp::new() from getting too cluttered, by factoring out the selection of .fwsignature* items. This will continue to grow as we add GPUs.
--- drivers/gpu/nova-core/firmware/gsp.rs | 31 +++++++++++++++------------ 1 file changed, 17 insertions(+), 14 deletions(-)
drivers/gpu/nova-core/firmware/gsp.rs +17 -14
@@ -146,6 +146,22 @@ pub(crate) struct GspFirmware { }impl GspFirmware { +fn find_gsp_sigs_section (chipset:Chipset ) ->Option <&'staticstr > { +match chipset.arch () { +Architecture ::Turing if matches! (chipset,Chipset ::TU116 |Chipset ::TU117 ) => { +Some (".fwsignature_tu11x" ) + } +Architecture ::Turing =>Some (".fwsignature_tu10x" ), +// GA100 uses the same firmware as Turing +Architecture ::Ampere if chipset ==Chipset ::GA100 =>Some (".fwsignature_tu10x" ), +Architecture ::Ampere =>Some (".fwsignature_ga10x" ), +Architecture ::Ada =>Some (".fwsignature_ad10x" ), +Architecture ::Hopper =>Some (".fwsignature_gh10x" ), +Architecture ::BlackwellGB10x =>Some (".fwsignature_gb10x" ), +Architecture ::BlackwellGB20x =>Some (".fwsignature_gb20x" ), + } + } +/// Loads the GSP firmware binaries, map them into `dev`'s address-space, and creates the page /// tables expected by the GSP bootloader to load it. pub(crate) fn new<'a>(
@@ -211,20 +227,7 @@ pub(crate) fn new<'a>( }, size, signatures: { - let sigs_section = match chipset.arch() { -Architecture ::Turing -if matches! (chipset,Chipset ::TU116 |Chipset ::TU117 ) => { -".fwsignature_tu11x" - } -Architecture ::Turing =>".fwsignature_tu10x" , -// GA100 uses the same firmware as Turing -Architecture ::Ampere if chipset ==Chipset ::GA100 =>".fwsignature_tu10x" , -Architecture ::Ampere =>".fwsignature_ga10x" , -Architecture ::Ada =>".fwsignature_ad10x" , -Architecture ::Hopper =>".fwsignature_gh10x" , -Architecture ::BlackwellGB10x =>".fwsignature_gb10x" , -Architecture ::BlackwellGB20x =>".fwsignature_gb20x" , - }; + let sigs_section = Self::find_gsp_sigs_section(chipset).ok_or(ENOTSUPP)?; elf::elf64_section (firmware.data (), sigs_section) .ok_or (EINVAL )
Signature · 1 line
2.53.0
Alexandre Courbot
maintainerRe: [PATCH v9 02/31] gpu: nova-core: factor .fwsignature* selection into a new find_gsp_sigs_section()
Quoted 24 lines · John Hubbard
Keep
Gsp::new()from getting too cluttered, by factoring out the selection of .fwsignature* items. This will continue to grow as we add GPUs.Reviewed-by Gary Guo <[email protected]>Signed-off-by John Hubbard <[email protected]>--- drivers/gpu/nova-core/firmware/gsp.rs | 31 +++++++++++++++------------ 1 file changed, 17 insertions(+), 14 deletions(-)drivers/gpu/nova-core/firmware/gsp.rs +6
-0@@ -146,6 +146,22 @@ pub(crate) struct GspFirmware { }impl GspFirmware { +fn find_gsp_sigs_section (chipset:Chipset ) ->Option <&'staticstr > { +match chipset.arch () { +Architecture ::Turing if matches! (chipset,Chipset ::TU116 |Chipset ::TU117 ) => { +Some (".fwsignature_tu11x" ) + } +Architecture ::Turing =>Some (".fwsignature_tu10x" ),
drivers/gpu/nova-core/firmware/gsp.rs pub(crate) struct GspFirmware { · line 164
Quoted 10 lines
drivers/gpu/nova-core/firmware/gsp.rs +10
-0+// GA100 uses the same firmware as Turing + Architecture::Ampere if chipset == Chipset::GA100 => Some(".fwsignature_tu10x"), + Architecture::Ampere => Some(".fwsignature_ga10x"), + Architecture::Ada => Some(".fwsignature_ad10x"), + Architecture::Hopper => Some(".fwsignature_gh10x"), + Architecture::BlackwellGB10x => Some(".fwsignature_gb10x"), + Architecture::BlackwellGB20x => Some(".fwsignature_gb20x"), + } + } +
So in v8 I pointed out, on this very patch, that this method doesn't need to return an Option [1]. Which you agreed to [2]. And yet this is unchanged?
Oh, actually this is fixed in the next patch, for whatever reason. Why? The original match statement was even exhaustive to begin with, so I don't see why that Option was even introduced in the first place.
Please apply the feedback on the patch it was given on.
[1] https://lore.kernel.org/all/177443554510.105362.9416236198599659187.b4-review@b4/
[2] https://lore.kernel.org/all/[email protected]/
Re: [PATCH v9 02/31] gpu: nova-core: factor .fwsignature* selection into a new find_gsp_sigs_section()
Quoted 40 lines · Alexandre Courbot
Quoted 24 lines · John Hubbard
Keep
Gsp::new()from getting too cluttered, by factoring out the selection of .fwsignature* items. This will continue to grow as we add GPUs.Reviewed-by Gary Guo <[email protected]>Signed-off-by John Hubbard <[email protected]>--- drivers/gpu/nova-core/firmware/gsp.rs | 31 +++++++++++++++------------ 1 file changed, 17 insertions(+), 14 deletions(-)drivers/gpu/nova-core/firmware/gsp.rs +6
-0@@ -146,6 +146,22 @@ pub(crate) struct GspFirmware { }impl GspFirmware { +fn find_gsp_sigs_section (chipset:Chipset ) ->Option <&'staticstr > { +match chipset.arch () { +Architecture ::Turing if matches! (chipset,Chipset ::TU116 |Chipset ::TU117 ) => { +Some (".fwsignature_tu11x" ) + } +Architecture ::Turing =>Some (".fwsignature_tu10x" ),drivers/gpu/nova-core/firmware/gsp.rs pub(crate) struct GspFirmware { · line 164
Quoted 10 lines
drivers/gpu/nova-core/firmware/gsp.rs +10
-0+// GA100 uses the same firmware as Turing + Architecture::Ampere if chipset == Chipset::GA100 => Some(".fwsignature_tu10x"), + Architecture::Ampere => Some(".fwsignature_ga10x"), + Architecture::Ada => Some(".fwsignature_ad10x"), + Architecture::Hopper => Some(".fwsignature_gh10x"), + Architecture::BlackwellGB10x => Some(".fwsignature_gb10x"), + Architecture::BlackwellGB20x => Some(".fwsignature_gb20x"), + } + } +So in v8 I pointed out, on this very patch, that this method doesn't need to return an
Option[1]. Which you agreed to [2]. And yet this is unchanged?
Quoted 1 line
Oh, actually this is fixed in the next patch, for whatever reason. Why?
It's an off-by-one error in chosing which commit to edit during git rebase.
Quoted 2 lines
The original match statement was even exhaustive to begin with, so I don't see why that
Optionwas even introduced in the first place.
Because at various points during the many months that this patchset has existed, there were unsupported Arches. Turing, for example.
thanks,
Signature · 1 line
John Hubbard
PATCH v9 3/31 gpu: nova-core: use GPU Architecture to simplify HAL selections
In reply to John HubbardReplace per-chipset match arms with Architecture-based matching in the falcon and FB HAL selection functions. This reduces the number of match arms that need updating when new chipsets are added within an existing architecture.
--- drivers/gpu/nova-core/falcon/hal.rs | 22 ++++++++++++++-------- drivers/gpu/nova-core/fb/hal.rs | 20 ++++++++++++-------- drivers/gpu/nova-core/firmware/gsp.rs | 22 +++++++++++----------- 3 files changed, 37 insertions(+), 27 deletions(-)
drivers/gpu/nova-core/falcon/hal.rs +14 -8
@@ -9,7 +9,10 @@ FalconBromParams, FalconEngine, // }, - gpu::Chipset, + gpu::{ +Architecture , +Chipset ,// + }, };mod ga102;
@@ -74,17 +77,20 @@ fn signature_reg_fuse_version(pub (super )fn falcon_hal <E :FalconEngine + 'static>( chipset:Chipset , ) ->Result <KBox <dyn FalconHal <E >>> { -use Chipset ::*; - -let hal =match chipset { -TU102 |TU104 |TU106 |TU116 |TU117 => { +let hal =match chipset.arch () { +Architecture ::Turing => {KBox ::new (tu102::Tu102 ::<E >::new (),GFP_KERNEL )?as KBox <dyn FalconHal <E >> } -GA102 |GA103 |GA104 |GA106 |GA107 |AD102 |AD103 |AD104 |AD106 |AD107 |GH100 - |GB100 |GB102 |GB202 |GB203 |GB205 |GB206 |GB207 => { +// TODO: support GA100. Its boot sequence is a lot like Turing, except that it handles the +// FRTS steps differently (specifically, it skips FWSEC-FRTS). +Architecture ::Ampere if chipset ==Chipset ::GA100 =>return Err (ENOTSUPP ), +Architecture ::Ampere + |Architecture ::Hopper + |Architecture ::Ada + |Architecture ::BlackwellGB10x + |Architecture ::BlackwellGB20x => {KBox ::new (ga102::Ga102 ::<E >::new (),GFP_KERNEL )?as KBox <dyn FalconHal <E >> } - _ =>return Err (ENOTSUPP ), };Ok (hal)
drivers/gpu/nova-core/fb/hal.rs +12 -8
@@ -4,7 +4,10 @@use crate ::{ driver::Bar0 , - gpu::Chipset ,// + gpu::{ +Architecture , +Chipset ,// + }, };mod ga100;
@@ -29,12 +32,13 @@ pub(crate) trait FbHal {/// Returns the HAL corresponding to `chipset`. pub (super )fn fb_hal (chipset:Chipset ) -> &'staticdyn FbHal { -use Chipset ::*; - -match chipset { -TU102 |TU104 |TU106 |TU117 |TU116 => tu102::TU102_HAL , -GA100 => ga100::GA100_HAL , -GA102 |GA103 |GA104 |GA106 |GA107 |AD102 |AD103 |AD104 |AD106 |AD107 |GH100 - |GB100 |GB102 |GB202 |GB203 |GB205 |GB206 |GB207 => ga102::GA102_HAL , +match chipset.arch () { +Architecture ::Turing => tu102::TU102_HAL , +Architecture ::Ampere if chipset ==Chipset ::GA100 => ga100::GA100_HAL , +Architecture ::Ampere => ga102::GA102_HAL , +Architecture ::Ada + |Architecture ::Hopper + |Architecture ::BlackwellGB10x + |Architecture ::BlackwellGB20x => ga102::GA102_HAL , } }
drivers/gpu/nova-core/firmware/gsp.rs +11 -11
@@ -146,19 +146,19 @@ pub(crate) struct GspFirmware { }impl GspFirmware { -fn find_gsp_sigs_section (chipset:Chipset ) ->Option <&'staticstr > { +fn find_gsp_sigs_section (chipset:Chipset ) -> &'staticstr {match chipset.arch () {Architecture ::Turing if matches! (chipset,Chipset ::TU116 |Chipset ::TU117 ) => { -Some (".fwsignature_tu11x" ) +".fwsignature_tu11x" } -Architecture ::Turing =>Some (".fwsignature_tu10x" ), -// GA100 uses the same firmware as Turing -Architecture ::Ampere if chipset ==Chipset ::GA100 =>Some (".fwsignature_tu10x" ), -Architecture ::Ampere =>Some (".fwsignature_ga10x" ), -Architecture ::Ada =>Some (".fwsignature_ad10x" ), -Architecture ::Hopper =>Some (".fwsignature_gh10x" ), -Architecture ::BlackwellGB10x =>Some (".fwsignature_gb10x" ), -Architecture ::BlackwellGB20x =>Some (".fwsignature_gb20x" ), +Architecture ::Turing =>".fwsignature_tu10x" , +// GA100 uses the same firmware as Turing. +Architecture ::Ampere if chipset ==Chipset ::GA100 =>".fwsignature_tu10x" , +Architecture ::Ampere =>".fwsignature_ga10x" , +Architecture ::Ada =>".fwsignature_ad10x" , +Architecture ::Hopper =>".fwsignature_gh10x" , +Architecture ::BlackwellGB10x =>".fwsignature_gb10x" , +Architecture ::BlackwellGB20x =>".fwsignature_gb20x" , } }
@@ -227,7 +227,7 @@ pub(crate) fn new<'a>( }, size, signatures: { - let sigs_section = Self::find_gsp_sigs_section(chipset).ok_or(ENOTSUPP)?; + let sigs_section = Self::find_gsp_sigs_section(chipset); elf::elf64_section (firmware.data (), sigs_section) .ok_or (EINVAL )
Signature · 1 line
2.53.0
PATCH v9 4/31 gpu: nova-core: add Copy/Clone to Spec and Revision, add chipset() accessor
In reply to John HubbardDerive Clone and Copy for Revision and Spec. Both are small value types (4 bytes total) and Copy makes them easier to use in later patches that pass them across function boundaries.
Add a Spec::chipset() accessor for use by later patches that need the chipset outside of gpu.rs.
--- drivers/gpu/nova-core/gpu.rs | 8 ++++++++ 1 file changed, 8 insertions(+)
drivers/gpu/nova-core/gpu.rs +8 -0
@@ -183,6 +183,7 @@ fn from(value: Architecture) -> Self { } } +#[derive( Clone , Copy )] pub (crate )struct Revision { major:u8 , minor:u8 ,
@@ -204,6 +205,7 @@ fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result { }/// Structure holding a basic description of the GPU: `Chipset` and `Revision`. +#[derive( Clone , Copy )] pub (crate )struct Spec { chipset:Chipset , revision:Revision ,
@@ -240,6 +242,12 @@ fn new(dev: &device::Device, bar: &Bar0) -> Result<Spec> {dev_err! (dev,"Unsupported chipset: {}\n" , boot42); }) } + +/// Returns this GPU's chipset. +#[expect(dead_code)] +pub (crate )fn chipset (self) ->Chipset { + self.chipset + } }impl TryFrom <regs::NV_PMC_BOOT_42 >for Spec {
Signature · 1 line
2.53.0
PATCH v9 5/31 gpu: nova-core: set DMA mask width based on GPU architecture
In reply to John HubbardReplace the hardcoded 47-bit DMA mask with per-architecture values. Add Architecture::dma_mask() with an exhaustive match, so new architectures get a compile-time reminder to specify their width.
Set the DMA mask in Gpu::new(). Gpu owns all DMA allocations for the device, so no concurrent allocations can exist while the constructor is still running.
Move Spec creation into probe() so the dev_info is printed early, and pass Spec into Gpu::new().
--- drivers/gpu/nova-core/driver.rs | 24 ++++++-------------- drivers/gpu/nova-core/gpu.rs | 39 +++++++++++++++++++++++---------- 2 files changed, 35 insertions(+), 28 deletions(-)
drivers/gpu/nova-core/driver.rs +7 -17
@@ -4,8 +4,6 @@ auxiliary, device::Core, devres::Devres, - dma::Device, - dma::DmaMask, pci, pci::{Class ,
@@ -23,7 +21,10 @@ }, }; -use crate ::gpu::Gpu ; +use crate ::gpu::{ +Gpu , +Spec ,// +};/// Counter for generating unique auxiliary device IDs. static AUXILIARY_ID_COUNTER :Atomic <u32 > =Atomic ::new (0 );
@@ -38,14 +39,6 @@ pub(crate) struct NovaCore {const BAR0_SIZE :usize =SZ_16M ; -// For now we only support Ampere which can use up to 47-bit DMA addresses. -// -// TODO: Add an abstraction for this to support newer GPUs which may support -// larger DMA addresses. Limiting these GPUs to smaller address widths won't -// have any adverse affects, unless installed on systems which require larger -// DMA addresses. These systems should be quite rare. -const GPU_DMA_BITS :u32 =47 ; -pub (crate )type Bar0 = pci::Bar <BAR0_SIZE >; kernel::pci_device_table!(
@@ -84,18 +77,15 @@ fn probe(pdev: &pci::Device<Core>, _info: &Self::IdInfo) -> impl PinInit<Self, E pdev.enable_device_mem ()?; pdev.set_master (); -// SAFETY: No concurrent DMA allocations or mappings can be made because -// the device is still being probed and therefore isn't being used by -// other threads of execution. -unsafe { pdev.dma_set_mask_and_coherent (DmaMask ::new ::<GPU_DMA_BITS >())? }; -let bar =Arc ::pin_init ( pdev.iomap_region_sized ::<BAR0_SIZE >(0 ,c"nova-core/bar0" ),GFP_KERNEL , )?; +let spec =Spec ::new (pdev.as_ref (), bar.access (pdev.as_ref ())?)?; +dev_info! (pdev,"NVIDIA ({})\n" , spec); Ok(try_pin_init!(Self { - gpu <- Gpu::new(pdev, bar.clone(), bar.access(pdev.as_ref())?), + gpu <- Gpu::new(pdev, bar.clone(), bar.access(pdev.as_ref())?, spec), _reg <- auxiliary::Registration::new( pdev.as_ref(), c"nova-drm",
drivers/gpu/nova-core/gpu.rs +28 -11
@@ -3,6 +3,10 @@use kernel::{ device, devres::Devres , + dma::{ +Device , +DmaMask ,// + }, fmt, pci, prelude::*,
@@ -160,6 +164,16 @@ pub(crate) enum Architecture { BlackwellGB20x = 0x1b, } +impl Architecture { +/// Returns the DMA mask supported by this architecture. +pub (crate )const fn dma_mask (&self) ->DmaMask { +match self { +Self ::Turing |Self ::Ampere |Self ::Ada =>DmaMask ::new ::<47 >(), +Self ::Hopper |Self ::BlackwellGB10x |Self ::BlackwellGB20x =>DmaMask ::new ::<52 >(), + } + } +} +impl TryFrom <u8 >for Architecture {type Error =Error ;
@@ -212,7 +226,7 @@ pub(crate) struct Spec { }impl Spec { -fn new (dev: &device::Device , bar: &Bar0 ) ->Result <Spec > { +pub (crate )fn new (dev: &device::Device , bar: &Bar0 ) ->Result <Spec > {// Some brief notes about boot0 and boot42, in chronological order: // // NV04 through NV50:
@@ -244,7 +258,6 @@ fn new(dev: &device::Device, bar: &Bar0) -> Result<Spec> { }/// Returns this GPU's chipset. -#[expect(dead_code)] pub (crate )fn chipset (self) ->Chipset { self.chipset }
@@ -292,36 +305,40 @@ pub(crate) struct Gpu {impl Gpu {pub (crate )fn new <'a>( - pdev: &'a pci::Device <device::Bound >, + pdev: &'a pci::Device <device::Core >, devres_bar:Arc <Devres <Bar0 >>, bar: &'aBar0 , + spec:Spec , ) ->impl PinInit <Self ,Error > + 'a { -try_pin_init! (Self { - spec:Spec ::new (pdev.as_ref (), bar).inspect (|spec| { -dev_info! (pdev,"NVIDIA ({})\n" , spec); - })?, +let dma_mask = spec.chipset ().arch ().dma_mask (); +try_pin_init! (Self {// We must wait for GFW_BOOT completion before doing any significant setup on the GPU. _: { +// SAFETY: `Gpu` owns all DMA allocations for this device, and we are +// still constructing it, so no concurrent DMA allocations can exist. +unsafe { pdev.dma_set_mask_and_coherent (dma_mask)? }; + gfw::wait_gfw_boot_completion (bar) .inspect_err (|_|dev_err! (pdev,"GFW boot did not complete\n" ))?; }, - sysmem_flush:SysmemFlush ::register (pdev.as_ref (), bar, spec.chipset)?, + sysmem_flush:SysmemFlush ::register (pdev.as_ref (), bar, spec.chipset ())?, gsp_falcon:Falcon ::new ( pdev.as_ref (), - spec.chipset, + spec.chipset (), ) .inspect (|falcon| falcon.clear_swgen0_intr (bar))?, - sec2_falcon:Falcon ::new (pdev.as_ref (), spec.chipset)?, + sec2_falcon:Falcon ::new (pdev.as_ref (), spec.chipset ())?, gsp <-Gsp ::new (pdev), - _: { gsp.boot (pdev, bar, spec.chipset, gsp_falcon, sec2_falcon)? }, + _: { gsp.boot (pdev, bar, spec.chipset (), gsp_falcon, sec2_falcon)? }, bar: devres_bar, + spec, }) }
Signature · 1 line
2.53.0
Alexandre Courbot
maintainerRe: [PATCH v9 05/31] gpu: nova-core: set DMA mask width based on GPU architecture
Quoted 62 lines · John Hubbard
Replace the hardcoded 47-bit DMA mask with per-architecture values. Add
Architecture::dma_mask()with an exhaustive match, so new architectures get a compile-time reminder to specify their width.Set the DMA mask in
Gpu::new(). Gpu owns all DMA allocations for the device, so no concurrent allocations can exist while the constructor is still running.Move Spec creation into
probe()so thedev_infois printed early, and pass Spec intoGpu::new().Signed-off-by John Hubbard <[email protected]>--- drivers/gpu/nova-core/driver.rs | 24 ++++++-------------- drivers/gpu/nova-core/gpu.rs | 39 +++++++++++++++++++++++---------- 2 files changed, 35 insertions(+), 28 deletions(-)drivers/gpu/nova-core/driver.rs +4
-12@@ -4,8 +4,6 @@ auxiliary, device::Core, devres::Devres, - dma::Device, - dma::DmaMask, pci, pci::{Class ,@@ -23,7 +21,10 @@ }, }; -use crate ::gpu::Gpu ; +use crate ::gpu::{ +Gpu , +Spec ,// +};/// Counter for generating unique auxiliary device IDs. static AUXILIARY_ID_COUNTER :Atomic <u32 > =Atomic ::new (0 );@@ -38,14 +39,6 @@ pub(crate) struct NovaCore {const BAR0_SIZE :usize =SZ_16M ; -// For now we only support Ampere which can use up to 47-bit DMA addresses. -// -// TODO: Add an abstraction for this to support newer GPUs which may support -// larger DMA addresses. Limiting these GPUs to smaller address widths won't -// have any adverse affects, unless installed on systems which require larger -// DMA addresses. These systems should be quite rare. -const GPU_DMA_BITS :u32 =47 ; -pub (crate )type Bar0 = pci::Bar <BAR0_SIZE >; kernel::pci_device_table!(@@ -84,18 +77,15 @@ fn probe(pdev: &pci::Device<Core>, _info: &Self::IdInfo) -> impl PinInit<Self, E pdev.enable_device_mem ()?; pdev.set_master (); -// SAFETY: No concurrent DMA allocations or mappings can be made because
drivers/gpu/nova-core/driver.rs fn probe(pdev: &pci::Device<Core>, _info: &Self::IdInfo) -> impl PinInit<Self, E · line 85
Quoted 10 lines
drivers/gpu/nova-core/driver.rs +2
-4-// the device is still being probed and therefore isn't being used by -// other threads of execution. -unsafe { pdev.dma_set_mask_and_coherent (DmaMask ::new ::<GPU_DMA_BITS >())? }; -let bar =Arc ::pin_init ( pdev.iomap_region_sized ::<BAR0_SIZE >(0 ,c"nova-core/bar0" ),GFP_KERNEL , )?; +let spec =Spec ::new (pdev.as_ref (), bar.access (pdev.as_ref ())?)?; +dev_info! (pdev,"NVIDIA ({})\n" , spec);
Now that we have moved to DMA mask into Gpu::new, what is the point of creating spec here? Its sole purpose is to be passed to Gpu::new, and that doesn't change by the end of the series.
Quoted 85 lines
drivers/gpu/nova-core/driver.rs +1
-1Ok(try_pin_init!(Self { - gpu <- Gpu::new(pdev, bar.clone(), bar.access(pdev.as_ref())?), + gpu <- Gpu::new(pdev, bar.clone(), bar.access(pdev.as_ref())?, spec), _reg <- auxiliary::Registration::new( pdev.as_ref(), c"nova-drm",drivers/gpu/nova-core/gpu.rs +24
-8@@ -3,6 +3,10 @@use kernel::{ device, devres::Devres , + dma::{ +Device , +DmaMask ,// + }, fmt, pci, prelude::*,@@ -160,6 +164,16 @@ pub(crate) enum Architecture { BlackwellGB20x = 0x1b, } +impl Architecture { +/// Returns the DMA mask supported by this architecture. +pub (crate )const fn dma_mask (&self) ->DmaMask { +match self { +Self ::Turing |Self ::Ampere |Self ::Ada =>DmaMask ::new ::<47 >(), +Self ::Hopper |Self ::BlackwellGB10x |Self ::BlackwellGB20x =>DmaMask ::new ::<52 >(), + } + } +} +impl TryFrom <u8 >for Architecture {type Error =Error ;@@ -212,7 +226,7 @@ pub(crate) struct Spec { }impl Spec { -fn new (dev: &device::Device , bar: &Bar0 ) ->Result <Spec > { +pub (crate )fn new (dev: &device::Device , bar: &Bar0 ) ->Result <Spec > {// Some brief notes about boot0 and boot42, in chronological order: // // NV04 through NV50: @@ -244,7 +258,6 @@ fn new(dev: &device::Device, bar: &Bar0) -> Result<Spec> { }/// Returns this GPU's chipset. -#[expect(dead_code)] pub (crate )fn chipset (self) ->Chipset { self.chipset }@@ -292,36 +305,40 @@ pub(crate) struct Gpu {impl Gpu {pub (crate )fn new <'a>( - pdev: &'a pci::Device <device::Bound >, + pdev: &'a pci::Device <device::Core >, devres_bar:Arc <Devres <Bar0 >>, bar: &'aBar0 , + spec:Spec , ) ->impl PinInit <Self ,Error > + 'a { -try_pin_init! (Self { - spec:Spec ::new (pdev.as_ref (), bar).inspect (|spec| { -dev_info! (pdev,"NVIDIA ({})\n" , spec); - })?, +let dma_mask = spec.chipset ().arch ().dma_mask (); +try_pin_init! (Self {// We must wait for GFW_BOOT completion before doing any significant setup on the GPU. _: { +// SAFETY: `Gpu` owns all DMA allocations for this device, and we are +// still constructing it, so no concurrent DMA allocations can exist. +unsafe { pdev.dma_set_mask_and_coherent (dma_mask)? }; + gfw::wait_gfw_boot_completion (bar) .inspect_err (|_|dev_err! (pdev,"GFW boot did not complete\n" ))?; }, - sysmem_flush:SysmemFlush ::register (pdev.as_ref (), bar, spec.chipset)?, + sysmem_flush:SysmemFlush ::register (pdev.as_ref (), bar, spec.chipset ())?,
drivers/gpu/nova-core/gpu.rs pub(crate) struct Gpu { · line 334
Quoted 10 lines
drivers/gpu/nova-core/gpu.rs +2
-2gsp_falcon: Falcon::new( pdev.as_ref(), - spec.chipset, + spec.chipset(), ) .inspect(|falcon| falcon.clear_swgen0_intr(bar))?, - sec2_falcon: Falcon::new(pdev.as_ref(), spec.chipset)?, + sec2_falcon: Falcon::new(pdev.as_ref(), spec.chipset())?,
Ok, so you've removed the local variable as per my v8 feedback - now you can also access chipset (the member, not the method - which should not be needed anyway as spec doesn't need to be created in driver.rs) directly, and remove some noise from the diff.
Re: [PATCH v9 05/31] gpu: nova-core: set DMA mask width based on GPU architecture
Quoted 1 line · Alexandre Courbot
On Thu Mar 26, 2026 at 10:38 AM JST, John Hubbard wrote:
...
Quoted 5 lines
Quoted 5 lines
kernel::pci_device_table!(
drivers/gpu/nova-core/driver.rs +0
-0@@ -84,18 +77,15 @@ fn probe(pdev: &pci::Device<Core>, _info: &Self::IdInfo) -> impl PinInit<Self, E pdev.enable_device_mem ()?; pdev.set_master ();
Quoted 15 lines
drivers/gpu/nova-core/driver.rs fn probe(pdev: &pci::Device<Core>, _info: &Self::IdInfo) -> impl PinInit<Self, E · line 85
Quoted 11 lines
drivers/gpu/nova-core/driver.rs +2
-5-// SAFETY: No concurrent DMA allocations or mappings can be made because -// the device is still being probed and therefore isn't being used by -// other threads of execution. -unsafe { pdev.dma_set_mask_and_coherent (DmaMask ::new ::<GPU_DMA_BITS >())? }; -let bar =Arc ::pin_init ( pdev.iomap_region_sized ::<BAR0_SIZE >(0 ,c"nova-core/bar0" ),GFP_KERNEL , )?; +let spec =Spec ::new (pdev.as_ref (), bar.access (pdev.as_ref ())?)?; +dev_info! (pdev,"NVIDIA ({})\n" , spec);Now that we have moved to DMA mask into
Gpu::new, what is the point of creatingspechere? Its sole purpose is to be passed toGpu::new, and that doesn't change by the end of the series.
Agreed. For v10, I've moved Spec creation back inside Gpu::new() where it was before.
The original reason for pulling it into probe() was that the DMA mask lived there (per your v6 feedback about the safety argument). Now that the DMA mask moved into Gpu::new() with a better safety justification, there is no reason for Spec to remain in probe().
...
Quoted 35 lines
Quoted 35 lines
drivers/gpu/nova-core/gpu.rs +10
-7impl Gpu {pub (crate )fn new <'a>( - pdev: &'a pci::Device <device::Bound >, + pdev: &'a pci::Device <device::Core >, devres_bar:Arc <Devres <Bar0 >>, bar: &'aBar0 , + spec:Spec , ) ->impl PinInit <Self ,Error > + 'a { -try_pin_init! (Self { - spec:Spec ::new (pdev.as_ref (), bar).inspect (|spec| { -dev_info! (pdev,"NVIDIA ({})\n" , spec); - })?, +let dma_mask = spec.chipset ().arch ().dma_mask (); +try_pin_init! (Self {// We must wait for GFW_BOOT completion before doing any significant setup on the GPU. _: { +// SAFETY: `Gpu` owns all DMA allocations for this device, and we are +// still constructing it, so no concurrent DMA allocations can exist. +unsafe { pdev.dma_set_mask_and_coherent (dma_mask)? }; + gfw::wait_gfw_boot_completion (bar) .inspect_err (|_|dev_err! (pdev,"GFW boot did not complete\n" ))?; }, - sysmem_flush:SysmemFlush ::register (pdev.as_ref (), bar, spec.chipset)?, + sysmem_flush:SysmemFlush ::register (pdev.as_ref (), bar, spec.chipset ())?, gsp_falcon:Falcon ::new ( pdev.as_ref (), - spec.chipset, + spec.chipset (), ) .inspect (|falcon| falcon.clear_swgen0_intr (bar))?,
Quoted 8 lines
drivers/gpu/nova-core/gpu.rs pub(crate) struct Gpu { · line 334
Quoted 2 lines
drivers/gpu/nova-core/gpu.rs +1
-1- sec2_falcon: Falcon::new(pdev.as_ref(), spec.chipset)?, + sec2_falcon: Falcon::new(pdev.as_ref(), spec.chipset())?,Ok, so you've removed the local variable as per my v8 feedback - now you can also access
chipset(the member, not the method - which should not be needed anyway asspecdoesn't need to be created indriver.rs) directly, and remove some noise from the diff.
Done. With Spec back inside Gpu::new(), the try_pin_init! macro gives direct field access to spec.chipset, so the diff no longer touches those lines at all.
thanks,
Signature · 1 line
John Hubbard
PATCH v9 6/31 gpu: nova-core: Hopper/Blackwell: skip GFW boot waiting
In reply to John HubbardHopper and Blackwell GPUs use FSP-based secure boot and do not require waiting for GFW_BOOT completion. Move the GFW_BOOT wait into a GPU HAL so the decision and the wait both live in the HAL.
Pre-Hopper families (Tu102 HAL) wait for GFW_BOOT completion. Hopper and later (Gh100 HAL) skip it and boot via FSP instead.
--- drivers/gpu/nova-core/gpu.rs | 6 +++-- drivers/gpu/nova-core/gpu/hal.rs | 41 ++++++++++++++++++++++++++++++++ 2 files changed, 45 insertions(+), 2 deletions(-) create mode 100644 drivers/gpu/nova-core/gpu/hal.rs
drivers/gpu/nova-core/gpu.rs +4 -2
@@ -21,11 +21,12 @@ Falcon, // }, fb::SysmemFlush, - gfw, gsp::Gsp, regs, }; +mod hal; +macro_rules! define_chipset { ({ $($variant:ident = $value:expr),* $(,)* }) => {
@@ -311,6 +312,7 @@ pub(crate) fn new<'a>( spec: Spec, ) -> impl PinInit<Self, Error> + 'a {let dma_mask = spec.chipset ().arch ().dma_mask (); +let hal = hal::gpu_hal (spec.chipset ());try_pin_init! (Self {// We must wait for GFW_BOOT completion before doing any significant setup on the GPU.
@@ -319,7 +321,7 @@ pub(crate) fn new<'a>(// still constructing it, so no concurrent DMA allocations can exist. unsafe { pdev.dma_set_mask_and_coherent (dma_mask)? }; - gfw::wait_gfw_boot_completion (bar) + hal.wait_gfw_boot_completion (bar) .inspect_err (|_|dev_err! (pdev,"GFW boot did not complete\n" ))?; },
drivers/gpu/nova-core/gpu/hal.rs new file +41 -0
41 lines not on this page · raw message
Signature · 1 line
2.53.0
Alexandre Courbot
maintainerRe: [PATCH v9 06/31] gpu: nova-core: Hopper/Blackwell: skip GFW boot waiting
Quoted 77 lines · John Hubbard
Hopper and Blackwell GPUs use FSP-based secure boot and do not require waiting for
GFW_BOOTcompletion. Move theGFW_BOOTwait into a GPU HAL so the decision and the wait both live in the HAL.Pre-Hopper families (Tu102 HAL) wait for
GFW_BOOTcompletion. Hopper and later (Gh100 HAL) skip it and boot via FSP instead.Signed-off-by John Hubbard <[email protected]>--- drivers/gpu/nova-core/gpu.rs | 6 +++-- drivers/gpu/nova-core/gpu/hal.rs | 41 ++++++++++++++++++++++++++++++++ 2 files changed, 45 insertions(+), 2 deletions(-) create mode 100644 drivers/gpu/nova-core/gpu/hal.rsdrivers/gpu/nova-core/gpu.rs +4
-2@@ -21,11 +21,12 @@ Falcon, // }, fb::SysmemFlush, - gfw, gsp::Gsp, regs, }; +mod hal; +macro_rules! define_chipset { ({ $($variant:ident = $value:expr),* $(,)* }) => {@@ -311,6 +312,7 @@ pub(crate) fn new<'a>( spec: Spec, ) -> impl PinInit<Self, Error> + 'a {let dma_mask = spec.chipset ().arch ().dma_mask (); +let hal = hal::gpu_hal (spec.chipset ());try_pin_init! (Self {// We must wait for GFW_BOOT completion before doing any significant setup on the GPU. @@ -319,7 +321,7 @@ pub(crate) fn new<'a>(// still constructing it, so no concurrent DMA allocations can exist. unsafe { pdev.dma_set_mask_and_coherent (dma_mask)? }; - gfw::wait_gfw_boot_completion (bar) + hal.wait_gfw_boot_completion (bar) .inspect_err (|_|dev_err! (pdev,"GFW boot did not complete\n" ))?; },drivers/gpu/nova-core/gpu/hal.rs new file +22
-0@@ -0,0 +1,41 @@ +// SPDX-License-Identifier: GPL-2.0 + +use kernel::prelude::*; + +use crate ::{ + driver::Bar0 , + gfw, + gpu::{ +Architecture , +Chipset ,// + }, +}; + +pub (crate )trait GpuHal { +/// Waits for GFW_BOOT completion if required by this hardware family. +fn wait_gfw_boot_completion (&self, bar: &Bar0 ) ->Result ; +} + +struct Tu102 ; +struct Gh100 ; + +impl GpuHal for Tu102 {
drivers/gpu/nova-core/gpu/hal.rs line 32
Quoted 10 lines
drivers/gpu/nova-core/gpu/hal.rs new file +10
-0+fn wait_gfw_boot_completion (&self, bar: &Bar0 ) ->Result { + gfw::wait_gfw_boot_completion (bar) + } +} + +impl GpuHal for Gh100 { +fn wait_gfw_boot_completion (&self, _bar: &Bar0 ) ->Result { +Ok (()) + } +}
Please take a look at how other HALs are implemented: each HAL instance is in its own module. That's not just a cosmetic choice; it allows us to keep the chipset's specific HAL struct and its helpers completely private and forces us to make code-sharing explicit. Furthermore, this particular HAL is bound to grow, so let's split it properly from the start.
If you do that it also makes more sense to use constants (contrary to Gary's feedback on v8), if only to align with the rest of the driver.
Once this is done, making gpu::hal::tu102 absorb the gfw module is trivial, so let's do that while we are at it - having gfw as being driver-wide makes little sense since it has a very limited role for a specific subset of the chips we support.
Gary Guo
reviewerRe: [PATCH v9 06/31] gpu: nova-core: Hopper/Blackwell: skip GFW boot waiting
Quoted 96 lines · Alexandre Courbot
Quoted 77 lines · John Hubbard
Hopper and Blackwell GPUs use FSP-based secure boot and do not require waiting for
GFW_BOOTcompletion. Move theGFW_BOOTwait into a GPU HAL so the decision and the wait both live in the HAL.Pre-Hopper families (Tu102 HAL) wait for
GFW_BOOTcompletion. Hopper and later (Gh100 HAL) skip it and boot via FSP instead.Signed-off-by John Hubbard <[email protected]>--- drivers/gpu/nova-core/gpu.rs | 6 +++-- drivers/gpu/nova-core/gpu/hal.rs | 41 ++++++++++++++++++++++++++++++++ 2 files changed, 45 insertions(+), 2 deletions(-) create mode 100644 drivers/gpu/nova-core/gpu/hal.rsdrivers/gpu/nova-core/gpu.rs +4
-2@@ -21,11 +21,12 @@ Falcon, // }, fb::SysmemFlush, - gfw, gsp::Gsp, regs, }; +mod hal; +macro_rules! define_chipset { ({ $($variant:ident = $value:expr),* $(,)* }) => {@@ -311,6 +312,7 @@ pub(crate) fn new<'a>( spec: Spec, ) -> impl PinInit<Self, Error> + 'a {let dma_mask = spec.chipset ().arch ().dma_mask (); +let hal = hal::gpu_hal (spec.chipset ());try_pin_init! (Self {// We must wait for GFW_BOOT completion before doing any significant setup on the GPU. @@ -319,7 +321,7 @@ pub(crate) fn new<'a>(// still constructing it, so no concurrent DMA allocations can exist. unsafe { pdev.dma_set_mask_and_coherent (dma_mask)? }; - gfw::wait_gfw_boot_completion (bar) + hal.wait_gfw_boot_completion (bar) .inspect_err (|_|dev_err! (pdev,"GFW boot did not complete\n" ))?; },drivers/gpu/nova-core/gpu/hal.rs new file +22
-0@@ -0,0 +1,41 @@ +// SPDX-License-Identifier: GPL-2.0 + +use kernel::prelude::*; + +use crate ::{ + driver::Bar0 , + gfw, + gpu::{ +Architecture , +Chipset ,// + }, +}; + +pub (crate )trait GpuHal { +/// Waits for GFW_BOOT completion if required by this hardware family. +fn wait_gfw_boot_completion (&self, bar: &Bar0 ) ->Result ; +} + +struct Tu102 ; +struct Gh100 ; + +impl GpuHal for Tu102 {drivers/gpu/nova-core/gpu/hal.rs line 32
Quoted 10 lines
drivers/gpu/nova-core/gpu/hal.rs new file +10
-0+fn wait_gfw_boot_completion (&self, bar: &Bar0 ) ->Result { + gfw::wait_gfw_boot_completion (bar) + } +} + +impl GpuHal for Gh100 { +fn wait_gfw_boot_completion (&self, _bar: &Bar0 ) ->Result { +Ok (()) + } +}Please take a look at how other HALs are implemented: each HAL instance is in its own module. That's not just a cosmetic choice; it allows us to keep the chipset's specific HAL struct and its helpers completely private and forces us to make code-sharing explicit. Furthermore, this particular HAL is bound to grow, so let's split it properly from the start.
Quoted 2 lines
If you do that it also makes more sense to use constants (contrary to Gary's feedback on v8), if only to align with the rest of the driver.
The exsiting cases in fb/hal declare the constants without even exposing it (the only use case is to pass it to XXX_HAL.
These looks redundant and should be changed to
pub(super) const GA100_HAL: &dyn FbHal = &Ga100;
etc. instead.
Best,
Gary
Quoted 5 lines
Once this is done, making
gpu::hal::tu102absorb thegfwmodule is trivial, so let's do that while we are at it - havinggfwas being driver-wide makes little sense since it has a very limited role for a specific subset of the chips we support.
Re: [PATCH v9 06/31] gpu: nova-core: Hopper/Blackwell: skip GFW boot waiting
In reply to Alexandre CourbotQuoted 96 lines · Alexandre Courbot
Quoted 77 lines · John Hubbard
Hopper and Blackwell GPUs use FSP-based secure boot and do not require waiting for
GFW_BOOTcompletion. Move theGFW_BOOTwait into a GPU HAL so the decision and the wait both live in the HAL.Pre-Hopper families (Tu102 HAL) wait for
GFW_BOOTcompletion. Hopper and later (Gh100 HAL) skip it and boot via FSP instead.Signed-off-by John Hubbard <[email protected]>--- drivers/gpu/nova-core/gpu.rs | 6 +++-- drivers/gpu/nova-core/gpu/hal.rs | 41 ++++++++++++++++++++++++++++++++ 2 files changed, 45 insertions(+), 2 deletions(-) create mode 100644 drivers/gpu/nova-core/gpu/hal.rsdrivers/gpu/nova-core/gpu.rs +4
-2@@ -21,11 +21,12 @@ Falcon, // }, fb::SysmemFlush, - gfw, gsp::Gsp, regs, }; +mod hal; +macro_rules! define_chipset { ({ $($variant:ident = $value:expr),* $(,)* }) => {@@ -311,6 +312,7 @@ pub(crate) fn new<'a>( spec: Spec, ) -> impl PinInit<Self, Error> + 'a {let dma_mask = spec.chipset ().arch ().dma_mask (); +let hal = hal::gpu_hal (spec.chipset ());try_pin_init! (Self {// We must wait for GFW_BOOT completion before doing any significant setup on the GPU. @@ -319,7 +321,7 @@ pub(crate) fn new<'a>(// still constructing it, so no concurrent DMA allocations can exist. unsafe { pdev.dma_set_mask_and_coherent (dma_mask)? }; - gfw::wait_gfw_boot_completion (bar) + hal.wait_gfw_boot_completion (bar) .inspect_err (|_|dev_err! (pdev,"GFW boot did not complete\n" ))?; },drivers/gpu/nova-core/gpu/hal.rs new file +22
-0@@ -0,0 +1,41 @@ +// SPDX-License-Identifier: GPL-2.0 + +use kernel::prelude::*; + +use crate ::{ + driver::Bar0 , + gfw, + gpu::{ +Architecture , +Chipset ,// + }, +}; + +pub (crate )trait GpuHal { +/// Waits for GFW_BOOT completion if required by this hardware family. +fn wait_gfw_boot_completion (&self, bar: &Bar0 ) ->Result ; +} + +struct Tu102 ; +struct Gh100 ; + +impl GpuHal for Tu102 {drivers/gpu/nova-core/gpu/hal.rs line 32
Quoted 10 lines
drivers/gpu/nova-core/gpu/hal.rs new file +10
-0+fn wait_gfw_boot_completion (&self, bar: &Bar0 ) ->Result { + gfw::wait_gfw_boot_completion (bar) + } +} + +impl GpuHal for Gh100 { +fn wait_gfw_boot_completion (&self, _bar: &Bar0 ) ->Result { +Ok (()) + } +}Please take a look at how other HALs are implemented: each HAL instance is in its own module. That's not just a cosmetic choice; it allows us to keep the chipset's specific HAL struct and its helpers completely private and forces us to make code-sharing explicit. Furthermore, this particular HAL is bound to grow, so let's split it properly from the start.
Quoted 7 lines
If you do that it also makes more sense to use constants (contrary to Gary's feedback on v8), if only to align with the rest of the driver.
Once this is done, making
gpu::hal::tu102absorb thegfwmodule is trivial, so let's do that while we are at it - havinggfwas being driver-wide makes little sense since it has a very limited role for a specific subset of the chips we support.
I feel a HAL might be overkill for this. Looking at the series, this is also the only method. I am doubtful future architectures will have to once again wait for GFW boot (is that expected?).
If not, we can just match or conditional on .arch(). We do that already in other places.
Something like:
if spec.chipset().arch() < Architecture::Hopper {
gfw::wait_gfw_boot_completion(bar)?;}
Thoughts?
thanks,
--
Joel Fernandes
Re: [PATCH v9 06/31] gpu: nova-core: Hopper/Blackwell: skip GFW boot waiting
Quoted 2 lines · Joel Fernandes
Quoted 1 line · Alexandre Courbot
On Thu Mar 26, 2026 at 10:38 AM JST, John Hubbard wrote:
...
Quoted 30 lines
Quoted 30 lines
Quoted 9 lines
drivers/gpu/nova-core/gpu/hal.rs new file +9
-0+pub (crate )trait GpuHal { +/// Waits for GFW_BOOT completion if required by this hardware family. +fn wait_gfw_boot_completion (&self, bar: &Bar0 ) ->Result ; +} + +struct Tu102 ; +struct Gh100 ; + +impl GpuHal for Tu102 {drivers/gpu/nova-core/gpu/hal.rs line 32
Quoted 10 lines
drivers/gpu/nova-core/gpu/hal.rs new file +10
-0+fn wait_gfw_boot_completion (&self, bar: &Bar0 ) ->Result { + gfw::wait_gfw_boot_completion (bar) + } +} + +impl GpuHal for Gh100 { +fn wait_gfw_boot_completion (&self, _bar: &Bar0 ) ->Result { +Ok (()) + } +}Please take a look at how other HALs are implemented: each HAL instance is in its own module. That's not just a cosmetic choice; it allows us to keep the chipset's specific HAL struct and its helpers completely private and forces us to make code-sharing explicit. Furthermore, this particular HAL is bound to grow, so let's split it properly from the start.
If you do that it also makes more sense to use constants (contrary to Gary's feedback on v8), if only to align with the rest of the driver.
Quoted 8 lines
Quoted 4 lines
Once this is done, making
gpu::hal::tu102absorb thegfwmodule is trivial, so let's do that while we are at it - havinggfwas being driver-wide makes little sense since it has a very limited role for a specific subset of the chips we support.I feel a HAL might be overkill for this. Looking at the series, this is also the only method. I am doubtful future architectures will have to once again wait for GFW boot (is that expected?).
Definitely not! We are moving to futurue firmware that does all of its own initialization, without all of these intrusive and fussy steps and interventions from the kernel driver that we are doing today.
Quoted 4 lines
If not, we can just match or conditional on .arch(). We do that already in other places.
Quoted 8 lines
Something like:
if spec.chipset().arch() < Architecture::Hopper { gfw::wait_gfw_boot_completion(bar)?; }Thoughts?
I have a feeling this matches an earlier version of the patchset, actually. :).
I also think a HAL for this tiny aspect is overkill, but I also don't really mind either putting it into a HAL, or not. Because either way the code is readable.
thanks,
John Hubbard
Alexandre Courbot
maintainerRe: [PATCH v9 06/31] gpu: nova-core: Hopper/Blackwell: skip GFW boot waiting
In reply to Joel FernandesQuoted 111 lines · Joel Fernandes
Quoted 96 lines · Alexandre Courbot
Quoted 77 lines · John Hubbard
Hopper and Blackwell GPUs use FSP-based secure boot and do not require waiting for
GFW_BOOTcompletion. Move theGFW_BOOTwait into a GPU HAL so the decision and the wait both live in the HAL.Pre-Hopper families (Tu102 HAL) wait for
GFW_BOOTcompletion. Hopper and later (Gh100 HAL) skip it and boot via FSP instead.Signed-off-by John Hubbard <[email protected]>--- drivers/gpu/nova-core/gpu.rs | 6 +++-- drivers/gpu/nova-core/gpu/hal.rs | 41 ++++++++++++++++++++++++++++++++ 2 files changed, 45 insertions(+), 2 deletions(-) create mode 100644 drivers/gpu/nova-core/gpu/hal.rsdrivers/gpu/nova-core/gpu.rs +4
-2@@ -21,11 +21,12 @@ Falcon, // }, fb::SysmemFlush, - gfw, gsp::Gsp, regs, }; +mod hal; +macro_rules! define_chipset { ({ $($variant:ident = $value:expr),* $(,)* }) => {@@ -311,6 +312,7 @@ pub(crate) fn new<'a>( spec: Spec, ) -> impl PinInit<Self, Error> + 'a {let dma_mask = spec.chipset ().arch ().dma_mask (); +let hal = hal::gpu_hal (spec.chipset ());try_pin_init! (Self {// We must wait for GFW_BOOT completion before doing any significant setup on the GPU. @@ -319,7 +321,7 @@ pub(crate) fn new<'a>(// still constructing it, so no concurrent DMA allocations can exist. unsafe { pdev.dma_set_mask_and_coherent (dma_mask)? }; - gfw::wait_gfw_boot_completion (bar) + hal.wait_gfw_boot_completion (bar) .inspect_err (|_|dev_err! (pdev,"GFW boot did not complete\n" ))?; },drivers/gpu/nova-core/gpu/hal.rs new file +22
-0@@ -0,0 +1,41 @@ +// SPDX-License-Identifier: GPL-2.0 + +use kernel::prelude::*; + +use crate ::{ + driver::Bar0 , + gfw, + gpu::{ +Architecture , +Chipset ,// + }, +}; + +pub (crate )trait GpuHal { +/// Waits for GFW_BOOT completion if required by this hardware family. +fn wait_gfw_boot_completion (&self, bar: &Bar0 ) ->Result ; +} + +struct Tu102 ; +struct Gh100 ; + +impl GpuHal for Tu102 {drivers/gpu/nova-core/gpu/hal.rs line 32
Quoted 10 lines
drivers/gpu/nova-core/gpu/hal.rs new file +10
-0+fn wait_gfw_boot_completion (&self, bar: &Bar0 ) ->Result { + gfw::wait_gfw_boot_completion (bar) + } +} + +impl GpuHal for Gh100 { +fn wait_gfw_boot_completion (&self, _bar: &Bar0 ) ->Result { +Ok (()) + } +}Please take a look at how other HALs are implemented: each HAL instance is in its own module. That's not just a cosmetic choice; it allows us to keep the chipset's specific HAL struct and its helpers completely private and forces us to make code-sharing explicit. Furthermore, this particular HAL is bound to grow, so let's split it properly from the start.
Quoted 7 lines
If you do that it also makes more sense to use constants (contrary to Gary's feedback on v8), if only to align with the rest of the driver.
Once this is done, making
gpu::hal::tu102absorb thegfwmodule is trivial, so let's do that while we are at it - havinggfwas being driver-wide makes little sense since it has a very limited role for a specific subset of the chips we support.I feel a HAL might be overkill for this. Looking at the series, this is also the only method. I am doubtful future architectures will have to once again wait for GFW boot (is that expected?).
Quoted 7 lines
If not, we can just match or conditional on .arch(). We do that already in other places.
Something like:
if spec.chipset().arch() < Architecture::Hopper { gfw::wait_gfw_boot_completion(bar)?;}
It's not about the size, it's whether the code paths diverge enough. In this case they clearly do, and using a HAL lets us get rid of a minor module that was at the root of the project (gfw.rs) entirely.
I expect this HAL to further grow with the different boot paths as well. Not sure if that will happen in this series, but it will eventually.
Re: [PATCH v9 06/31] gpu: nova-core: Hopper/Blackwell: skip GFW boot waiting
Quoted 23 lines · Alexandre Courbot
Quoted 22 lines · Joel Fernandes
Quoted 4 lines · Alexandre Courbot
Please take a look at how other HALs are implemented: each HAL instance is in its own module. That's not just a cosmetic choice; it allows us to keep the chipset's specific HAL struct and its helpers completely private and forces us to make code-sharing explicit. Furthermore, this
Quoted 8 lines
particular HAL is bound to grow, so let's split it properly from the start.
If you do that it also makes more sense to use constants (contrary to Gary's feedback on v8), if only to align with the rest of the driver. Once this is done, makinggpu::hal::tu102absorb thegfwmodule is trivial, so let's do that while we are at it - havinggfwas being driver-wide makes little sense since it has a very limited role for a specific subset of the chips we support.I feel a HAL might be overkill for this. Looking at the series, this is also the only method. I am doubtful future architectures will have to once again wait for GFW boot (is that expected?).
If not, we can just match or conditional on .arch(). We do that already in other places.
Quoted 6 lines
Quoted 4 lines
Something like:
if spec.chipset().arch() < Architecture::Hopper { gfw::wait_gfw_boot_completion(bar)?;}
It's not about the size
Simple things can trivially use match/if on chipset/arch, I just don't see the benefit of a HAL for simple things, and only drawbacks. Even code-wise doing the simple snippet above is simpler and cleaner, no need separate new .rs file.
Even if we look at the HAL approach:
Some one reading the code always thinks that a wait is required but the wait "mechanism" is arch/chipset-specific, not that NO wait is actually required sometimes. ONLY if they look at the HAL implementation will they know that on Hopper+ it is not required.
hal.wait_gfw_boot_completion(bar)
.inspect_err(|_| dev_err!(pdev, "GFW boot did not complete\n"))?;Instead in the snippet above, it is absolutely clear to the reader that Hopper+ does not need to do GFW wait.
Quoted 6 lines
, it's whether the code paths diverge enough. In
this case they clearly do, and using a HAL lets us get rid of a minor module that was at the root of the project (gfw.rs) entirely.I expect this HAL to further grow with the different boot paths as well. Not sure if that will happen in this series, but it will eventually.
But just inlining the module in gpu.rs will also get rid of the module? That's not a strong argument for a HAL. gfw just has one function.
Also, I checked and nouveau does not use HALs for GFW boot.
Other than that, I am concerned about HAL fragmentation (we already have other more specific HALs like the fb HAL and falcon HAL). So should those functionalities also go into gpu HAL? Its not clear.
What about other code doing match on chipset -- should all that also go into this kitchen-sink gpu HAL then? It
needs to be consistent, not "let's put gfw in a HAL because we feel like it even though we know we're never going to ever have to do per-chipset/arch gfw wait." There is not much reason for that as far as I can see.
The argument that the HAL will grow in the future also doesn't hold, since a HAL can be trivially added if and when needed. My understanding is we don't want to add code until we need it and you haven't provided any "future" things that will be added to this new common gpu HAL.
Please keep it simple :). The snippet I shared above is just 3 lines, not new 41 line boiler plate HAL file.
Now if some variant of Blackwell starts doing some custom GFW boot scheme, I am all for a HAL...
thanks,
Signature · 1 line
Joel Fernandes
PATCH v9 7/31 gpu: nova-core: move firmware image parsing code to firmware.rs
In reply to John HubbardUp until now, only the GSP required parsing of its firmware headers. However, upcoming support for Hopper/Blackwell+ adds another firmware image (FMC), along with another format (ELF32).
Therefore, the current ELF64 section parsing support needs to be moved up a level, so that both of the above can use it.
There are no functional changes. This is pure code movement.
--- drivers/gpu/nova-core/firmware.rs | 88 +++++++++++++++++++++++++ drivers/gpu/nova-core/firmware/gsp.rs | 93 ++------------------------- 2 files changed, 94 insertions(+), 87 deletions(-)
drivers/gpu/nova-core/firmware.rs +88 -0
@@ -457,3 +457,91 @@ pub(crate) const fn create( this.0 } } + +/// Ad-hoc and temporary module to extract sections from ELF images. +/// +/// Some firmware images are currently packaged as ELF files, where sections names are used as keys +/// to specific and related bits of data. Future firmware versions are scheduled to move away from +/// that scheme before nova-core becomes stable, which means this module will eventually be +/// removed. +mod elf { +use core::mem::size_of; + +use kernel::{ + bindings, + str::CStr , + transmute::FromBytes ,// + }; + +/// Newtype to provide a [`FromBytes`] implementation. +#[repr(transparent)] +struct Elf64Hdr (bindings::elf64_hdr ); +// SAFETY: all bit patterns are valid for this type, and it doesn't use interior mutability. +unsafe impl FromBytes for Elf64Hdr {} + +#[repr(transparent)] +struct Elf64SHdr (bindings::elf64_shdr ); +// SAFETY: all bit patterns are valid for this type, and it doesn't use interior mutability. +unsafe impl FromBytes for Elf64SHdr {} + +/// Tries to extract section with name `name` from the ELF64 image `elf`, and returns it. +pub (super )fn elf64_section <'a, 'b>(elf: &'a [u8 ], name: &'bstr ) ->Option <&'a [u8 ]> { +let hdr = &elf + .get (0 ..size_of ::<bindings::elf64_hdr >()) + .and_then (Elf64Hdr ::from_bytes)? + .0 ; + +// Get all the section headers. +let mut shdr = { +let shdr_num = usize::from (hdr.e_shnum); +let shdr_start = usize::try_from (hdr.e_shoff).ok ()?; +let shdr_end = shdr_num + .checked_mul (size_of ::<Elf64SHdr >()) + .and_then (|v| v.checked_add (shdr_start))?; + + elf.get (shdr_start..shdr_end) + .map (|slice| slice.chunks_exact (size_of ::<Elf64SHdr >()))? + }; + +// Get the strings table. +let strhdr = shdr + .clone () + .nth (usize::from (hdr.e_shstrndx)) + .and_then (Elf64SHdr ::from_bytes)?; + +// Find the section which name matches `name` and return it. + shdr.find (|&sh| { +let Some (hdr) =Elf64SHdr ::from_bytes (sh)else { +return false ; + }; + +let Some (name_idx) = strhdr + .0 + .sh_offset + .checked_add (u64::from (hdr.0 .sh_name)) + .and_then (|idx| usize::try_from (idx).ok ()) +else { +return false ; + }; + +// Get the start of the name. + elf.get (name_idx..) + .and_then (|nstr|CStr ::from_bytes_until_nul (nstr).ok ()) +// Convert into str. + .and_then (|c_str| c_str.to_str ().ok ()) +// Check that the name matches. + .map (|str| str == name) + .unwrap_or (false ) + }) +// Return the slice containing the section. + .and_then (|sh| { +let hdr =Elf64SHdr ::from_bytes (sh)?; +let start = usize::try_from (hdr.0 .sh_offset).ok ()?; +let end = usize::try_from (hdr.0 .sh_size) + .ok () + .and_then (|sh_size| start.checked_add (sh_size))?; + + elf.get (start..end) + }) + } +}
drivers/gpu/nova-core/firmware/gsp.rs +6 -87
110 lines not on this page · raw message
Signature · 1 line
2.53.0
PATCH v9 8/31 gpu: nova-core: factor out an elf_str() function
In reply to John HubbardFactor out a chunk of complexity into a new subroutine. This is an incremental step in adding ELF32 support to the existing ELF64 section support, for handling GPU firmware.
--- drivers/gpu/nova-core/firmware.rs | 40 ++++++++++++------------------- 1 file changed, 15 insertions(+), 25 deletions(-)
drivers/gpu/nova-core/firmware.rs +15 -25
@@ -484,6 +484,13 @@ unsafe impl FromBytes for Elf64Hdr {}// SAFETY: all bit patterns are valid for this type, and it doesn't use interior mutability. unsafe impl FromBytes for Elf64SHdr {} +/// Returns a NULL-terminated string from the ELF image at `offset`. +fn elf_str (elf: &[u8 ], offset:u64 ) ->Option <&str > { +let idx = usize::try_from (offset).ok ()?; +let bytes = elf.get (idx..)?; +CStr ::from_bytes_until_nul (bytes).ok ()?.to_str ().ok () + } +/// Tries to extract section with name `name` from the ELF64 image `elf`, and returns it. pub (super )fn elf64_section <'a, 'b>(elf: &'a [u8 ], name: &'bstr ) ->Option <&'a [u8 ]> {let hdr = &elf
@@ -510,32 +517,15 @@ pub(super) fn elf64_section<'a, 'b>(elf: &'a [u8], name: &'b str) -> Option<&'a .and_then(Elf64SHdr::from_bytes)?;// Find the section which name matches `name` and return it. - shdr.find (|&sh| { -let Some (hdr) =Elf64SHdr ::from_bytes (sh)else { -return false ; - }; - -let Some (name_idx) = strhdr - .0 - .sh_offset - .checked_add (u64::from (hdr.0 .sh_name)) - .and_then (|idx| usize::try_from (idx).ok ()) -else { -return false ; - }; - -// Get the start of the name. - elf.get (name_idx..) - .and_then (|nstr|CStr ::from_bytes_until_nul (nstr).ok ()) -// Convert into str. - .and_then (|c_str| c_str.to_str ().ok ()) -// Check that the name matches. - .map (|str| str == name) - .unwrap_or (false ) - }) -// Return the slice containing the section. - .and_then (|sh| { + shdr.find_map (|sh| {let hdr =Elf64SHdr ::from_bytes (sh)?; +let name_offset = strhdr.0 .sh_offset.checked_add (u64::from (hdr.0 .sh_name))?; +let section_name =elf_str (elf, name_offset)?; + +if section_name != name { +return None ; + } +let start = usize::try_from (hdr.0 .sh_offset).ok ()?;let end = usize::try_from (hdr.0 .sh_size) .ok ()
Signature · 1 line
2.53.0
PATCH v9 9/31 gpu: nova-core: don't assume 64-bit firmware images
In reply to John HubbardIntroduce a single ELF format abstraction that ties each ELF header type to its matching section-header type. This keeps the shared section parser ready for upcoming ELF32 support and avoids mixing 32-bit and 64-bit ELF layouts by mistake.
--- drivers/gpu/nova-core/firmware.rs | 111 ++++++++++++++++++++++-------- 1 file changed, 84 insertions(+), 27 deletions(-)
drivers/gpu/nova-core/firmware.rs +84 -27
@@ -473,17 +473,72 @@ mod elf { transmute::FromBytes, // }; +/// Trait to abstract over ELF header differences. +trait ElfHeader :FromBytes { +fn shnum (&self) ->u16 ; +fn shoff (&self) ->u64 ; +fn shstrndx (&self) ->u16 ; + } + +/// Trait to abstract over ELF section-header differences. +trait ElfSectionHeader :FromBytes { +fn name (&self) ->u32 ; +fn offset (&self) ->u64 ; +fn size (&self) ->u64 ; + } + +/// Trait describing a matching ELF header and section-header format. +trait ElfFormat { +type Header :ElfHeader ; +type SectionHeader :ElfSectionHeader ; + } +/// Newtype to provide a [`FromBytes`] implementation. #[repr(transparent)] struct Elf64Hdr (bindings::elf64_hdr );// SAFETY: all bit patterns are valid for this type, and it doesn't use interior mutability. unsafe impl FromBytes for Elf64Hdr {} +impl ElfHeader for Elf64Hdr { +fn shnum (&self) ->u16 { + self.0 .e_shnum + } + +fn shoff (&self) ->u64 { + self.0 .e_shoff + } + +fn shstrndx (&self) ->u16 { + self.0 .e_shstrndx + } + } +#[repr(transparent)] struct Elf64SHdr (bindings::elf64_shdr );// SAFETY: all bit patterns are valid for this type, and it doesn't use interior mutability. unsafe impl FromBytes for Elf64SHdr {} +impl ElfSectionHeader for Elf64SHdr { +fn name (&self) ->u32 { + self.0 .sh_name + } + +fn offset (&self) ->u64 { + self.0 .sh_offset + } + +fn size (&self) ->u64 { + self.0 .sh_size + } + } + +struct Elf64Format ; + +impl ElfFormat for Elf64Format { +type Header =Elf64Hdr ; +type SectionHeader =Elf64SHdr ; + } +/// Returns a NULL-terminated string from the ELF image at `offset`. fn elf_str (elf: &[u8 ], offset:u64 ) ->Option <&str > {let idx = usize::try_from (offset).ok ()?;
@@ -491,47 +546,49 @@ fn elf_str(elf: &[u8], offset: u64) -> Option<&str> {CStr ::from_bytes_until_nul (bytes).ok ()?.to_str ().ok () } -/// Tries to extract section with name `name` from the ELF64 image `elf`, and returns it. -pub (super )fn elf64_section <'a, 'b>(elf: &'a [u8 ], name: &'bstr ) ->Option <&'a [u8 ]> { -let hdr = &elf - .get (0 ..size_of ::<bindings::elf64_hdr >()) - .and_then (Elf64Hdr ::from_bytes)? - .0 ; - -// Get all the section headers. -let mut shdr = { -let shdr_num = usize::from (hdr.e_shnum); -let shdr_start = usize::try_from (hdr.e_shoff).ok ()?; -let shdr_end = shdr_num - .checked_mul (size_of ::<Elf64SHdr >()) - .and_then (|v| v.checked_add (shdr_start))?; - - elf.get (shdr_start..shdr_end) - .map (|slice| slice.chunks_exact (size_of ::<Elf64SHdr >()))? - }; +fn elf_section_generic <'a,F >(elf: &'a [u8 ], name: &str ) ->Option <&'a [u8 ]> +where +F :ElfFormat , + { +let hdr =F ::Header ::from_bytes (elf.get (0 ..size_of ::<F ::Header >())?)?; + +let shdr_num = usize::from (hdr.shnum ()); +let shdr_start = usize::try_from (hdr.shoff ()).ok ()?; +let shdr_end = shdr_num + .checked_mul (size_of ::<F ::SectionHeader >()) + .and_then (|v| v.checked_add (shdr_start))?; + +// Get all the section headers as an iterator over byte chunks. +let shdr_bytes = elf.get (shdr_start..shdr_end)?; +let mut shdr_iter = shdr_bytes.chunks_exact (size_of ::<F ::SectionHeader >());// Get the strings table. -let strhdr = shdr +let strhdr = shdr_iter .clone () - .nth (usize::from (hdr.e_shstrndx)) - .and_then (Elf64SHdr ::from_bytes)?; + .nth (usize::from (hdr.shstrndx ())) + .and_then (F ::SectionHeader ::from_bytes)?;// Find the section which name matches `name` and return it. - shdr.find_map (|sh| { -let hdr =Elf64SHdr ::from_bytes (sh)?; -let name_offset = strhdr.0 .sh_offset.checked_add (u64::from (hdr.0 .sh_name))?; + shdr_iter.find_map (|sh_bytes| { +let sh =F ::SectionHeader ::from_bytes (sh_bytes)?; +let name_offset = strhdr.offset ().checked_add (u64::from (sh.name ()))?;let section_name =elf_str (elf, name_offset)?;if section_name != name {return None ; } -let start = usize::try_from (hdr.0 .sh_offset).ok ()?; -let end = usize::try_from (hdr.0 .sh_size) +let start = usize::try_from (sh.offset ()).ok ()?; +let end = usize::try_from (sh.size ()) .ok () - .and_then (|sh_size| start.checked_add (sh_size))?; + .and_then (|sz| start.checked_add (sz))?; elf.get (start..end) }) } + +/// Tries to extract section with name `name` from the ELF64 image `elf`, and returns it. +pub (super )fn elf64_section <'a>(elf: &'a [u8 ], name: &str ) ->Option <&'a [u8 ]> { +elf_section_generic ::<Elf64Format >(elf, name) + } }
Signature · 1 line
2.53.0
PATCH v9 10/31 gpu: nova-core: add support for 32-bit firmware images
In reply to John HubbardAdd ELF32 header and section header newtypes with ElfHeader and ElfSectionHeader trait implementations, mirroring the existing ELF64 support. Add elf32_section() for extracting sections from ELF32 images.
--- drivers/gpu/nova-core/firmware.rs | 53 +++++++++++++++++++++++++++++++ 1 file changed, 53 insertions(+)
drivers/gpu/nova-core/firmware.rs +53 -0
@@ -539,6 +539,53 @@ impl ElfFormat for Elf64Format {type SectionHeader =Elf64SHdr ; } +/// Newtype to provide [`FromBytes`] and [`ElfHeader`] implementations for ELF32. +#[repr(transparent)] +struct Elf32Hdr (bindings::elf32_hdr ); +// SAFETY: all bit patterns are valid for this type, and it doesn't use interior mutability. +unsafe impl FromBytes for Elf32Hdr {} + +impl ElfHeader for Elf32Hdr { +fn shnum (&self) ->u16 { + self.0 .e_shnum + } + +fn shoff (&self) ->u64 { + u64::from (self.0 .e_shoff) + } + +fn shstrndx (&self) ->u16 { + self.0 .e_shstrndx + } + } + +/// Newtype to provide [`FromBytes`] and [`ElfSectionHeader`] implementations for ELF32. +#[repr(transparent)] +struct Elf32SHdr (bindings::elf32_shdr ); +// SAFETY: all bit patterns are valid for this type, and it doesn't use interior mutability. +unsafe impl FromBytes for Elf32SHdr {} + +impl ElfSectionHeader for Elf32SHdr { +fn name (&self) ->u32 { + self.0 .sh_name + } + +fn offset (&self) ->u64 { + u64::from (self.0 .sh_offset) + } + +fn size (&self) ->u64 { + u64::from (self.0 .sh_size) + } + } + +struct Elf32Format ; + +impl ElfFormat for Elf32Format { +type Header =Elf32Hdr ; +type SectionHeader =Elf32SHdr ; + } +/// Returns a NULL-terminated string from the ELF image at `offset`. fn elf_str (elf: &[u8 ], offset:u64 ) ->Option <&str > {let idx = usize::try_from (offset).ok ()?;
@@ -591,4 +638,10 @@ fn elf_section_generic<'a, F>(elf: &'a [u8], name: &str) -> Option<&'a [u8]>pub (super )fn elf64_section <'a>(elf: &'a [u8 ], name: &str ) ->Option <&'a [u8 ]> {elf_section_generic ::<Elf64Format >(elf, name) } + +/// Extract the section with name `name` from the ELF32 image `elf`. +#[expect(dead_code)] +pub (super )fn elf32_section <'a>(elf: &'a [u8 ], name: &str ) ->Option <&'a [u8 ]> { +elf_section_generic ::<Elf32Format >(elf, name) + } }
Signature · 1 line
2.53.0
PATCH v9 11/31 gpu: nova-core: add auto-detection of 32-bit, 64-bit firmware images
In reply to John HubbardAdd elf_section() which automatically detects ELF32 vs ELF64 based on the ELF header's class byte, and dispatches to the appropriate parser. Switch gsp.rs callers from elf64_section() to elf_section(), making both elf32_section() and elf64_section() private.
--- drivers/gpu/nova-core/firmware.rs | 22 ++++++++++++++++++---- drivers/gpu/nova-core/firmware/gsp.rs | 4 ++-- 2 files changed, 20 insertions(+), 6 deletions(-)
drivers/gpu/nova-core/firmware.rs +18 -4
@@ -634,14 +634,28 @@ fn elf_section_generic<'a, F>(elf: &'a [u8], name: &str) -> Option<&'a [u8]> }) } -/// Tries to extract section with name `name` from the ELF64 image `elf`, and returns it. -pub (super )fn elf64_section <'a>(elf: &'a [u8 ], name: &str ) ->Option <&'a [u8 ]> { +/// Extract the section with name `name` from the ELF64 image `elf`. +fn elf64_section <'a>(elf: &'a [u8 ], name: &str ) ->Option <&'a [u8 ]> {elf_section_generic ::<Elf64Format >(elf, name) }/// Extract the section with name `name` from the ELF32 image `elf`. -#[expect(dead_code)] -pub (super )fn elf32_section <'a>(elf: &'a [u8 ], name: &str ) ->Option <&'a [u8 ]> { +fn elf32_section <'a>(elf: &'a [u8 ], name: &str ) ->Option <&'a [u8 ]> {elf_section_generic ::<Elf32Format >(elf, name) } + +/// Automatically detects ELF32 vs ELF64 based on the ELF header. +pub (super )fn elf_section <'a>(elf: &'a [u8 ], name: &str ) ->Option <&'a [u8 ]> { +// Check ELF magic. +if elf.len () <5 || elf.get (0 ..4 )? !=b"\x7fELF" { +return None ; + } + +// Check ELF class: 1 = 32-bit, 2 = 64-bit. +match elf.get (4 )? { +1 =>elf32_section (elf, name), +2 =>elf64_section (elf, name), + _ =>None , + } + } }
drivers/gpu/nova-core/firmware/gsp.rs +2 -2
@@ -91,7 +91,7 @@ pub(crate) fn new<'a>( pin_init::pin_init_scope (move || {let firmware =super ::request_firmware (dev, chipset,"gsp" , ver)?; -let fw_section = elf::elf64_section (firmware.data (),".fwimage" ).ok_or (EINVAL )?; +let fw_section = elf::elf_section (firmware.data (),".fwimage" ).ok_or (EINVAL )?;let size = fw_section.len ();
@@ -148,7 +148,7 @@ pub(crate) fn new<'a>( signatures: { let sigs_section = Self::find_gsp_sigs_section(chipset); - elf::elf64_section (firmware.data (), sigs_section) + elf::elf_section (firmware.data (), sigs_section) .ok_or (EINVAL ) .and_then (|data|DmaObject ::from_data (dev, data))? },
Signature · 1 line
2.53.0
PATCH v9 12/31 gpu: nova-core: Hopper/Blackwell: add FMC firmware image, in support of FSP
In reply to John HubbardFSP is the Falcon that runs FMC firmware on Hopper and Blackwell. Load the FMC ELF in two forms: the image section that FSP boots from, and the full Firmware object for later signature extraction during Chain of Trust verification.
--- drivers/gpu/nova-core/firmware.rs | 1 + drivers/gpu/nova-core/firmware/fsp.rs | 46 +++++++++++++++++++++++++++ 2 files changed, 47 insertions(+) create mode 100644 drivers/gpu/nova-core/firmware/fsp.rs
drivers/gpu/nova-core/firmware.rs +1 -0
@@ -27,6 +27,7 @@ };pub (crate )mod booter; +pub (crate )mod fsp;pub (crate )mod fwsec;pub (crate )mod gsp;pub (crate )mod riscv;
drivers/gpu/nova-core/firmware/fsp.rs new file +46 -0
46 lines not on this page · raw message
Signature · 1 line
2.53.0
PATCH v9 13/31 gpu: nova-core: Hopper/Blackwell: add FSP falcon engine stub
In reply to John HubbardAdd the FSP (Firmware System Processor) falcon engine type that will handle secure boot and Chain of Trust operations on Hopper and Blackwell architectures.
The FSP falcon replaces SEC2's role in the boot sequence for these newer architectures. This initial stub just defines the falcon type and its base address.
--- drivers/gpu/nova-core/falcon.rs | 1 + drivers/gpu/nova-core/falcon/fsp.rs | 30 +++++++++++++++++++++++++++++ 2 files changed, 31 insertions(+) create mode 100644 drivers/gpu/nova-core/falcon/fsp.rs
drivers/gpu/nova-core/falcon.rs +1 -0
@@ -32,6 +32,7 @@ regs::macros::RegisterBase, // }; +pub (crate )mod fsp;pub (crate )mod gsp;mod hal;pub (crate )mod sec2;
drivers/gpu/nova-core/falcon/fsp.rs new file +30 -0
@@ -0,0 +1,30 @@ +// SPDX-License-Identifier: GPL-2.0 + +//! FSP (Firmware System Processor) falcon engine for Hopper/Blackwell GPUs. +//! +//! The FSP falcon handles secure boot and Chain of Trust operations +//! on Hopper and Blackwell architectures, replacing SEC2's role. + +use crate ::{ + falcon::{ +FalconEngine , +PFalcon2Base , +PFalconBase ,// + }, + regs::macros::RegisterBase , +}; + +/// Type specifying the `Fsp` falcon engine. Cannot be instantiated. +pub (crate )struct Fsp (()); + +impl RegisterBase <PFalconBase >for Fsp { +const BASE :usize =0x8f2000 ; +} + +impl RegisterBase <PFalcon2Base >for Fsp { +const BASE :usize =0x8f3000 ; +} + +impl FalconEngine for Fsp { +const ID :Self =Fsp (()); +}
Signature · 1 line
2.53.0
PATCH v9 14/31 gpu: nova-core: Hopper/Blackwell: add FSP falcon EMEM operations
In reply to John HubbardAdd external memory (EMEM) read/write operations to the GPU's FSP falcon engine. These operations use Falcon PIO (Programmed I/O) to communicate with the FSP through indirect memory access.
--- drivers/gpu/nova-core/falcon/fsp.rs | 120 +++++++++++++++++++++++++++- drivers/gpu/nova-core/regs.rs | 12 +++ 2 files changed, 131 insertions(+), 1 deletion(-)
drivers/gpu/nova-core/falcon/fsp.rs +119 -1
@@ -5,13 +5,26 @@//! The FSP falcon handles secure boot and Chain of Trust operations //! on Hopper and Blackwell architectures, replacing SEC2's role. +use kernel::{ + io::{ +Io , +IoCapable ,// + }, + prelude::*,// +}; +use crate ::{ + driver::Bar0 , falcon::{ +Falcon ,FalconEngine ,PFalcon2Base ,PFalconBase ,// }, - regs::macros::RegisterBase , + regs::{ + self, + macros::RegisterBase ,// + }, };/// Type specifying the `Fsp` falcon engine. Cannot be instantiated.
@@ -28,3 +41,108 @@ impl RegisterBase<PFalcon2Base> for Fsp {impl FalconEngine for Fsp {const ID :Self =Fsp (()); } + +/// Maximum addressable EMEM size, derived from the 24-bit offset field +/// in NV_PFALCON_FALCON_EMEM_CTL. +const EMEM_MAX_SIZE :usize =1 <<24 ; + +/// I/O backend for the FSP falcon's external memory (EMEM). +/// +/// Each 32-bit access programs a byte offset via the EMEM_CTL register, +/// then reads or writes through the EMEM_DATA register. +pub (crate )struct Emem <'a> { + bar: &'aBar0 , +} + +impl <'a>Emem <'a> { +fn new (bar: &'aBar0 ) ->Self { +Self { bar } + } +} + +impl IoCapable <u32 >for Emem <'_> { +unsafe fn io_read (&self, address:usize ) ->u32 { +// The Io trait validates that EMEM accesses fit within the 24-bit offset field. +let offset = addressas u32 ; + + regs::NV_PFALCON_FALCON_EMEM_CTL ::default () + .set_rd_mode (true ) + .set_offset (offset) + .write (self.bar, &Fsp ::ID ); + + regs::NV_PFALCON_FALCON_EMEM_DATA ::read (self.bar, &Fsp ::ID ).data () + } + +unsafe fn io_write (&self, value:u32 , address:usize ) { +// The Io trait validates that EMEM accesses fit within the 24-bit offset field. +let offset = addressas u32 ; + + regs::NV_PFALCON_FALCON_EMEM_CTL ::default () + .set_wr_mode (true ) + .set_offset (offset) + .write (self.bar, &Fsp ::ID ); + + regs::NV_PFALCON_FALCON_EMEM_DATA ::default () + .set_data (value) + .write (self.bar, &Fsp ::ID ); + } +} + +impl Io for Emem <'_> { +fn addr (&self) ->usize { +0 + } + +fn maxsize (&self) ->usize { +EMEM_MAX_SIZE + } +} + +impl Falcon <Fsp > { +/// Returns an EMEM I/O accessor for this FSP falcon. +pub (crate )fn emem <'a>(&self, bar: &'aBar0 ) ->Emem <'a> { +Emem ::new (bar) + } + +/// Writes `data` to FSP external memory at byte `offset`. +/// +/// Data is interpreted as little-endian 32-bit words. +/// Returns `EINVAL` if offset or data length is not 4-byte aligned. +#[expect(unused)] +pub (crate )fn write_emem (&self, bar: &Bar0 , offset:u32 , data: &[u8 ]) ->Result { +if offset %4 !=0 || data.len () %4 !=0 { +return Err (EINVAL ); + } + +let emem = self.emem (bar); +let mut off = offsetas usize ; +for chunkin data.chunks_exact (4 ) { +let word = u32::from_le_bytes ([chunk[0 ], chunk[1 ], chunk[2 ], chunk[3 ]]); + emem.try_write32 (word, off)?; + off +=4 ; + } + +Ok (()) + } + +/// Reads FSP external memory at byte `offset` into `data`. +/// +/// Data is stored as little-endian 32-bit words. +/// Returns `EINVAL` if offset or data length is not 4-byte aligned. +#[expect(unused)] +pub (crate )fn read_emem (&self, bar: &Bar0 , offset:u32 , data: &mut [u8 ]) ->Result { +if offset %4 !=0 || data.len () %4 !=0 { +return Err (EINVAL ); + } + +let emem = self.emem (bar); +let mut off = offsetas usize ; +for chunkin data.chunks_exact_mut (4 ) { +let word = emem.try_read32 (off)?; + chunk.copy_from_slice (&word.to_le_bytes ()); + off +=4 ; + } + +Ok (()) + } +}
drivers/gpu/nova-core/regs.rs +12 -0
@@ -461,6 +461,18 @@ pub(crate) fn reset_engine<E: FalconEngine>(bar: &Bar0) { 8:8 br_fetch as bool; }); +// Falcon EMEM PIO registers (used by FSP on Hopper/Blackwell). +// These provide the falcon external memory communication interface. +register! (NV_PFALCON_FALCON_EMEM_CTL @PFalconBase [0x00000ac0 ] { +23 :0 offsetas u32 ;// EMEM byte offset (must be 4-byte aligned) +24 :24 wr_modeas bool ;// Write mode +25 :25 rd_modeas bool ;// Read mode +}); + +register! (NV_PFALCON_FALCON_EMEM_DATA @PFalconBase [0x00000ac4 ] { +31 :0 dataas u32 ;// EMEM data register +}); +// The modules below provide registers that are not identical on all supported chips. They should // only be used in HAL modules.
Signature · 1 line
2.53.0
PATCH v9 15/31 gpu: nova-core: Hopper/Blackwell: add FSP message infrastructure
In reply to John HubbardAdd the FSP messaging infrastructure needed for Chain of Trust communication on Hopper/Blackwell GPUs.
--- drivers/gpu/nova-core/falcon/fsp.rs | 79 ++++++++++++++++++++++++++++- drivers/gpu/nova-core/regs.rs | 18 +++++++ 2 files changed, 95 insertions(+), 2 deletions(-)
drivers/gpu/nova-core/falcon/fsp.rs +77 -2
@@ -108,7 +108,6 @@ pub(crate) fn emem<'a>(&self, bar: &'a Bar0) -> Emem<'a> {/// /// Data is interpreted as little-endian 32-bit words. /// Returns `EINVAL` if offset or data length is not 4-byte aligned. -#[expect(unused)] pub (crate )fn write_emem (&self, bar: &Bar0 , offset:u32 , data: &[u8 ]) ->Result {if offset %4 !=0 || data.len () %4 !=0 {return Err (EINVAL );
@@ -129,7 +128,6 @@ pub(crate) fn write_emem(&self, bar: &Bar0, offset: u32, data: &[u8]) -> Result/// /// Data is stored as little-endian 32-bit words. /// Returns `EINVAL` if offset or data length is not 4-byte aligned. -#[expect(unused)] pub (crate )fn read_emem (&self, bar: &Bar0 , offset:u32 , data: &mut [u8 ]) ->Result {if offset %4 !=0 || data.len () %4 !=0 {return Err (EINVAL );
@@ -145,4 +143,81 @@ pub(crate) fn read_emem(&self, bar: &Bar0, offset: u32, data: &mut [u8]) -> ResuOk (()) } + +/// Poll FSP for incoming data. +/// +/// Returns the size of available data in bytes, or 0 if no data is available. +/// +/// The FSP message queue is not circular - pointers are reset to 0 after each +/// message exchange, so `tail >= head` is always true when data is present. +#[expect(unused)] +pub (crate )fn poll_msgq (&self, bar: &Bar0 ) ->u32 { +let head = regs::NV_PFSP_MSGQ_HEAD ::read (bar).address (); +let tail = regs::NV_PFSP_MSGQ_TAIL ::read (bar).address (); + +if head == tail { +return 0 ; + } + +// TAIL points at last DWORD written, so add 4 to get total size + tail.saturating_sub (head) +4 + } + +/// Send message to FSP. +/// +/// Writes a message to FSP EMEM and updates queue pointers to notify FSP. +/// +/// # Arguments +/// * `bar` - BAR0 memory mapping +/// * `packet` - Message data (must be 4-byte aligned in length) +/// +/// # Returns +/// `Ok(())` on success, `Err(EINVAL)` if packet is empty or not 4-byte aligned +#[expect(unused)] +pub (crate )fn send_msg (&self, bar: &Bar0 , packet: &[u8 ]) ->Result { +if packet.is_empty () { +return Err (EINVAL ); + } + +// Write message to EMEM at offset 0 (validates 4-byte alignment) + self.write_emem (bar,0 , packet)?; + +// Update queue pointers - TAIL points at last DWORD written +let tail_offset = u32::try_from (packet.len () -4 ).map_err (|_|EINVAL )?; + regs::NV_PFSP_QUEUE_TAIL ::default () + .set_address (tail_offset) + .write (bar); + regs::NV_PFSP_QUEUE_HEAD ::default () + .set_address (0 ) + .write (bar); + +Ok (()) + } + +/// Receive message from FSP. +/// +/// Reads a message from FSP EMEM and resets queue pointers. +/// +/// # Arguments +/// * `bar` - BAR0 memory mapping +/// * `buffer` - Buffer to receive message data +/// * `size` - Size of message to read in bytes (from `poll_msgq`) +/// +/// # Returns +/// `Ok(bytes_read)` on success, `Err(EINVAL)` if size is 0, exceeds buffer, or not aligned +#[expect(unused)] +pub (crate )fn recv_msg (&self, bar: &Bar0 , buffer: &mut [u8 ], size:usize ) ->Result <usize > { +if size ==0 || size > buffer.len () { +return Err (EINVAL ); + } + +// Read response from EMEM at offset 0 (validates 4-byte alignment) + self.read_emem (bar,0 , &mut buffer[..size])?; + +// Reset message queue pointers after reading + regs::NV_PFSP_MSGQ_TAIL ::default ().set_address (0 ).write (bar); + regs::NV_PFSP_MSGQ_HEAD ::default ().set_address (0 ).write (bar); + +Ok (size) + } }
drivers/gpu/nova-core/regs.rs +18 -0
@@ -473,6 +473,24 @@ pub(crate) fn reset_engine<E: FalconEngine>(bar: &Bar0) { 31:0 data as u32; // EMEM data register }); +// FSP (Firmware System Processor) queue registers for Hopper/Blackwell Chain of Trust +// These registers manage falcon EMEM communication queues +register! (NV_PFSP_QUEUE_HEAD @0x008f2c00 { +31 :0 addressas u32 ; +}); + +register! (NV_PFSP_QUEUE_TAIL @0x008f2c04 { +31 :0 addressas u32 ; +}); + +register! (NV_PFSP_MSGQ_HEAD @0x008f2c80 { +31 :0 addressas u32 ; +}); + +register! (NV_PFSP_MSGQ_TAIL @0x008f2c84 { +31 :0 addressas u32 ; +}); +// The modules below provide registers that are not identical on all supported chips. They should // only be used in HAL modules.
Signature · 1 line
2.53.0
PATCH v9 16/31 rust: ptr: add const_align_up()
In reply to John HubbardAdd const_align_up() to kernel::ptr as the const-compatible equivalent of Alignable::align_up().
--- rust/kernel/ptr.rs | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+)
rust/kernel/ptr.rs +24 -0
@@ -253,3 +253,27 @@ fn size(p: *const Self) -> usize { p.len () *size_of ::<T >() } } + +/// Aligns `value` up to `align`. +/// +/// This is the const-compatible equivalent of [`Alignable::align_up`]. +/// +/// Returns [`None`] on overflow. +/// +/// # Examples +/// +/// ``` +/// use kernel::ptr::{const_align_up, Alignment}; +/// use kernel::sizes::SZ_4K; +/// +/// assert_eq!(const_align_up(0x4f, Alignment::new::<16>()), Some(0x50)); +/// assert_eq!(const_align_up(0x40, Alignment::new::<16>()), Some(0x40)); +/// assert_eq!(const_align_up(1, Alignment::new::<SZ_4K>()), Some(SZ_4K)); +/// ``` +#[inline(always)] +pub const fn const_align_up (value:usize , align:Alignment ) ->Option <usize > { +match value.checked_add (align.as_usize () -1 ) { +Some (v) =>Some (v & align.mask ()), +None =>None , + } +}
Signature · 1 line
2.53.0
Re: [PATCH v9 16/31] rust: ptr: add const_align_up()
Quoted 10 lines · John Hubbard
Add
const_align_up()tokernel::ptras the const-compatible equivalent ofAlignable::align_up().Suggested-by Danilo Krummrich <[email protected]>Suggested-by Gary Guo <[email protected]>Suggested-by Miguel Ojeda <[email protected]>Reviewed-by Alice Ryhl <[email protected]>Reviewed-by Gary Guo <[email protected]>Signed-off-by John Hubbard <[email protected]>
Cheers,
Miguel
Re: [PATCH v9 16/31] rust: ptr: add const_align_up()
Quoted 5 lines · Miguel Ojeda
Quoted 4 lines · John Hubbard
Add
const_align_up()tokernel::ptras the const-compatible equivalent ofAlignable::align_up().
Quoted 9 lines
Quoted 6 lines
Suggested-by Danilo Krummrich <[email protected]>Suggested-by Gary Guo <[email protected]>Suggested-by Miguel Ojeda <[email protected]>Reviewed-by Alice Ryhl <[email protected]>Reviewed-by Gary Guo <[email protected]>Signed-off-by John Hubbard <[email protected]>Acked-by Miguel Ojeda <[email protected]>
I probably should ask this out loud, just to be sure: is this patch on track to get merged though one of the various rust-* repositories? Or more to the point, is there anything I can do to help here?
thanks,
Signature · 1 line
John Hubbard
Re: [PATCH v9 16/31] rust: ptr: add const_align_up()
Quoted 5 lines · John Hubbard
I probably should ask this out loud, just to be sure: is this patch on track to get merged though one of the various rust-* repositories? Or more to the point, is there anything I can do to help here?
Since it is in a series that uses it in later patches, the usual assumption is that it is meant to land together. That is why I provided the Acked-by, i.e. so that it can be merged elsewhere.
But if you want me to pick it up this cycle instead (e.g. perhaps because you don't intend to land the series this cycle and you would prefer to have one less patch to worry about), then I am happy to do that too, yeah.
(Sometimes we avoid that if the users are unlikely to land etc., i.e. the usual no dead code rule, but this series seems like it will land and the patch contains a general enough tool.)
Up to you!
I hope that clarifies.
Cheers,
Miguel
Alexandre Courbot
maintainerRe: [PATCH v9 16/31] rust: ptr: add const_align_up()
Quoted 11 lines · Miguel Ojeda
Quoted 5 lines · John Hubbard
I probably should ask this out loud, just to be sure: is this patch on track to get merged though one of the various rust-* repositories? Or more to the point, is there anything I can do to help here?
Since it is in a series that uses it in later patches, the usual assumption is that it is meant to land together. That is why I provided the Acked-by, i.e. so that it can be merged elsewhere.
Quoted 8 lines
But if you want me to pick it up this cycle instead (e.g. perhaps because you don't intend to land the series this cycle and you would prefer to have one less patch to worry about), then I am happy to do that too, yeah.
(Sometimes we avoid that if the users are unlikely to land etc., i.e. the usual no dead code rule, but this series seems like it will land and the patch contains a general enough tool.)
The series won't land this cycle (but is the priority for the next one), and this patch is clearly an outlier as it belongs in the kernel crate, so it looks like a good candidate for you to pick if you don't mind the temporary dead code. Aligning constants up is a common operation that is worth making available early IMHO. :)
Re: [PATCH v9 16/31] rust: ptr: add const_align_up()
Quoted 6 lines · Alexandre Courbot
The series won't land this cycle (but is the priority for the next one), and this patch is clearly an outlier as it belongs in the kernel crate, so it looks like a good candidate for you to pick if you don't mind the temporary dead code. Aligning constants up is a common operation that is worth making available early IMHO. :)
Sounds good!
Cheers,
Miguel
Re: [PATCH v9 16/31] rust: ptr: add const_align_up()
In reply to John HubbardQuoted 22 lines · John Hubbard
Add
const_align_up()tokernel::ptras the const-compatible equivalent ofAlignable::align_up().Suggested-by Danilo Krummrich <[email protected]>Suggested-by Gary Guo <[email protected]>Suggested-by Miguel Ojeda <[email protected]>Reviewed-by Alice Ryhl <[email protected]>Reviewed-by Gary Guo <[email protected]>Signed-off-by John Hubbard <[email protected]>--- rust/kernel/ptr.rs | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+)rust/kernel/ptr.rs +1
-0@@ -253,3 +253,27 @@ fn size(p: *const Self) -> usize { p.len () *size_of ::<T >() } } +
rust/kernel/ptr.rs fn size(p: *const Self) -> usize { · line 266
Quoted 10 lines
rust/kernel/ptr.rs +10
-0+/// Aligns `value` up to `align`. +/// +/// This is the const-compatible equivalent of [`Alignable::align_up`]. +/// +/// Returns [`None`] on overflow. +/// +/// # Examples +/// +/// ``` +/// use kernel::ptr::{const_align_up, Alignment};
IIUC we use the one-import-per-line style (minus the unneeded //) in examples as well (I suppose this can be fixed when applying).
Re: [PATCH v9 16/31] rust: ptr: add const_align_up()
Quoted 1 line · Alexandre Courbot
On Thu Mar 26, 2026 at 10:38 AM JST, John Hubbard wrote:
...
Quoted 5 lines
Quoted 5 lines
rust/kernel/ptr.rs +5
-0+/// Aligns `value` up to `align`. +/// +/// This is the const-compatible equivalent of [`Alignable::align_up`]. +/// +/// Returns [`None`] on overflow.
Quoted 9 lines
rust/kernel/ptr.rs fn size(p: *const Self) -> usize { · line 266
Quoted 5 lines
rust/kernel/ptr.rs +5
-0+/// +/// # Examples +/// +/// ``` +/// use kernel::ptr::{const_align_up, Alignment}; IIUC we use the one-import-per-line style (minus the unneeded
//) in examples as well (I suppose this can be fixed when applying).
Actually no, it's the opposite! Rust for Linux code overwhelmingly (I counted ~200 cases) prefers the "put it all in one line" style, in examples.
In fact, I did both grep and AI-powered searches, and failed to find even a single example of the one-import-per-line style in doc comment examples.
Quoted 1 line
Reviewed-by Alexandre Courbot <[email protected]>
Thanks for the review!
thanks,
Signature · 1 line
John Hubbard
Re: [PATCH v9 16/31] rust: ptr: add const_align_up()
Quoted 8 lines · John Hubbard
Actually no, it's the opposite! Rust for Linux code overwhelmingly (I counted ~200 cases) prefers the "put it all in one line" style, in examples.
In fact, I did both grep and AI-powered searches, and failed to find even a single example of the one-import-per-line style in doc comment examples.
Yeah, it is because it is not decided -- Andreas, for instance, had a case a month ago where there were many imports for a particular example, so it would take a lot of lines (if not hidden) and, in principle, merge conflicts shouldn't be an issue that often there:
https://lore.kernel.org/rust-for-linux/[email protected]/
On the other hand, consistency is good (and simpler to not to remember different rules depending on the context etc.).
Thoughts/feedback on the matter would be nice to have -- thanks!
Cheers,
Miguel
Danilo Krummrich
maintainerRe: [PATCH v9 16/31] rust: ptr: add const_align_up()
Quoted 1 line · Miguel Ojeda
Thoughts/feedback on the matter would be nice to have -- thanks!
For the stuff I maintain I generally tell people to follow the kernel import style in examples as well. Especially when the imports are part of the example, as it would be teaching people the wrong thing otherwise.
I.e. it would be a bit odd if an example illustrates the wrong thing.
If they are hidden it depends a bit, and for some cases, like the one you mentioned, it might make sense to keep it concise.
But in the case of this patch the imports are part of the example (i.e. not hidden), so they should follow the usual kernel rules.
Re: [PATCH v9 16/31] rust: ptr: add const_align_up()
Quoted 5 lines · Danilo Krummrich
For the stuff I maintain I generally tell people to follow the kernel import style in examples as well. Especially when the imports are part of the example, as it would be teaching people the wrong thing otherwise.
Quoted 7 lines
I.e. it would be a bit odd if an example illustrates the wrong thing.
If they are hidden it depends a bit, and for some cases, like the one you mentioned, it might make sense to keep it concise.
But in the case of this patch the imports are part of the example (i.e. not hidden), so they should follow the usual kernel rules.
Thanks for the feedback!
For context for others: we also talked about it in one of the Rust for Linux calls, and for now, at least for visible (i.e. non-hidden with #) imports, we will follow the usual style.
So adjusted in the patch.
Cheers,
Miguel
Re: [PATCH v9 16/31] rust: ptr: add const_align_up()
In reply to John HubbardQuoted 10 lines · John Hubbard
Add
const_align_up()tokernel::ptras the const-compatible equivalent ofAlignable::align_up().Suggested-by Danilo Krummrich <[email protected]>Suggested-by Gary Guo <[email protected]>Suggested-by Miguel Ojeda <[email protected]>Reviewed-by Alice Ryhl <[email protected]>Reviewed-by Gary Guo <[email protected]>Signed-off-by John Hubbard <[email protected]>
Applied (just this one) to rust-next -- thanks everyone!
[ Adjusted imports style. - Miguel ]
Cheers,
Miguel
PATCH v9 17/31 gpu: nova-core: Hopper/Blackwell: calculate reserved FB heap size
In reply to John HubbardVarious "reserved" areas of FB (frame buffer: vidmem) have to be calculated, because the GSP booting process needs this information.
PMU_RESERVED_SIZE is computed at compile time using const_align_up(). The total reserved size is computed at runtime using Alignable::align_up because it depends on the heap layout.
--- drivers/gpu/nova-core/fb.rs | 8 ++++++++ drivers/gpu/nova-core/gsp/fw.rs | 6 +++++- 2 files changed, 13 insertions(+), 1 deletion(-)
drivers/gpu/nova-core/fb.rs +8 -0
@@ -10,6 +10,7 @@ fmt, prelude::*, ptr::{ + const_align_up,Alignable ,Alignment ,// },
@@ -270,3 +271,10 @@ pub(crate) fn new(chipset: Chipset, bar: &Bar0, gsp_fw: &GspFirmware) -> Result< }) } } + +/// PMU reserved size, aligned to 128KB. +pub (crate )const PMU_RESERVED_SIZE :u32 = +match const_align_up (SZ_8M +SZ_16M +SZ_4K ,Alignment ::new ::<SZ_128K >()) { +Some (v) => vas u32 , +None =>panic! ("PMU_RESERVED_SIZE: alignment overflow" ), + };
drivers/gpu/nova-core/gsp/fw.rs +5 -1
@@ -27,7 +27,10 @@ };use crate ::{ - fb::FbLayout , + fb::{ +FbLayout , +PMU_RESERVED_SIZE ,// + }, firmware::gsp::GspFirmware , gpu::Chipset , gsp::{
@@ -246,6 +249,7 @@ pub(crate) fn new<'a>( fbSize: fb_layout.fb.end - fb_layout.fb.start, vgaWorkspaceOffset: fb_layout.vga_workspace.start, vgaWorkspaceSize: fb_layout.vga_workspace.end - fb_layout.vga_workspace.start, + pmuReservedSize: PMU_RESERVED_SIZE, ..Zeroable ::init_zeroed () });
Signature · 1 line
2.53.0
Alexandre Courbot
maintainerRe: [PATCH v9 17/31] gpu: nova-core: Hopper/Blackwell: calculate reserved FB heap size
Quoted 8 lines · John Hubbard
Various "reserved" areas of FB (frame buffer: vidmem) have to be calculated, because the GSP booting process needs this information.
PMU_RESERVED_SIZEis computed at compile time usingconst_align_up(). The total reserved size is computed at runtime usingAlignable::align_upbecause it depends on the heap layout.Signed-off-by John Hubbard <[email protected]>
Is this Blackwell-specific? Because it seems to be done unconditionally, contrary to what the title says.
Quoted 18 lines
--- drivers/gpu/nova-core/fb.rs | 8 ++++++++ drivers/gpu/nova-core/gsp/fw.rs | 6 +++++- 2 files changed, 13 insertions(+), 1 deletion(-)drivers/gpu/nova-core/fb.rs +1
-0@@ -10,6 +10,7 @@ fmt, prelude::*, ptr::{ + const_align_up,Alignable ,Alignment ,// },
drivers/gpu/nova-core/fb.rs pub(crate) fn new(chipset: Chipset, bar: &Bar0, gsp_fw: &GspFirmware) -> Result< · line 280
Quoted 10 lines
drivers/gpu/nova-core/fb.rs +7
-0@@ -270,3 +271,10 @@ pub(crate) fn new(chipset: Chipset, bar: &Bar0, gsp_fw: &GspFirmware) -> Result< }) } } + +/// PMU reserved size, aligned to 128KB. +pub (crate )const PMU_RESERVED_SIZE :u32 = +match const_align_up (SZ_8M +SZ_16M +SZ_4K ,Alignment ::new ::<SZ_128K >()) { +Some (v) => vas u32 , +None =>panic! ("PMU_RESERVED_SIZE: alignment overflow" ), + };
I had hoped we could use unwrap(), but it is only stable in a const block from 1.83. Maybe we can revisit once is MSRV is bumped.
Meanwhile, we can replace the as u32 with usize_into_u32 from Nova's num module.
Re: [PATCH v9 17/31] gpu: nova-core: Hopper/Blackwell: calculate reserved FB heap size
Quoted 4 lines · Alexandre Courbot
Quoted 3 lines · John Hubbard
Various "reserved" areas of FB (frame buffer: vidmem) have to be calculated, because the GSP booting process needs this information.
Quoted 8 lines
Quoted 5 lines
PMU_RESERVED_SIZEis computed at compile time usingconst_align_up(). The total reserved size is computed at runtime usingAlignable::align_upbecause it depends on the heap layout.Signed-off-by John Hubbard <[email protected]>Is this Blackwell-specific? Because it seems to be done unconditionally, contrary to what the title says.
Let me work through this again. Blackwell wouldn't boot without this, but I am not sure that unconditional changes are what I intended.
Some of my rebases have been rather violent, and I may have lost a conditional clause somewhere along the way. I'll check.
Quoted 33 lines
Quoted 19 lines
--- drivers/gpu/nova-core/fb.rs | 8 ++++++++ drivers/gpu/nova-core/gsp/fw.rs | 6 +++++- 2 files changed, 13 insertions(+), 1 deletion(-)drivers/gpu/nova-core/fb.rs +1
-0@@ -10,6 +10,7 @@ fmt, prelude::*, ptr::{ + const_align_up,Alignable ,Alignment ,// },drivers/gpu/nova-core/fb.rs pub(crate) fn new(chipset: Chipset, bar: &Bar0, gsp_fw: &GspFirmware) -> Result< · line 280
Quoted 10 lines
drivers/gpu/nova-core/fb.rs +7
-0@@ -270,3 +271,10 @@ pub(crate) fn new(chipset: Chipset, bar: &Bar0, gsp_fw: &GspFirmware) -> Result< }) } } + +/// PMU reserved size, aligned to 128KB. +pub (crate )const PMU_RESERVED_SIZE :u32 = +match const_align_up (SZ_8M +SZ_16M +SZ_4K ,Alignment ::new ::<SZ_128K >()) { +Some (v) => vas u32 , +None =>panic! ("PMU_RESERVED_SIZE: alignment overflow" ), + };I had hoped we could use
unwrap(), but it is only stable in a const block from 1.83. Maybe we can revisit once is MSRV is bumped.
Quoted 2 lines
Meanwhile, we can replace the
as u32withusize_into_u32from Nova'snummodule.
OK. And in fact, SizeConstants may help, I'll check.
thanks,
Signature · 1 line
John Hubbard
PATCH v9 18/31 gpu: nova-core: add MCTP/NVDM protocol types for firmware communication
In reply to John HubbardAdd the MCTP (Management Component Transport Protocol) and NVDM (NVIDIA Device Management) wire-format types used for communication between the kernel driver and GPU firmware processors.
This includes typed MCTP transport headers, NVDM message headers, and NVDM message type identifiers. Both the FSP boot path and the upcoming GSP RPC message queue share this protocol layer.
--- drivers/gpu/nova-core/mctp.rs | 126 +++++++++++++++++++++++++++++ drivers/gpu/nova-core/nova_core.rs | 1 + 2 files changed, 127 insertions(+) create mode 100644 drivers/gpu/nova-core/mctp.rs
drivers/gpu/nova-core/mctp.rs new file +126 -0
@@ -0,0 +1,126 @@ +// SPDX-License-Identifier: GPL-2.0 + +//! MCTP/NVDM protocol types for NVIDIA GPU firmware communication. +//! +//! MCTP (Management Component Transport Protocol) carries NVDM (NVIDIA +//! Device Management) messages between the kernel driver and GPU firmware +//! processors such as FSP and GSP. + +#![expect(dead_code)] + +/// NVDM message type identifiers carried over MCTP. +#[derive( Debug , Clone , Copy , PartialEq , Eq )] +#[repr( u8 )] +pub (crate )enum NvdmType { +/// Chain of Trust boot message. +Cot =0x14 , +/// FSP command response. +FspResponse =0x15 , +} + +impl TryFrom <u8 >for NvdmType { +type Error =u8 ; + +fn try_from (value:u8 ) ->Result <Self ,Self ::Error > { +match value { + xif x ==Self ::Cot as u8 =>Ok (Self ::Cot ), + xif x ==Self ::FspResponse as u8 =>Ok (Self ::FspResponse ), + _ =>Err (value), + } + } +} + +impl From <NvdmType >for u8 { +fn from (value:NvdmType ) ->Self { + valueas u8 + } +} + +bitfield! { +pub (crate )struct MctpHeader (u32 ),"MCTP transport header for NVIDIA firmware messages." { +31 :31 somas bool ,"Start-of-message bit." ; +30 :30 eomas bool ,"End-of-message bit." ; +29 :28 seqas u8 ,"Packet sequence number." ; +23 :16 seidas u8 ,"Source endpoint ID." ; + } +} + +impl MctpHeader { +/// Build a single-packet MCTP header (SOM=1, EOM=1, SEQ=0, SEID=0). +pub (crate )fn single_packet () ->Self { +Self ::default ().set_som (true ).set_eom (true ) + } + +/// Return the raw packed u32. +pub (crate )const fn raw (self) ->u32 { + self.0 + } + +/// Check if this is a complete single-packet message (SOM=1 and EOM=1). +pub (crate )fn is_single_packet (self) ->bool { + self.som () && self.eom () + } +} + +impl From <u32 >for MctpHeader { +fn from (raw:u32 ) ->Self { +Self (raw) + } +} + +/// MCTP message type for PCI vendor-defined messages. +const MSG_TYPE_VENDOR_PCI :u8 =0x7e ; + +/// NVIDIA PCI vendor ID. +const VENDOR_ID_NV :u16 =0x10de ; + +bitfield! { +pub (crate )struct NvdmHeader (u32 ),"NVIDIA Vendor-Defined Message header over MCTP." { +31 :24 raw_nvdm_typeas u8 ,"Raw NVDM message type." ; +23 :8 vendor_idas u16 ,"PCI vendor ID." ; +6 :0 msg_typeas u8 ,"MCTP vendor-defined message type." ; + } +} + +impl NvdmHeader { +/// Build an NVDM header for the given message type. +pub (crate )fn new (nvdm_type:NvdmType ) ->Self { +Self ::default () + .set_msg_type (MSG_TYPE_VENDOR_PCI ) + .set_vendor_id (VENDOR_ID_NV ) + .set_nvdm_type (nvdm_type) + } + +/// Return the raw packed u32. +pub (crate )const fn raw (self) ->u32 { + self.0 + } + +/// Extract the NVDM type field as a typed value. +pub (crate )fn nvdm_type (self) -> core::result::Result <NvdmType ,u8 > { +NvdmType ::try_from (self.raw_nvdm_type ()) + } + +/// Extract the NVDM type field as a raw value. +pub (crate )fn nvdm_type_raw (self) ->u32 { + u32::from (self.raw_nvdm_type ()) + } + +/// Set the NVDM type field from a typed value. +pub (crate )fn set_nvdm_type (self, nvdm_type:NvdmType ) ->Self { + self.set_raw_nvdm_type (u8::from (nvdm_type)) + } + +/// Validate this header against the expected NVIDIA NVDM format and type. +pub (crate )fn validate (self, expected_type:NvdmType ) ->bool { + self.msg_type () ==MSG_TYPE_VENDOR_PCI + && self.vendor_id () ==VENDOR_ID_NV + &&matches! (self.nvdm_type (),Ok (nvdm_type)if nvdm_type == expected_type) + } +} + +impl From <u32 >for NvdmHeader { +fn from (raw:u32 ) ->Self { +Self (raw) + } +}
drivers/gpu/nova-core/nova_core.rs +1 -0
@@ -21,6 +21,7 @@mod gfw;mod gpu;mod gsp; +mod mctp;mod num;mod regs;mod sbuffer;
Signature · 1 line
2.53.0
PATCH v9 19/31 gpu: nova-core: Hopper/Blackwell: add FSP secure boot completion waiting
In reply to John HubbardAdd the FSP (Firmware System Processor) module for Hopper/Blackwell GPUs. These architectures use a simplified firmware boot sequence:
FMC --> FSP --> GSP, with no SEC2 involvement.
This commit adds the ability to wait for FSP secure boot completion by polling the I2CS thermal scratch register until FSP signals success.
--- drivers/gpu/nova-core/fsp.rs | 148 +++++++++++++++++++++++++++++ drivers/gpu/nova-core/nova_core.rs | 1 + drivers/gpu/nova-core/regs.rs | 29 ++++++ 3 files changed, 178 insertions(+) create mode 100644 drivers/gpu/nova-core/fsp.rs
drivers/gpu/nova-core/fsp.rs new file +148 -0
@@ -0,0 +1,148 @@ +// SPDX-License-Identifier: GPL-2.0 + +//! FSP (Firmware System Processor) interface for Hopper/Blackwell GPUs. +//! +//! Hopper/Blackwell use a simplified firmware boot sequence: FMC --> FSP --> GSP. +//! Unlike Turing/Ampere/Ada, there is NO SEC2 (Security Engine 2) usage. +//! FSP handles secure boot directly using FMC firmware + Chain of Trust. + +use kernel::{ + device, + io::poll::read_poll_timeout, + prelude::*, + time::Delta , + transmute::{ +AsBytes , +FromBytes ,// + }, +}; + +use crate ::regs; + +/// FSP secure boot completion timeout in milliseconds. +/// +/// GB20x requires a longer timeout than Hopper/GB10x. +const fn fsp_secure_boot_timeout_ms (arch:crate ::gpu::Architecture ) ->i64 { +match arch { +crate ::gpu::Architecture ::BlackwellGB20x =>5000 , + _ =>4000 , + } +} + +/// GSP FMC initialization parameters. +#[repr( C )] +#[derive( Debug , Clone , Copy , Default )] +struct GspFmcInitParams { +/// CC initialization "registry keys". + regkeys:u32 , +} + +// SAFETY: GspFmcInitParams is a simple C struct with only primitive types. +unsafe impl AsBytes for GspFmcInitParams {} +// SAFETY: All bit patterns are valid for the primitive fields. +unsafe impl FromBytes for GspFmcInitParams {} + +/// GSP ACR (Authenticated Code RAM) boot parameters. +#[repr( C )] +#[derive( Debug , Clone , Copy , Default )] +struct GspAcrBootGspRmParams { +/// Physical memory aperture through which gspRmDescPa is accessed. + target:u32 , +/// Size in bytes of the GSP-RM descriptor structure. + gsp_rm_desc_size:u32 , +/// Physical offset in the target aperture of the GSP-RM descriptor structure. + gsp_rm_desc_offset:u64 , +/// Physical offset in FB to set the start of the WPR containing GSP-RM. + wpr_carveout_offset:u64 , +/// Size in bytes of the WPR containing GSP-RM. + wpr_carveout_size:u32 , +/// Whether to boot GSP-RM or GSP-Proxy through ACR. + b_is_gsp_rm_boot:u32 , +} + +// SAFETY: GspAcrBootGspRmParams is a simple C struct with only primitive types. +unsafe impl AsBytes for GspAcrBootGspRmParams {} +// SAFETY: All bit patterns are valid for the primitive fields. +unsafe impl FromBytes for GspAcrBootGspRmParams {} + +/// GSP RM boot parameters. +#[repr( C )] +#[derive( Debug , Clone , Copy , Default )] +struct GspRmParams { +/// Physical memory aperture through which bootArgsOffset is accessed. + target:u32 , +/// Physical offset in the memory aperture that will be passed to GSP-RM. + boot_args_offset:u64 , +} + +// SAFETY: GspRmParams is a simple C struct with only primitive types. +unsafe impl AsBytes for GspRmParams {} +// SAFETY: All bit patterns are valid for the primitive fields. +unsafe impl FromBytes for GspRmParams {} + +/// GSP SPDM (Security Protocol and Data Model) parameters. +#[repr( C )] +#[derive( Debug , Clone , Copy , Default )] +struct GspSpdmParams { +/// Physical memory aperture through which all addresses are accessed. + target:u32 , +/// Physical offset in the memory aperture where SPDM payload buffer is stored. + payload_buffer_offset:u64 , +/// Size of the above payload buffer. + payload_buffer_size:u32 , +} + +// SAFETY: GspSpdmParams is a simple C struct with only primitive types. +unsafe impl AsBytes for GspSpdmParams {} +// SAFETY: All bit patterns are valid for the primitive fields. +unsafe impl FromBytes for GspSpdmParams {} + +/// Complete GSP FMC boot parameters passed to FSP. +#[repr( C )] +#[derive( Debug , Clone , Copy , Default )] +pub (crate )struct GspFmcBootParams { + init_params:GspFmcInitParams , + boot_gsp_rm_params:GspAcrBootGspRmParams , + gsp_rm_params:GspRmParams , + gsp_spdm_params:GspSpdmParams , +} + +// SAFETY: GspFmcBootParams is composed of C structs with only primitive types. +unsafe impl AsBytes for GspFmcBootParams {} +// SAFETY: All bit patterns are valid for the primitive fields. +unsafe impl FromBytes for GspFmcBootParams {} + +/// FSP interface for Hopper/Blackwell GPUs. +pub (crate )struct Fsp ; + +impl Fsp { +/// Wait for FSP secure boot completion. +/// +/// Polls the thermal scratch register until FSP signals boot completion +/// or timeout occurs. +#[expect(dead_code)] +pub (crate )fn wait_secure_boot ( + dev: &device::Device <device::Bound >, + bar: &crate ::driver::Bar0 , + arch:crate ::gpu::Architecture , + ) ->Result { +debug_assert! ( + regs::read_fsp_boot_complete_status (bar, arch).is_some (), +"wait_secure_boot called on non-FSP architecture" + ); + +let timeout =Delta ::from_millis (fsp_secure_boot_timeout_ms (arch)); + +read_poll_timeout ( + || regs::read_fsp_boot_complete_status (bar, arch).ok_or (ENOTSUPP ), + |&status| status == regs::FSP_BOOT_COMPLETE_SUCCESS , +Delta ::from_millis (10 ), + timeout, + ) + .map_err (|_| { +dev_err! (dev,"FSP secure boot completion timeout\n" ); +ETIMEDOUT + }) + .map (|_| ()) + } +}
drivers/gpu/nova-core/nova_core.rs +1 -0
@@ -18,6 +18,7 @@mod falcon;mod fb;mod firmware; +mod fsp;mod gfw;mod gpu;mod gsp;
drivers/gpu/nova-core/regs.rs +29 -0
@@ -8,6 +8,7 @@pub (crate )mod macros;use kernel::{ + io::Io , prelude::*, time,// };
@@ -491,6 +492,34 @@ pub(crate) fn reset_engine<E: FalconEngine>(bar: &Bar0) { 31:0 address as u32; }); +// PTHERM registers + +// FSP secure boot completion status register used by FSP to signal boot completion. +// This is the NV_THERM_I2CS_SCRATCH register. +// Different architectures use different addresses: +// - Hopper (GH100) and Blackwell GB10x: 0x000200bc +// - Blackwell GB20x: 0x00ad00bc +pub (crate )fn fsp_thermal_scratch_reg_addr (arch:Architecture ) ->Result <usize > { +match arch { +Architecture ::Hopper |Architecture ::BlackwellGB10x =>Ok (0x000200bc ), +Architecture ::BlackwellGB20x =>Ok (0x00ad00bc ), + _ =>Err (kernel::error::code::ENOTSUPP ), + } +} + +/// FSP writes this value to indicate successful boot completion. +pub (crate )const FSP_BOOT_COMPLETE_SUCCESS :u32 =0xff ; + +/// Read FSP boot completion status from the architecture-specific thermal scratch register. +/// +/// Returns `None` if the architecture does not have an FSP. +pub (crate )fn read_fsp_boot_complete_status ( + bar: &crate ::driver::Bar0 , + arch:Architecture , +) ->Option <u32 > { +let addr =fsp_thermal_scratch_reg_addr (arch).ok ()?; +Some (bar.read32 (addr)) +}// The modules below provide registers that are not identical on all supported chips. They should // only be used in HAL modules.
Signature · 1 line
2.53.0
Alexandre Courbot
maintainerRe: [PATCH v9 19/31] gpu: nova-core: Hopper/Blackwell: add FSP secure boot completion waiting
Quoted 7 lines · John Hubbard
Add the FSP (Firmware System Processor) module for Hopper/Blackwell GPUs. These architectures use a simplified firmware boot sequence:
FMC --> FSP --> GSP, with no SEC2 involvement.This commit adds the ability to wait for FSP secure boot completion by polling the I2CS thermal scratch register until FSP signals success.
This does more than just the boot completion waiting (which is just the wait_secure_boot method) - it looks like most of the content of fsp.rs should be moved to different patches.
Quoted 35 lines
Signed-off-by John Hubbard <[email protected]>--- drivers/gpu/nova-core/fsp.rs | 148 +++++++++++++++++++++++++++++ drivers/gpu/nova-core/nova_core.rs | 1 + drivers/gpu/nova-core/regs.rs | 29 ++++++ 3 files changed, 178 insertions(+) create mode 100644 drivers/gpu/nova-core/fsp.rsdrivers/gpu/nova-core/fsp.rs new file +20
-0@@ -0,0 +1,148 @@ +// SPDX-License-Identifier: GPL-2.0 + +//! FSP (Firmware System Processor) interface for Hopper/Blackwell GPUs. +//! +//! Hopper/Blackwell use a simplified firmware boot sequence: FMC --> FSP --> GSP. +//! Unlike Turing/Ampere/Ada, there is NO SEC2 (Security Engine 2) usage. +//! FSP handles secure boot directly using FMC firmware + Chain of Trust. + +use kernel::{ + device, + io::poll::read_poll_timeout, + prelude::*, + time::Delta , + transmute::{ +AsBytes , +FromBytes ,// + }, +}; + +use crate ::regs;
drivers/gpu/nova-core/fsp.rs line 30
Quoted 10 lines
drivers/gpu/nova-core/fsp.rs new file +10
-0+ +/// FSP secure boot completion timeout in milliseconds. +/// +/// GB20x requires a longer timeout than Hopper/GB10x. +const fn fsp_secure_boot_timeout_ms (arch:crate ::gpu::Architecture ) ->i64 { +match arch { +crate ::gpu::Architecture ::BlackwellGB20x =>5000 , + _ =>4000 , + } +}
Since this is a timeout, how about harmonizing to 5000 for everyone and turning this into a constant? Waiting 1 more second in case of a boot failure should be acceptable. :)
Re: [PATCH v9 19/31] gpu: nova-core: Hopper/Blackwell: add FSP secure boot completion waiting
Quoted 4 lines · Alexandre Courbot
Quoted 3 lines · John Hubbard
Add the FSP (Firmware System Processor) module for Hopper/Blackwell GPUs. These architectures use a simplified firmware boot sequence:
Quoted 8 lines
Quoted 4 lines
FMC --> FSP --> GSP, with no SEC2 involvement.This commit adds the ability to wait for FSP secure boot completion by polling the I2CS thermal scratch register until FSP signals success.
This does more than just the boot completion waiting (which is just the
wait_secure_bootmethod) - it looks like most of the content offsp.rsshould be moved to different patches.
"I" will do that, no problem. Especially no problem since you already did it for me in a branch. :) Thanks!
...
Quoted 6 lines
Quoted 6 lines
drivers/gpu/nova-core/fsp.rs new file +6
-0+ +/// FSP secure boot completion timeout in milliseconds. +/// +/// GB20x requires a longer timeout than Hopper/GB10x. +const fn fsp_secure_boot_timeout_ms (arch:crate ::gpu::Architecture ) ->i64 { +match arch {
Quoted 9 lines
drivers/gpu/nova-core/fsp.rs line 30
Quoted 4 lines
drivers/gpu/nova-core/fsp.rs new file +4
-0+ crate::gpu::Architecture::BlackwellGB20x => 5000, + _ => 4000, + } +}Since this is a timeout, how about harmonizing to 5000 for everyone and turning this into a constant? Waiting 1 more second in case of a boot failure should be acceptable. :)
Yes, will do.
thanks,
Signature · 1 line
John Hubbard
PATCH v9 20/31 gpu: nova-core: Hopper/Blackwell: add FMC signature extraction
In reply to John HubbardAdd extract_fmc_signatures() which extracts SHA-384 hash, RSA public key, and RSA signature from FMC ELF32 firmware sections. These are needed for FSP Chain of Trust verification.
--- drivers/gpu/nova-core/firmware.rs | 3 +- drivers/gpu/nova-core/fsp.rs | 79 +++++++++++++++++++++++++++++++ 2 files changed, 81 insertions(+), 1 deletion(-)
drivers/gpu/nova-core/firmware.rs +2 -1
@@ -26,6 +26,7 @@ }, }; +pub (crate )use elf::elf_section;pub (crate )mod booter;pub (crate )mod fsp;pub (crate )mod fwsec;
@@ -646,7 +647,7 @@ fn elf32_section<'a>(elf: &'a [u8], name: &str) -> Option<&'a [u8]> { }/// Automatically detects ELF32 vs ELF64 based on the ELF header. -pub (super )fn elf_section <'a>(elf: &'a [u8 ], name: &str ) ->Option <&'a [u8 ]> { +pub (crate )fn elf_section <'a>(elf: &'a [u8 ], name: &str ) ->Option <&'a [u8 ]> {// Check ELF magic. if elf.len () <5 || elf.get (0 ..4 )? !=b"\x7fELF" {return None ;
drivers/gpu/nova-core/fsp.rs +79 -0
89 lines not on this page · raw message
Signature · 1 line
2.53.0
PATCH v9 21/31 gpu: nova-core: Hopper/Blackwell: add FSP send/receive messaging
In reply to John HubbardAdd send_sync_fsp() which sends an MCTP/NVDM message to FSP and waits for the response. Response validation uses the typed MctpHeader and NvdmHeader wrappers from the previous commit.
A MessageToFsp trait provides the NVDM type constant for each message struct, so send_sync_fsp() can verify that the response matches the request.
--- drivers/gpu/nova-core/falcon/fsp.rs | 3 - drivers/gpu/nova-core/fsp.rs | 123 ++++++++++++++++++++++++++++ 2 files changed, 123 insertions(+), 3 deletions(-)
drivers/gpu/nova-core/falcon/fsp.rs +0 -3
@@ -150,7 +150,6 @@ pub(crate) fn read_emem(&self, bar: &Bar0, offset: u32, data: &mut [u8]) -> Resu/// /// The FSP message queue is not circular - pointers are reset to 0 after each /// message exchange, so `tail >= head` is always true when data is present. -#[expect(unused)] pub (crate )fn poll_msgq (&self, bar: &Bar0 ) ->u32 {let head = regs::NV_PFSP_MSGQ_HEAD ::read (bar).address ();let tail = regs::NV_PFSP_MSGQ_TAIL ::read (bar).address ();
@@ -173,7 +172,6 @@ pub(crate) fn poll_msgq(&self, bar: &Bar0) -> u32 {/// /// # Returns /// `Ok(())` on success, `Err(EINVAL)` if packet is empty or not 4-byte aligned -#[expect(unused)] pub (crate )fn send_msg (&self, bar: &Bar0 , packet: &[u8 ]) ->Result {if packet.is_empty () {return Err (EINVAL );
@@ -205,7 +203,6 @@ pub(crate) fn send_msg(&self, bar: &Bar0, packet: &[u8]) -> Result {/// /// # Returns /// `Ok(bytes_read)` on success, `Err(EINVAL)` if size is 0, exceeds buffer, or not aligned -#[expect(unused)] pub (crate )fn recv_msg (&self, bar: &Bar0 , buffer: &mut [u8 ], size:usize ) ->Result <usize > {if size ==0 || size > buffer.len () {return Err (EINVAL );
drivers/gpu/nova-core/fsp.rs +123 -0
139 lines not on this page · raw message
Signature · 1 line
2.53.0
Alexandre Courbot
maintainerRe: [PATCH v9 21/31] gpu: nova-core: Hopper/Blackwell: add FSP send/receive messaging
On Thu Mar 26, 2026 at 10:38 AM JST, John Hubbard wrote:
<snip>
Quoted 45 lines
drivers/gpu/nova-core/fsp.rs +30
-0@@ -19,6 +19,15 @@use crate ::regs; +use crate ::mctp::{ +MctpHeader , +NvdmHeader , +NvdmType ,// +}; + +/// FSP message timeout in milliseconds. +const FSP_MSG_TIMEOUT_MS :i64 =2000 ; +/// FSP secure boot completion timeout in milliseconds. /// /// GB20x requires a longer timeout than Hopper/GB10x. @@ -124,6 +133,37 @@ pub(crate) struct FmcSignatures { public_key: [u8; FSP_PKEY_SIZE], signature: [u8; FSP_SIG_SIZE], } + +/// FSP Command Response payload structure. +/// NVDM_PAYLOAD_COMMAND_RESPONSE structure. +#[repr( C , packed)] +#[derive( Clone , Copy )] +struct NvdmPayloadCommandResponse { + task_id:u32 , + command_nvdm_type:u32 , + error_code:u32 , +} + +/// Complete FSP response structure with MCTP and NVDM headers. +#[repr( C , packed)] +#[derive( Clone , Copy )] +struct FspResponse { + mctp_header:u32 , + nvdm_header:u32 , + response:NvdmPayloadCommandResponse , +} + +// SAFETY: FspResponse is a packed C struct with only integral fields.
drivers/gpu/nova-core/fsp.rs pub(crate) struct FmcSignatures { · line 166
Quoted 10 lines
drivers/gpu/nova-core/fsp.rs +10
-0+unsafe impl FromBytes for FspResponse {} + +/// Trait implemented by types representing a message to send to FSP. +/// +/// This provides [`Fsp::send_sync_fsp`] with the information it needs to send +/// a given message, following the same pattern as GSP's `CommandToGsp`. +pub (crate )trait MessageToFsp :AsBytes { +/// NVDM type identifying this message to FSP. +const NVDM_TYPE :u32 ; +}
A trait is useful to provide some kind of polymorphism. This trait is only ever implemented by FspMessage (which strangely is added in a different patch), so it seems pretty pointless (unless we have plans to implement it on other types, but this series doesn't do it).
Quoted 4 lines
drivers/gpu/nova-core/fsp.rs +0
-0/// FSP interface for Hopper/Blackwell GPUs. pub (crate )struct Fsp ;
drivers/gpu/nova-core/fsp.rs pub(crate) fn extract_fmc_signatures( · line 273
Quoted 10 lines
drivers/gpu/nova-core/fsp.rs +7
-0@@ -224,4 +264,87 @@ pub(crate) fn extract_fmc_signatures(Ok (signatures) } + +/// Send message to FSP and wait for response. +#[expect(dead_code)] +fn send_sync_fsp <M >( + dev: &device::Device <device::Bound >, + bar: &crate ::driver::Bar0 , + fsp_falcon: &crate::falcon::Falcon<crate::falcon::fsp::Fsp>,
Please import relevant items, this is very heavy to read (applies to other patches in the series as well).
PATCH v9 22/31 gpu: nova-core: Hopper/Blackwell: add FspCotVersion type
In reply to John HubbardAdd FspCotVersion to represent the FSP Chain of Trust protocol version, and Chipset::fsp_cot_version() which returns the version for each architecture. Hopper uses version 1, Blackwell uses version 2. Non-FSP architectures return None.
--- drivers/gpu/nova-core/fsp.rs | 19 +++++++++++++++++++ drivers/gpu/nova-core/gpu.rs | 16 ++++++++++++++++ 2 files changed, 35 insertions(+)
drivers/gpu/nova-core/fsp.rs +19 -0
@@ -25,6 +25,25 @@ NvdmType, // }; +/// FSP Chain of Trust protocol version. +/// +/// Hopper (GH100) uses version 1, Blackwell uses version 2. +#[derive( Debug , Clone , Copy )] +pub (crate )struct FspCotVersion (u16 ); + +impl FspCotVersion { +/// Create a new FSP COT version. +pub (crate )const fn new (version:u16 ) ->Self { +Self (version) + } + +/// Return the raw protocol version number for the wire format. +#[expect(dead_code)] +pub (crate )const fn raw (self) ->u16 { + self.0 + } +} +/// FSP message timeout in milliseconds. const FSP_MSG_TIMEOUT_MS :i64 =2000 ;
drivers/gpu/nova-core/gpu.rs +16 -0
@@ -21,6 +21,7 @@ Falcon, // }, fb::SysmemFlush, + fsp::FspCotVersion, gsp::Gsp, regs, };
@@ -132,6 +133,21 @@ pub(crate) const fn arch(self) -> Architecture {pub (crate )const fn needs_fwsec_bootloader (self) ->bool {matches! (self.arch (),Architecture ::Turing ) ||matches! (self,Self ::GA100 ) } + +/// Returns the FSP Chain of Trust (COT) protocol version for this chipset. +/// +/// Hopper (GH100) uses version 1, Blackwell uses version 2. +/// Returns `None` for architectures that do not use FSP. +#[expect(dead_code)] +pub (crate )const fn fsp_cot_version (&self) ->Option <FspCotVersion > { +match self.arch () { +Architecture ::Hopper =>Some (FspCotVersion ::new (1 )), +Architecture ::BlackwellGB10x |Architecture ::BlackwellGB20x => { +Some (FspCotVersion ::new (2 )) + } + _ =>None , + } + } }// TODO
Signature · 1 line
2.53.0
PATCH v9 23/31 gpu: nova-core: Hopper/Blackwell: larger non-WPR heap
In reply to John HubbardAdd dedicated FB HALs for Hopper (GH100) and Blackwell (GB100) with architecture-specific non-WPR heap sizes. Hopper uses 2 MiB, Blackwell uses 2 MiB + 128 KiB. These are needed for the larger reserved memory regions that Hopper/Blackwell GPUs require.
Also adds the non_wpr_heap_size() method to the FbHal trait, and the total_reserved_size field to FbLayout.
--- drivers/gpu/nova-core/fb.rs | 16 ++++++++--- drivers/gpu/nova-core/fb/hal.rs | 19 +++++++++----- drivers/gpu/nova-core/fb/hal/ga102.rs | 2 +- drivers/gpu/nova-core/fb/hal/gb100.rs | 38 +++++++++++++++++++++++++++ drivers/gpu/nova-core/fb/hal/gh100.rs | 38 +++++++++++++++++++++++++++ 5 files changed, 102 insertions(+), 11 deletions(-) create mode 100644 drivers/gpu/nova-core/fb/hal/gb100.rs create mode 100644 drivers/gpu/nova-core/fb/hal/gh100.rs
drivers/gpu/nova-core/fb.rs +12 -4
@@ -31,7 +31,7 @@ regs, }; -mod hal; +pub (crate )mod hal;/// Type holding the sysmem flush memory page, a page of memory to be written into the /// `NV_PFB_NISO_FLUSH_SYSMEM_ADDR*` registers and used to maintain memory coherency.
@@ -99,6 +99,15 @@ pub(crate) fn unregister(&self, bar: &Bar0) { } } +/// Calculate non-WPR heap size based on chipset architecture. +/// This matches the logic used in FSP for consistency. +pub (crate )fn calc_non_wpr_heap_size (chipset:Chipset ) ->u64 { + hal::fb_hal (chipset) + .non_wpr_heap_size () + .map (u64::from) + .unwrap_or (usize_as_u64 (SZ_1M )) +} +pub (crate )struct FbRange (Range <u64 >);impl FbRange {
@@ -253,9 +262,8 @@ pub(crate) fn new(chipset: Chipset, bar: &Bar0, gsp_fw: &GspFirmware) -> Result< };let heap = { -const HEAP_SIZE :u64 =usize_as_u64 (SZ_1M ); - -FbRange (wpr2.start -HEAP_SIZE ..wpr2.start) +let heap_size =calc_non_wpr_heap_size (chipset); +FbRange (wpr2.start - heap_size..wpr2.start) };Ok (Self {
drivers/gpu/nova-core/fb/hal.rs +13 -6
@@ -12,6 +12,8 @@mod ga100;mod ga102; +mod gb100; +mod gh100;mod tu102;pub (crate )trait FbHal {
@@ -28,17 +30,22 @@ pub(crate) trait FbHal {/// Returns the VRAM size, in bytes. fn vidmem_size (&self, bar: &Bar0 ) ->u64 ; + +/// Returns the non-WPR heap size for GPUs that need large reserved memory. +/// +/// Returns `None` for GPUs that don't need extra reserved memory. +fn non_wpr_heap_size (&self) ->Option <u32 > { +None + } }/// Returns the HAL corresponding to `chipset`. -pub (super )fn fb_hal (chipset:Chipset ) -> &'staticdyn FbHal { +pub (crate )fn fb_hal (chipset:Chipset ) -> &'staticdyn FbHal {match chipset.arch () {Architecture ::Turing => tu102::TU102_HAL ,Architecture ::Ampere if chipset ==Chipset ::GA100 => ga100::GA100_HAL , -Architecture ::Ampere => ga102::GA102_HAL , -Architecture ::Ada - |Architecture ::Hopper - |Architecture ::BlackwellGB10x - |Architecture ::BlackwellGB20x => ga102::GA102_HAL , +Architecture ::Ampere |Architecture ::Ada => ga102::GA102_HAL , +Architecture ::Hopper => gh100::GH100_HAL , +Architecture ::BlackwellGB10x |Architecture ::BlackwellGB20x => gb100::GB100_HAL , } }
drivers/gpu/nova-core/fb/hal/ga102.rs +1 -1
@@ -8,7 +8,7 @@ regs, // }; -fn vidmem_size_ga102 (bar: &Bar0 ) ->u64 { +pub (super )fn vidmem_size_ga102 (bar: &Bar0 ) ->u64 { regs::NV_USABLE_FB_SIZE_IN_MB ::read (bar).usable_fb_size () }
drivers/gpu/nova-core/fb/hal/gb100.rs new file +38 -0
@@ -0,0 +1,38 @@ +// SPDX-License-Identifier: GPL-2.0 + +use kernel::prelude::*; + +use crate ::{ + driver::Bar0 , + fb::hal::FbHal ,// +}; + +struct Gb100 ; + +impl FbHal for Gb100 { +fn read_sysmem_flush_page (&self, bar: &Bar0 ) ->u64 { +super ::ga100::read_sysmem_flush_page_ga100 (bar) + } + +fn write_sysmem_flush_page (&self, bar: &Bar0 , addr:u64 ) ->Result { +super ::ga100::write_sysmem_flush_page_ga100 (bar, addr); + +Ok (()) + } + +fn supports_display (&self, bar: &Bar0 ) ->bool { +super ::ga100::display_enabled_ga100 (bar) + } + +fn vidmem_size (&self, bar: &Bar0 ) ->u64 { +super ::ga102::vidmem_size_ga102 (bar) + } + +fn non_wpr_heap_size (&self) ->Option <u32 > { +// 2 MiB + 128 KiB non-WPR heap for Blackwell (see Open RM: kgspCalculateFbLayout_GB100). +Some (0x220000 ) + } +} + +const GB100 :Gb100 =Gb100 ; +pub (super )const GB100_HAL : &dyn FbHal = &GB100 ;
drivers/gpu/nova-core/fb/hal/gh100.rs new file +38 -0
@@ -0,0 +1,38 @@ +// SPDX-License-Identifier: GPL-2.0 + +use kernel::prelude::*; + +use crate ::{ + driver::Bar0 , + fb::hal::FbHal ,// +}; + +struct Gh100 ; + +impl FbHal for Gh100 { +fn read_sysmem_flush_page (&self, bar: &Bar0 ) ->u64 { +super ::ga100::read_sysmem_flush_page_ga100 (bar) + } + +fn write_sysmem_flush_page (&self, bar: &Bar0 , addr:u64 ) ->Result { +super ::ga100::write_sysmem_flush_page_ga100 (bar, addr); + +Ok (()) + } + +fn supports_display (&self, bar: &Bar0 ) ->bool { +super ::ga100::display_enabled_ga100 (bar) + } + +fn vidmem_size (&self, bar: &Bar0 ) ->u64 { +super ::ga102::vidmem_size_ga102 (bar) + } + +fn non_wpr_heap_size (&self) ->Option <u32 > { +// 2 MiB non-WPR heap for Hopper (see Open RM: kgspCalculateFbLayout_GH100). +Some (0x200000 ) + } +} + +const GH100 :Gh100 =Gh100 ; +pub (super )const GH100_HAL : &dyn FbHal = &GH100 ;
Signature · 1 line
2.53.0
PATCH v9 24/31 gpu: nova-core: Hopper/Blackwell: add FSP Chain of Trust boot
In reply to John HubbardAdd boot_fmc() which builds and sends the Chain of Trust message to FSP, and FmcBootArgs which bundles the DMA-coherent boot parameters that FSP reads at boot time. The FspFirmware struct fields become pub(crate) and fmc_full changes from DmaObject to KVec<u8> for CPU-side signature extraction.
--- drivers/gpu/nova-core/firmware/fsp.rs | 8 +- drivers/gpu/nova-core/fsp.rs | 170 +++++++++++++++++++++++++- drivers/gpu/nova-core/gpu.rs | 1 - drivers/gpu/nova-core/mctp.rs | 7 -- 4 files changed, 172 insertions(+), 14 deletions(-)
drivers/gpu/nova-core/firmware/fsp.rs +4 -4
@@ -14,16 +14,16 @@ gpu::Chipset, // }; -#[expect(unused)] +#[expect(dead_code)] pub (crate )struct FspFirmware {/// FMC firmware image data (only the "image" ELF section). - fmc_image:DmaObject , -/// Full FMC ELF (for signature extraction. +pub (crate ) fmc_image:DmaObject , +/// Full FMC ELF for signature extraction. pub (crate ) fmc_elf:Firmware , }impl FspFirmware { -#[expect(unused)] +#[expect(dead_code)] pub (crate )fn new ( dev: &device::Device <device::Bound >, chipset: Chipset,
drivers/gpu/nova-core/fsp.rs +168 -2
203 lines not on this page · raw message
drivers/gpu/nova-core/gpu.rs +0 -1
@@ -138,7 +138,6 @@ pub(crate) const fn needs_fwsec_bootloader(self) -> bool {/// /// Hopper (GH100) uses version 1, Blackwell uses version 2. /// Returns `None` for architectures that do not use FSP. -#[expect(dead_code)] pub (crate )const fn fsp_cot_version (&self) ->Option <FspCotVersion > {match self.arch () {Architecture ::Hopper =>Some (FspCotVersion ::new (1 )),
drivers/gpu/nova-core/mctp.rs +0 -7
@@ -6,8 +6,6 @@//! Device Management) messages between the kernel driver and GPU firmware //! processors such as FSP and GSP. -#![expect(dead_code)] -/// NVDM message type identifiers carried over MCTP. #[derive( Debug , Clone , Copy , PartialEq , Eq )] #[repr( u8 )]
@@ -101,11 +99,6 @@ pub(crate) fn nvdm_type(self) -> core::result::Result<NvdmType, u8> {NvdmType ::try_from (self.raw_nvdm_type ()) } -/// Extract the NVDM type field as a raw value. -pub (crate )fn nvdm_type_raw (self) ->u32 { - u32::from (self.raw_nvdm_type ()) - } -/// Set the NVDM type field from a typed value. pub (crate )fn set_nvdm_type (self, nvdm_type:NvdmType ) ->Self { self.set_raw_nvdm_type (u8::from (nvdm_type))
Signature · 1 line
2.53.0
Alexandre Courbot
maintainerRe: [PATCH v9 24/31] gpu: nova-core: Hopper/Blackwell: add FSP Chain of Trust boot
Quoted 21 lines · John Hubbard
Add
boot_fmc()which builds and sends the Chain of Trust message to FSP, and FmcBootArgs which bundles the DMA-coherent boot parameters that FSP reads at boot time. The FspFirmware struct fields become pub(crate) andfmc_fullchanges from DmaObject to KVec<u8> for CPU-side signature extraction.Co-developed-by Alexandre Courbot <[email protected]>Signed-off-by Alexandre Courbot <[email protected]>Signed-off-by John Hubbard <[email protected]>--- drivers/gpu/nova-core/firmware/fsp.rs | 8 +- drivers/gpu/nova-core/fsp.rs | 170 +++++++++++++++++++++++++- drivers/gpu/nova-core/gpu.rs | 1 - drivers/gpu/nova-core/mctp.rs | 7 -- 4 files changed, 172 insertions(+), 14 deletions(-)drivers/gpu/nova-core/firmware/fsp.rs +0
-0
drivers/gpu/nova-core/firmware/fsp.rs line 17
Quoted 5 lines
drivers/gpu/nova-core/firmware/fsp.rs +1
-1@@ -14,16 +14,16 @@ gpu::Chipset, // }; -#[expect(unused)] +#[expect(dead_code)]
Why?
drivers/gpu/nova-core/firmware/fsp.rs line 22
Quoted 7 lines
drivers/gpu/nova-core/firmware/fsp.rs +2
-2pub (crate )struct FspFirmware {/// FMC firmware image data (only the "image" ELF section). - fmc_image:DmaObject , -/// Full FMC ELF (for signature extraction. +pub (crate ) fmc_image:DmaObject , +/// Full FMC ELF for signature extraction. pub (crate ) fmc_elf:Firmware ,
Let's make the comment for fmc_elf correct since its introduction instead of fixing it here?
drivers/gpu/nova-core/firmware/fsp.rs line 26
Quoted 5 lines
drivers/gpu/nova-core/firmware/fsp.rs +1
-1}impl FspFirmware { -#[expect(unused)] +#[expect(dead_code)]
Same here, I don't see the point. If it's not unused anymore, let's remove the expect entirely. If it is, let's keep the more accurate unused.
Btw, this is the kind of stuff you'd normally catch by looking at the diff before sending it. I shouldn't have to do this.
Re: [PATCH v9 24/31] gpu: nova-core: Hopper/Blackwell: add FSP Chain of Trust boot
Quoted 25 lines · Alexandre Courbot
Quoted 24 lines · John Hubbard
Add
boot_fmc()which builds and sends the Chain of Trust message to FSP, and FmcBootArgs which bundles the DMA-coherent boot parameters that FSP reads at boot time. The FspFirmware struct fields become pub(crate) andfmc_fullchanges from DmaObject to KVec<u8> for CPU-side signature extraction.Co-developed-by Alexandre Courbot <[email protected]>Signed-off-by Alexandre Courbot <[email protected]>Signed-off-by John Hubbard <[email protected]>--- drivers/gpu/nova-core/firmware/fsp.rs | 8 +- drivers/gpu/nova-core/fsp.rs | 170 +++++++++++++++++++++++++- drivers/gpu/nova-core/gpu.rs | 1 - drivers/gpu/nova-core/mctp.rs | 7 -- 4 files changed, 172 insertions(+), 14 deletions(-)drivers/gpu/nova-core/firmware/fsp.rs +0
-0@@ -14,16 +14,16 @@ gpu::Chipset, // };
Quoted 4 lines
drivers/gpu/nova-core/firmware/fsp.rs line 17
Quoted 2 lines
drivers/gpu/nova-core/firmware/fsp.rs +1
-1-#[expect(unused)] +#[expect(dead_code)] Why?
dead_code is the specific lint that fires here. unused is a lint group that *contains* dead_code plus a dozen others (unused_imports, unused_variables, unused_mut, etc). Since the only warning is "this struct is never constructed," dead_code names the exact lint.
That said, you're right that this change doesn't belong in this patch. I've moved it to the introducing commit in v10.
Quoted 11 lines
drivers/gpu/nova-core/firmware/fsp.rs line 22
Quoted 8 lines
drivers/gpu/nova-core/firmware/fsp.rs +2
-2pub (crate )struct FspFirmware {/// FMC firmware image data (only the "image" ELF section). - fmc_image:DmaObject , -/// Full FMC ELF (for signature extraction. +pub (crate ) fmc_image:DmaObject , +/// Full FMC ELF for signature extraction. pub (crate ) fmc_elf:Firmware ,Let's make the comment for
fmc_elfcorrect since its introduction instead of fixing it here?
Agreed, done in v10. The introducing commit now has the correct comment from the start.
Quoted 10 lines
drivers/gpu/nova-core/firmware/fsp.rs line 26
Quoted 6 lines
drivers/gpu/nova-core/firmware/fsp.rs +1
-1}impl FspFirmware { -#[expect(unused)] +#[expect(dead_code)] Same here, I don't see the point. If it's not unused anymore, let's remove the
expectentirely. If it is, let's keep the more accurateunused.
One small correction: unused is actually the *less* specific choice. It is a lint group containing dead_code, unused_imports, unused_variables, and about a dozen others. dead_code is the single lint that actually fires on an unreferenced struct or function. #[expect(...)] is meant to name the expected warning, so using the specific lint is more precise.
But you're right that this change belonged in the introducing commit, not here. Fixed in v10: the introducing commit uses #[expect(dead_code)] from the start, and this patch only changes fmc_image to pub(crate).
Quoted 3 lines
Btw, this is the kind of stuff you'd normally catch by looking at the diff before sending it. I shouldn't have to do this.
I actually spend lots of time fooling around with dead_code and unused, trying to get it just right. There are a lot of patches that add and remove these.
In this case, after the dust settled after applying the v8 review feedback, I did notice this unused-->dead_code diff that we are discussing, but I just let it go, because it's only a couple of lines that end up getting vaporized by the end of the series anyway, and I was anxious to get all the other things (especially Gary/Sashiko's big discovery about the two Blackwell arches) posted.
thanks,
Signature · 1 line
John Hubbard
Alexandre Courbot
maintainerRe: [PATCH v9 24/31] gpu: nova-core: Hopper/Blackwell: add FSP Chain of Trust boot
In reply to John HubbardQuoted 5 lines · John Hubbard
Add
boot_fmc()which builds and sends the Chain of Trust message to FSP, and FmcBootArgs which bundles the DMA-coherent boot parameters that FSP reads at boot time. The FspFirmware struct fields become pub(crate) andfmc_fullchanges from DmaObject to KVec<u8> for CPU-side signature extraction.
The temporary KVec field has been removed, so this commit message needs updating too.
Quoted 3 lines
Co-developed-by Alexandre Courbot <[email protected]>Signed-off-by Alexandre Courbot <[email protected]>
Was I involved in the development of this? The code must have evolved beyond recognition, you can probably remove this. :)
<snip>
Quoted 26 lines
drivers/gpu/nova-core/gpu.rs +0
-1@@ -138,7 +138,6 @@ pub(crate) const fn needs_fwsec_bootloader(self) -> bool {/// /// Hopper (GH100) uses version 1, Blackwell uses version 2. /// Returns `None` for architectures that do not use FSP. -#[expect(dead_code)] pub (crate )const fn fsp_cot_version (&self) ->Option <FspCotVersion > {match self.arch () {Architecture ::Hopper =>Some (FspCotVersion ::new (1 )),drivers/gpu/nova-core/mctp.rs +0
-2@@ -6,8 +6,6 @@//! Device Management) messages between the kernel driver and GPU firmware //! processors such as FSP and GSP. -#![expect(dead_code)] -/// NVDM message type identifiers carried over MCTP. #[derive( Debug , Clone , Copy , PartialEq , Eq )] #[repr( u8 )]
drivers/gpu/nova-core/mctp.rs pub(crate) fn nvdm_type(self) -> core::result::Result<NvdmType, u8> { · line 107
Quoted 7 lines
drivers/gpu/nova-core/mctp.rs +0
-4@@ -101,11 +99,6 @@ pub(crate) fn nvdm_type(self) -> core::result::Result<NvdmType, u8> {NvdmType ::try_from (self.raw_nvdm_type ()) } -/// Extract the NVDM type field as a raw value. -pub (crate )fn nvdm_type_raw (self) ->u32 { - u32::from (self.raw_nvdm_type ()) - }
This method was introduced a few patches before, and I don't think it is ever used - you can probably drop it since the beginning.
Re: [PATCH v9 24/31] gpu: nova-core: Hopper/Blackwell: add FSP Chain of Trust boot
Quoted 10 lines · Alexandre Courbot
Quoted 5 lines · John Hubbard
Add
boot_fmc()which builds and sends the Chain of Trust message to FSP, and FmcBootArgs which bundles the DMA-coherent boot parameters that FSP reads at boot time. The FspFirmware struct fields become pub(crate) andfmc_fullchanges from DmaObject to KVec<u8> for CPU-side signature extraction.The temporary
KVecfield has been removed, so this commit message needs updating too.
Will do.
Quoted 6 lines
Quoted 3 lines
Co-developed-by Alexandre Courbot <[email protected]>Signed-off-by Alexandre Courbot <[email protected]>Was I involved in the development of this? The code must have evolved beyond recognition, you can probably remove this. :)
Yes, long ago. :) OK.
Quoted 31 lines
<snip>
Quoted 29 lines
drivers/gpu/nova-core/gpu.rs +0
-1@@ -138,7 +138,6 @@ pub(crate) const fn needs_fwsec_bootloader(self) -> bool {/// /// Hopper (GH100) uses version 1, Blackwell uses version 2. /// Returns `None` for architectures that do not use FSP. -#[expect(dead_code)] pub (crate )const fn fsp_cot_version (&self) ->Option <FspCotVersion > {match self.arch () {Architecture ::Hopper =>Some (FspCotVersion ::new (1 )),drivers/gpu/nova-core/mctp.rs +0
-2@@ -6,8 +6,6 @@//! Device Management) messages between the kernel driver and GPU firmware //! processors such as FSP and GSP. -#![expect(dead_code)] -/// NVDM message type identifiers carried over MCTP. #[derive( Debug , Clone , Copy , PartialEq , Eq )] #[repr( u8 )] @@ -101,11 +99,6 @@ pub(crate) fn nvdm_type(self) -> core::result::Result<NvdmType, u8> {NvdmType ::try_from (self.raw_nvdm_type ()) }
Quoted 8 lines
drivers/gpu/nova-core/mctp.rs pub(crate) fn nvdm_type(self) -> core::result::Result<NvdmType, u8> { · line 107
Quoted 4 lines
drivers/gpu/nova-core/mctp.rs +0
-4-/// Extract the NVDM type field as a raw value. -pub (crate )fn nvdm_type_raw (self) ->u32 { - u32::from (self.raw_nvdm_type ()) - }This method was introduced a few patches before, and I don't think it is ever used - you can probably drop it since the beginning.
OK.
thanks,
Signature · 1 line
John Hubbard
PATCH v9 25/31 gpu: nova-core: Blackwell: use correct sysmem flush registers
In reply to John HubbardBlackwell GPUs moved the sysmem flush page registers away from the legacy NV_PFB_NISO_FLUSH_SYSMEM_ADDR used by Ampere/Ada.
GB10x uses HSHUB0 registers, with both a primary and EG (egress) pair that must be programmed to the same address. GB20x uses FBHUB0 registers.
Add separate GB100 and GB202 fb HALs, and split the Blackwell HAL dispatch so that each uses its respective registers.
--- drivers/gpu/nova-core/fb/hal.rs | 8 +++- drivers/gpu/nova-core/fb/hal/gb100.rs | 47 +++++++++++++++++--- drivers/gpu/nova-core/fb/hal/gb202.rs | 62 +++++++++++++++++++++++++++ drivers/gpu/nova-core/regs.rs | 36 ++++++++++++++++ 4 files changed, 147 insertions(+), 6 deletions(-) create mode 100644 drivers/gpu/nova-core/fb/hal/gb202.rs
drivers/gpu/nova-core/fb/hal.rs +7 -1
@@ -13,9 +13,14 @@mod ga100;mod ga102;mod gb100; +mod gb202;mod gh100;mod tu102; +/// Non-WPR heap size for Blackwell (2 MiB + 128 KiB). +/// See Open RM: kgspCalculateFbLayout_GB100. +const BLACKWELL_NON_WPR_HEAP_SIZE :u32 =0x220000 ; +pub (crate )trait FbHal {/// Returns the address of the currently-registered sysmem flush page. fn read_sysmem_flush_page (&self, bar: &Bar0 ) ->u64 ;
@@ -46,6 +51,7 @@ pub(crate) fn fb_hal(chipset: Chipset) -> &'static dyn FbHal { Architecture::Ampere if chipset == Chipset::GA100 => ga100::GA100_HAL, Architecture::Ampere | Architecture::Ada => ga102::GA102_HAL, Architecture::Hopper => gh100::GH100_HAL, - Architecture::BlackwellGB10x | Architecture::BlackwellGB20x => gb100::GB100_HAL, + Architecture::BlackwellGB10x => gb100::GB100_HAL, + Architecture::BlackwellGB20x => gb202::GB202_HAL, } }
drivers/gpu/nova-core/fb/hal/gb100.rs +42 -5
71 lines not on this page · raw message
drivers/gpu/nova-core/fb/hal/gb202.rs new file +62 -0
62 lines not on this page · raw message
drivers/gpu/nova-core/regs.rs +36 -0
@@ -116,6 +116,42 @@ fn fmt(&self, f: &mut kernel::fmt::Formatter<'_>) -> kernel::fmt::Result { 23:0 adr_63_40 as u32; }); +// Blackwell GB10x sysmem flush registers (HSHUB0). +// +// GB10x GPUs use two pairs of HSHUB registers for sysmembar: a primary pair and an EG +// (egress) pair. Both must be programmed to the same address. Hardware ignores bits 7:0 +// of each LO register. HSHUB0 base is 0x00891000. + +register! (NV_PFB_HSHUB0_PCIE_FLUSH_SYSMEM_ADDR_LO @0x00891e50 { +31 :0 adras u32 ; +}); + +register! (NV_PFB_HSHUB0_PCIE_FLUSH_SYSMEM_ADDR_HI @0x00891e54 { +19 :0 adras u32 ; +}); + +register! (NV_PFB_HSHUB0_EG_PCIE_FLUSH_SYSMEM_ADDR_LO @0x008916c0 { +31 :0 adras u32 ; +}); + +register! (NV_PFB_HSHUB0_EG_PCIE_FLUSH_SYSMEM_ADDR_HI @0x008916c4 { +19 :0 adras u32 ; +}); + +// Blackwell GB20x sysmem flush registers (FBHUB0). +// +// Unlike the older NV_PFB_NISO_FLUSH_SYSMEM_ADDR registers which encode the address with an +// 8-bit right-shift, these registers take the raw address split into lower/upper 32-bit halves. +// The hardware ignores bits 7:0 of the LO register. + +register! (NV_PFB_FBHUB0_PCIE_FLUSH_SYSMEM_ADDR_LO @0x008a1d58 { +31 :0 adras u32 ; +}); + +register! (NV_PFB_FBHUB0_PCIE_FLUSH_SYSMEM_ADDR_HI @0x008a1d5c { +19 :0 adras u32 ; +}); +register! (NV_PFB_PRI_MMU_LOCAL_MEMORY_RANGE @0x00100ce0 {3 :0 lower_scaleas u8 ;9 :4 lower_magas u8 ;
Signature · 1 line
2.53.0
PATCH v9 26/31 gpu: nova-core: make WPR heap sizing fallible
In reply to John HubbardMake management_overhead() fail on multiplication or alignment overflow instead of silently saturating. Propagate that failure through wpr_heap_size() and the framebuffer layout code that consumes it.
This is not Blackwell-specific, so keep it separate from the larger WPR2 heap change that follows.
--- drivers/gpu/nova-core/fb.rs | 2 +- drivers/gpu/nova-core/gsp/fw.rs | 16 +++++++++------- 2 files changed, 10 insertions(+), 8 deletions(-)
drivers/gpu/nova-core/fb.rs +1 -1
@@ -247,7 +247,7 @@ pub(crate) fn new(chipset: Chipset, bar: &Bar0, gsp_fw: &GspFirmware) -> Result<let wpr2_heap = {const WPR2_HEAP_DOWN_ALIGN :Alignment =Alignment ::new ::<SZ_1M >();let wpr2_heap_size = - gsp::LibosParams ::from_chipset (chipset).wpr_heap_size (chipset, fb.end); + 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 );FbRange (wpr2_heap_addr..(elf.start).align_down (WPR2_HEAP_DOWN_ALIGN ))
drivers/gpu/nova-core/gsp/fw.rs +9 -7
@@ -125,13 +125,14 @@ fn client_alloc_size() -> u64 {/// Returns the amount of memory to reserve for management purposes for a framebuffer of size /// `fb_size`. -fn management_overhead (fb_size:u64 ) ->u64 { +fn management_overhead (fb_size:u64 ) ->Result <u64 > {let fb_size_gb = fb_size.div_ceil (u64::from_safe_cast (kernel::sizes::SZ_1G )); u64::from (bindings::GSP_FW_HEAP_PARAM_SIZE_PER_GB_FB ) - .saturating_mul (fb_size_gb) + .checked_mul (fb_size_gb) + .ok_or (EINVAL )? .align_up (GSP_HEAP_ALIGNMENT ) - .unwrap_or (u64::MAX ) + .ok_or (EINVAL ) } }
@@ -174,18 +175,19 @@ pub(crate) fn from_chipset(chipset: Chipset) -> &'static LibosParams {/// Returns the amount of memory (in bytes) to allocate for the WPR heap for a framebuffer size /// of `fb_size` (in bytes) for `chipset`. -pub (crate )fn wpr_heap_size (&self, chipset:Chipset , fb_size:u64 ) ->u64 { +pub (crate )fn wpr_heap_size (&self, chipset:Chipset , fb_size:u64 ) ->Result <u64 > {// The WPR heap will contain the following: // LIBOS carveout, - self.carveout_size +Ok (self + .carveout_size// RM boot working memory, .saturating_add (GspFwHeapParams ::base_rm_size (chipset))// One RM client, .saturating_add (GspFwHeapParams ::client_alloc_size ())// Overhead for memory management. - .saturating_add (GspFwHeapParams ::management_overhead (fb_size)) + .saturating_add (GspFwHeapParams ::management_overhead (fb_size)?)// Clamp to the supported heap sizes. - .clamp (self.allowed_heap_size.start, self.allowed_heap_size.end -1 ) + .clamp (self.allowed_heap_size.start, self.allowed_heap_size.end -1 )) } }
Signature · 1 line
2.53.0
Alexandre Courbot
maintainerRe: [PATCH v9 26/31] gpu: nova-core: make WPR heap sizing fallible
Quoted 8 lines · John Hubbard
Make
management_overhead()fail on multiplication or alignment overflow instead of silently saturating. Propagate that failure throughwpr_heap_size()and the framebuffer layout code that consumes it.This is not Blackwell-specific, so keep it separate from the larger WPR2 heap change that follows.
Signed-off-by John Hubbard <[email protected]>
This looks completely independent from the series. Staging it for merging when drm-rust-next reopens as this is clearly correct.
Re: [PATCH v9 26/31] gpu: nova-core: make WPR heap sizing fallible
Quoted 5 lines · Alexandre Courbot
Quoted 4 lines · John Hubbard
Make
management_overhead()fail on multiplication or alignment overflow instead of silently saturating. Propagate that failure throughwpr_heap_size()and the framebuffer layout code that consumes it.
Quoted 7 lines
Quoted 4 lines
This is not Blackwell-specific, so keep it separate from the larger WPR2 heap change that follows.
Signed-off-by John Hubbard <[email protected]>This looks completely independent from the series. Staging it for merging when drm-rust-next reopens as this is clearly correct.
OK.
thanks,
Signature · 1 line
John Hubbard
Alexandre Courbot
maintainerRe: [PATCH v9 26/31] gpu: nova-core: make WPR heap sizing fallible
In reply to Alexandre CourbotQuoted 5 lines · Alexandre Courbot
Quoted 4 lines · John Hubbard
Make
management_overhead()fail on multiplication or alignment overflow instead of silently saturating. Propagate that failure throughwpr_heap_size()and the framebuffer layout code that consumes it.
Quoted 7 lines
Quoted 4 lines
This is not Blackwell-specific, so keep it separate from the larger WPR2 heap change that follows.
Signed-off-by John Hubbard <[email protected]>This looks completely independent from the series. Staging it for merging when drm-rust-next reopens as this is clearly correct.
Pushed into drm-rust-next, thanks!
PATCH v9 27/31 gpu: nova-core: Hopper/Blackwell: larger WPR2 (GSP) heap
In reply to John HubbardHopper, Blackwell and later GPUs require a larger heap for WPR2.
--- drivers/gpu/nova-core/gsp/fw.rs | 63 +++++++++++++++++++++++++-------- 1 file changed, 49 insertions(+), 14 deletions(-)
drivers/gpu/nova-core/gsp/fw.rs +49 -14
@@ -106,21 +106,41 @@ enum GspFwHeapParams {}/// Minimum required alignment for the GSP heap. const GSP_HEAP_ALIGNMENT :Alignment =Alignment ::new ::<{1 <<20 }>(); +// These constants override the generated bindings for architecture-specific heap sizing. +// See Open RM: kgspCalculateGspFwHeapSize and related functions. +// +// 14MB for Hopper/Blackwell+. +const GSP_FW_HEAP_PARAM_BASE_RM_SIZE_GH100 :u64 =14 * num::usize_as_u64 (SZ_1M ); +// 142MB client alloc for ~188MB total. +const GSP_FW_HEAP_PARAM_CLIENT_ALLOC_SIZE_GH100 :u64 =142 * num::usize_as_u64 (SZ_1M ); +// Hopper/Blackwell+ minimum heap size: 170MB (88 + 12 + 70). +// See Open RM: GSP_FW_HEAP_SIZE_OVERRIDE_LIBOS3_BAREMETAL_MIN_MB for the base 88MB, +// plus Hopper+ additions in kgspCalculateGspFwHeapSize_GH100. +const GSP_FW_HEAP_SIZE_OVERRIDE_LIBOS3_BAREMETAL_MIN_MB_HOPPER :u64 =170 ; +impl GspFwHeapParams {/// Returns the amount of GSP-RM heap memory used during GSP-RM boot and initialization (up to /// and including the first client subdevice allocation). -fn base_rm_size (_chipset:Chipset ) ->u64 { -// TODO: this needs to be updated to return the correct value for Hopper+ once support for -// them is added: -// u64::from(bindings::GSP_FW_HEAP_PARAM_BASE_RM_SIZE_GH100) - u64::from (bindings::GSP_FW_HEAP_PARAM_BASE_RM_SIZE_TU10X ) +fn base_rm_size (chipset:Chipset ) ->u64 { +use crate ::gpu::Architecture ; +match chipset.arch () { +Architecture ::Hopper |Architecture ::BlackwellGB10x |Architecture ::BlackwellGB20x => { +GSP_FW_HEAP_PARAM_BASE_RM_SIZE_GH100 + } + _ => u64::from (bindings::GSP_FW_HEAP_PARAM_BASE_RM_SIZE_TU10X ), + } }/// Returns the amount of heap memory required to support a single channel allocation. -fn client_alloc_size () ->u64 { - u64::from (bindings::GSP_FW_HEAP_PARAM_CLIENT_ALLOC_SIZE ) - .align_up (GSP_HEAP_ALIGNMENT ) - .unwrap_or (u64::MAX ) +fn client_alloc_size (chipset:Chipset ) ->Result <u64 > { +use crate ::gpu::Architecture ; +let size =match chipset.arch () { +Architecture ::Hopper |Architecture ::BlackwellGB10x |Architecture ::BlackwellGB20x => { +GSP_FW_HEAP_PARAM_CLIENT_ALLOC_SIZE_GH100 + } + _ => u64::from (bindings::GSP_FW_HEAP_PARAM_CLIENT_ALLOC_SIZE ), + }; + size.align_up (GSP_HEAP_ALIGNMENT ).ok_or (EINVAL ) }/// Returns the amount of memory to reserve for management purposes for a framebuffer of size
@@ -164,12 +184,27 @@ impl LibosParams { * num::usize_as_u64(SZ_1M), }; +/// Hopper/Blackwell+ GPUs need a larger minimum heap size than the bindings specify. +/// The r570 bindings set LIBOS3_BAREMETAL_MIN_MB to 88MB, but Hopper/Blackwell+ actually +/// requires 170MB (88 + 12 + 70). +const LIBOS_HOPPER :LibosParams =LibosParams { + carveout_size: num::u32_as_u64 (bindings::GSP_FW_HEAP_PARAM_OS_SIZE_LIBOS3_BAREMETAL ), + allowed_heap_size:GSP_FW_HEAP_SIZE_OVERRIDE_LIBOS3_BAREMETAL_MIN_MB_HOPPER + * num::usize_as_u64 (SZ_1M ) + ..num::u32_as_u64 (bindings::GSP_FW_HEAP_SIZE_OVERRIDE_LIBOS3_BAREMETAL_MAX_MB ) + * num::usize_as_u64 (SZ_1M ), + }; +/// Returns the libos parameters corresponding to `chipset`. pub (crate )fn from_chipset (chipset:Chipset ) -> &'staticLibosParams { -if chipset <Chipset ::GA102 { - &Self ::LIBOS2 - }else { - &Self ::LIBOS3 +use crate ::gpu::Architecture ; +match chipset.arch () { +Architecture ::Turing => &Self ::LIBOS2 , +Architecture ::Ampere if chipset ==Chipset ::GA100 => &Self ::LIBOS2 , +Architecture ::Ampere |Architecture ::Ada => &Self ::LIBOS3 , +Architecture ::Hopper |Architecture ::BlackwellGB10x |Architecture ::BlackwellGB20x => { + &Self ::LIBOS_HOPPER + } } }
@@ -183,7 +218,7 @@ pub(crate) fn wpr_heap_size(&self, chipset: Chipset, fb_size: u64) -> Result<u64// RM boot working memory, .saturating_add(GspFwHeapParams::base_rm_size(chipset))// One RM client, - .saturating_add (GspFwHeapParams ::client_alloc_size ()) + .saturating_add (GspFwHeapParams ::client_alloc_size (chipset)?)// Overhead for memory management. .saturating_add (GspFwHeapParams ::management_overhead (fb_size)?)// Clamp to the supported heap sizes.
Signature · 1 line
2.53.0
PATCH v9 28/31 gpu: nova-core: refactor SEC2 booter loading into BooterFirmware::run()
In reply to John HubbardMove the SEC2 reset/load/boot sequence into a BooterFirmware::run() method, and call it from a thin run_booter() helper on Gsp. This is almost a pure refactoring with no behavior change, done in preparation for adding an alternative FSP boot path. The one slight difference is that an MBOX1 printing typo is fixed:
Previous output:
NovaCore 0000:e1:00.0: SEC2 MBOX0: 0x0, MBOX10x1
Fixed output:
NovaCore 0000:e1:00.0: SEC2 MBOX0: 0x0, MBOX1: 0x1
--- drivers/gpu/nova-core/firmware/booter.rs | 30 +++++++++++++++++ drivers/gpu/nova-core/gsp/boot.rs | 43 +++++++++++------------- 2 files changed, 50 insertions(+), 23 deletions(-)
drivers/gpu/nova-core/firmware/booter.rs +30 -0
@@ -8,6 +8,7 @@use kernel::{ device, + dma::Coherent , prelude::*, transmute::FromBytes ,// };
@@ -396,6 +397,35 @@ pub(crate) fn new( ucode: ucode_signed, }) } + +/// Load and run the booter firmware on SEC2. +/// +/// Resets SEC2, loads this firmware image, then boots with the WPR metadata +/// address passed via the SEC2 mailboxes. +pub (crate )fn run <T >( + &self, + dev: &device::Device <device::Bound >, + bar: &Bar0 , + sec2_falcon: &Falcon <Sec2 >, + wpr_meta: &Coherent <T >, + ) ->Result { + sec2_falcon.reset (bar)?; + sec2_falcon.load (dev, bar, self)?; +let wpr_handle = wpr_meta.dma_handle (); +let (mbox0, mbox1) = sec2_falcon.boot ( + bar, +Some (wpr_handleas u32 ), +Some ((wpr_handle >>32 )as u32 ), + )?; +dev_dbg! (dev,"SEC2 MBOX0: {:#x}, MBOX1: {:#x}\n" , mbox0, mbox1); + +if mbox0 !=0 { +dev_err! (dev,"Booter-load failed with error {:#x}\n" , mbox0); +return Err (ENODEV ); + } + +Ok (()) + } }impl FalconDmaLoadable for BooterFirmware {
drivers/gpu/nova-core/gsp/boot.rs +20 -23
61 lines not on this page · raw message
Signature · 1 line
2.53.0
PATCH v9 29/31 gpu: nova-core: Hopper/Blackwell: add GSP lockdown release polling
In reply to John HubbardOn Hopper and Blackwell, FSP boots GSP with hardware lockdown enabled. After FSP Chain of Trust completes, the driver must poll for lockdown release before proceeding with GSP initialization. Add the register bit and helper functions needed for this polling.
--- drivers/gpu/nova-core/gsp/boot.rs | 80 ++++++++++++++++++++++++++++++- drivers/gpu/nova-core/regs.rs | 1 + 2 files changed, 80 insertions(+), 1 deletion(-)
drivers/gpu/nova-core/gsp/boot.rs +79 -1
@@ -14,7 +14,8 @@ falcon::{ gsp::Gsp, sec2::Sec2, - Falcon, // + Falcon, + FalconEngine, // }, fb::FbLayout, firmware::{
@@ -43,6 +44,54 @@ vbios::Vbios, }; +/// GSP lockdown pattern written by firmware to mbox0 while RISC-V branch privilege +/// lockdown is active. The low byte varies, the upper 24 bits are fixed. +const GSP_LOCKDOWN_PATTERN :u32 =0xbadf4100 ; +const GSP_LOCKDOWN_MASK :u32 =0xffffff00 ; + +/// GSP falcon mailbox state, used to track lockdown release status. +struct GspMbox { + mbox0:u32 , + mbox1:u32 , +} + +impl GspMbox { +/// Read both mailboxes from the GSP falcon. +fn read (gsp_falcon: &Falcon <Gsp >, bar: &Bar0 ) ->Self { +Self { + mbox0: gsp_falcon.read_mailbox0 (bar), + mbox1: gsp_falcon.read_mailbox1 (bar), + } + } + +/// Returns true if the lockdown pattern is present in mbox0. +fn is_locked_down (&self) ->bool { + self.mbox0 !=0 && (self.mbox0 &GSP_LOCKDOWN_MASK ) ==GSP_LOCKDOWN_PATTERN + } + +/// Combines mailbox0 and mailbox1 into a 64-bit address. +fn combined_addr (&self) ->u64 { + (u64::from (self.mbox1) <<32 ) | u64::from (self.mbox0) + } + +/// Returns true if GSP lockdown has been released. +/// +/// Checks the lockdown pattern, validates the boot params address, +/// and verifies the HWCFG2 lockdown bit is clear. +fn lockdown_released (&self, bar: &Bar0 , fmc_boot_params_addr:u64 ) ->bool { +if self.is_locked_down () { +return false ; + } + +if self.mbox0 !=0 && self.combined_addr () != fmc_boot_params_addr { +return true ; + } + +let hwcfg2 = regs::NV_PFALCON_FALCON_HWCFG2 ::read (bar, &crate ::falcon::gsp::Gsp ::ID ); + !hwcfg2.riscv_br_priv_lockdown () + } +} +impl super ::Gsp {/// Helper function to load and run the FWSEC-FRTS firmware and confirm that it has properly /// created the WPR2 region.
@@ -147,6 +196,35 @@ fn run_booter( booter.run (dev, bar, sec2_falcon, wpr_meta) } +/// Wait for GSP lockdown to be released after FSP Chain of Trust. +#[expect(dead_code)] +fn wait_for_gsp_lockdown_release ( + dev: &device::Device <device::Bound >, + bar: &Bar0 , + gsp_falcon: &Falcon <Gsp >, + fmc_boot_params_addr:u64 , + ) ->Result { +dev_dbg! (dev,"Waiting for GSP lockdown release\n" ); + +let mbox =read_poll_timeout ( + ||Ok (GspMbox ::read (gsp_falcon, bar)), + |mbox| mbox.lockdown_released (bar, fmc_boot_params_addr), +Delta ::from_millis (10 ), +Delta ::from_secs (30 ), + ) + .inspect_err (|_| { +dev_err! (dev,"GSP lockdown release timeout\n" ); + })?; + +if mbox.mbox0 !=0 { +dev_err! (dev,"GSP-FMC boot failed (mbox: {:#x})\n" , mbox.mbox0); +return Err (EIO ); + } + +dev_dbg! (dev,"GSP lockdown released\n" ); +Ok (()) + } +/// Attempt to boot the GSP. /// /// This is a GPU-dependent and complex procedure that involves loading firmware files from
drivers/gpu/nova-core/regs.rs +1 -0
@@ -321,6 +321,7 @@ pub(crate) fn vga_workspace_addr(self) -> Option<u64> {register! (NV_PFALCON_FALCON_HWCFG2 @PFalconBase [0x000000f4 ] {10 :10 riscvas bool ;12 :12 mem_scrubbingas bool ,"Set to 0 after memory scrubbing is completed" ; +13 :13 riscv_br_priv_lockdownas bool ,"RISC-V branch privilege lockdown bit" ;31 :31 reset_readyas bool ,"Signal indicating that reset is completed (GA102+)" ; });
Signature · 1 line
2.53.0
PATCH v9 30/31 gpu: nova-core: Hopper/Blackwell: new location for PCI config mirror
In reply to John HubbardHopper and Blackwell GPUs use a different PCI config space mirror address (0x088000) compared to older architectures (0x088480). Update SetSystemInfo to accept a chipset parameter and select the correct address based on architecture.
--- drivers/gpu/nova-core/gsp/boot.rs | 2 +- drivers/gpu/nova-core/gsp/commands.rs | 8 +++++--- drivers/gpu/nova-core/gsp/fw/commands.rs | 22 +++++++++++++++++++--- 3 files changed, 25 insertions(+), 7 deletions(-)
drivers/gpu/nova-core/gsp/boot.rs +1 -1
@@ -254,7 +254,7 @@ pub(crate) fn boot(let wpr_meta =Coherent ::init (dev,GFP_KERNEL ,GspFwWprMeta ::new (&gsp_fw, &fb_layout))?; self.cmdq - .send_command_no_wait (bar, commands::SetSystemInfo ::new (pdev))?; + .send_command_no_wait (bar, commands::SetSystemInfo ::new (pdev, chipset))?; self.cmdq .send_command_no_wait (bar, commands::SetRegistry ::new ())?;
drivers/gpu/nova-core/gsp/commands.rs +5 -3
@@ -19,6 +19,7 @@use crate ::{ driver::Bar0 , + gpu::Chipset , gsp::{ cmdq::{Cmdq ,
@@ -37,12 +38,13 @@/// The `GspSetSystemInfo` command. pub (crate )struct SetSystemInfo <'a> { pdev: &'a pci::Device <device::Bound >, + chipset:Chipset , }impl <'a>SetSystemInfo <'a> {/// Creates a new `GspSetSystemInfo` command using the parameters of `pdev`. -pub (crate )fn new (pdev: &'a pci::Device <device::Bound >) ->Self { -Self { pdev } +pub (crate )fn new (pdev: &'a pci::Device <device::Bound >, chipset:Chipset ) ->Self { +Self { pdev, chipset } } }
@@ -53,7 +55,7 @@ impl<'a> CommandToGsp for SetSystemInfo<'a> {type InitError =Error ;fn init (&self) ->impl Init <Self ::Command ,Self ::InitError > { -GspSetSystemInfo ::init (self.pdev) +GspSetSystemInfo ::init (self.pdev, self.chipset) } }
drivers/gpu/nova-core/gsp/fw/commands.rs +19 -3
@@ -10,7 +10,13 @@ }, // }; -use crate ::gsp::GSP_PAGE_SIZE ; +use crate ::{ + gpu::{ +Architecture , +Chipset ,// + }, + gsp::GSP_PAGE_SIZE ,// +};use super ::bindings;
@@ -24,7 +30,10 @@ pub(crate) struct GspSetSystemInfo { impl GspSetSystemInfo { /// Returns an in-place initializer for the `GspSetSystemInfo` command. #[allow(non_snake_case)] - pub(crate) fn init<'a>(dev: &'a pci::Device<device::Bound>) -> impl Init<Self, Error> + 'a { + pub(crate) fn init<'a>( + dev: &'a pci::Device<device::Bound>, + chipset: Chipset, + ) -> impl Init<Self, Error> + 'a { type InnerGspSystemInfo = bindings::GspSystemInfo; let init_inner = try_init!(InnerGspSystemInfo { gpuPhysAddr: dev.resource_start(0)?,
@@ -35,7 +44,14 @@ pub(crate) fn init<'a>(dev: &'a pci::Device<device::Bound>) -> impl Init<Self, E// Using TASK_SIZE in r535_gsp_rpc_set_system_info() seems wrong because // TASK_SIZE is per-task. That's probably a design issue in GSP-RM though. maxUserVa: (1 << 47) - 4096, - pciConfigMirrorBase: 0x088000, +// Hopper, Blackwell, and later moved the PCI config mirror window to 0x092000. +// Older architectures continue to use the legacy window at 0x088000. + pciConfigMirrorBase: match chipset.arch() { +Architecture ::Turing |Architecture ::Ampere |Architecture ::Ada =>0x088000 , +Architecture ::Hopper + |Architecture ::BlackwellGB10x + |Architecture ::BlackwellGB20x =>0x092000 , + }, pciConfigMirrorSize: 0x001000, PCIDeviceID: (u32::from(dev.device_id()) << 16) | u32::from(dev.vendor_id().as_raw()),
Signature · 1 line
2.53.0
Alexandre Courbot
maintainerRe: [PATCH v9 30/31] gpu: nova-core: Hopper/Blackwell: new location for PCI config mirror
Quoted 4 lines · John Hubbard
Hopper and Blackwell GPUs use a different PCI config space mirror address (
0x088000) compared to older architectures (0x088480). Update SetSystemInfo to accept a chipset parameter and select the correct address based on architecture.
The offsets in the code are different from the commit log, can you double-check?
Re: [PATCH v9 30/31] gpu: nova-core: Hopper/Blackwell: new location for PCI config mirror
Quoted 8 lines · Alexandre Courbot
Quoted 4 lines · John Hubbard
Hopper and Blackwell GPUs use a different PCI config space mirror address (
0x088000) compared to older architectures (0x088480). Update SetSystemInfo to accept a chipset parameter and select the correct address based on architecture.The offsets in the code are different from the commit log, can you double-check?
I have no idea how I managed to scramble and mangle that commit log. The code diffs are the Truth here. Will fix the log.
thanks,
Signature · 1 line
John Hubbard
PATCH v9 31/31 gpu: nova-core: Hopper/Blackwell: integrate FSP boot path into boot()
In reply to John HubbardAdd the FSP boot path for Hopper and Blackwell GPUs. These architectures use FSP with FMC firmware for Chain of Trust boot, rather than SEC2.
boot() now dispatches to boot_via_sec2() or boot_via_fsp() based on architecture. The SEC2 path keeps its original command ordering. The FSP path sends SetSystemInfo/SetRegistry after GSP becomes active. The GSP sequencer only runs for SEC2-based architectures.
--- drivers/gpu/nova-core/firmware/fsp.rs | 2 - drivers/gpu/nova-core/fsp.rs | 5 - drivers/gpu/nova-core/gsp/boot.rs | 177 ++++++++++++++++++++------ 3 files changed, 139 insertions(+), 45 deletions(-)
drivers/gpu/nova-core/firmware/fsp.rs +0 -2
@@ -14,7 +14,6 @@ gpu::Chipset, // }; -#[expect(dead_code)] pub (crate )struct FspFirmware {/// FMC firmware image data (only the "image" ELF section). pub (crate ) fmc_image:DmaObject ,
@@ -23,7 +22,6 @@ pub(crate) struct FspFirmware { }impl FspFirmware { -#[expect(dead_code)] pub (crate )fn new ( dev: &device::Device <device::Bound >, chipset: Chipset,
drivers/gpu/nova-core/fsp.rs +0 -5
@@ -240,7 +240,6 @@ pub(crate) struct FmcBootArgs<'a> {impl <'a>FmcBootArgs <'a> {/// Build FMC boot arguments, allocating the DMA-coherent boot parameter /// structure that FSP will read. -#[expect(dead_code)] #[allow(clippy::too_many_arguments)] pub (crate )fn new ( dev: &device::Device<device::Bound>,
@@ -286,7 +285,6 @@ pub(crate) fn new(/// DMA address of the FMC boot parameters, needed after boot for lockdown /// release polling. -#[expect(dead_code)] pub (crate )fn boot_params_dma_handle (&self) ->u64 { self.fmc_boot_params.dma_handle () }
@@ -299,7 +297,6 @@ impl Fsp {/// /// Polls the thermal scratch register until FSP signals boot completion /// or timeout occurs. -#[expect(dead_code)] pub (crate )fn wait_secure_boot ( dev: &device::Device <device::Bound >, bar: &crate::driver::Bar0,
@@ -329,7 +326,6 @@ pub(crate) fn wait_secure_boot(/// /// Extracts real cryptographic signatures from FMC ELF32 firmware sections. /// Returns signatures in a heap-allocated structure to prevent stack overflow. -#[expect(dead_code)] pub (crate )fn extract_fmc_signatures ( dev: &device::Device <device::Bound >, fmc_fw_data: &[u8],
@@ -396,7 +392,6 @@ pub(crate) fn extract_fmc_signatures(/// /// Builds the COT message from the pre-configured [`FmcBootArgs`], sends it /// to FSP, and waits for the response. -#[expect(dead_code)] pub (crate )fn boot_fmc ( dev: &device::Device <device::Bound >, bar: &crate::driver::Bar0,
drivers/gpu/nova-core/gsp/boot.rs +139 -38
233 lines not on this page · raw message
Signature · 1 line
2.53.0
Alexandre Courbot
maintainerQuoted 2 lines
gpu: nova-core: move firmware image parsing code to
firmware.rs
gpu: nova-core: factor out anelf_str()function
These two commits pushed to drm-rust-next, thanks!
The rest will need to wait until drm-rust-next reopens as -rc6 has just been tagged.
Quoted 7 lines · Alexandre Courbot
Quoted 2 lines
gpu: nova-core: move firmware image parsing code to
firmware.rs
gpu: nova-core: factor out anelf_str()functionThese two commits pushed to drm-rust-next, thanks!
The rest will need to wait until
drm-rust-nextreopens as -rc6 has just been tagged.
Sounds good!
thanks,
Signature · 1 line
John Hubbard
Alexandre Courbot
maintainerOn Thu Mar 26, 2026 at 10:38 AM JST, John Hubbard wrote:
<snip>
Quoted 29 lines
gpu: nova-core: Hopper/Blackwell: basic GPU identification
gpu: nova-core: factor .fwsignature* selection into a new
find_gsp_sigs_section()
gpu: nova-core: use GPU Architecture to simplify HAL selections
gpu: nova-core: add Copy/Clone to Spec and Revision, addchipset()
accessor
gpu: nova-core: set DMA mask width based on GPU architecture
gpu: nova-core: Hopper/Blackwell: skip GFW boot waiting
gpu: nova-core: move firmware image parsing code tofirmware.rs
gpu: nova-core: factor out anelf_str()function
gpu: nova-core: don't assume 64-bit firmware images
gpu: nova-core: add support for 32-bit firmware images
gpu: nova-core: add auto-detection of 32-bit, 64-bit firmware images
gpu: nova-core: Hopper/Blackwell: add FMC firmware image, in support
of FSP
gpu: nova-core: Hopper/Blackwell: add FSP falcon engine stub
gpu: nova-core: Hopper/Blackwell: add FSP falcon EMEM operations
gpu: nova-core: Hopper/Blackwell: add FSP message infrastructure
rust: ptr: addconst_align_up()
gpu: nova-core: Hopper/Blackwell: calculate reserved FB heap size
gpu: nova-core: add MCTP/NVDM protocol types for firmware
communication
gpu: nova-core: Hopper/Blackwell: add FSP secure boot completion
waiting
gpu: nova-core: Hopper/Blackwell: add FMC signature extraction
gpu: nova-core: Hopper/Blackwell: add FSP send/receive messaging
gpu: nova-core: Hopper/Blackwell: add FspCotVersion type
gpu: nova-core: Hopper/Blackwell: larger non-WPR heap
gpu: nova-core: Hopper/Blackwell: add FSP Chain of Trust boot
Quoted 8 lines
gpu: nova-core: Blackwell: use correct sysmem flush registers
gpu: nova-core: make WPR heap sizing fallible
gpu: nova-core: Hopper/Blackwell: larger WPR2 (GSP) heap
gpu: nova-core: refactor SEC2 booter loading into
BooterFirmware::run()
gpu: nova-core: Hopper/Blackwell: add GSP lockdown release polling
gpu: nova-core: Hopper/Blackwell: new location for PCI config mirror
gpu: nova-core: Hopper/Blackwell: integrate FSP boot path intoboot()
A few remarks on the ordering:
- Patches 2 and 3 should come first, so the code is reorganized before we add the new architecture (and to reduce the overall diff). This also allows us to apply these patches earlier, as they are valuable regardless of Blackwell support.
- Patch 26 looks like it is independent from the rest of the series - it could have been merged earlier if it was placed at the beginning of the series.
- Same for patch 17, although the commit log mentions Blackwell (but not the code).
- The progression of the series is such that it adds new features that remain unused until the final patch which exercices the FSP boot path. We could avoid that by introducing boot_via_fsp early in the series (making it just return ENOPSUPP), and completing it as the FSP features become available. This removes a lot of dead_codes, and also provides a logical order for the patches since it can follow the flow of boot_via_fsp.
I still want to dive in depth into the messaging parts, but I think I'll keep that for next respin to avoid giving too much feedback on a single revision. :) At least we can say that the overall structure seems to be converging.
Quoted 1 line · Alexandre Courbot
On Thu Mar 26, 2026 at 10:38 AM JST, John Hubbard wrote:
...
Quoted 19 lines
A few remarks on the ordering:
- Patches 2 and 3 should come first, so the code is reorganized before we add the new architecture (and to reduce the overall diff). This also allows us to apply these patches earlier, as they are valuable regardless of Blackwell support.
- Patch 26 looks like it is independent from the rest of the series - it could have been merged earlier if it was placed at the beginning of the series.
- Same for patch 17, although the commit log mentions Blackwell (but not the code).
- The progression of the series is such that it adds new features that remain unused until the final patch which exercices the FSP boot path. We could avoid that by introducingboot_via_fspearly in the series (making it just returnENOPSUPP), and completing it as the FSP features become available. This removes a lot ofdead_codes, and also provides a logical order for the patches since it can follow the flow ofboot_via_fsp.
OK.
Quoted 4 lines
I still want to dive in depth into the messaging parts, but I think I'll keep that for next respin to avoid giving too much feedback on a single revision. :) At least we can say that the overall structure seems to be converging.
Yes, and I'll also apply SizeConstants to the series, now that it's available to us in this particular branch setup.
thanks,
Signature · 1 line
John Hubbard