Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp4306158imu; Mon, 12 Nov 2018 08:55:26 -0800 (PST) X-Google-Smtp-Source: AJdET5f3X+YaLqLOR1NK8ayT+g+Pi60rz081zSDwZuuQtp76YjH+WTHk6nGYs3KgnjQ9xMNak3Y/ X-Received: by 2002:a65:5a05:: with SMTP id y5-v6mr1459066pgs.161.1542041726908; Mon, 12 Nov 2018 08:55:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542041726; cv=none; d=google.com; s=arc-20160816; b=Vw45nyuhuzUiuC5CHCMERVT3/J7XoRMPA1klZeQtbaxk4zTabppch+hufvHR7chs1J qUnZbpa1mBbIJG3m9Qn2ibaEtpIBY2dtdsvlRMThsZEovdIYBtnr/nBOLHhtN/hkM32Z MC40Bh4pMW5DftN/aGi6CZZDba7TghZveb4AH8r1U/8tZC9jphWxDEMEzdMxXFvpo+Fq wnu74fs102iiMr+PVqBF8PwHqyZP9/nw7ua18araADZmAdFuL3LiVwEDMDL29Nn4FBkH URiPYxqR0gPkH33AAY4eJqIYNXjDPx+HSay+zyO8fOhHh58c84HsaS1PFPFixsYQsmEH 0bfQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=1y9a/w7ynOExGR3zs17sO7dfV+dDcXKyzZGBqDB0abE=; b=ICMsOAs+3S9Xh3CGsuYCB76GITq+U56qpPcDV7xYR+EgDytBLju4+iH60+j4ueUKDb dzMHHRg+C9ZQ0gYkI/gDL+e+7IQHVTgJxXqMsrMt11H4nlQ6tTY2OxxIkLdIq/n/MAfl JicrIW9AWrtlbesiD2j0gDSjzfKpZ6vObEG9I4put9JV1gz4By/K23iGiUbTmGa5ymIa yf1aL1iaFLihPzfH7oXXYCgy/5M9WllvfFWKo4UeWOm/+N4BXCB/VaSP72lBuHc5Wdxz n1mnoiLLZXzM5rLXnIoETkRdhwr856EDDqZTVNJrtS9DgD2sBg62a4epNf0U3wcZv196 U+Lg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q21-v6si18151274plr.359.2018.11.12.08.55.11; Mon, 12 Nov 2018 08:55:26 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729674AbeKMCqN (ORCPT + 99 others); Mon, 12 Nov 2018 21:46:13 -0500 Received: from bhuna.collabora.co.uk ([46.235.227.227]:54960 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727057AbeKMCqL (ORCPT ); Mon, 12 Nov 2018 21:46:11 -0500 Received: from localhost.localdomain (unknown [IPv6:2a02:8109:92c0:207d:68ed:6b77:5dd1:d3e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: robertfoss) by bhuna.collabora.co.uk (Postfix) with ESMTPSA id BCF8F27E985; Mon, 12 Nov 2018 16:52:06 +0000 (GMT) From: Robert Foss To: airlied@linux.ie, kraxel@redhat.com, dri-devel@lists.freedesktop.org, virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, Rob Herring , Gustavo Padovan , Emil Velikov Cc: Robert Foss Subject: [PATCH v5 0/4] virgl: fence fd support Date: Mon, 12 Nov 2018 17:51:53 +0100 Message-Id: <20181112165157.32765-1-robert.foss@collabora.com> X-Mailer: git-send-email 2.17.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This series implements fence support for drm/virtio and has been tested using qemu, kmscube and the below branches. Rob Herring solved a reference counting issue and suggested a context check for the execbuf ioctl, his changes have been included in the below commits to keep the tree working at all commits. The linux series can be found here: https://gitlab.collabora.com/robertfoss/linux/commits/virtio_fences_v5 As for mesa, the branch can be found here: https://gitlab.collabora.com/robertfoss/mesa/commits/virtio_fences_v3 Changes since v4: - drm/virtio: add uapi for in and out explicit fences - Emil/Gerd: Improved commit message and fence_fd comment Changes since v3: - Rebased on drm-misc-next - drm/virtio: add virtio_gpu_alloc_fence() - Gerd: Clarified and extended commit message - Emil: Fixed whitespace issue - Emil: Changed label name from fail_fence to fail_backoff - Emil: Remove special case for !fence->drv in virtio_gpu_fence_cleanup() - drm/virtio: add uapi for in and out explicit fences - Emil: Added r-b - Emil: Move fence_fd assignment to after sanity checks - drm/virtio: add in-fences support for explicit synchronization - Move all in_fence handling to the same VIRTGPU_EXECBUF_FENCE_FD_IN block - Emil: Make sure to always call dma_fence_put() - Emil: Added r-b - drm/virtio: add out-fences support for explicit synchronization - Emil: Combine with in-fences patch - drm/virtio: bump driver version after explicit synchronization addition - Emil: Added r-b Changes since v2: - drm/virtio: add virtio_gpu_alloc_fence() - Forward port and fix compilation issues - drm/virtio: add uapi for in and out explicit fences - Check exbuf->flags for unsupported flags - drm/virtio: add in-fences support for explicit synchronization Gustavo Padovan (1): drm/virtio: bump driver version after explicit synchronization addition Robert Foss (3): drm/virtio: add virtio_gpu_alloc_fence() drm/virtio: add uapi for in and out explicit fences drm/virtio: add in/out fence support for explicit synchronization drivers/gpu/drm/virtio/virtgpu_drv.h | 8 +- drivers/gpu/drm/virtio/virtgpu_fence.c | 29 +++++-- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 108 +++++++++++++++++++++---- drivers/gpu/drm/virtio/virtgpu_plane.c | 46 +++++++++-- drivers/gpu/drm/virtio/virtgpu_vq.c | 2 +- include/uapi/drm/virtgpu_drm.h | 13 ++- 6 files changed, 173 insertions(+), 33 deletions(-) -- 2.17.1