From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org
Subject: [RFC] Add DMA_RESV_USAGE flags
Date: Mon, 17 May 2021 16:11:18 +0200 [thread overview]
Message-ID: <20210517141129.2225-1-christian.koenig@amd.com> (raw)
We had a long outstanding problem in amdgpu that buffers exported to user drivers by DMA-buf serialize all command submissions using them.
In other words we can't compose the buffer with different engines and then send it to another driver for display further processing.
This was added to work around the fact that i915 didn't wanted to wait for shared fences in the dma_resv objects before displaying a buffer.
Since this problem is now causing issues with Vulkan we need to find a better solution for that.
The patch set here tries to do this by adding an usage flag to the shared fences noting when and how they should participate in implicit synchronization.
Please review and/or comment,
Christian.
next reply other threads:[~2021-05-17 14:11 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 14:11 Christian König [this message]
2021-05-17 14:11 ` [PATCH 01/11] dma-buf: fix invalid debug print Christian König
2021-05-17 14:11 ` [PATCH 02/11] dma-buf: add SPDX header and fix style in dma-resv.c Christian König
2021-05-17 14:11 ` [PATCH 03/11] dma-buf: cleanup dma-resv shared fence debugging a bit Christian König
2021-05-17 14:11 ` [PATCH 04/11] dma-buf: rename and cleanup dma_resv_get_excl Christian König
2021-05-17 14:11 ` [PATCH 05/11] dma-buf: rename and cleanup dma_resv_get_list Christian König
2021-05-17 14:11 ` [PATCH 06/11] dma-buf: add dma_resv_list_fence helper Christian König
2021-05-17 14:11 ` [PATCH 07/11] dma-buf: add dma_resv_replace_shared Christian König
2021-05-17 14:11 ` [PATCH 08/11] dma-buf: improve shared fence abstraction Christian König
2021-05-17 14:11 ` [PATCH 09/11] dma-buf: add shared fence usage flags Christian König
2021-05-17 20:36 ` Daniel Vetter
2021-05-18 12:54 ` Christian König
2021-05-17 14:11 ` [PATCH 10/11] drm/i915: also wait for shared dmabuf fences before flip Christian König
2021-05-17 14:11 ` [PATCH 11/11] drm/amdgpu: fix shared access to exported DMA-bufs Christian König
2021-05-17 15:04 ` [RFC] Add DMA_RESV_USAGE flags Daniel Vetter
2021-05-17 19:38 ` Christian König
2021-05-17 20:15 ` Jason Ekstrand
2021-05-17 20:15 ` Daniel Vetter
2021-05-17 22:49 ` Jason Ekstrand
2021-05-18 5:59 ` Daniel Vetter
2021-05-18 10:29 ` Daniel Vetter
2021-05-18 12:49 ` Christian König
2021-05-18 13:26 ` Daniel Stone
2021-05-18 13:51 ` Christian König
2021-05-18 16:48 ` Daniel Vetter
2021-05-18 17:40 ` Christian König
2021-05-18 21:17 ` Daniel Vetter
2021-05-18 22:06 ` Jason Ekstrand
2021-05-19 10:52 ` Michel Dänzer
2021-05-19 15:21 ` Jason Ekstrand
2021-05-19 15:48 ` Michel Dänzer
2021-05-20 7:55 ` Daniel Vetter
2021-05-20 8:13 ` Michel Dänzer
2021-05-20 10:00 ` Christian König
2021-05-20 14:18 ` Daniel Vetter
2021-05-20 14:30 ` Michel Dänzer
2021-05-20 17:08 ` Jason Ekstrand
2021-05-31 12:49 ` Michel Dänzer
2021-05-20 10:50 ` Christian König
2021-05-20 17:23 ` Jason Ekstrand
2021-05-20 19:04 ` Jason Ekstrand
2021-05-20 19:14 ` Daniel Vetter
2021-05-21 7:27 ` Christian König
2021-05-21 9:36 ` Bas Nieuwenhuizen
2021-05-21 7:24 ` Christian König
2021-05-19 11:43 ` Christian König
2021-05-19 15:35 ` Jason Ekstrand
2021-05-19 11:24 ` Christian König
2021-05-20 7:58 ` Daniel Vetter
2021-05-18 21:31 ` Dave Airlie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210517141129.2225-1-christian.koenig@amd.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).