From: Dave Airlie <airlied@gmail.com>
To: dri-devel@lists.freedesktop.org
Subject: [RFC] DRM synchronisation objects
Date: Tue, 4 Apr 2017 14:27:25 +1000 [thread overview]
Message-ID: <20170404042733.17203-1-airlied@gmail.com> (raw)
This series enhances my previous semaphore work on for amdgpu,
with a generic DRM sync object. (drm_syncobj).
It first enhances sync_file to have a type/flags so we can have
different semantics for different sync files, and a wait
to retrieve the type of sync_file for userspace.
Then it adds drm sync objects which are just a drm wrapper around
a sync_file object, allowing creation/info/destroy and import/export
of the objects.
Next it enhances sync_file to have semaphore semantics for Vulkan.
Finally it adds amdgpu support to it's command submission paths to
use the new code.
I've hopefully fixed up the things pointed out in the last
review of the sync_file fence changes, I do wonder if we should
just block poll on semaphore objects as currently I've no use
case for this.
Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-04-04 4:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 4:27 Dave Airlie [this message]
2017-04-04 4:27 ` [PATCH 1/8] sync_file: add type/flags to sync file object creation Dave Airlie
2017-04-04 7:08 ` Daniel Vetter
2017-04-04 4:27 ` [PATCH 2/8] sync_file: export some interfaces needed by drm sync objects Dave Airlie
2017-04-04 7:10 ` Daniel Vetter
2017-04-04 4:27 ` [PATCH 3/8] drm: introduce sync objects as sync file objects with no fd Dave Airlie
2017-04-04 7:42 ` Daniel Vetter
[not found] ` <CAPM=9tyj6k4hqJWrwDW8Ch+TZCOoXRuAK2g71ciUm5vxpwmkuw@mail.gmail.com>
[not found] ` <CAKMK7uFoFvsREVtSxsoOeM6OPDM-iGOATtcAK6p65LzG39D6oQ@mail.gmail.com>
2017-04-11 6:00 ` Daniel Vetter
2017-04-04 4:27 ` [PATCH 4/8] sync_file: add a mutex to protect fence and callback members. (v4) Dave Airlie
2017-04-04 7:52 ` Daniel Vetter
2017-04-04 8:07 ` Christian König
2017-04-11 2:57 ` Dave Airlie
2017-04-04 4:27 ` [PATCH 5/8] sync_file: add support for a semaphore object Dave Airlie
2017-04-04 7:59 ` Daniel Vetter
2017-04-04 11:52 ` Chris Wilson
2017-04-04 11:59 ` Chris Wilson
2017-04-04 4:27 ` [PATCH 6/8] drm/syncobj: add semaphore support helpers Dave Airlie
2017-04-04 8:07 ` Daniel Vetter
2017-04-04 4:27 ` [PATCH 7/8] amdgpu/cs: split out fence dependency checking Dave Airlie
2017-04-04 7:37 ` Christian König
2017-04-04 4:27 ` [PATCH 8/8] amdgpu: use sync file for shared semaphores (v2) Dave Airlie
2017-04-04 7:40 ` Christian König
2017-04-04 8:10 ` Daniel Vetter
2017-04-04 11:05 ` Christian König
2017-04-11 3:18 ` Dave Airlie
2017-04-11 6:55 ` Christian König
2017-04-04 4:35 ` [RFC] DRM synchronisation objects Dave Airlie
2017-04-04 8:02 ` Christian König
2017-04-04 8:11 ` Daniel Vetter
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=20170404042733.17203-1-airlied@gmail.com \
--to=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.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 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.