All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Gary Guo" <gary@garyguo.net>
Cc: Danilo Krummrich <dakr@kernel.org>,
	Joel Fernandes <joelagnelf@nvidia.com>,
	rust-for-linux@vger.kernel.org, nouveau@lists.freedesktop.org
Subject: Re: [PATCH v8 00/13] gpu: nova-core: add Turing support
Date: Sat, 24 Jan 2026 08:01:12 +0900	[thread overview]
Message-ID: <DFWCCFH7XXAS.2H84Y5B5E1M3D@nvidia.com> (raw)
In-Reply-To: <DFW6PEK1UDTS.3GHOOT5I32WSR@garyguo.net>

On Sat Jan 24, 2026 at 3:36 AM JST, Gary Guo wrote:
> On Thu Jan 22, 2026 at 10:28 PM GMT, Timur Tabi wrote:
>> Note: This patchset requires "[PATCH v3 2/7] rust: io: always inline
>> functions using build_assert with arguments" in order to compile
>> with CLIPPY.
>>
>> This patch set adds basic support for pre-booting GSP-RM
>> on Turing.
>>
>> There is also partial support for GA100, but it's currently not
>> fully implemented.  GA100 is considered experimental in Nouveau,
>> and so it hasn't been tested with NovaCore either.
>>
>> The latest linux-firmware.git is required because it contains the
>> Generic Bootloader image that has not yet been propogated to
>> distros.
>>
>> Summary of changes:
>>
>> 1. Introduce non-secure IMEM support.  For GA102 and later, only secure IMEM
>> is used.
>> 2. Because of non-secure IMEM, Turing booter firmware images need some of
>> the headers parsed differently for stuff like the load target address.
>> 3. Add support the tu10x firmware signature section in the ELF image.
>> 4. Add several new registers used only on Turing.
>> 5. Some functions that were considered generic Falcon operations are
>> actually different on Turing vs GA102+, so they are moved to the HAL.
>> 6. The FRTS FWSEC firmware in VBIOS uses a different version of the
>> descriptor header.
>> 7. On Turing/GA100 LIBOS args struct needs to have its 'size' field
>> aligned to 4KB.  So pad the struct to make it 4K.
>> 8. Turing Falcons do not support DMA, so PIO is used to copy images
>> into IMEM/DMEM.
>> 9. Load the Generic Bootloader from disk and use it to boot FWSEC on
>> Turing and GA100.
>>
>> Changes from v7:
>> 1. Fix unused warnings in some commits that introduce an identifier
>> but don't actually use it until a later commit.
>> 2. Split out the Generic Bootloader code from the PIO code into a
>> separate patch.
>> 3. Removed accidentally included vbios.rs.orig
>
> I've checked the Rust language aspect of the series and on the internal API
> design and it looks good. I haven't checked that the actually hardware
> operations are functioning as intended, though.
>
> Danilo/Alex, feel free to convert this to an Reviewed-by or Acked-by, whichever
> you see fit.

Gratefully adding your Reviewed-by! :) Thanks for the review.

WARNING: multiple messages have this Message-ID (diff)
From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Gary Guo" <gary@garyguo.net>
Cc: "Timur Tabi" <ttabi@nvidia.com>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"John Hubbard" <jhubbard@nvidia.com>,
	"Joel Fernandes" <joelagnelf@nvidia.com>,
	<rust-for-linux@vger.kernel.org>, <nouveau@lists.freedesktop.org>
Subject: Re: [PATCH v8 00/13] gpu: nova-core: add Turing support
Date: Sat, 24 Jan 2026 08:01:12 +0900	[thread overview]
Message-ID: <DFWCCFH7XXAS.2H84Y5B5E1M3D@nvidia.com> (raw)
In-Reply-To: <DFW6PEK1UDTS.3GHOOT5I32WSR@garyguo.net>

On Sat Jan 24, 2026 at 3:36 AM JST, Gary Guo wrote:
> On Thu Jan 22, 2026 at 10:28 PM GMT, Timur Tabi wrote:
>> Note: This patchset requires "[PATCH v3 2/7] rust: io: always inline
>> functions using build_assert with arguments" in order to compile
>> with CLIPPY.
>>
>> This patch set adds basic support for pre-booting GSP-RM
>> on Turing.
>>
>> There is also partial support for GA100, but it's currently not
>> fully implemented.  GA100 is considered experimental in Nouveau,
>> and so it hasn't been tested with NovaCore either.
>>
>> The latest linux-firmware.git is required because it contains the
>> Generic Bootloader image that has not yet been propogated to
>> distros.
>>
>> Summary of changes:
>>
>> 1. Introduce non-secure IMEM support.  For GA102 and later, only secure IMEM
>> is used.
>> 2. Because of non-secure IMEM, Turing booter firmware images need some of
>> the headers parsed differently for stuff like the load target address.
>> 3. Add support the tu10x firmware signature section in the ELF image.
>> 4. Add several new registers used only on Turing.
>> 5. Some functions that were considered generic Falcon operations are
>> actually different on Turing vs GA102+, so they are moved to the HAL.
>> 6. The FRTS FWSEC firmware in VBIOS uses a different version of the
>> descriptor header.
>> 7. On Turing/GA100 LIBOS args struct needs to have its 'size' field
>> aligned to 4KB.  So pad the struct to make it 4K.
>> 8. Turing Falcons do not support DMA, so PIO is used to copy images
>> into IMEM/DMEM.
>> 9. Load the Generic Bootloader from disk and use it to boot FWSEC on
>> Turing and GA100.
>>
>> Changes from v7:
>> 1. Fix unused warnings in some commits that introduce an identifier
>> but don't actually use it until a later commit.
>> 2. Split out the Generic Bootloader code from the PIO code into a
>> separate patch.
>> 3. Removed accidentally included vbios.rs.orig
>
> I've checked the Rust language aspect of the series and on the internal API
> design and it looks good. I haven't checked that the actually hardware
> operations are functioning as intended, though.
>
> Danilo/Alex, feel free to convert this to an Reviewed-by or Acked-by, whichever
> you see fit.

Gratefully adding your Reviewed-by! :) Thanks for the review.

  reply	other threads:[~2026-01-23 23:01 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 22:28 [PATCH v8 00/13] gpu: nova-core: add Turing support Timur Tabi
2026-01-22 22:28 ` [PATCH v8 01/13] gpu: nova-core: rename Imem to ImemSecure Timur Tabi
2026-01-22 22:28 ` [PATCH v8 02/13] gpu: nova-core: add ImemNonSecure section infrastructure Timur Tabi
2026-01-23 18:07   ` Gary Guo
2026-01-23 23:02     ` Alexandre Courbot
2026-01-23 23:02       ` Alexandre Courbot
2026-01-22 22:28 ` [PATCH v8 03/13] gpu: nova-core: support header parsing on Turing/GA100 Timur Tabi
2026-01-22 22:28 ` [PATCH v8 04/13] gpu: nova-core: add support for Turing/GA100 fwsignature Timur Tabi
2026-01-22 22:28 ` [PATCH v8 05/13] gpu: nova-core: add NV_PFALCON_FALCON_DMATRFCMD::with_falcon_mem() Timur Tabi
2026-01-22 22:28 ` [PATCH v8 06/13] gpu: nova-core: move some functions into the HAL Timur Tabi
2026-01-22 22:28 ` [PATCH v8 07/13] gpu: nova-core: Add basic Turing HAL Timur Tabi
2026-01-22 22:28 ` [PATCH v8 08/13] gpu: nova-core: add NV_PFALCON_FALCON_ENGINE::reset_engine() Timur Tabi
2026-01-22 22:28 ` [PATCH v8 09/13] gpu: nova-core: add Falcon HAL method load_method() Timur Tabi
2026-01-24  2:26   ` Alexandre Courbot
2026-01-24  2:26     ` Alexandre Courbot
2026-01-24  4:56     ` Timur Tabi
2026-01-24  4:56       ` Timur Tabi
2026-01-24 11:56       ` Miguel Ojeda
2026-01-24 11:56         ` Miguel Ojeda
2026-01-24 12:04         ` Danilo Krummrich
2026-01-24 12:04           ` Danilo Krummrich
2026-01-24 12:40       ` Alexandre Courbot
2026-01-22 22:28 ` [PATCH v8 10/13] gpu: nova-core: add FalconUCodeDescV2 support Timur Tabi
2026-01-22 22:28 ` [PATCH v8 11/13] gpu: nova-core: align LibosMemoryRegionInitArgument size to page size Timur Tabi
2026-01-23 18:14   ` Gary Guo
2026-01-23 18:41     ` Timur Tabi
2026-01-23 20:15       ` John Hubbard
2026-01-23 22:54     ` Alexandre Courbot
2026-01-23 22:54       ` Alexandre Courbot
2026-01-22 22:28 ` [PATCH v8 12/13] gpu: nova-core: add PIO support for loading firmware images Timur Tabi
2026-01-22 22:28 ` [PATCH v8 13/13] gpu: nova-core: use the Generic Bootloader to boot FWSEC Timur Tabi
2026-01-23 12:20 ` [PATCH v8 00/13] gpu: nova-core: add Turing support Danilo Krummrich
2026-01-23 12:20   ` Danilo Krummrich
2026-01-24  2:27   ` Alexandre Courbot
2026-01-24  2:27     ` Alexandre Courbot
2026-01-23 18:36 ` Gary Guo
2026-01-23 23:01   ` Alexandre Courbot [this message]
2026-01-23 23:01     ` Alexandre Courbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DFWCCFH7XXAS.2H84Y5B5E1M3D@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=joelagnelf@nvidia.com \
    --cc=nouveau@lists.freedesktop.org \
    --cc=rust-for-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.