nouveau.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: "Alexandre Courbot" <acourbot@nvidia.com>,
	"Joel Fernandes" <joelagnelf@nvidia.com>,
	"Timur Tabi" <ttabi@nvidia.com>,
	"Alistair Popple" <apopple@nvidia.com>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	nouveau@lists.freedesktop.org, linux-pci@vger.kernel.org,
	rust-for-linux@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	"Elle Rhumsaa" <elle@weathered-steel.dev>
Subject: Re: [PATCH v5 3/4] gpu: nova-core: avoid probing non-display/compute PCI functions
Date: Thu, 21 Aug 2025 09:54:41 -0700	[thread overview]
Message-ID: <753aa207-a2ed-4836-9525-5fbf68aff6ef@nvidia.com> (raw)
In-Reply-To: <DC81S5SN8N76.YH4323TLNHJK@kernel.org>

On 8/21/25 3:52 AM, Danilo Krummrich wrote:
> On Thu Aug 21, 2025 at 6:42 AM CEST, John Hubbard wrote:
>> NovaCore has so far been too imprecise about figuring out if .probe()
>> has found a supported PCI PF (Physical Function). By that I mean:
>> .probe() sets up BAR0 (which involves a lot of very careful devres and
>> Device<Bound> details behind the scenes). And then if it is dealing with
>> a non-supported device such as the .1 audio PF on many GPUs, it fails
>> out due to an unexpected BAR0 size. We have been fortunate that the BAR0
>> sizes are different.
>>
>> Really, we should be filtering on PCI class ID instead. These days I
>> think we can confidently pick out Nova's supported PF's via PCI class
>> ID. And if not, then we'll revisit.
>>
>> The approach here is to filter on "Display VGA" or "Display 3D", which
>> is how PCI class IDs express "this is a modern GPU's PF".
>>
>> Cc: Danilo Krummrich <dakr@kernel.org>
>> Cc: Alexandre Courbot <acourbot@nvidia.com>
>> Cc: Elle Rhumsaa <elle@weathered-steel.dev>
>> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
>> ---
>>   drivers/gpu/nova-core/driver.rs | 33 ++++++++++++++++++++++++++++-----
>>   rust/kernel/pci.rs              | 21 +++++++++++++++++++++
> 
> Can you please split this one up in two patches?

Sure.

> 
>>   2 files changed, 49 insertions(+), 5 deletions(-)

thanks,
-- 
John Hubbard


  reply	other threads:[~2025-08-21 16:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21  4:42 [PATCH v5 0/4] rust, nova-core: PCI Class, Vendor support John Hubbard
2025-08-21  4:42 ` [PATCH v5 1/4] rust: pci: provide access to PCI Class and Class-related items John Hubbard
2025-08-21 10:51   ` Danilo Krummrich
2025-08-21 16:54     ` John Hubbard
2025-08-21  4:42 ` [PATCH v5 2/4] rust: pci: provide access to PCI Vendor values John Hubbard
     [not found]   ` <aKznsxvFqW_2jJkv@archiso>
2025-08-26 19:25     ` John Hubbard
2025-08-21  4:42 ` [PATCH v5 3/4] gpu: nova-core: avoid probing non-display/compute PCI functions John Hubbard
2025-08-21 10:52   ` Danilo Krummrich
2025-08-21 16:54     ` John Hubbard [this message]
2025-08-21  4:42 ` [PATCH v5 4/4] rust: pci: use pci::Vendor instead of bindings::PCI_VENDOR_ID_* John Hubbard

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=753aa207-a2ed-4836-9525-5fbf68aff6ef@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=airlied@gmail.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=apopple@nvidia.com \
    --cc=bhelgaas@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=elle@weathered-steel.dev \
    --cc=gary@garyguo.net \
    --cc=joelagnelf@nvidia.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tmgross@umich.edu \
    --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;
as well as URLs for NNTP newsgroup(s).