From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Jana, Mousumi" <mousumi.jana@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Ursulin, Tvrtko" <tvrtko.ursulin@intel.com>
Subject: Re: [PATCH v8 2/2] drm/i915/guc: Close deregister-context race against CT-loss
Date: Tue, 26 Dec 2023 10:11:56 -0500 [thread overview]
Message-ID: <ZYrtPPQARTXBSAgM@intel.com> (raw)
In-Reply-To: <b89b77629fa2c54a7bef358eb66d89cfe454ba5e.camel@intel.com>
On Wed, Dec 20, 2023 at 11:08:59PM +0000, Teres Alexis, Alan Previn wrote:
> On Wed, 2023-12-13 at 16:23 -0500, Vivi, Rodrigo wrote:
> > On Tue, Dec 12, 2023 at 08:57:16AM -0800, Alan Previn wrote:
> > > If we are at the end of suspend or very early in resume
> > > its possible an async fence signal (via rcu_call) is triggered
> > > to free_engines which could lead us to the execution of
> > > the context destruction worker (after a prior worker flush).
> alan:snip
> >
> > > Thus, do an unroll in guc_lrc_desc_unpin and deregister_destroyed_-
> > > contexts if guc_lrc_desc_unpin fails due to CT send falure.
> > > When unrolling, keep the context in the GuC's destroy-list so
> > > it can get picked up on the next destroy worker invocation
> > > (if suspend aborted) or get fully purged as part of a GuC
> > > sanitization (end of suspend) or a reset flow.
> > >
> > > Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com>
> > > Signed-off-by: Anshuman Gupta <anshuman.gupta@intel.com>
> > > Tested-by: Mousumi Jana <mousumi.jana@intel.com>
> > > Acked-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> >
> > Thanks for all the explanations, patience and great work!
> >
> > Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> alan: Thanks Rodrigo for the RB last week, just quick update:
>
> I've cant reproduce the BAT failures that seem to be intermittent
> on platform and test - however, a noticable number of failures
> do keep occuring on i915_selftest @live @requests where the
> last test leaked a wakeref and the failing test hangs waiting
> for gt to idle before starting its test.
>
> i have to debug this further although from code inspection
> is unrelated to the patches in this series.
> Hopefully its a different issue.
Yeap, likely not related. Anyway, I'm sorry for not merging
this sooner. Could you please send a rebased version? This
on is not applying cleanly anymore.
next prev parent reply other threads:[~2023-12-26 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 16:57 [PATCH v8 0/2] Resolve suspend-resume racing with GuC destroy-context-worker Alan Previn
2023-12-12 16:57 ` [PATCH v8 1/2] drm/i915/guc: Flush context destruction worker at suspend Alan Previn
2023-12-12 16:57 ` [PATCH v8 2/2] drm/i915/guc: Close deregister-context race against CT-loss Alan Previn
2023-12-13 21:23 ` Rodrigo Vivi
2023-12-20 23:08 ` Teres Alexis, Alan Previn
2023-12-26 15:11 ` Rodrigo Vivi [this message]
2023-12-28 4:00 ` Teres Alexis, Alan Previn
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=ZYrtPPQARTXBSAgM@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mousumi.jana@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;
as well as URLs for NNTP newsgroup(s).