From: Zhi Wang <zhiw@nvidia.com>
To: <dakr@kernel.org>, <acourbot@nvidia.com>
Cc: <airlied@gmail.com>, <simona@ffwll.ch>, <ojeda@kernel.org>,
<alex.gaynor@gmail.com>, <boqun.feng@gmail.com>,
<gary@garyguo.net>, <bjorn3_gh@protonmail.com>,
<lossin@kernel.org>, <a.hindborg@kernel.org>,
<aliceryhl@google.com>, <tmgross@umich.edu>,
<jhubbard@nvidia.com>, <ecourtney@nvidia.com>,
<joelagnelf@nvidia.com>, <apopple@nvidia.com>, <cjia@nvidia.com>,
<smitra@nvidia.com>, <kjaju@nvidia.com>, <alkumar@nvidia.com>,
<ankita@nvidia.com>, <aniketa@nvidia.com>, <kwankhede@nvidia.com>,
<targupta@nvidia.com>, <nova-gpu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, <zhiwang@kernel.org>,
Zhi Wang <zhiw@nvidia.com>
Subject: [PATCH v2 0/1] gpu: nova-core: populate GSP_VF_INFO for vGPU
Date: Tue, 4 Aug 2026 20:00:44 +0300 [thread overview]
Message-ID: <20260804170045.902069-1-zhiw@nvidia.com> (raw)
This is v2 of a follow-up to the "Boot GSP with vGPU enabled" series
[1]. It provides GSP-RM with the VF topology required for per-VF
interrupt and doorbell event routing.
When vGPU mode is enabled, GspSetSystemInfo reads the SR-IOV topology
through the typed Rust PCI capability API and fills the embedded
GSP_VF_INFO. When vGPU mode is disabled, the structure remains zeroed.
This series depends on the separately posted "[PATCH v7 0/1] Rust PCI
capability infrastructure and SR-IOV support" series [3], which provides
the capability finder and VF BAR iterator used here. The prerequisite
patch ID below identifies the exact dependency used to prepare this
version.
Changes since v1 [2]:
- Adapted to the v7 Rust PCI API by handling the optional capability
result and consuming the logical VF BAR iterator. (Zhi)
- Made the VF information builder an associated function of
GspSetSystemInfo. (Danilo [4])
- Removed the unrelated GpuacctPerfmonUtilSamples registration. (Zhi)
- Rebased onto the latest drm-rust-next. (Zhi)
[1] https://lore.kernel.org/nova-gpu/20260709150206.1046839-1-zhiw@nvidia.com/
[2] https://lore.kernel.org/nova-gpu/20260730181404.776028-1-zhiw@nvidia.com/
[3] https://lore.kernel.org/rust-for-linux/20260804161612.776752-1-zhiw@nvidia.com/
[4] https://lore.kernel.org/nova-gpu/DKC83N1YHAGM.3BRAAMYUVIL4Y@kernel.org/
Zhi Wang (1):
gpu: nova-core: populate GSP_VF_INFO when vGPU is enabled
drivers/gpu/nova-core/gsp/boot.rs | 6 ++--
drivers/gpu/nova-core/gsp/commands.rs | 15 ++++++++--
drivers/gpu/nova-core/gsp/fw/commands.rs | 37 +++++++++++++++++++++++-
3 files changed, 52 insertions(+), 6 deletions(-)
base-commit: 44e7e7f7cffb10a93bb88e7cb59b7b8b3e2deb1c
prerequisite-patch-id: 4ff67e7d1ab069e291277346b23a5a195e751cff
--
2.53.0
next reply other threads:[~2026-08-04 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 17:00 Zhi Wang [this message]
2026-08-04 17:00 ` [PATCH v2 1/1] gpu: nova-core: populate GSP_VF_INFO when vGPU is enabled Zhi Wang
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=20260804170045.902069-1-zhiw@nvidia.com \
--to=zhiw@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=alkumar@nvidia.com \
--cc=aniketa@nvidia.com \
--cc=ankita@nvidia.com \
--cc=apopple@nvidia.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=cjia@nvidia.com \
--cc=dakr@kernel.org \
--cc=ecourtney@nvidia.com \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=joelagnelf@nvidia.com \
--cc=kjaju@nvidia.com \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=simona@ffwll.ch \
--cc=smitra@nvidia.com \
--cc=targupta@nvidia.com \
--cc=tmgross@umich.edu \
--cc=zhiwang@kernel.org \
/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