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 X-Spam-Level: X-Spam-Status: No, score=1.0 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5B9B3C433B4 for ; Tue, 27 Apr 2021 12:50:22 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id 103E460E09 for ; Tue, 27 Apr 2021 12:50:22 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 103E460E09 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 4FF3E6E96A; Tue, 27 Apr 2021 12:50:17 +0000 (UTC) Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) by gabe.freedesktop.org (Postfix) with ESMTPS id 0E45A6E087; Tue, 27 Apr 2021 12:50:16 +0000 (UTC) Received: by mail-ej1-x629.google.com with SMTP id t4so6039594ejo.0; Tue, 27 Apr 2021 05:50:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=jY87nJkTrAkIMXhmw+c4zxTY+My2zdoG2SvKbZwcYmc=; b=c9rEeJuD0yyZBGtyZF4sKBOqq18PcgqpRMKwbD2xt9ws4Xn/mQQLA7VB44xKgpFRHO TR30DoQA/Vk6pbbZr2GYrGiJQ5HJukWomKDOQ0y6DwoV8CU95ecj+AabMTsbHwTwOBFW awuvGI+yiK2lZejB5SNB7vwGdjSCot3nK/Xcb6IiME0mvGtA5A/5CZiPaCJJoai9Zf1c Bt9YKksVrG9ENww3k6POTpQS7XsWFH10dlogjcU6N5a3dEQlUCzl/V5cFLK14Kb6RZBI pCW5udx95W6/MlgNQ13z/tWT6nhAVkMKJabI60hHv8Yi5XpKhOKKc80xFChDeb1xf4tU WYQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=jY87nJkTrAkIMXhmw+c4zxTY+My2zdoG2SvKbZwcYmc=; b=oOw6TQ0tBB7SH94nZ+fKdItGj0Xhz3u7vX5/5aJUx2q7Bk+TXrSKKsoP/2yJCSfnF9 F0esqyxvsb1dYFt3hROTzNZRPhPskxx3HBCBxcYKz+X7z+vHqi+vzQ3/LYbjGBc6Me1U eJoTW/dSLy7al6NVarA9CgxapB8mekUDUl0K1aTztG7ogVHm5ECOJXRHV/OxlsLuBFyX 6spbUqzfRQ1Z/wIt253ZwGm4PPXx68EN+7VJguFzlFMYxAoyXV9+bqVmpcvCDIFuVVT3 tnMZzaodEr4Pqh5MEs66f0E0p2JNvCFvES1CmphxVM/eb7hl3ilQK+qw6J2T3OS8bzqB 5q7w== X-Gm-Message-State: AOAM531/hQofTjQHIC4XkkfoSWrLDA8j1gbbgjsqxwWp22JMWyTgwQOu hwVF+M1StqgYh4Dlm2xem8LIvJfAy7s= X-Google-Smtp-Source: ABdhPJz5HyrfUag3eybg7xrPEq2JiL0r4pNbUlVq1x126ZaIxWw9hPgcUa0YdXLZJooBN57OwAwTZQ== X-Received: by 2002:a17:906:168f:: with SMTP id s15mr645900ejd.220.1619527814677; Tue, 27 Apr 2021 05:50:14 -0700 (PDT) Received: from ?IPv6:2a02:908:1252:fb60:a79d:3e10:541f:6c50? ([2a02:908:1252:fb60:a79d:3e10:541f:6c50]) by smtp.gmail.com with ESMTPSA id h16sm2448165edr.19.2021.04.27.05.50.13 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 27 Apr 2021 05:50:14 -0700 (PDT) Subject: Re: [Mesa-dev] [RFC] Linux Graphics Next: Explicit fences everywhere and no BO fences - initial proposal To: =?UTF-8?B?TWFyZWsgT2zFocOhaw==?= , Daniel Vetter References: From: =?UTF-8?Q?Christian_K=c3=b6nig?= Message-ID: <735e0d2e-f2c9-c546-ea6c-b5bbb0fe03a6@gmail.com> Date: Tue, 27 Apr 2021 14:50:13 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US 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: ML Mesa-dev , dri-devel Content-Type: multipart/mixed; boundary="===============0925002177==" Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" This is a multi-part message in MIME format. --===============0925002177== Content-Type: multipart/alternative; boundary="------------015F91BE34F475AF3074F40E" Content-Language: en-US This is a multi-part message in MIME format. --------------015F91BE34F475AF3074F40E Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Only amd -> external. We can easily install something in an user queue which waits for a dma_fence in the kernel. But we can't easily wait for an user queue as dependency of a dma_fence. The good thing is we have this wait before signal case on Vulkan timeline semaphores which have the same problem in the kernel. The good news is I think we can relatively easily convert i915 and older amdgpu device to something which is compatible with user fences. So yes, getting that fixed case by case should work. Christian Am 27.04.21 um 14:46 schrieb Marek Olšák: > I'll defer to Christian and Alex to decide whether dropping sync with > non-amd devices (GPUs, cameras etc.) is acceptable. > > Rewriting those drivers to this new sync model could be done on a case > by case basis. > > For now, would we only lose the "amd -> external" dependency? Or the > "external -> amd" dependency too? > > Marek > > On Tue., Apr. 27, 2021, 08:15 Daniel Vetter, > wrote: > > On Tue, Apr 27, 2021 at 2:11 PM Marek Olšák > wrote: > > Ok. I'll interpret this as "yes, it will work, let's do it". > > It works if all you care about is drm/amdgpu. I'm not sure that's a > reasonable approach for upstream, but it definitely is an approach :-) > > We've already gone somewhat through the pain of drm/amdgpu redefining > how implicit sync works without sufficiently talking with other > people, maybe we should avoid a repeat of this ... > -Daniel > > > > > Marek > > > > On Tue., Apr. 27, 2021, 08:06 Christian König, > > wrote: > >> > >> Correct, we wouldn't have synchronization between device with > and without user queues any more. > >> > >> That could only be a problem for A+I Laptops. > >> > >> Memory management will just work with preemption fences which > pause the user queues of a process before evicting something. That > will be a dma_fence, but also a well known approach. > >> > >> Christian. > >> > >> Am 27.04.21 um 13:49 schrieb Marek Olšák: > >> > >> If we don't use future fences for DMA fences at all, e.g. we > don't use them for memory management, it can work, right? Memory > management can suspend user queues anytime. It doesn't need to use > DMA fences. There might be something that I'm missing here. > >> > >> What would we lose without DMA fences? Just inter-device > synchronization? I think that might be acceptable. > >> > >> The only case when the kernel will wait on a future fence is > before a page flip. Everything today already depends on userspace > not hanging the gpu, which makes everything a future fence. > >> > >> Marek > >> > >> On Tue., Apr. 27, 2021, 04:02 Daniel Vetter, > wrote: > >>> > >>> On Mon, Apr 26, 2021 at 04:59:28PM -0400, Marek Olšák wrote: > >>> > Thanks everybody. The initial proposal is dead. Here are > some thoughts on > >>> > how to do it differently. > >>> > > >>> > I think we can have direct command submission from userspace via > >>> > memory-mapped queues ("user queues") without changing window > systems. > >>> > > >>> > The memory management doesn't have to use GPU page faults > like HMM. > >>> > Instead, it can wait for user queues of a specific process > to go idle and > >>> > then unmap the queues, so that userspace can't submit > anything. Buffer > >>> > evictions, pinning, etc. can be executed when all queues are > unmapped > >>> > (suspended). Thus, no BO fences and page faults are needed. > >>> > > >>> > Inter-process synchronization can use timeline semaphores. > Userspace will > >>> > query the wait and signal value for a shared buffer from the > kernel. The > >>> > kernel will keep a history of those queries to know which > process is > >>> > responsible for signalling which buffer. There is only the > wait-timeout > >>> > issue and how to identify the culprit. One of the solutions > is to have the > >>> > GPU send all GPU signal commands and all timed out wait > commands via an > >>> > interrupt to the kernel driver to monitor and validate > userspace behavior. > >>> > With that, it can be identified whether the culprit is the > waiting process > >>> > or the signalling process and which one. Invalid signal/wait > parameters can > >>> > also be detected. The kernel can force-signal only the > semaphores that time > >>> > out, and punish the processes which caused the timeout or > used invalid > >>> > signal/wait parameters. > >>> > > >>> > The question is whether this synchronization solution is > robust enough for > >>> > dma_fence and whatever the kernel and window systems need. > >>> > >>> The proper model here is the preempt-ctx dma_fence that amdkfd > uses > >>> (without page faults). That means dma_fence for > synchronization is doa, at > >>> least as-is, and we're back to figuring out the winsys problem. > >>> > >>> "We'll solve it with timeouts" is very tempting, but doesn't > work. It's > >>> akin to saying that we're solving deadlock issues in a locking > design by > >>> doing a global s/mutex_lock/mutex_lock_timeout/ in the kernel. > Sure it > >>> avoids having to reach the reset button, but that's about it. > >>> > >>> And the fundamental problem is that once you throw in > userspace command > >>> submission (and syncing, at least within the userspace driver, > otherwise > >>> there's kinda no point if you still need the kernel for > cross-engine sync) > >>> means you get deadlocks if you still use dma_fence for sync under > >>> perfectly legit use-case. We've discussed that one ad nauseam > last summer: > >>> > >>> > https://dri.freedesktop.org/docs/drm/driver-api/dma-buf.html?highlight=dma_fence#indefinite-dma-fences > > >>> > >>> See silly diagramm at the bottom. > >>> > >>> Now I think all isn't lost, because imo the first step to > getting to this > >>> brave new world is rebuilding the driver on top of userspace > fences, and > >>> with the adjusted cmd submit model. You probably don't want to > use amdkfd, > >>> but port that as a context flag or similar to render nodes for > gl/vk. Of > >>> course that means you can only use this mode in headless, without > >>> glx/wayland winsys support, but it's a start. > >>> -Daniel > >>> > >>> > > >>> > Marek > >>> > > >>> > On Tue, Apr 20, 2021 at 4:34 PM Daniel Stone > > wrote: > >>> > > >>> > > Hi, > >>> > > > >>> > > On Tue, 20 Apr 2021 at 20:30, Daniel Vetter > > wrote: > >>> > > > >>> > >> The thing is, you can't do this in drm/scheduler. At > least not without > >>> > >> splitting up the dma_fence in the kernel into separate > memory fences > >>> > >> and sync fences > >>> > > > >>> > > > >>> > > I'm starting to think this thread needs its own glossary ... > >>> > > > >>> > > I propose we use 'residency fence' for execution fences > which enact > >>> > > memory-residency operations, e.g. faulting in a page > ultimately depending > >>> > > on GPU work retiring. > >>> > > > >>> > > And 'value fence' for the pure-userspace model suggested > by timeline > >>> > > semaphores, i.e. fences being (*addr == val) rather than > being able to look > >>> > > at ctx seqno. > >>> > > > >>> > > Cheers, > >>> > > Daniel > >>> > > _______________________________________________ > >>> > > mesa-dev mailing list > >>> > > mesa-dev@lists.freedesktop.org > > >>> > > https://lists.freedesktop.org/mailman/listinfo/mesa-dev > > >>> > > > >>> > >>> -- > >>> Daniel Vetter > >>> Software Engineer, Intel Corporation > >>> http://blog.ffwll.ch > >> > >> > >> _______________________________________________ > >> mesa-dev mailing list > >> mesa-dev@lists.freedesktop.org > > >> https://lists.freedesktop.org/mailman/listinfo/mesa-dev > > >> > >> > > > -- > Daniel Vetter > Software Engineer, Intel Corporation > http://blog.ffwll.ch > --------------015F91BE34F475AF3074F40E Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Only amd -> external.

We can easily install something in an user queue which waits for a dma_fence in the kernel.

But we can't easily wait for an user queue as dependency of a dma_fence.

The good thing is we have this wait before signal case on Vulkan timeline semaphores which have the same problem in the kernel.

The good news is I think we can relatively easily convert i915 and older amdgpu device to something which is compatible with user fences.

So yes, getting that fixed case by case should work.

Christian

Am 27.04.21 um 14:46 schrieb Marek Olšák:
I'll defer to Christian and Alex to decide whether dropping sync with non-amd devices (GPUs, cameras etc.) is acceptable.

Rewriting those drivers to this new sync model could be done on a case by case basis.

For now, would we only lose the "amd -> external" dependency? Or the "external -> amd" dependency too?

Marek

On Tue., Apr. 27, 2021, 08:15 Daniel Vetter, <daniel@ffwll.ch> wrote:
On Tue, Apr 27, 2021 at 2:11 PM Marek Olšák <maraeo@gmail.com> wrote:
> Ok. I'll interpret this as "yes, it will work, let's do it".

It works if all you care about is drm/amdgpu. I'm not sure that's a
reasonable approach for upstream, but it definitely is an approach :-)

We've already gone somewhat through the pain of drm/amdgpu redefining
how implicit sync works without sufficiently talking with other
people, maybe we should avoid a repeat of this ...
-Daniel

>
> Marek
>
> On Tue., Apr. 27, 2021, 08:06 Christian König, <ckoenig.leichtzumerken@gmail.com> wrote:
>>
>> Correct, we wouldn't have synchronization between device with and without user queues any more.
>>
>> That could only be a problem for A+I Laptops.
>>
>> Memory management will just work with preemption fences which pause the user queues of a process before evicting something. That will be a dma_fence, but also a well known approach.
>>
>> Christian.
>>
>> Am 27.04.21 um 13:49 schrieb Marek Olšák:
>>
>> If we don't use future fences for DMA fences at all, e.g. we don't use them for memory management, it can work, right? Memory management can suspend user queues anytime. It doesn't need to use DMA fences. There might be something that I'm missing here.
>>
>> What would we lose without DMA fences? Just inter-device synchronization? I think that might be acceptable.
>>
>> The only case when the kernel will wait on a future fence is before a page flip. Everything today already depends on userspace not hanging the gpu, which makes everything a future fence.
>>
>> Marek
>>
>> On Tue., Apr. 27, 2021, 04:02 Daniel Vetter, <daniel@ffwll.ch> wrote:
>>>
>>> On Mon, Apr 26, 2021 at 04:59:28PM -0400, Marek Olšák wrote:
>>> > Thanks everybody. The initial proposal is dead. Here are some thoughts on
>>> > how to do it differently.
>>> >
>>> > I think we can have direct command submission from userspace via
>>> > memory-mapped queues ("user queues") without changing window systems.
>>> >
>>> > The memory management doesn't have to use GPU page faults like HMM.
>>> > Instead, it can wait for user queues of a specific process to go idle and
>>> > then unmap the queues, so that userspace can't submit anything. Buffer
>>> > evictions, pinning, etc. can be executed when all queues are unmapped
>>> > (suspended). Thus, no BO fences and page faults are needed.
>>> >
>>> > Inter-process synchronization can use timeline semaphores. Userspace will
>>> > query the wait and signal value for a shared buffer from the kernel. The
>>> > kernel will keep a history of those queries to know which process is
>>> > responsible for signalling which buffer. There is only the wait-timeout
>>> > issue and how to identify the culprit. One of the solutions is to have the
>>> > GPU send all GPU signal commands and all timed out wait commands via an
>>> > interrupt to the kernel driver to monitor and validate userspace behavior.
>>> > With that, it can be identified whether the culprit is the waiting process
>>> > or the signalling process and which one. Invalid signal/wait parameters can
>>> > also be detected. The kernel can force-signal only the semaphores that time
>>> > out, and punish the processes which caused the timeout or used invalid
>>> > signal/wait parameters.
>>> >
>>> > The question is whether this synchronization solution is robust enough for
>>> > dma_fence and whatever the kernel and window systems need.
>>>
>>> The proper model here is the preempt-ctx dma_fence that amdkfd uses
>>> (without page faults). That means dma_fence for synchronization is doa, at
>>> least as-is, and we're back to figuring out the winsys problem.
>>>
>>> "We'll solve it with timeouts" is very tempting, but doesn't work. It's
>>> akin to saying that we're solving deadlock issues in a locking design by
>>> doing a global s/mutex_lock/mutex_lock_timeout/ in the kernel. Sure it
>>> avoids having to reach the reset button, but that's about it.
>>>
>>> And the fundamental problem is that once you throw in userspace command
>>> submission (and syncing, at least within the userspace driver, otherwise
>>> there's kinda no point if you still need the kernel for cross-engine sync)
>>> means you get deadlocks if you still use dma_fence for sync under
>>> perfectly legit use-case. We've discussed that one ad nauseam last summer:
>>>
>>> https://dri.freedesktop.org/docs/drm/driver-api/dma-buf.html?highlight=dma_fence#indefinite-dma-fences
>>>
>>> See silly diagramm at the bottom.
>>>
>>> Now I think all isn't lost, because imo the first step to getting to this
>>> brave new world is rebuilding the driver on top of userspace fences, and
>>> with the adjusted cmd submit model. You probably don't want to use amdkfd,
>>> but port that as a context flag or similar to render nodes for gl/vk. Of
>>> course that means you can only use this mode in headless, without
>>> glx/wayland winsys support, but it's a start.
>>> -Daniel
>>>
>>> >
>>> > Marek
>>> >
>>> > On Tue, Apr 20, 2021 at 4:34 PM Daniel Stone <daniel@fooishbar.org> wrote:
>>> >
>>> > > Hi,
>>> > >
>>> > > On Tue, 20 Apr 2021 at 20:30, Daniel Vetter <daniel@ffwll.ch> wrote:
>>> > >
>>> > >> The thing is, you can't do this in drm/scheduler. At least not without
>>> > >> splitting up the dma_fence in the kernel into separate memory fences
>>> > >> and sync fences
>>> > >
>>> > >
>>> > > I'm starting to think this thread needs its own glossary ...
>>> > >
>>> > > I propose we use 'residency fence' for execution fences which enact
>>> > > memory-residency operations, e.g. faulting in a page ultimately depending
>>> > > on GPU work retiring.
>>> > >
>>> > > And 'value fence' for the pure-userspace model suggested by timeline
>>> > > semaphores, i.e. fences being (*addr == val) rather than being able to look
>>> > > at ctx seqno.
>>> > >
>>> > > Cheers,
>>> > > Daniel
>>> > > _______________________________________________
>>> > > mesa-dev mailing list
>>> > > mesa-dev@lists.freedesktop.org
>>> > > https://lists.freedesktop.org/mailman/listinfo/mesa-dev
>>> > >
>>>
>>> --
>>> Daniel Vetter
>>> Software Engineer, Intel Corporation
>>> http://blog.ffwll.ch
>>
>>
>> _______________________________________________
>> mesa-dev mailing list
>> mesa-dev@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/mesa-dev
>>
>>


--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

--------------015F91BE34F475AF3074F40E-- --===============0925002177== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0925002177==--