Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"Ursulin, Tvrtko" <tvrtko.ursulin@intel.com>
Subject: Re: [PATCH v9 0/2] Resolve suspend-resume racing with GuC destroy-context-worker
Date: Tue, 2 Jan 2024 17:40:44 +0000	[thread overview]
Message-ID: <6711fcb78aba723e1f04e607226e859047fa0916.camel@intel.com> (raw)
In-Reply-To: <20231228045558.536585-1-alan.previn.teres.alexis@intel.com>

On Wed, 2023-12-27 at 20:55 -0800, Teres Alexis, Alan Previn wrote:
> This series is the result of debugging issues root caused to
> races between the GuC's destroyed_worker_func being triggered
> vs repeating suspend-resume cycles with concurrent delayed
> fence signals for engine-freeing.
> 
alan:snip.

alan: I did not receive the CI-premerge email where the following was reported:
      IGT changes
      Possible regressions
      igt@i915_selftest@live@gt_pm:
      shard-rkl: PASS -> DMESG-FAIL
After going thru the error in dmesg and codes, i am confident this failure not
related to the series. This selftest calls rdmsrl functions (that doen't do
any requests / guc submissions) but gets a reply power of zero (the bug reported).
So this is unrelated.


Hi @"Vivi, Rodrigo" <rodrigo.vivi@intel.com>, just an FYI note that after the last
requested rebase, BAT passed twice in a row now so i am confident failures on rev7
and prior was unrelated and that this series is ready for merging. Thanks again
for all your help and patiences - this was a long one  :)

  parent reply	other threads:[~2024-01-02 17:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-28  4:55 [PATCH v9 0/2] Resolve suspend-resume racing with GuC destroy-context-worker Alan Previn
2023-12-28  4:55 ` [PATCH v9 1/2] drm/i915/guc: Flush context destruction worker at suspend Alan Previn
2023-12-28  4:55 ` [PATCH v9 2/2] drm/i915/guc: Close deregister-context race against CT-loss Alan Previn
2023-12-29 21:51   ` Alan Previn
2024-01-02 17:40 ` Teres Alexis, Alan Previn [this message]
2024-01-04  8:32 ` ✗ Fi.CI.SPARSE: warning for Resolve suspend-resume racing with GuC destroy-context-worker (rev13) Patchwork
2024-01-04  8:43 ` ✓ Fi.CI.BAT: success " Patchwork
2024-01-04 10:57 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-01-04 17:39   ` Teres Alexis, Alan Previn
2024-01-09 17:41     ` Matt Roper
2024-01-09 22:42     ` Rodrigo Vivi

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=6711fcb78aba723e1f04e607226e859047fa0916.camel@intel.com \
    --to=alan.previn.teres.alexis@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=tvrtko.ursulin@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