NVIDIA GPU driver infrastructure
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: "Joel Fernandes" <joel@joelfernandes.org>,
	"Alexandre Courbot" <acourbot@nvidia.com>,
	"Timur Tabi" <ttabi@nvidia.com>,
	"Alistair Popple" <apopple@nvidia.com>,
	"Eliot Courtney" <ecourtney@nvidia.com>,
	"Shashank Sharma" <shashanks@nvidia.com>,
	"Zhi Wang" <zhiw@nvidia.com>, "David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"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>,
	nova-gpu@lists.linux.dev, LKML <linux-kernel@vger.kernel.org>,
	"Joel Fernandes" <joelagnelf@nvidia.com>,
	"Will Pierce" <wpierce@nvidia.com>
Subject: Re: [PATCH 04/17] gpu: nova-core: allocate PCI MSI vector during probe
Date: Thu, 13 Aug 2026 15:29:46 -0700	[thread overview]
Message-ID: <39b44d64-928e-4d65-81d5-a06809233c99@nvidia.com> (raw)
In-Reply-To: <DKO63NHZUU47.27B9TJ6B1FB8N@kernel.org>

On 8/13/26 3:26 PM, Danilo Krummrich wrote:
> On Thu Aug 13, 2026 at 11:43 PM CEST, John Hubbard wrote:
>> On 8/13/26 2:31 PM, Danilo Krummrich wrote:
>>> On Sat Aug 8, 2026 at 5:11 AM CEST, John Hubbard wrote:
...
>>> I was about to ask if we really need to bother with MSI and shouln't just go for
>>> MSI-X only.
>>
>> I have an expensive, recent motherboard in my test machine, and it seems to only
>> expose MSI for my Turing, Ampere and Blackwell GPUs, in the non-SRIOV configuration.
>> So I'm thinking that MSI-X only would not work.
> 
> Interesting, I just checked one of my Ada and one of my Ampere GPUs and neither
> reports MSI-X in the capabilities. Other devices show up with MSI-X though...
> 
> Are we sure it's not an endpoint limitation? I really thought it's not.

I haven't really dug into it, because it seems very clear that regardless
of the answer, we need to support both MSI and MSI-X in nova-core, right?

> 
>>> But then saw that the commit message mentions broken VFIO setups; can you expand
>>> on this a bit? Which setups is the commit message referring to?
>>
>> On Zhi Wang's Big Branch of Everything, he is able to run Windows guests in a
>> vGPU VM on top of nova-core. That system requires MSI-X. And I broke it with
>> an earlier internal version of this patchset.
>>
>> That information probably leaked into my commit message here. I can remove
>> it. Because I don't think it is based on anything else.
> 
> So I guess we can also drop the INTx fallback? AFAIK SR-IOV VFs won't work with
> INTx anyway.
> 
We could drop it. It's there mainly on General Principles, not because today's
GPUs use it.

thanks,
-- 
John Hubbard


  reply	other threads:[~2026-08-13 22:29 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-08  3:11 [PATCH 00/17] nova-core: GPU interrupt support and GSP event delivery John Hubbard
2026-08-08  3:11 ` [PATCH 01/17] rust: sync: completion: add wait_for_completion_timeout() John Hubbard
2026-08-09  2:40   ` Alexandre Courbot
2026-08-09 21:43     ` John Hubbard
2026-08-08  3:11 ` [PATCH 02/17] rust: pci: expose the whole interrupt vector allocation John Hubbard
2026-08-09 13:27   ` Danilo Krummrich
2026-08-08  3:11 ` [PATCH 03/17] rust: pci: expose the allocated interrupt type John Hubbard
2026-08-09 13:24   ` Danilo Krummrich
2026-08-09 21:42     ` John Hubbard
2026-08-10 22:53       ` Danilo Krummrich
2026-08-10 22:55         ` John Hubbard
2026-08-11  3:09         ` John Hubbard
2026-08-11 23:56           ` Danilo Krummrich
2026-08-08  3:11 ` [PATCH 04/17] gpu: nova-core: allocate PCI MSI vector during probe John Hubbard
2026-08-13 21:31   ` Danilo Krummrich
2026-08-13 21:37     ` Gary Guo
2026-08-13 21:43     ` John Hubbard
2026-08-13 22:26       ` Danilo Krummrich
2026-08-13 22:29         ` John Hubbard [this message]
2026-08-13 22:37           ` Danilo Krummrich
2026-08-13 22:45             ` John Hubbard
2026-08-14 12:12   ` Danilo Krummrich
2026-08-08  3:11 ` [PATCH 05/17] gpu: nova-core: add the GIN CPU interrupt tree and MSI EOI registers John Hubbard
2026-08-13 21:42   ` Danilo Krummrich
2026-08-13 21:43     ` John Hubbard
2026-08-08  3:11 ` [PATCH 06/17] gpu: nova-core: add the GIN interrupt tree API John Hubbard
2026-08-14 12:13   ` Danilo Krummrich
2026-08-08  3:11 ` [PATCH 07/17] gpu: nova-core: add the per-architecture GIN CPU interrupt HAL John Hubbard
2026-08-08  3:11 ` [PATCH 08/17] gpu: nova-core: allocate interrupt vectors for the serviced subtrees John Hubbard
2026-08-08  3:11 ` [PATCH 09/17] gpu: nova-core: add an interrupt delivery self-test John Hubbard
2026-08-08  3:11 ` [PATCH 10/17] gpu: nova-core: dispatch GSP events instead of discarding them John Hubbard
2026-08-08  3:11 ` [PATCH 11/17] gpu: nova-core: match GSP RPC replies by sequence, not just function John Hubbard
2026-08-08  3:11 ` [PATCH 12/17] gpu: nova-core: recover the GSP receive path from corrupt framing John Hubbard
2026-08-08  3:11 ` [PATCH 13/17] gpu: nova-core: bound a GSP wait by a single deadline John Hubbard
2026-08-08  3:11 ` [PATCH 14/17] gpu: nova-core: drive GSP events with the SWGEN0 interrupt John Hubbard
2026-08-08  3:11 ` [PATCH 15/17] gpu: nova-core: retrigger the GSP falcon and clear every latched cause John Hubbard
2026-08-08  3:11 ` [PATCH 16/17] gpu: nova-core: add KUnit tests for the interrupt tree and HALs John Hubbard
2026-08-08  3:11 ` [PATCH 17/17] gpu: nova-core: document the GIN interrupt controller and GSP events 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=39b44d64-928e-4d65-81d5-a06809233c99@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=ecourtney@nvidia.com \
    --cc=gary@garyguo.net \
    --cc=joel@joelfernandes.org \
    --cc=joelagnelf@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=nova-gpu@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=shashanks@nvidia.com \
    --cc=simona@ffwll.ch \
    --cc=tmgross@umich.edu \
    --cc=ttabi@nvidia.com \
    --cc=wpierce@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