Re: [Intel-gfx] [PATCH 2/3] drm/i915: Fix incorrect assert about pending power domain async-put work

2021-06-03 Thread Gupta, Anshuman
> -Original Message- > From: Deak, Imre > Sent: Wednesday, June 2, 2021 7:31 PM > To: Gupta, Anshuman > Cc: intel-gfx@lists.freedesktop.org > Subject: Re: [Intel-gfx] [PATCH 2/3] drm/i915: Fix incorrect assert about > pending > power domain async-put work &

Re: [Intel-gfx] [PATCH 2/3] drm/i915: Fix incorrect assert about pending power domain async-put work

2021-06-02 Thread Imre Deak
On Wed, Jun 02, 2021 at 02:35:28PM +0530, Anshuman Gupta wrote: > On 2021-05-26 at 20:07:28 +0530, Imre Deak wrote: > > It's possible that an already dequeued put_async_work() will release the > > reference (*) that was put asynchronously after the dequeue happened. > > This leaves an async-put

Re: [Intel-gfx] [PATCH 2/3] drm/i915: Fix incorrect assert about pending power domain async-put work

2021-06-02 Thread Anshuman Gupta
On 2021-05-26 at 20:07:28 +0530, Imre Deak wrote: > It's possible that an already dequeued put_async_work() will release the > reference (*) that was put asynchronously after the dequeue happened. > This leaves an async-put work pending, without any reference to release. > A subsequent async-put

[Intel-gfx] [PATCH 2/3] drm/i915: Fix incorrect assert about pending power domain async-put work

2021-05-26 Thread Imre Deak
It's possible that an already dequeued put_async_work() will release the reference (*) that was put asynchronously after the dequeue happened. This leaves an async-put work pending, without any reference to release. A subsequent async-put may trigger the