From: Gurchetan Singh <gurchetansingh@chromium.org>
To: dri-devel@lists.freedesktop.org
Cc: chadversary@chromium.org,
Gurchetan Singh <gurchetansingh@chromium.org>,
kraxel@redhat.com, jbates@chromium.org
Subject: [RFC PATCH 0/8] *** Per context fencing ***
Date: Mon, 9 Mar 2020 18:08:10 -0700 [thread overview]
Message-ID: <20200310010818.569-1-gurchetansingh@chromium.org> (raw)
We don't want fences from different 3D contexts/processes (GL, VK) to
be on the same timeline. Sending this out as a RFC to solicit feedback
on the general approach.
Gurchetan Singh (8):
drm/virtio: use fence_id when processing fences
drm/virtio: allocate a fence context for every 3D context
drm/virtio: plumb virtio_gpu_fpriv to virtio_gpu_fence_alloc
drm/virtio: rename sync_seq and last_seq
drm/virtio: track fence_id in virtio_gpu_fence
virtio/drm: rework virtio_fence_signaled
drm/virtio: check context when signaling
drm/virtio: enable per context fencing
drivers/gpu/drm/virtio/virtgpu_debugfs.c | 4 +-
drivers/gpu/drm/virtio/virtgpu_drv.h | 12 +++--
drivers/gpu/drm/virtio/virtgpu_fence.c | 66 ++++++++++++++++--------
drivers/gpu/drm/virtio/virtgpu_ioctl.c | 9 ++--
drivers/gpu/drm/virtio/virtgpu_kms.c | 1 +
drivers/gpu/drm/virtio/virtgpu_plane.c | 2 +-
drivers/gpu/drm/virtio/virtgpu_vq.c | 4 +-
7 files changed, 62 insertions(+), 36 deletions(-)
--
2.25.1.481.gfbce0eb801-goog
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-03-10 1:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 1:08 Gurchetan Singh [this message]
2020-03-10 1:08 ` [RFC PATCH 1/8] drm/virtio: use fence_id when processing fences Gurchetan Singh
2020-03-10 1:08 ` [RFC PATCH 2/8] drm/virtio: allocate a fence context for every 3D context Gurchetan Singh
2020-03-10 1:08 ` [RFC PATCH 3/8] drm/virtio: plumb virtio_gpu_fpriv to virtio_gpu_fence_alloc Gurchetan Singh
2020-03-10 1:08 ` [RFC PATCH 4/8] drm/virtio: rename sync_seq and last_seq Gurchetan Singh
2020-03-10 1:08 ` [RFC PATCH 5/8] drm/virtio: track fence_id in virtio_gpu_fence Gurchetan Singh
2020-03-10 1:08 ` [RFC PATCH 6/8] virtio/drm: rework virtio_fence_signaled Gurchetan Singh
2020-03-10 1:08 ` [RFC PATCH 7/8] drm/virtio: check context when signaling Gurchetan Singh
2020-03-10 1:08 ` [RFC PATCH 8/8] drm/virtio: enable per context fencing Gurchetan Singh
2020-03-10 7:43 ` [RFC PATCH 0/8] *** Per context fencing *** Gerd Hoffmann
2020-03-10 22:57 ` Gurchetan Singh
2020-03-11 10:36 ` Gerd Hoffmann
2020-03-11 17:35 ` Chia-I Wu
2020-03-12 9:06 ` Gerd Hoffmann
2020-03-11 23:36 ` Gurchetan Singh
2020-03-12 0:43 ` Chia-I Wu
2020-03-12 9:10 ` Gerd Hoffmann
2020-03-12 9:29 ` Gerd Hoffmann
2020-03-12 23:08 ` Gurchetan Singh
2020-03-13 21:20 ` Chia-I Wu
2020-03-16 7:44 ` Gerd Hoffmann
2020-03-17 20:32 ` Chia-I Wu
2020-03-18 6:40 ` Gerd Hoffmann
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=20200310010818.569-1-gurchetansingh@chromium.org \
--to=gurchetansingh@chromium.org \
--cc=chadversary@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jbates@chromium.org \
--cc=kraxel@redhat.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.