[PATCH v9 0/2] Resolve suspend-resume racing with GuC destroy-context-worker

Teres Alexis, Alan Previn alan.previn.teres.alexis at intel.com
Tue Jan 2 17:40:44 UTC 2024


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 at i915_selftest@live at 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 at 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  :)


More information about the Intel-gfx mailing list