From: Matthew Brost <matthew.brost@intel.com>
To: <intel-gfx@lists.freedesktop.org>, <dri-devel@lists.freedesktop.org>
Cc: matthew.brost@intel.com, tony.ye@intel.com,
tvrtko.ursulin@intel.com, daniele.ceraolospurio@intel.com,
carl.zhang@intel.com, jason.ekstrand@intel.com,
michal.mrozek@intel.com, jon.bloomfield@intel.com,
mesa-dev@lists.freedesktop.org, daniel.vetter@intel.com,
christian.koenig@amd.com, john.c.harrison@intel.com
Subject: [RFC PATCH 0/2] GuC submission / DRM scheduler integration plan + new uAPI
Date: Wed, 26 May 2021 16:33:55 -0700 [thread overview]
Message-ID: <20210526233357.9165-1-matthew.brost@intel.com> (raw)
Subject and patches say it all.
v2: Address comments, patches have details of changes
v3: Address comments, patches have details of changes
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Matthew Brost (2):
drm/doc/rfc: i915 GuC submission / DRM scheduler
drm/doc/rfc: i915 new parallel submission uAPI plan
Documentation/gpu/rfc/i915_parallel_execbuf.h | 145 ++++++++++++++++++
Documentation/gpu/rfc/i915_scheduler.rst | 136 ++++++++++++++++
Documentation/gpu/rfc/index.rst | 4 +
3 files changed, 285 insertions(+)
create mode 100644 Documentation/gpu/rfc/i915_parallel_execbuf.h
create mode 100644 Documentation/gpu/rfc/i915_scheduler.rst
--
2.28.0
next reply other threads:[~2021-05-26 23:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 23:33 Matthew Brost [this message]
2021-05-26 23:33 ` [RFC PATCH 1/2] drm/doc/rfc: i915 GuC submission / DRM scheduler Matthew Brost
2021-05-27 10:06 ` [Intel-gfx] " Tvrtko Ursulin
2021-05-27 11:24 ` Daniel Vetter
2021-06-04 17:39 ` Daniel Vetter
2021-06-04 19:48 ` [Mesa-dev] " Dave Airlie
2021-05-26 23:33 ` [RFC PATCH 2/2] drm/doc/rfc: i915 new parallel submission uAPI plan Matthew Brost
2021-05-27 15:01 ` [Intel-gfx] " Tvrtko Ursulin
2021-06-04 17:59 ` Daniel Vetter
2021-06-11 19:50 ` Matthew Brost
2021-06-17 16:46 ` Daniel Vetter
2021-06-17 17:27 ` Matthew Brost
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=20210526233357.9165-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=carl.zhang@intel.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jason.ekstrand@intel.com \
--cc=john.c.harrison@intel.com \
--cc=jon.bloomfield@intel.com \
--cc=mesa-dev@lists.freedesktop.org \
--cc=michal.mrozek@intel.com \
--cc=tony.ye@intel.com \
--cc=tvrtko.ursulin@intel.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).