From: Alan Previn <alan.previn.teres.alexis@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/1] Delay disabling GuC scheduling of an idle context
Date: Wed, 14 Sep 2022 19:12:17 -0700 [thread overview]
Message-ID: <20220915021218.1412111-1-alan.previn.teres.alexis@intel.com> (raw)
This series adds a delay before disabling scheduling of the guc-context
when a context has become idle to avoid costly re-registration that may
occur immediately after. The 2nd patch should explain it quite well.
The origin of this series was posted by Matthew Brost back in Oct 2021
(https://patchwork.freedesktop.org/series/96167/). However no real
world workload performance impact was available until recently proving
it's intended results.
This series is a redo of a prior patch that was reverted:
2ccddb758079d0c62ce03e69ee8929bb212f7799 drm/i915/guc: Add delay to
disable scheduling after pin count goes to zero
The cause for the reversion is now fixed here (was not caught due to
issues with CI reporting at that time). Two additional changes included
in this redo:
- Resolve race between guc_request_alloc and guc_context_close in
completing the delayed disable-guc-scheduling worker.
- GT Reset flow properly closing contexts that were pending for the
Matthew Brost (1):
drm/i915/guc: Delay disabling guc_id scheduling for better hysteresis
drivers/gpu/drm/i915/gem/i915_gem_context.c | 2 +-
drivers/gpu/drm/i915/gt/intel_context.h | 8 +
drivers/gpu/drm/i915/gt/intel_context_types.h | 7 +
drivers/gpu/drm/i915/gt/uc/intel_guc.h | 16 ++
.../gpu/drm/i915/gt/uc/intel_guc_debugfs.c | 60 +++++
.../gpu/drm/i915/gt/uc/intel_guc_submission.c | 220 +++++++++++++++---
drivers/gpu/drm/i915/i915_selftest.h | 2 +
7 files changed, 288 insertions(+), 27 deletions(-)
base-commit: 37b0cd34584fab54ae910bffd0f148c8ceb2a9c7
--
2.25.1
next reply other threads:[~2022-09-15 2:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 2:12 Alan Previn [this message]
2022-09-15 2:12 ` [Intel-gfx] [PATCH 1/1] drm/i915/guc: Delay disabling guc_id scheduling for better hysteresis Alan Previn
2022-09-15 8:48 ` Tvrtko Ursulin
2022-09-16 7:53 ` Teres Alexis, Alan Previn
2022-09-16 8:58 ` Tvrtko Ursulin
2022-09-16 15:36 ` Ceraolo Spurio, Daniele
2022-09-20 6:22 ` Teres Alexis, Alan Previn
2022-09-20 14:33 ` Tvrtko Ursulin
2022-09-21 7:59 ` Teres Alexis, Alan Previn
2022-09-21 22:30 ` Teres Alexis, Alan Previn
2022-09-21 22:30 ` Teres Alexis, Alan Previn
2022-09-15 3:22 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Delay disabling GuC scheduling of an idle context Patchwork
2022-09-15 3:41 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-15 20:41 ` [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=20220915021218.1412111-1-alan.previn.teres.alexis@intel.com \
--to=alan.previn.teres.alexis@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 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.