linux-kernel - Re: [PATCH 3/6] gpu: nova-core: Blackwell: basic GPU identification

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: <ff7f82b7-d812-4ccf-b5c7-263f0baaac3b@nvidia.com>
Date: Tue, 18 Nov 2025 23:07:42 -0800
From: John Hubbard <jhubbard@...dia.com>
To: Dave Airlie <airlied@...il.com>, Alexandre Courbot <acourbot@...dia.com>
Cc: Timur Tabi <ttabi@...dia.com>, "dakr@...nel.org" <dakr@...nel.org>,
 "lossin@...nel.org" <lossin@...nel.org>,
 "a.hindborg@...nel.org" <a.hindborg@...nel.org>,
 "boqun.feng@...il.com" <boqun.feng@...il.com>,
 "aliceryhl@...gle.com" <aliceryhl@...gle.com>, Zhi Wang <zhiw@...dia.com>,
 "simona@...ll.ch" <simona@...ll.ch>,
 "alex.gaynor@...il.com" <alex.gaynor@...il.com>,
 "ojeda@...nel.org" <ojeda@...nel.org>, "tmgross@...ch.edu"
 <tmgross@...ch.edu>,
 "nouveau@...ts.freedesktop.org" <nouveau@...ts.freedesktop.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>, Joel Fernandes <joelagnelf@...dia.com>,
 "bhelgaas@...gle.com" <bhelgaas@...gle.com>,
 "gary@...yguo.net" <gary@...yguo.net>, Alistair Popple <apopple@...dia.com>,
 Nouveau <nouveau-bounces@...ts.freedesktop.org>
Subject: Re: [PATCH 3/6] gpu: nova-core: Blackwell: basic GPU identification

On 11/18/25 7:15 PM, Dave Airlie wrote:
> On Wed, 19 Nov 2025 at 12:46, Alexandre Courbot <acourbot@...dia.com> wrote:
...
>>> Maybe let's just do the long lists of chipsets for now...?
>>
>> Yeah, I've hit this issue as well. The compiler might remove that
>> limitation in the future, or maybe we can craft a `chipset_range!()`
>> macro that hides the messy casting, but this exhaustive listing also has
>> the benefit of forcing us to consider every critical site whenever we
>> support a new chipset so I'm actually not too bothered by it.
> 
> I wrote some macros in my nova-core-experiments, had
> chipset_before/after/range I think
> 

aha, I was afraid someone was going to say "macros" out loud, at some
point. And now you've gone and done it. :)

Well, I think we probably want:

a) The ability to clearly specify a chipset range, and

b) For extra credit, maybe: also be able to specify entire GPU
architectures, and architecture ranges.

...again, without too much extraneous noise at the call sites: the goal is
to read it easily:

     GA102..=GA104 | Architecture::Blackwell


for example. Macros are going to require that to be less clean, but
let me poke around and see.

thanks,
-- 
John Hubbard