[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180212170747.GX695913@devbig577.frc2.facebook.com>
Date: Mon, 12 Feb 2018 09:07:47 -0800
From: Tejun Heo <tj@...nel.org>
To: Lukas Wunner <lukas@...ner.de>
Cc: Lai Jiangshan <jiangshanlai@...il.com>,
Alex Deucher <alexander.deucher@....com>,
Dave Airlie <airlied@...hat.com>,
Ben Skeggs <bskeggs@...hat.com>,
dri-devel@...ts.freedesktop.org, Peter Wu <peter@...ensteyn.nl>,
nouveau@...ts.freedesktop.org, Lyude Paul <lyude@...hat.com>,
Hans de Goede <hdegoede@...hat.com>,
Pierre Moreau <pierre.morrow@...e.fr>,
linux-kernel@...r.kernel.org,
Ismo Toijala <ismo.toijala@...il.com>,
intel-gfx@...ts.freedesktop.org, Liviu Dudau <Liviu.Dudau@....com>,
Archit Taneja <architt@...eaurora.org>
Subject: Re: [PATCH 1/5] workqueue: Allow retrieval of current task's work
struct
Hello,
On Sun, Feb 11, 2018 at 10:38:28AM +0100, Lukas Wunner wrote:
> Introduce a helper to retrieve the current task's work struct if it is
> a workqueue worker.
>
> This allows us to fix a long-standing deadlock in several DRM drivers
> wherein the ->runtime_suspend callback waits for a specific worker to
> finish and that worker in turn calls a function which waits for runtime
> suspend to finish. That function is invoked from multiple call sites
> and waiting for runtime suspend to finish is the correct thing to do
> except if it's executing in the context of the worker.
>
> Cc: Tejun Heo <tj@...nel.org>
> Cc: Lai Jiangshan <jiangshanlai@...il.com>
> Cc: Dave Airlie <airlied@...hat.com>
> Cc: Ben Skeggs <bskeggs@...hat.com>
> Cc: Alex Deucher <alexander.deucher@....com>
> Signed-off-by: Lukas Wunner <lukas@...ner.de>
I wonder whether it's too generic a name but there are other functions
named in a similar fashion and AFAICS current_work isn't used by
anyone in the tree, so it seems okay.
Acked-by: Tejun Heo <tj@...nel.org>
Please feel free to route as you see fit.
Thanks.
--
tejun
Powered by blists - more mailing lists