From: Matthew Brost <matthew.brost@intel.com>
To: <intel-gfx@lists.freedesktop.org>, <dri-devel@lists.freedesktop.org>
Cc: carl.zhang@intel.com, jason.ekstrand@intel.com, daniel.vetter@intel.com
Subject: [Intel-gfx] [RFC PATCH 0/5] GuC submission / DRM scheduler integration plan + new uAPI
Date: Thu, 6 May 2021 10:30:44 -0700 [thread overview]
Message-ID: <20210506173049.72503-1-matthew.brost@intel.com> (raw)
Subject and patches say it all.
Initial post of GuC submission patches, detailed in patch 1, coming
shortly.
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Matthew Brost (5):
drm/doc/rfc: i915 GuC submission / DRM scheduler integration plan
drm/doc/rfc: i915 new parallel submission uAPI plan
drm/i915: Expose logical engine instance to user
drm/i915: Introduce 'set parallel submit' extension
drm/i915: Update execbuf IOCTL to accept N BBs
Documentation/gpu/rfc/i915_scheduler.rst | 122 ++++++++++++++++++
Documentation/gpu/rfc/index.rst | 4 +
include/uapi/drm/i915_drm.h | 154 ++++++++++++++++++++++-
3 files changed, 278 insertions(+), 2 deletions(-)
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-06 17:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 17:30 Matthew Brost [this message]
2021-05-06 17:27 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for GuC submission / DRM scheduler integration plan + new uAPI Patchwork
2021-05-06 17:30 ` [Intel-gfx] [RFC PATCH 1/5] drm/doc/rfc: i915 GuC submission / DRM scheduler integration plan Matthew Brost
2021-05-11 14:34 ` Daniel Vetter
2021-05-11 14:58 ` Daniel Stone
2021-05-11 15:12 ` Daniel Vetter
2021-05-06 17:30 ` [Intel-gfx] [RFC PATCH 2/5] drm/doc/rfc: i915 new parallel submission uAPI plan Matthew Brost
2021-05-11 14:49 ` Daniel Vetter
2021-05-11 17:51 ` Matthew Brost
2021-05-06 17:30 ` [Intel-gfx] [RFC PATCH 3/5] drm/i915: Expose logical engine instance to user Matthew Brost
2021-05-11 14:53 ` Daniel Vetter
2021-05-06 17:30 ` [Intel-gfx] [RFC PATCH 4/5] drm/i915: Introduce 'set parallel submit' extension Matthew Brost
2021-05-11 15:11 ` Daniel Vetter
2021-05-11 18:44 ` Matthew Brost
2021-05-12 8:34 ` Daniel Vetter
2021-05-14 20:05 ` Matthew Brost
2021-05-17 13:55 ` Daniel Vetter
2021-05-17 17:46 ` Matthew Brost
2021-05-06 17:30 ` [Intel-gfx] [RFC PATCH 5/5] drm/i915: Update execbuf IOCTL to accept N BBs Matthew Brost
2021-05-11 15:13 ` Daniel Vetter
2021-05-11 18:01 ` 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=20210506173049.72503-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=carl.zhang@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jason.ekstrand@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