linux-kernel - Re: [PATCH v3 2/2] gpu: nova-core: add boot42 support for next-gen GPUs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <18f013a69371ecd86783d09f73c7fb66d860e7df.camel@nvidia.com>
Date: Thu, 30 Oct 2025 14:22:27 +0000
From: Timur Tabi <ttabi@...dia.com>
To: "dakr@...nel.org" <dakr@...nel.org>, John Hubbard <jhubbard@...dia.com>
CC: "lossin@...nel.org" <lossin@...nel.org>, "a.hindborg@...nel.org"
	<a.hindborg@...nel.org>, "boqun.feng@...il.com" <boqun.feng@...il.com>, Zhi
 Wang <zhiw@...dia.com>, "simona@...ll.ch" <simona@...ll.ch>,
	"tmgross@...ch.edu" <tmgross@...ch.edu>, "alex.gaynor@...il.com"
	<alex.gaynor@...il.com>, "nouveau@...ts.freedesktop.org"
	<nouveau@...ts.freedesktop.org>, "ojeda@...nel.org" <ojeda@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"rust-for-linux@...r.kernel.org" <rust-for-linux@...r.kernel.org>,
	"bjorn3_gh@...tonmail.com" <bjorn3_gh@...tonmail.com>, Edwin Peer
	<epeer@...dia.com>, "airlied@...il.com" <airlied@...il.com>,
	"aliceryhl@...gle.com" <aliceryhl@...gle.com>, "bhelgaas@...gle.com"
	<bhelgaas@...gle.com>, Joel Fernandes <joelagnelf@...dia.com>, Alexandre
 Courbot <acourbot@...dia.com>, "gary@...yguo.net" <gary@...yguo.net>,
	Alistair Popple <apopple@...dia.com>
Subject: Re: [PATCH v3 2/2] gpu: nova-core: add boot42 support for next-gen
 GPUs

On Wed, 2025-10-29 at 22:30 -0700, John Hubbard wrote:
> However, I don't want anyone to have to risk reading boot42 on some
> ancient GPU (earlier than Fermi, even), with uncertain results.
> 
> And our HW team has promised to leave behind arch0==0, arch1==1 in
> in boot0, more or less forever, specifically to help us out here.
> 
> With that in mind, I *do* want to read boot0 for the forseeable future,
> as a guide to whether to look at boot42. I really think that is the
> way to thread the needle here.

Sure, and this is exactly what is_ancient_gpu() does.  It tells you whether to use boot42
instead of boot0.  It is the only function that looks at boot0.