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 B1AADC433F5 for ; Sat, 5 Feb 2022 00:35:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1378755AbiBEAf6 (ORCPT ); Fri, 4 Feb 2022 19:35:58 -0500 Received: from linux.microsoft.com ([13.77.154.182]:59586 "EHLO linux.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238078AbiBEAf4 (ORCPT ); Fri, 4 Feb 2022 19:35:56 -0500 Received: from [192.168.1.17] (unknown [192.182.151.181]) by linux.microsoft.com (Postfix) with ESMTPSA id 1F50820B6C61; Fri, 4 Feb 2022 16:35:56 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 1F50820B6C61 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1644021356; bh=Lxh39MUIwPoB4L77nmzR+NxgwzKfDafwt/YKb1Z9Oyk=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=IumbASqLXkb8e1ibpmpHYMvxXZidJ5avumnPKdXaqW1EVALP1PWXs640zZhYUu0pe Iep8qGZJRpsZ3BxAFIzHRdIXowRYphqso9HBcgnuPiKS4S1Em5gr2KXO1ifjDBl0wO ooC33qR8biJi7OiVtyBVNYhh5VHBksZZKQhHimkY= Message-ID: Date: Fri, 4 Feb 2022 16:35:55 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.1 Subject: Re: [PATCH v1 9/9] drivers: hv: dxgkrnl: Implement DXGSYNCFILE Content-Language: en-US To: Daniel Vetter Cc: kys@microsoft.com, haiyangz@microsoft.com, sthemmin@microsoft.com, wei.liu@kernel.org, linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org, spronovo@microsoft.com, gregkh@linuxfoundation.org, DRI Development , jenatali@microsoft.com References: From: Iouri Tarassov In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/17/2022 1:35 AM, Daniel Vetter wrote: > On Mon, Jan 17, 2022 at 9:34 AM Iouri Tarassov > wrote: > > > > > btw another idea I had over the w/e: Another option might be to allow > different backends for sync_file, and then making sure that you cannot > ever mix dma_fence and hv_dxg_fence type sync_file up (in e.g. the > merge ioctl). > > The issue is that fundamentally dma_fence and memory fences (or umf > for userspace memory fences as we tend to call them) aren't > compatible, but some of the interop plans we have is to allow stuffing > either of them into fence container objects like sync_file. So going > that route for wddm monitored fence support too could be a really > future-proof approach, plus it'd allow you to still share the > sync_file interface code. Not that it's going to be much code sharing, > since all the implementation code needs to be distinct. > -Daniel Thanks Daniel! I will remove the patch for dxgsyncfile from the next set of upstream patches. It will be added later after a re-design. Iouri 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 gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id E3878C433EF for ; Sat, 5 Feb 2022 09:37:33 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 7199310F4D7; Sat, 5 Feb 2022 09:37:32 +0000 (UTC) Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by gabe.freedesktop.org (Postfix) with ESMTP id D379110E1BB for ; Sat, 5 Feb 2022 00:35:56 +0000 (UTC) Received: from [192.168.1.17] (unknown [192.182.151.181]) by linux.microsoft.com (Postfix) with ESMTPSA id 1F50820B6C61; Fri, 4 Feb 2022 16:35:56 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 1F50820B6C61 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1644021356; bh=Lxh39MUIwPoB4L77nmzR+NxgwzKfDafwt/YKb1Z9Oyk=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=IumbASqLXkb8e1ibpmpHYMvxXZidJ5avumnPKdXaqW1EVALP1PWXs640zZhYUu0pe Iep8qGZJRpsZ3BxAFIzHRdIXowRYphqso9HBcgnuPiKS4S1Em5gr2KXO1ifjDBl0wO ooC33qR8biJi7OiVtyBVNYhh5VHBksZZKQhHimkY= Message-ID: Date: Fri, 4 Feb 2022 16:35:55 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.1 Subject: Re: [PATCH v1 9/9] drivers: hv: dxgkrnl: Implement DXGSYNCFILE Content-Language: en-US To: Daniel Vetter References: From: Iouri Tarassov In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 05 Feb 2022 09:37:31 +0000 X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: wei.liu@kernel.org, sthemmin@microsoft.com, gregkh@linuxfoundation.org, haiyangz@microsoft.com, linux-hyperv@vger.kernel.org, DRI Development , linux-kernel@vger.kernel.org, spronovo@microsoft.com, jenatali@microsoft.com, kys@microsoft.com Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On 1/17/2022 1:35 AM, Daniel Vetter wrote: > On Mon, Jan 17, 2022 at 9:34 AM Iouri Tarassov > wrote: > > > > > btw another idea I had over the w/e: Another option might be to allow > different backends for sync_file, and then making sure that you cannot > ever mix dma_fence and hv_dxg_fence type sync_file up (in e.g. the > merge ioctl). > > The issue is that fundamentally dma_fence and memory fences (or umf > for userspace memory fences as we tend to call them) aren't > compatible, but some of the interop plans we have is to allow stuffing > either of them into fence container objects like sync_file. So going > that route for wddm monitored fence support too could be a really > future-proof approach, plus it'd allow you to still share the > sync_file interface code. Not that it's going to be much code sharing, > since all the implementation code needs to be distinct. > -Daniel Thanks Daniel! I will remove the patch for dxgsyncfile from the next set of upstream patches. It will be added later after a re-design. Iouri