From: John.C.Harrison@Intel.com
To: Intel-GFX@Lists.FreeDesktop.Org
Cc: John Harrison <John.C.Harrison@Intel.com>,
DRI-Devel@Lists.FreeDesktop.Org
Subject: [PATCH v2 0/2] Fix for two GuC issues
Date: Wed, 2 Nov 2022 12:21:07 -0700 [thread overview]
Message-ID: <20221102192109.2492625-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.
v2: Rename existing uses of _trylock rather than adding a _noretry
version. Also improve the comment a bit.
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/gem/i915_gem_mman.c | 2 +-
drivers/gpu/drm/i915/gt/intel_reset.c | 18 ++++++++++++++++--
drivers/gpu/drm/i915/gt/intel_reset.h | 1 +
.../gpu/drm/i915/gt/uc/intel_guc_submission.c | 7 ++++++-
4 files changed, 24 insertions(+), 4 deletions(-)
--
2.37.3
WARNING: multiple messages have this Message-ID (diff)
From: John.C.Harrison@Intel.com
To: Intel-GFX@Lists.FreeDesktop.Org
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: [Intel-gfx] [PATCH v2 0/2] Fix for two GuC issues
Date: Wed, 2 Nov 2022 12:21:07 -0700 [thread overview]
Message-ID: <20221102192109.2492625-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.
v2: Rename existing uses of _trylock rather than adding a _noretry
version. Also improve the comment a bit.
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/gem/i915_gem_mman.c | 2 +-
drivers/gpu/drm/i915/gt/intel_reset.c | 18 ++++++++++++++++--
drivers/gpu/drm/i915/gt/intel_reset.h | 1 +
.../gpu/drm/i915/gt/uc/intel_guc_submission.c | 7 ++++++-
4 files changed, 24 insertions(+), 4 deletions(-)
--
2.37.3
next reply other threads:[~2022-11-02 19:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 19:21 John.C.Harrison [this message]
2022-11-02 19:21 ` [Intel-gfx] [PATCH v2 0/2] Fix for two GuC issues John.C.Harrison
2022-11-02 19:21 ` [PATCH v2 1/2] drm/i915/guc: Properly initialise kernel contexts John.C.Harrison
2022-11-02 19:21 ` [Intel-gfx] " John.C.Harrison
2022-11-04 18:53 ` Ceraolo Spurio, Daniele
2022-11-04 18:53 ` [Intel-gfx] " Ceraolo Spurio, Daniele
2022-11-04 18:58 ` John Harrison
2022-11-04 18:58 ` [Intel-gfx] " John Harrison
2022-11-05 5:18 ` Lucas De Marchi
2022-11-05 5:18 ` [Intel-gfx] " Lucas De Marchi
2022-11-02 19:21 ` [PATCH v2 2/2] drm/i915/guc: Don't deadlock busyness stats vs reset John.C.Harrison
2022-11-02 19:21 ` [Intel-gfx] " John.C.Harrison
2022-11-03 11:31 ` Tvrtko Ursulin
2022-11-03 18:45 ` John Harrison
2022-11-03 18:54 ` Umesh Nerlige Ramappa
2022-11-03 18:54 ` Umesh Nerlige Ramappa
2022-11-02 20:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Fix for two GuC issues (rev2) Patchwork
2022-11-03 4:45 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-11-04 19:40 ` John Harrison
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=20221102192109.2492625-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 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.