From: Julia Zhang <julia.zhang@amd.com>
To: David Airlie <airlied@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Gurchetan Singh <gurchetansingh@chromium.org>,
Chia-I Wu <olvaffe@gmail.com>, <dri-devel@lists.freedesktop.org>,
<virtualization@lists.linux-foundation.org>,
Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
<xen-devel@lists.xenproject.org>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Chen Jiqian" <Jiqian.Chen@amd.com>,
"Huang Rui" <ray.huang@amd.com>,
"Penny Zheng" <penny.zheng@amd.com>,
"Zhu Lingshan" <Lingshan.Zhu@amd.com>,
"Anthony PERARD" <anthony.perard@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Jan Beulich" <jbeulich@suse.com>, "Paul Durrant" <paul@xen.org>,
"Julia Zhang" <julia.zhang@amd.com>
Subject: [PATCH 0/3] virtgpu: check if P2P is possiable or not
Date: Sat, 7 Dec 2024 18:50:20 +0800 [thread overview]
Message-ID: <20241207105023.542399-1-julia.zhang@amd.com> (raw)
To implement dGPU prime feature, virtgpu needs to import/export buffer
between virtio iGPU and passthrough dGPU. Before that, virtgpu should
check if P2P is possible or not. But calling function pci_p2pdma_distance
in guest VM will only get virtual p2pdma_distance instead of real physical
p2pdma_distance.
So this series introduce an implementation of virtgpu device_attach
callback to get p2pdma_distance. And also adds a new virtgpu command to
pass PCI notations from guest to host and a new xen privcmd to get physical
p2pdma_distance according to the PCI notations in host.
Julia Zhang (3):
xen:get p2pdma_distance
virtgpu: get p2pdma_distance
drm/virtio: Implement device_attach
drivers/gpu/drm/virtio/virtgpu_drv.h | 17 ++++++++
drivers/gpu/drm/virtio/virtgpu_prime.c | 59 +++++++++++++++++++++++++-
drivers/gpu/drm/virtio/virtgpu_vq.c | 53 +++++++++++++++++++++++
drivers/xen/privcmd.c | 42 ++++++++++++++++++
include/uapi/linux/virtio_gpu.h | 19 +++++++++
include/uapi/xen/privcmd.h | 12 ++++++
6 files changed, 201 insertions(+), 1 deletion(-)
--
2.34.1
next reply other threads:[~2024-12-07 10:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 10:50 Julia Zhang [this message]
2024-12-07 10:50 ` [PATCH 1/3] xen:get p2pdma_distance Julia Zhang
2024-12-07 10:50 ` [PATCH 2/3] virtgpu: get p2pdma_distance Julia Zhang
2024-12-07 10:50 ` [PATCH 3/3] drm/virtio: Implement device_attach Julia Zhang
2024-12-09 12:28 ` Christian König
2024-12-12 7:43 ` [PATCH 0/3] virtgpu: check if P2P is possiable or not Juergen Gross
2024-12-13 9:58 ` Zhang, Julia
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=20241207105023.542399-1-julia.zhang@amd.com \
--to=julia.zhang@amd.com \
--cc=Jiqian.Chen@amd.com \
--cc=Lingshan.Zhu@amd.com \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=anthony.perard@citrix.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=kraxel@redhat.com \
--cc=oleksandr_tyshchenko@epam.com \
--cc=olvaffe@gmail.com \
--cc=paul@xen.org \
--cc=penny.zheng@amd.com \
--cc=ray.huang@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xenproject.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