From: John.C.Harrison@Intel.com
To: Intel-GFX@Lists.FreeDesktop.Org
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: [Intel-gfx] [PATCH 0/2] Fix for two GuC issues
Date: Fri, 28 Oct 2022 12:46:47 -0700 [thread overview]
Message-ID: <20221028194649.1130223-1-John.C.Harrison@Intel.com> (raw)
From: John Harrison <John.C.Harrison@Intel.com>
Fix for a deadlock issue between the GuC busyness stats worker and GT
resets. Also fix kernel contexts not getting the correct scheduling
priority at start of day.
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
John Harrison (2):
drm/i915/guc: Properly initialise kernel contexts
drm/i915/guc: Don't deadlock busyness stats vs reset
drivers/gpu/drm/i915/gt/intel_reset.c | 15 ++++++++++++++-
drivers/gpu/drm/i915/gt/intel_reset.h | 1 +
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 9 +++++++--
3 files changed, 22 insertions(+), 3 deletions(-)
--
2.37.3
next reply other threads:[~2022-10-28 19:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 19:46 John.C.Harrison [this message]
2022-10-28 19:46 ` [Intel-gfx] [PATCH 1/2] drm/i915/guc: Properly initialise kernel contexts John.C.Harrison
2022-10-28 19:46 ` [Intel-gfx] [PATCH 2/2] drm/i915/guc: Don't deadlock busyness stats vs reset John.C.Harrison
2022-10-31 10:09 ` Tvrtko Ursulin
2022-10-31 12:51 ` Tvrtko Ursulin
2022-10-31 18:30 ` John Harrison
2022-11-01 9:58 ` Tvrtko Ursulin
2022-11-01 16:56 ` John Harrison
2022-11-02 8:17 ` Tvrtko Ursulin
2022-10-28 20:58 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Fix for two GuC issues Patchwork
2022-10-29 0:07 ` [Intel-gfx] ✗ Fi.CI.BAT: 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=20221028194649.1130223-1-John.C.Harrison@Intel.com \
--to=john.c.harrison@intel.com \
--cc=DRI-Devel@Lists.FreeDesktop.Org \
--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