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 B7D5CC433F5 for ; Tue, 8 Feb 2022 12:28:40 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id D890110E54A; Tue, 8 Feb 2022 12:28:39 +0000 (UTC) Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) by gabe.freedesktop.org (Postfix) with ESMTPS id 77D8A10E54A for ; Tue, 8 Feb 2022 12:28:38 +0000 (UTC) Received: by mail-ed1-x534.google.com with SMTP id co28so10028992edb.1 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=6FEB8ssb7ho5c+GJb/ID99jphmYpHbV95xeZ/z6HY0ZWFQCrR2j/fzaIeI8C2jWXNj IMi8fVUXvbxJrbEibpJLatMH/I05nwn1YGuJn8jOQk+gNMkGsElbz3FnR/qavX2QrA/Y ooiPR0vV5PiV64n9up5dsjW1y71dbLXCGnuAuDvqS8gPEBOSLcvvzUUYxJGZ9L4ydZRD unaiU3Cnt2MTuu+JKBTys1om3KvblK7BNbYmydhlMnZqIR/GQImj9sz/rW0Csk/GcQmn FLK/WgX0vpNID5vH+I2R5SMcU99SO1uoiFmqijgw5+1Nj/jipXtehp6MSNAgRepP6LNI /Sgg== X-Gm-Message-State: AOAM531ndw1T62x1C1YCtnukaF0GF6uW3gwnswZ0iGcJrqwS0v+aUqmb 5gXvNG1Fijz5vrB14YgcFEw3dg== 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 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 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: linux-hyperv@vger.kernel.org, sthemmin@microsoft.com, gregkh@linuxfoundation.org, haiyangz@microsoft.com, wei.liu@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 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 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 EB1E2C433FE for ; Tue, 8 Feb 2022 13:15:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233541AbiBHNP1 (ORCPT ); Tue, 8 Feb 2022 08:15:27 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55600 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238900AbiBHM2j (ORCPT ); Tue, 8 Feb 2022 07:28:39 -0500 Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4B8CEC03FEC0 for ; Tue, 8 Feb 2022 04:28:38 -0800 (PST) Received: by mail-ed1-x533.google.com with SMTP id eg42so21333213edb.7 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=oeGoQwBfym5nrKhM2fdEsJEPVhu1trDG35IKZf+ZkP0vtgToJuAIURclHUDBHd93PW QlPaTcuGMBStlIWwjBl4V3rDZb/vZyoI1k+PQRmD8RwPB5f6eJnAKek1rHj55bUw0TB0 bNA8Zt+NM0SfSha7bruwseFHlcveo3LMmendil8cmEs/vYdiMXyyyor+t+rITPCtdw9o rIiaVA86jBhgfUETBtsKzg+NjRVr+DPI9eXT9iiW92KQFutX7uPKGbvesQzMLKghfptW 80p3kr1oI5Fx4HnZzVSSgoBoPXzv2dI7rv1fWKsPGMK6rmSTeB7SdsswKtJio5zdKxvF /Bkg== X-Gm-Message-State: AOAM533+CQ2LgV57bMcawqDGMwCE+x9bcevtVYnUAWphcZuyFsKhAt7h 8Gnq4L+joalM1WVFkGRFEpUsp9G/yR0nlA== 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-kernel@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