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 99AF7C43219 for ; Tue, 8 Feb 2022 13:17:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242560AbiBHNQD (ORCPT ); Tue, 8 Feb 2022 08:16:03 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55602 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1357021AbiBHM2j (ORCPT ); Tue, 8 Feb 2022 07:28:39 -0500 Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 59776C03FECA for ; Tue, 8 Feb 2022 04:28:38 -0800 (PST) Received: by mail-ed1-x530.google.com with SMTP id w14so37156950edd.10 for ; Tue, 08 Feb 2022 04:28:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=NoHwUXlnI/2+4GtIY3B1wFAlk61LjWDTsV6HYfSmeLw=; b=jStChDdMyGG/3ayUzbTzNYlnwxLMllmGeEpkJs6CGf6RRNXXrXPhGDRdHajcPbEmqE H2DdMc34jqTdSGv+yO9e+d1+mcAZAwF0dv23gQg7pAlGRBFhHcNaiq4ABOqAXmmsuiqc zqjXzEnlHvvLUC1fv4wlOHsvBg14LJ1hMK0Oo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to; bh=NoHwUXlnI/2+4GtIY3B1wFAlk61LjWDTsV6HYfSmeLw=; b=xMv1g1Kve99cW2FxptBwLk5nGynOpm0oToOAUG+vpLwC2SI2ObIyWt0u2dCNGerEJR 3qX+aOLqy6+8huqt/7kVjXa822BkTox8NPztcUk+LNUSUl7LqQaZlmH5/+JstEchqs+A +ZmHd3jTT8a0gN2+EiDdyfzaSn0I119YK9md9f6BVtqesOo4Hk5pRdOmL5daeS2AYa6N ct43cSVNKQEoCXeAN61xsemnbAa3ZhE8PalNP6KDyD9zoYj55uzqiaifhicAm0Kpj3V6 ugm6A+JLEV5N+0zk269oTt32a3PGVYUG98+12oNxNzEy3Q1PtLPSKels4wF2cNxSndIy cdTw== X-Gm-Message-State: AOAM5326uOWZs2eO7BE29Yhy+6RIollcklUuDRSLehjPYNss14XwUMob wQHZe2kyxO+JHPHzCa/BGgYLzw== X-Google-Smtp-Source: ABdhPJz8CNq0yQJBtVXBnnXD7f1N+EwgFfAJSauIO2DyR45BhacerVDpgbvWItlXedF2YCVy901D6A== X-Received: by 2002:a05:6402:1601:: with SMTP id f1mr4223183edv.165.1644323316920; Tue, 08 Feb 2022 04:28:36 -0800 (PST) Received: from phenom.ffwll.local ([2a02:168:57f4:0:efd0:b9e5:5ae6:c2fa]) by smtp.gmail.com with ESMTPSA id ee23sm4753981edb.19.2022.02.08.04.28.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 08 Feb 2022 04:28:36 -0800 (PST) Date: Tue, 8 Feb 2022 13:28:34 +0100 From: Daniel Vetter To: Iouri Tarassov Cc: Daniel Vetter , 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 Subject: Re: [PATCH v1 9/9] drivers: hv: dxgkrnl: Implement DXGSYNCFILE Message-ID: Mail-Followup-To: Iouri Tarassov , 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: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: Linux phenom 5.10.0-8-amd64 Precedence: bulk List-ID: X-Mailing-List: linux-hyperv@vger.kernel.org On Fri, Feb 04, 2022 at 04:35:55PM -0800, Iouri Tarassov wrote: > > 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. Yeah sounds like a good plan forward to not hold up everything else meanwhile. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch