From: "Eliot Courtney" <ecourtney@nvidia.com>
To: "Alexandre Courbot" <acourbot@nvidia.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>
Cc: "John Hubbard" <jhubbard@nvidia.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Timur Tabi" <ttabi@nvidia.com>,
"Eliot Courtney" <ecourtney@nvidia.com>,
"Zhi Wang" <zhiw@nvidia.com>, <nova-gpu@lists.linux.dev>,
<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 07/12] gpu: nova-core: falcon: introduce and use with_fbif_transcfg
Date: Mon, 09 Nov 2026 14:36:26 +0900 [thread overview]
Message-ID: <DMQFQH7J9JW7.15D95LXV1PZ7E@nvidia.com> (raw)
In-Reply-To: <20261107-r000-fw-v2-7-fb37cc5b20cd@nvidia.com>
On Sat Nov 7, 2026 at 6:48 PM JST, Alexandre Courbot wrote:
> From: John Hubbard <jhubbard@nvidia.com>
>
> The generic bootloader programs the FBIF aperture of its context DMA
> slot and leaves it set after the bootloader has run. The r000
> load-and-execute events will need to do the same with apertures that
> GSP-RM chooses, and should not leave them behind.
>
> Add a falcon method that programs an FBIF context DMA slot, runs a
> closure, and restores the slot's previous value once the closure has
> succeeded, and use it to run the generic bootloader. The slot used by
> FWSEC is now restored after FWSEC has halted.
>
> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
> [acourbot: extract from later patch of the r000 series, convert unneeded
> call to `update` into a `write`, only check the validity of the DMA
> context once.]
> Co-developed-by: Alexandre Courbot <acourbot@nvidia.com>
> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
> ---
> drivers/gpu/nova-core/falcon.rs | 30 ++++++++++++++++++++++++
> drivers/gpu/nova-core/firmware/gen_bootloader.rs | 28 +++++++++-------------
> 2 files changed, 41 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/gpu/nova-core/falcon.rs b/drivers/gpu/nova-core/falcon.rs
> index b17a997860ef..ad497a5704ec 100644
> --- a/drivers/gpu/nova-core/falcon.rs
> +++ b/drivers/gpu/nova-core/falcon.rs
> @@ -513,6 +513,36 @@ pub(crate) fn pio_load<F: FalconFirmware<Target = E> + FalconPioLoadable>(
> Ok(())
> }
>
> + /// Programs FBIF context DMA slot `ctx_dma` with the value that `configure` returns, runs `f`,
> + /// and restores the slot once `f` has returned `Ok`.
> + ///
> + /// The slot keeps the programmed value if `f` fails, since a falcon that `f` started and that
> + /// has not halted may still be reading through the aperture.
> + ///
> + /// # Errors
> + ///
> + /// - `EINVAL` if `ctx_dma` is not a context DMA slot that the falcon has.
> + ///
> + /// Errors from `f` are propagated as-is.
> + pub(crate) fn with_fbif_transcfg<R>(
> + &self,
> + ctx_dma: u32,
> + configure: impl FnOnce(regs::NV_PFALCON_FBIF_TRANSCFG) -> regs::NV_PFALCON_FBIF_TRANSCFG,
> + f: impl FnOnce() -> Result<R>,
> + ) -> Result<R> {
> + let transcfg =
> + regs::NV_PFALCON_FBIF_TRANSCFG::try_at(usize::from_safe_cast(ctx_dma)).ok_or(EINVAL)?;
> +
> + let saved = self.pfalcon.read(transcfg);
> + self.pfalcon.update(transcfg, configure);
optional nit: this performs an extra read of the register (can just call
`configure` on `saved`)
Reviewed-by: Eliot Courtney <ecourtney@nvidia.com>
next prev parent reply other threads:[~2026-11-09 5:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 9:47 [PATCH v2 00/12] gpu: nova-core: generic bootloader and falcon DMA changes for r000 Alexandre Courbot
2026-11-07 9:47 ` [PATCH v2 01/12] gpu: nova-core: separate the generic falcon bootloader from FWSEC Alexandre Courbot
2026-11-07 9:47 ` [PATCH v2 02/12] gpu: nova-core: falcon: widen the IMEM PIO offset to 24 bits Alexandre Courbot
2026-11-09 4:32 ` Eliot Courtney
2026-11-07 9:47 ` [PATCH v2 03/12] gpu: nova-core: place the generic bootloader at the top of IMEM Alexandre Courbot
2026-11-09 4:53 ` Eliot Courtney
2026-11-07 9:48 ` [PATCH v2 04/12] gpu: nova-core: move the bootloader DMEM descriptor out of FWSEC Alexandre Courbot
2026-11-07 9:48 ` [PATCH v2 05/12] gpu: nova-core: run the generic bootloader from its own type Alexandre Courbot
2026-11-09 4:59 ` Eliot Courtney
2026-11-07 9:48 ` [PATCH v2 06/12] rust: io: register: implement Copy and Clone for RegisterArrayLoc Alexandre Courbot
2026-11-07 13:05 ` Danilo Krummrich
2026-11-09 5:00 ` Eliot Courtney
2026-11-07 9:48 ` [PATCH v2 07/12] gpu: nova-core: falcon: introduce and use with_fbif_transcfg Alexandre Courbot
2026-11-09 5:36 ` Eliot Courtney [this message]
2026-11-07 9:48 ` [PATCH v2 08/12] gpu: nova-core: falcon: rename the local variables of dma_wr() Alexandre Courbot
2026-11-09 5:39 ` Eliot Courtney
2026-11-07 9:48 ` [PATCH v2 09/12] gpu: nova-core: falcon: allow DMEM DMA transfers to request tagging Alexandre Courbot
2026-11-09 5:47 ` Eliot Courtney
2026-11-07 9:48 ` [PATCH v2 10/12] gpu: nova-core: falcon: allow DMA transfers to read from a framebuffer address Alexandre Courbot
2026-11-07 9:48 ` [PATCH v2 11/12] gpu: nova-core: falcon: check the per-block DMA offsets for overflow Alexandre Courbot
2026-11-07 9:48 ` [PATCH v2 12/12] gpu: nova-core: falcon: program the FBIF_TRANSCFG register in dma_wr 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=DMQFQH7J9JW7.15D95LXV1PZ7E@nvidia.com \
--to=ecourtney@nvidia.com \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=dakr@kernel.org \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=ttabi@nvidia.com \
--cc=zhiw@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®