From: John Hubbard <jhubbard@nvidia.com>
To: Eliot Courtney <ecourtney@nvidia.com>,
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: Alistair Popple <apopple@nvidia.com>,
Timur Tabi <ttabi@nvidia.com>,
nova-gpu@lists.linux.dev, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v5 7/7] gpu: nova-core: run Booter Unloader and FWSEC-SB upon unbinding
Date: Mon, 18 May 2026 19:42:05 -0700 [thread overview]
Message-ID: <b5fb1462-c409-4ddc-a6c4-a83dcfaeae63@nvidia.com> (raw)
In-Reply-To: <DIMAVKJECLKH.UXLZASCKVJK0@nvidia.com>
On 5/18/26 7:33 PM, Eliot Courtney wrote:
> On Fri May 15, 2026 at 3:12 PM JST, Alexandre Courbot wrote:
...
>> @@ -129,6 +130,7 @@ pub(crate) fn unload(
>> dev: &device::Device<device::Bound>,
>> bar: &Bar0,
>> gsp_falcon: &Falcon<Gsp>,
>> + sec2_falcon: &Falcon<Sec2>,
>> ) -> Result {
>> // Shut down the GSP.
>> Self::shutdown_gsp(
>> @@ -139,6 +141,18 @@ pub(crate) fn unload(
>> )
>> .inspect_err(|e| dev_err!(dev, "Unload guest driver failed: {:?}\n", e))?;
>
> Suppose that shutdown_gsp fails. In that case, we early return and don't
> try to reset. Is that the correct behaviour? Maybe we still want to try
> to reset even though shutdown didn't work. OpenRM looks like it still
> tries the reset even if shutdown fails.
For shutdown and teardown paths, a counter-intuitive bit of lore
exists, which is, as suggested above: try to tear everything down,
even if one part of the teardown fails. Just soldier on.
Sorry for the drive by comment. I have many reviews that I need to
*properly* get done and haven't yet. But this is worth pointing
out because it is such a common pitfall.
thanks,
--
John Hubbard
next prev parent reply other threads:[~2026-05-19 2:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 6:12 [PATCH v5 0/7] gpu: nova-core: run unload sequence " Alexandre Courbot
2026-05-15 6:12 ` [PATCH v5 1/7] gpu: nova-core: remove unneeded get_gsp_info proxy function Alexandre Courbot
2026-05-15 6:12 ` [PATCH v5 2/7] gpu: nova-core: do not import firmware commands into GSP command module Alexandre Courbot
2026-05-15 6:12 ` [PATCH v5 3/7] gpu: nova-core: send UNLOADING_GUEST_DRIVER GSP command upon unloading Alexandre Courbot
2026-05-15 6:12 ` [PATCH v5 4/7] gpu: nova-core: refactor SEC2 booter loading into BooterFirmware::run() Alexandre Courbot
2026-05-15 6:12 ` [PATCH v5 5/7] gpu: nova-core: gsp: shuffle boot code a bit to keep chipset-specific parts close Alexandre Courbot
2026-05-15 6:12 ` [PATCH v5 6/7] gpu: nova-core: gsp: move chipset-specific parts of the boot process into a HAL Alexandre Courbot
2026-05-19 1:32 ` Eliot Courtney
2026-05-15 6:12 ` [PATCH v5 7/7] gpu: nova-core: run Booter Unloader and FWSEC-SB upon unbinding Alexandre Courbot
2026-05-19 2:33 ` Eliot Courtney
2026-05-19 2:42 ` John Hubbard [this message]
2026-05-21 11:03 ` Alexandre Courbot
2026-05-21 13:04 ` Eliot Courtney
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=b5fb1462-c409-4ddc-a6c4-a83dcfaeae63@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ecourtney@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 \
/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
Powered by JetHome