From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/7] Per context dynamic (sub)slice power-gating
Date: Tue, 8 Jan 2019 11:22:45 +0000 [thread overview]
Message-ID: <20190108112252.29002-1-tvrtko.ursulin@linux.intel.com> (raw)
From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Changes since last version:
* Rebase for drm-tip changes (RUNTIME_INFO).
Lionel Landwerlin (2):
drm/i915: Record the sseu configuration per-context & engine
drm/i915/perf: lock powergating configuration to default when active
Tvrtko Ursulin (5):
drm/i915/execlists: Move RPCS setup to context pin
drm/i915: Add timeline barrier support
drm/i915: Expose RPCS (SSEU) configuration to userspace (Gen11 only)
drm/i915/icl: Support co-existence between per-context SSEU and OA
drm/i915/selftests: Context SSEU reconfiguration tests
drivers/gpu/drm/i915/i915_drv.h | 14 +
drivers/gpu/drm/i915/i915_gem_context.c | 354 ++++++++++++-
drivers/gpu/drm/i915/i915_gem_context.h | 10 +
drivers/gpu/drm/i915/i915_perf.c | 13 +-
drivers/gpu/drm/i915/i915_request.c | 13 +
drivers/gpu/drm/i915/i915_request.h | 10 +
drivers/gpu/drm/i915/i915_timeline.c | 3 +
drivers/gpu/drm/i915/i915_timeline.h | 27 +
drivers/gpu/drm/i915/intel_lrc.c | 100 ++--
drivers/gpu/drm/i915/intel_lrc.h | 2 +
.../gpu/drm/i915/selftests/i915_gem_context.c | 486 ++++++++++++++++++
.../gpu/drm/i915/selftests/mock_timeline.c | 2 +
include/uapi/drm/i915_drm.h | 43 ++
13 files changed, 1040 insertions(+), 37 deletions(-)
--
2.19.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-01-08 11:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 11:22 Tvrtko Ursulin [this message]
2019-01-08 11:22 ` [PATCH 1/7] drm/i915/execlists: Move RPCS setup to context pin Tvrtko Ursulin
2019-01-08 13:11 ` Joonas Lahtinen
2019-01-08 11:22 ` [PATCH 2/7] drm/i915: Record the sseu configuration per-context & engine Tvrtko Ursulin
2019-01-08 13:17 ` Joonas Lahtinen
2019-01-08 11:22 ` [PATCH 3/7] drm/i915/perf: lock powergating configuration to default when active Tvrtko Ursulin
2019-01-08 13:40 ` Joonas Lahtinen
2019-01-08 11:22 ` [PATCH 4/7] drm/i915: Add timeline barrier support Tvrtko Ursulin
2019-01-08 11:22 ` [PATCH 5/7] drm/i915: Expose RPCS (SSEU) configuration to userspace (Gen11 only) Tvrtko Ursulin
2019-01-08 14:22 ` Joonas Lahtinen
2019-01-08 14:35 ` Tvrtko Ursulin
2019-01-08 14:57 ` Chris Wilson
2019-01-08 11:22 ` [PATCH 6/7] drm/i915/icl: Support co-existence between per-context SSEU and OA Tvrtko Ursulin
2019-01-08 13:59 ` Joonas Lahtinen
2019-01-08 11:22 ` [PATCH 7/7] drm/i915/selftests: Context SSEU reconfiguration tests Tvrtko Ursulin
2019-01-08 12:50 ` Chris Wilson
2019-01-08 13:58 ` Joonas Lahtinen
2019-01-08 14:38 ` Tvrtko Ursulin
2019-01-08 13:33 ` ✗ Fi.CI.CHECKPATCH: warning for Per context dynamic (sub)slice power-gating (rev10) Patchwork
2019-01-08 13:36 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-08 13:52 ` ✓ Fi.CI.BAT: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2018-12-31 16:06 [PATCH 0/7] Per context dynamic (sub)slice power-gating Tvrtko Ursulin
2018-12-14 12:34 Tvrtko Ursulin
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=20190108112252.29002-1-tvrtko.ursulin@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
/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