From: Simon Ser <contact@emersion.fr>
To: Rob Clark <robdclark@gmail.com>
Cc: dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
"Daniel Vetter" <daniel@ffwll.ch>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
"Michel Dänzer" <michel@daenzer.net>,
"Pekka Paalanen" <ppaalanen@gmail.com>,
"Rob Clark" <robdclark@chromium.org>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Andrey Grodzovsky" <andrey.grodzovsky@amd.com>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
"Christian König" <christian.koenig@amd.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
freedreno@lists.freedesktop.org,
"Gustavo Padovan" <gustavo@padovan.org>,
"Jack Zhang" <Jack.Zhang1@amd.com>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org,
"Luben Tuikov" <luben.tuikov@amd.com>,
"Melissa Wen" <mwen@igalia.com>,
"Steven Price" <steven.price@arm.com>,
"Tian Tao" <tiantao6@hisilicon.com>
Subject: Re: [PATCH v3 0/9] dma-fence: Deadline awareness
Date: Thu, 09 Sep 2021 16:16:05 +0000 [thread overview]
Message-ID: <i-XmBd_5J3_d8cdm-IT6Ery2kHN0FPZCX968aU5idvxQxNlvDJguLLThtF2NF15LF8gGsH4uI2w0s0CL_39KGpzoGpuCgcz2_-4Wjf3AYEM=@emersion.fr> (raw)
In-Reply-To: <20210903184806.1680887-1-robdclark@gmail.com>
Out of curiosity, would it be reasonable to allow user-space (more
precisely, the compositor) to set the deadline via an IOCTL without
actually performing an atomic commit with the FB?
Some compositors might want to wait themselves for FB fence completions
to ensure a client doesn't block the whole desktop (by submitting a
very costly rendering job). In this case it would make sense for the
compositor to indicate that it intends to display the buffer on next
vblank if it's ready by that point, without queueing a page-flip yet.
next prev parent reply other threads:[~2021-09-09 16:16 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 18:47 [PATCH v3 0/9] dma-fence: Deadline awareness Rob Clark
2021-09-03 18:47 ` [PATCH v3 1/9] dma-fence: Add deadline awareness Rob Clark
2021-09-08 17:55 ` Daniel Vetter
2021-09-03 18:47 ` [PATCH v3 2/9] drm/vblank: Add helper to get next vblank time Rob Clark
2021-09-03 18:47 ` [PATCH v3 3/9] drm/atomic-helper: Set fence deadline for vblank Rob Clark
2021-09-03 18:47 ` [PATCH v3 4/9] drm/scheduler: Add fence deadline support Rob Clark
2021-09-08 17:45 ` Daniel Vetter
2021-09-09 6:22 ` Christian König
2021-09-14 13:38 ` Daniel Vetter
2021-09-21 15:57 ` Rob Clark
2021-09-21 16:35 ` Rob Clark
2021-09-21 16:45 ` Christian König
2021-09-21 20:09 ` Andrey Grodzovsky
2021-09-21 20:47 ` Rob Clark
2021-09-22 2:18 ` Andrey Grodzovsky
2021-09-22 3:32 ` Rob Clark
2021-09-22 14:31 ` Andrey Grodzovsky
2021-09-22 15:01 ` Rob Clark
2021-09-03 18:47 ` [PATCH v3 5/9] drm/msm: Add deadline based boost support Rob Clark
2021-09-08 17:48 ` Daniel Vetter
2021-09-08 17:57 ` Rob Clark
2021-09-03 18:47 ` [PATCH v3 6/9] dma-buf/fence-array: Add fence deadline support Rob Clark
2021-09-08 18:00 ` Daniel Vetter
2021-09-09 6:55 ` Christian König
2021-09-03 18:47 ` [PATCH v3 7/9] dma-buf/fence-chain: " Rob Clark
2021-09-08 17:54 ` Daniel Vetter
2021-09-08 18:19 ` Rob Clark
2021-09-08 18:45 ` Daniel Vetter
2021-09-09 6:31 ` Christian König
2021-09-03 18:47 ` [PATCH v3 8/9] dma-buf/sync_file: Add SET_DEADLINE ioctl Rob Clark
2021-09-08 17:50 ` Daniel Vetter
2021-09-08 18:23 ` Rob Clark
2021-09-08 18:49 ` Daniel Vetter
2021-09-08 19:40 ` Rob Clark
2021-09-08 21:10 ` Daniel Vetter
2021-09-21 18:08 ` Rob Clark
2021-09-27 8:42 ` Pekka Paalanen
2021-09-27 8:53 ` Christian König
2021-09-27 14:36 ` Rob Clark
2021-09-28 7:57 ` Pekka Paalanen
2021-09-03 18:48 ` [PATCH v3 9/9] dma-buf/sw_sync: Add fence deadline support Rob Clark
2021-09-09 16:16 ` Simon Ser [this message]
2021-09-09 16:35 ` [PATCH v3 0/9] dma-fence: Deadline awareness Rob Clark
2021-09-09 16:42 ` Simon Ser
2021-09-09 17:08 ` Rob Clark
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='i-XmBd_5J3_d8cdm-IT6Ery2kHN0FPZCX968aU5idvxQxNlvDJguLLThtF2NF15LF8gGsH4uI2w0s0CL_39KGpzoGpuCgcz2_-4Wjf3AYEM=@emersion.fr' \
--to=contact@emersion.fr \
--cc=Jack.Zhang1@amd.com \
--cc=alexander.deucher@amd.com \
--cc=andrey.grodzovsky@amd.com \
--cc=boris.brezillon@collabora.com \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=luben.tuikov@amd.com \
--cc=michel@daenzer.net \
--cc=mwen@igalia.com \
--cc=ppaalanen@gmail.com \
--cc=robdclark@chromium.org \
--cc=robdclark@gmail.com \
--cc=steven.price@arm.com \
--cc=tiantao6@hisilicon.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.