From: Rohan Garg <rohan.garg@collabora.com>
To: dri-devel@lists.freedesktop.org
Cc: kernel@collabora.com
Subject: [PATCH v5 0/2] Introducing IOCTL's to set/get label's for a buffer object
Date: Thu, 14 May 2020 17:05:31 +0200 [thread overview]
Message-ID: <cover.1589468282.git.rohan.garg@collabora.com> (raw)
Hi
I've been reworking these label'ing patches in conjunction
with their userspace usage that can be found here [1].
The intention is that these patches will be useful for driver
developers and application developers alike in conjuction with
something like the OpenGL Label'ing extension [2].
Cheers
Rohan Garg
[1] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/2426/
[2] https://www.khronos.org/registry/OpenGL/extensions/EXT/EXT_debug_label.txt
Rohan Garg (2):
drm/ioctl: Add a ioctl to set and get a label on GEM objects
panfrost: Set default labeling helpers
drivers/gpu/drm/drm_gem.c | 54 ++++++++++++++++++
drivers/gpu/drm/drm_internal.h | 14 +++++
drivers/gpu/drm/drm_ioctl.c | 74 +++++++++++++++++++++++++
drivers/gpu/drm/panfrost/panfrost_drv.c | 3 +
include/drm/drm_drv.h | 32 +++++++++++
include/drm/drm_gem.h | 16 +++++-
include/uapi/drm/drm.h | 21 ++++++-
7 files changed, 212 insertions(+), 2 deletions(-)
--
2.17.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-05-14 15:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 15:05 Rohan Garg [this message]
2020-05-14 15:05 ` [PATCH v5 1/2] drm/ioctl: Add a ioctl to set and get a label on GEM objects Rohan Garg
2020-05-19 23:48 ` Emil Velikov
2020-05-21 0:07 ` Rohan Garg
2020-05-21 1:19 ` Emil Velikov
2020-05-14 15:05 ` [PATCH v5 2/2] panfrost: Set default labeling helpers Rohan Garg
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=cover.1589468282.git.rohan.garg@collabora.com \
--to=rohan.garg@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.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 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).