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,
jason.ekstrand@intel.com, michal.mrozek@intel.com,
jon.bloomfield@intel.com, karl@freedesktop.org,
mesa-dev@lists.freedesktop.org, daniel.vetter@intel.com,
christian.koenig@amd.com, john.c.harrison@intel.com
Subject: [RFC 0/2] GuC submission / DRM scheduler integration plan + new uAPI
Date: Tue, 18 May 2021 16:58:28 -0700 [thread overview]
Message-ID: <20210518235830.133834-1-matthew.brost@intel.com> (raw)
Subject and patches say it all.
v2: Address comments, patches has 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 | 144 ++++++++++++++++++
Documentation/gpu/rfc/i915_scheduler.rst | 136 +++++++++++++++++
Documentation/gpu/rfc/index.rst | 4 +
3 files changed, 284 insertions(+)
create mode 100644 Documentation/gpu/rfc/i915_parallel_execbuf.h
create mode 100644 Documentation/gpu/rfc/i915_scheduler.rst
--
2.28.0
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Brost <matthew.brost@intel.com>
To: <intel-gfx@lists.freedesktop.org>, <dri-devel@lists.freedesktop.org>
Cc: jason.ekstrand@intel.com, karl@freedesktop.org,
mesa-dev@lists.freedesktop.org, daniel.vetter@intel.com,
christian.koenig@amd.com
Subject: [Intel-gfx] [RFC 0/2] GuC submission / DRM scheduler integration plan + new uAPI
Date: Tue, 18 May 2021 16:58:28 -0700 [thread overview]
Message-ID: <20210518235830.133834-1-matthew.brost@intel.com> (raw)
Subject and patches say it all.
v2: Address comments, patches has 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 | 144 ++++++++++++++++++
Documentation/gpu/rfc/i915_scheduler.rst | 136 +++++++++++++++++
Documentation/gpu/rfc/index.rst | 4 +
3 files changed, 284 insertions(+)
create mode 100644 Documentation/gpu/rfc/i915_parallel_execbuf.h
create mode 100644 Documentation/gpu/rfc/i915_scheduler.rst
--
2.28.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2021-05-18 23:40 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 23:58 Matthew Brost [this message]
2021-05-18 23:58 ` [Intel-gfx] [RFC 0/2] GuC submission / DRM scheduler integration plan + new uAPI Matthew Brost
2021-05-18 23:47 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for GuC submission / DRM scheduler integration plan + new uAPI (rev2) Patchwork
2021-05-18 23:51 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2021-05-18 23:58 ` [RFC 1/2] drm/doc/rfc: i915 GuC submission / DRM scheduler Matthew Brost
2021-05-18 23:58 ` [Intel-gfx] " Matthew Brost
2021-05-18 23:58 ` [RFC 2/2] drm/doc/rfc: i915 new parallel submission uAPI plan Matthew Brost
2021-05-18 23:58 ` [Intel-gfx] " Matthew Brost
2021-05-19 11:10 ` Daniel Vetter
2021-05-19 11:10 ` Daniel Vetter
2021-05-19 15:29 ` Tvrtko Ursulin
2021-05-19 15:29 ` Tvrtko Ursulin
2021-05-19 17:11 ` Matthew Brost
2021-05-19 17:11 ` Matthew Brost
2021-05-20 9:54 ` Daniel Vetter
2021-05-20 9:54 ` Daniel Vetter
2021-05-20 10:57 ` Tvrtko Ursulin
2021-05-20 10:57 ` Tvrtko Ursulin
2021-05-20 19:41 ` Daniel Vetter
2021-05-20 19:41 ` Daniel Vetter
2021-05-21 12:12 ` Tvrtko Ursulin
2021-05-21 12:12 ` Tvrtko Ursulin
2021-05-21 16:26 ` Matthew Brost
2021-05-21 16:26 ` Matthew Brost
2021-05-20 15:10 ` Matthew Brost
2021-05-20 15:10 ` Matthew Brost
2021-05-20 19:44 ` Daniel Vetter
2021-05-20 19:44 ` Daniel Vetter
2021-05-21 16:20 ` Matthew Brost
2021-05-21 16:20 ` Matthew Brost
2021-05-19 11:45 ` [Mesa-dev] " Christian König
2021-05-19 11:45 ` [Intel-gfx] " Christian König
2021-05-19 16:51 ` Matthew Brost
2021-05-19 16:51 ` [Intel-gfx] " Matthew Brost
2021-05-20 11:11 ` Christian König
2021-05-20 11:11 ` [Intel-gfx] " Christian König
2021-05-20 15:39 ` Matthew Brost
2021-05-20 15:39 ` [Intel-gfx] " Matthew Brost
2021-05-20 21:38 ` Jason Ekstrand
2021-05-20 21:38 ` Jason Ekstrand
2021-05-21 8:35 ` Christian König
2021-05-21 8:35 ` Christian König
2021-05-21 16:14 ` Matthew Brost
2021-05-21 16:14 ` Matthew Brost
2021-05-19 13:57 ` Marcin Ślusarz
2021-05-19 13:57 ` [Intel-gfx] " Marcin Ślusarz
2021-05-21 12:00 ` [Intel-gfx] " Tvrtko Ursulin
2021-05-21 12:00 ` Tvrtko Ursulin
2021-05-21 16:48 ` Matthew Brost
2021-05-21 16:48 ` Matthew Brost
2021-05-24 15:33 ` Tvrtko Ursulin
2021-05-24 15:33 ` Tvrtko Ursulin
2021-05-19 0:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success for GuC submission / DRM scheduler integration plan + new uAPI (rev2) Patchwork
2021-05-20 1:49 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=20210518235830.133834-1-matthew.brost@intel.com \
--to=matthew.brost@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=karl@freedesktop.org \
--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 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.