Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp835568imu; Mon, 5 Nov 2018 09:27:14 -0800 (PST) X-Google-Smtp-Source: AJdET5fQoWw7dY7L+9dhGBIN607QBnVnV1rv2p8meT+wPmAgIl/i0Ko0eZdTBZV2NJNl7qDUXu5d X-Received: by 2002:a17:902:5a09:: with SMTP id q9-v6mr23156178pli.186.1541438833952; Mon, 05 Nov 2018 09:27:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541438833; cv=none; d=google.com; s=arc-20160816; b=QFOvtXuL6GTnbI/6xNvrYhfGcQUZ/qo8XudyBNo7plcDo3Id1MUF/gyXIdGorFkWbZ pNiBf33P8wwsNFcJb6BrUYdSiB85snnqPZZ2TNPat+PRtUhuMSgZHrnQ8I0ehu1pzbJ2 Ih35SQ/RU/IUDxRoo5BeA0Qb5g8SGCmCbCS3LQzo3HfUCw5tyvVtOCFFKvft2U8w77C1 3XxkcPInaAgF7bvOlGLnekadCv6LBk5SXG4NZIbdlKYMj35c8Qt8PFrSG8WVxnZfeM4o bek88Ec7MElV1/40YZ+3AiJfNlpK+bxPiEaI8CL8QBpGDIAbu2p1YCm0lO0jy1QOblpj Sm5w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=/rPtXWdr9zPsS89v3neMnANv2NEkrpY/+jwT1FPed3g=; b=AqTUS+ep/MHyiPBitxGQX2LZQz8OXanJr7TNibywtyrQpx1mW1N28C1CQQySrYucAu ysAFkhZgPA1zqOlwcEcMPFtTGja/N5mZWRGALBJGMfryZ8IAmOeTSZhi5vdPXhzkYP/R linS73lLppvD2AQ0mGPo3f4gL4s6bg0YMhv0Ez+ziE38Qp6PrN07gLxgtfdq5mwzrNeL or7v9nPEuYJ9W0RNmzdvIBPvr3mSPnTBvC0YZruCBTj64R6DxUhhnF23kVNAWdM5iAba 5EC2I1Bo4ZrFMU2BxSWX8alUChu1ZGu+UwF3OiXPKnSyjt7C8kadFeAlEgNb/z84cVSw 7+3Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=nu7ySlQ+; 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=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e12-v6si43029624pfi.271.2018.11.05.09.26.57; Mon, 05 Nov 2018 09:27:13 -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; dkim=pass header.i=@gmail.com header.s=20161025 header.b=nu7ySlQ+; 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=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729945AbeKFCrM (ORCPT + 99 others); Mon, 5 Nov 2018 21:47:12 -0500 Received: from mail-vs1-f65.google.com ([209.85.217.65]:43768 "EHLO mail-vs1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729748AbeKFCrM (ORCPT ); Mon, 5 Nov 2018 21:47:12 -0500 Received: by mail-vs1-f65.google.com with SMTP id k14so5576866vsm.10 for ; Mon, 05 Nov 2018 09:26:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/rPtXWdr9zPsS89v3neMnANv2NEkrpY/+jwT1FPed3g=; b=nu7ySlQ+rz1nebXK1+aAg8vpZ1DYji3T9SWSFBMcvZ5ibyXBeIwEC0ZaQL+R2b3LfI fUpGemHu1cauPlJOM1eq/2snCWD7i/A6Rb5zA7G2iPDWB1OIDBaYhYat1uTdsmXbpEsU +fMMah/f4icoAOyhg6L+kQAymfaWN+v3Gy5crz7obtX6IgLvgFqFXoX3CNhCHqZctGBr LhlCoqzpyC9AjeoutilpOwMsT7A9cg2cFSxb9oj9lwCJD5Y7jVVLipzZ7Fwsu5oWVFmr pdUfyLLX24TiipupsMBb2PimX28B1TPOVvxUPXVEwMRQIDQPOz/PnVzqGiGg9Hp2zsCW guJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/rPtXWdr9zPsS89v3neMnANv2NEkrpY/+jwT1FPed3g=; b=pew+C5a3VV7lwsuS3nLv0Hd44oYqkQUyewaWIDG/0wQnCxnWh+nYufoNRoMoRn2B3Q iqwdeW39oOpW8hbdyIfs3pWFfPn2DtsU9tGHT5ZgNT5v5HwET3MG0lCSzOtWdq75qqiJ zKK22aJIgYvrvVkvplzOTGhaDJw/7/cZwezYtKVVYsQJj7M7Pe209aGv0SCi5yabppFQ G7ZxmsxzWl1PBJB5GgaO2J3lYDfzlREZ/htEn7g1OKOxC3WNDHia1enkWsB5ZqqlpgUE IHQOUC/aV0twBcRp4hA+j0nWXVcYVh7ll2qmjerUaQKUx6P87hCBvoEW1ZopHpsiAfgf /hMQ== X-Gm-Message-State: AGRZ1gLKuEYoXL5DU0c47wMZHTCa437Qt0HqrrK6CU1C28djErtfB4Bo hwQ5UItd3MfRzTIOa3ZOPbgA0IH19yeSKwGjpB+L1fZj X-Received: by 2002:a67:3144:: with SMTP id x65mr9772343vsx.186.1541438789530; Mon, 05 Nov 2018 09:26:29 -0800 (PST) MIME-Version: 1.0 References: <20181105114152.2088-1-robert.foss@collabora.com> <20181105114152.2088-4-robert.foss@collabora.com> In-Reply-To: <20181105114152.2088-4-robert.foss@collabora.com> From: Emil Velikov Date: Mon, 5 Nov 2018 17:25:05 +0000 Message-ID: Subject: Re: [PATCH v4 3/4] drm/virtio: add in/out fence support for explicit synchronization To: Robert Foss Cc: David Airlie , Gerd Hoffmann , ML dri-devel , "open list:VIRTIO GPU DRIVER" , "Linux-Kernel@Vger. Kernel. Org" , Rob Herring , Gustavo Padovan , Emil Velikov Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 5 Nov 2018 at 11:42, Robert Foss wrote: > > When the execbuf call receives an in-fence it will get the dma_fence > related to that fence fd and wait on it before submitting the draw call. > > On the out-fence side we get fence returned by the submitted draw call > and attach it to a sync_file and send the sync_file fd to userspace. On > error -1 is returned to userspace. > > Signed-off-by: Gustavo Padovan > Signed-off-by: Robert Foss > Suggested-by: Rob Herring > Reviewed-by: Emil Velikov > --- > > Changes since v3: > - Move all in_fence handling to the same VIRTGPU_EXECBUF_FENCE_FD_IN block Fwiw my suggestion was to explicitly document whether the IOCTL can support, simultaneously, IN and OUT fence. Merging the two patches makes things a bit meh. But as before - it's for Gerd to make the final call. -Emil