[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240110095627.227454-1-julia.zhang@amd.com>
Date: Wed, 10 Jan 2024 17:56:26 +0800
From: Julia Zhang <julia.zhang@....com>
To: Gurchetan Singh <gurchetansingh@...omium.org>, Chia-I Wu
<olvaffe@...il.com>, David Airlie <airlied@...hat.com>, Gerd Hoffmann
<kraxel@...hat.com>, <linux-kernel@...r.kernel.org>,
<dri-devel@...ts.freedesktop.org>, <amd-gfx@...ts.freedesktop.org>,
<virtualization@...ts.linux-foundation.org>
CC: Alex Deucher <alexander.deucher@....com>,
Christian König <christian.koenig@....com>, Daniel Vetter
<daniel@...ll.ch>, David Airlie <airlied@...il.com>, Erik Faye-Lund
<kusmabite@...il.com>, Marek Olšák
<marek.olsak@....com>, Pierre-Eric Pelloux-Prayer
<pierre-eric.pelloux-prayer@....com>, Honglei Huang <honglei1.huang@....com>,
Chen Jiqian <Jiqian.Chen@....com>, Huang Rui <ray.huang@....com>, Julia Zhang
<julia.zhang@....com>
Subject: [PATCH 0/1] Implement device_attach for virtio gpu
To realize dGPU prime feature for virtio gpu, we are trying let dGPU import
vram object of virtio gpu. But this feature would finally call function
virtio_dma_buf_ops.device_attach(), which was set as drm_gem_map_attach().
drm_gem_map_attach() requires drm_gem_object_funcs.get_sg_table to be
implemented, or else return ENOSYS. But virtio gpu driver has not
implemented it for vram object and actually vram object does not require
it. So this add a new implementation of device_attach() to call
drm_gem_map_attach() for shmem object and return 0 for vram object as it
actually did before the requirement was added.
Julia Zhang (1):
drm/virtio: Implement device_attach
drivers/gpu/drm/virtio/virtgpu_prime.c | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
--
2.34.1
Powered by blists - more mailing lists