Re: [PATCH v4 2/3] drm/i915/guc: Close deregister-context race against CT-loss

2023-10-04 Thread Teres Alexis, Alan Previn
On Wed, 2023-10-04 at 06:34 +, Gupta, Anshuman wrote: > > > -Original Message- > > From: Teres Alexis, Alan Previn > @@ -289,6 +289,13 @@ int intel_gt_resume(struct intel_gt *gt) > > > > static void wait_for_suspend(struct intel_gt *gt) { > > + /* > > +* On rare occasions,

RE: [PATCH v4 2/3] drm/i915/guc: Close deregister-context race against CT-loss

2023-10-04 Thread Gupta, Anshuman
, John C > ; Anshuman Gupta Alan Previn > ; Gupta, > Anshuman ; Jana, Mousumi > > Subject: [PATCH v4 2/3] drm/i915/guc: Close deregister-context race against > CT- > loss > > If we are at the end of suspend or very early in resume its possible an async > fence > si

[PATCH v4 2/3] drm/i915/guc: Close deregister-context race against CT-loss

2023-09-26 Thread Alan Previn
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). Thus, when suspending, insert an rcu_barrier at the start of