public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <ttabi@nvidia.com>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>, Zhi Wang <zhiw@nvidia.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
	Surath Mitra <smitra@nvidia.com>,
	"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
	Andy Currid <acurrid@nvidia.com>,
	"Tarun Gupta (SW-GPU)" <targupta@nvidia.com>,
	"airlied@gmail.com" <airlied@gmail.com>,
	"zhiwang@kernel.org" <zhiwang@kernel.org>,
	"dakr@kernel.org" <dakr@kernel.org>,
	Ankit Agrawal <ankita@nvidia.com>,
	"kevin.tian@intel.com" <kevin.tian@intel.com>,
	"daniel@ffwll.ch" <daniel@ffwll.ch>, Neo Jia <cjia@nvidia.com>,
	Aniket Agashe <aniketa@nvidia.com>,
	Kirti Wankhede <kwankhede@nvidia.com>
Subject: Re: [RFC v2 10/14] vfio/nvidia-vgpu: introduce vGPU host RPC channel
Date: Wed, 3 Sep 2025 22:36:58 +0000	[thread overview]
Message-ID: <4db1511072f680aa814ee1da21c9054fdf5365e2.camel@nvidia.com> (raw)
In-Reply-To: <20250903221111.3866249-11-zhiw@nvidia.com>

On Wed, 2025-09-03 at 15:11 -0700, Zhi Wang wrote:
> +typedef struct {
> +	NvU8   vgpu_uuid[VM_UUID_SIZE];
> +	NvU32  dbdf;
> +	NvU32  driver_vm_vf_dbdf;
> +	NvU32  vgpu_device_instance_id;
> +	NvU32  vgpu_type;
> +	NvU32  vm_pid;
> +	NvU32  swizz_id;
> +	NvU32  num_channels;
> +	NvU32  num_plugin_channels;
> +	NvU32  vmm_cap;
> +	NvU32  migration_feature;
> +	NvU32  hypervisor_type;
> +	NvU32  host_cpu_arch;
> +	NvU64  host_page_size;

> +	NvBool rev1[3];
> +	NvBool enable_uvm;
> +	NvBool linux_interrupt_optimization;
> +	NvBool vmm_migration_supported;
> +	NvBool rev2;
> +	NvBool enable_console_vnc;
> +	NvBool use_non_stall_linux_events;
> +	NvBool rev3[3];

This is 12 bytes

> +	NvU16  placement_id;

This is 2 bytes, for a total of 14 so far ...


> +	NvU32  rev4;

This is misaligned.

> +	NvU32  channel_usage_threshold_percentage;
> +	NvBool rev5;
> +	NvU32  rev6;
> +	NvBool rev7;
> +} NV_VGPU_CPU_RPC_DATA_COPY_CONFIG_PARAMS;

  reply	other threads:[~2025-09-03 22:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-03 22:10 [RFC v2 00/14] Introduce NVIDIA GPU Virtualization (vGPU) Support Zhi Wang
2025-09-03 22:10 ` [RFC v2 01/14] vfio/nvidia-vgpu: introduce vGPU lifecycle management prelude Zhi Wang
2025-09-03 22:10 ` [RFC v2 02/14] vfio/nvidia-vgpu: allocate GSP RM client for NVIDIA vGPU manager Zhi Wang
2025-09-03 22:11 ` [RFC v2 03/14] vfio/nvidia-vgpu: introduce vGPU type uploading Zhi Wang
2025-09-04  9:37   ` Danilo Krummrich
2025-09-04  9:41     ` Danilo Krummrich
2025-09-04 12:15       ` Jason Gunthorpe
2025-09-04 12:45         ` Danilo Krummrich
2025-09-04 13:58           ` Jason Gunthorpe
2025-09-04 15:43       ` Zhi Wang
2025-09-06 10:34         ` Danilo Krummrich
2025-09-03 22:11 ` [RFC v2 04/14] vfio/nvidia-vgpu: allocate vGPU channels when creating vGPUs Zhi Wang
2025-09-03 22:11 ` [RFC v2 05/14] vfio/nvidia-vgpu: allocate vGPU FB memory " Zhi Wang
2025-09-03 22:11 ` [RFC v2 06/14] vfio/nvidia-vgpu: allocate mgmt heap " Zhi Wang
2025-09-03 22:11 ` [RFC v2 07/14] vfio/nvidia-vgpu: map mgmt heap when creating a vGPU Zhi Wang
2025-09-03 22:11 ` [RFC v2 08/14] vfio/nvidia-vgpu: allocate GSP RM client when creating vGPUs Zhi Wang
2025-09-03 22:11 ` [RFC v2 09/14] vfio/nvidia-vgpu: bootload the new vGPU Zhi Wang
2025-09-03 22:11 ` [RFC v2 10/14] vfio/nvidia-vgpu: introduce vGPU host RPC channel Zhi Wang
2025-09-03 22:36   ` Timur Tabi [this message]
2025-09-03 22:11 ` [RFC v2 11/14] vfio/nvidia-vgpu: introduce NVIDIA vGPU VFIO variant driver Zhi Wang
2025-09-03 22:11 ` [RFC v2 12/14] vfio/nvidia-vgpu: scrub the guest FB memory of a vGPU Zhi Wang
2025-09-03 22:11 ` [RFC v2 13/14] vfio/nvidia-vgpu: introduce vGPU logging Zhi Wang
2025-09-03 22:11 ` [RFC v2 14/14] vfio/nvidia-vgpu: add a kernel doc to introduce NVIDIA vGPU 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=4db1511072f680aa814ee1da21c9054fdf5365e2.camel@nvidia.com \
    --to=ttabi@nvidia.com \
    --cc=acurrid@nvidia.com \
    --cc=airlied@gmail.com \
    --cc=alex.williamson@redhat.com \
    --cc=aniketa@nvidia.com \
    --cc=ankita@nvidia.com \
    --cc=cjia@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=daniel@ffwll.ch \
    --cc=jgg@nvidia.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=smitra@nvidia.com \
    --cc=targupta@nvidia.com \
    --cc=zhiw@nvidia.com \
    --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