From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E9770C677F1 for ; Thu, 19 Jan 2023 00:43:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229748AbjASAnP (ORCPT ); Wed, 18 Jan 2023 19:43:15 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52956 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229770AbjASAnF (ORCPT ); Wed, 18 Jan 2023 19:43:05 -0500 Received: from madras.collabora.co.uk (madras.collabora.co.uk [46.235.227.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7F48659E6F for ; Wed, 18 Jan 2023 16:43:00 -0800 (PST) Received: from workpc.. (109-252-117-89.nat.spd-mgts.ru [109.252.117.89]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: dmitry.osipenko) by madras.collabora.co.uk (Postfix) with ESMTPSA id 4B0DF6600864; Thu, 19 Jan 2023 00:42:58 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1674088979; bh=y/gY+85NjTLhBn5wfhTsCF0KzUxBtwU+VsZUtinaWsM=; h=From:To:Cc:Subject:Date:From; b=ObxgNy00VQe6VFaTDvpux7dxn/S4GD77rvxR7sS5Kl5tbMGHTm3GhoMxKkBScly1c nOb27Ks5sppviP4L443OpFtU/LGRlu+dATKoB8MHGEjf9YTWtpoBUrkhBBSYs2RW/G jfVwThzYeCF1fnRGj2PQ2Muu3I+M14Agqv4O2Bd5/8HlZEMMaZIMAEaU1T8onGaail jDzVfbiMHjzhTiGxKW0wLp7/c4SscuXyM8dJq8hLH0SHQfvKUE6E0+thKYxM0NKJhL KkTYqe00PP9H1Io1r3ldlWcXopbCI3UVFJFbCbYawqcS3tkRcIGATyyvxA3sKPG09U mgFx5X8ef3VPQ== From: Dmitry Osipenko To: David Airlie , Gerd Hoffmann , Gurchetan Singh , Chia-I Wu , Daniel Vetter , Rob Clark , =?UTF-8?q?Marek=20Ol=C5=A1=C3=A1k?= Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, kernel@collabora.com, virtualization@lists.linux-foundation.org Subject: [PATCH v1 0/1] Add sync object UAPI support to VirtIO-GPU driver Date: Thu, 19 Jan 2023 03:41:42 +0300 Message-Id: <20230119004143.968942-1-dmitry.osipenko@collabora.com> X-Mailer: git-send-email 2.39.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org We have multiple Vulkan context types that are awaiting for the addition of the sync object DRM UAPI support to the VirtIO-GPU kernel driver: 1. Venus context 2. Native contexts (virtio-freedreno, virtio-intel, virtio-amdgpu) Mesa core supports DRM sync object UAPI, providing Vulkan drivers with a generic fencing implementation that we want to utilize. This patch adds initial sync objects support. It creates fundament for a further fencing improvements. Later on we will want to extend the VirtIO-GPU fencing API with passing fence IDs to host for waiting, it will be a new additional VirtIO-GPU IOCTL and more. Today we have several VirtIO-GPU context drivers in works that require VirtIO-GPU to support sync objects UAPI. The patch is heavily inspired by the sync object UAPI implementation of the MSM driver. Dmitry Osipenko (1): drm/virtio: Support sync objects drivers/gpu/drm/virtio/virtgpu_drv.c | 3 +- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 223 ++++++++++++++++++++++++- include/uapi/drm/virtgpu_drm.h | 16 +- 3 files changed, 239 insertions(+), 3 deletions(-) -- 2.39.0