mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	<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 v3 0/1] gpu: nova-core: populate VF information in GSP_INIT
Date: Mon, 19 Oct 2026 20:16:25 +0300	[thread overview]
Message-ID: <cover.1792429308.git.zhiw@nvidia.com> (raw)

This patch supplies VF topology to GSP-RM through GSP_INIT when vGPU
mode is enabled, allowing firmware to configure per-VF interrupt and
doorbell routing.

This patch depends on the PCI extended capability and SR-IOV support
patch, which has already been merged into driver-core-testing.

To avoid conflicts with the series currently under review, this patch is
based on a local merge of driver-core-testing into drm-rust-next, with
the following series applied on top:

- GSP command-queue preparation v4 [1].
- NVKV codec v4 [2].
- Boot on the r000 GSP firmware v3 [3].
- Channel ID allocation v9 [4], with its cv! v5 prerequisite [5].

Changes since v2 [6]:
- Rebase onto the integrated base and populate VF information through
  the GSP_INIT NVKV schema.
- Use the merged PCI API's first_vf_offset() accessor and logical VF BAR
  iterator.

[1] https://lore.kernel.org/nova-gpu/20261009-cmdq-rpc-v4-0-c9ab8de1d3f2@nvidia.com/
[2] https://lore.kernel.org/nova-gpu/20261016-b4-nvkv-v4-0-e8b92b91aa5b@nvidia.com/
[3] https://lore.kernel.org/nova-gpu/20260918010719.1176945-1-jhubbard@nvidia.com/
[4] https://lore.kernel.org/nova-gpu/20260930-chid-v9-0-0d6cca376cff@nvidia.com/
[5] https://lore.kernel.org/nova-gpu/20261013-cv-v5-0-113a538dfaef@nvidia.com/
[6] https://lore.kernel.org/nova-gpu/20260804170045.902069-1-zhiw@nvidia.com/

Zhi Wang (1):
  gpu: nova-core: populate VF information in GSP_INIT

 drivers/gpu/nova-core/gsp/fw/commands.rs | 34 +++++++++++++++++++++++-
 1 file changed, 33 insertions(+), 1 deletion(-)


base-commit: a767f1cd2b0da50e0dfc48d7991f55c92369ce6f

             reply	other threads:[~2026-10-19 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 17:16 Zhi Wang [this message]
2026-10-19 17:16 ` [PATCH v3 1/1] " 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=cover.1792429308.git.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=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

all inboxes | Powered by JetHome®