[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a2d9da054ace3f0ff59373c5a6252f25e1c3df4b.camel@redhat.com>
Date: Tue, 14 Apr 2020 12:52:51 -0400
From: Lyude Paul <lyude@...hat.com>
To: Tejun Heo <tj@...nel.org>
Cc: Daniel Vetter <daniel@...ll.ch>, nouveau@...ts.freedesktop.org,
dri-devel@...ts.freedesktop.org,
Ville Syrjälä
<ville.syrjala@...ux.intel.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...ux.ie>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/9] drm/vblank: Add vblank works
On Mon, 2020-04-13 at 16:42 -0400, Tejun Heo wrote:
> Hello,
>
> On Mon, Apr 13, 2020 at 04:18:57PM -0400, Lyude Paul wrote:
> > Hi Tejun! Sorry to bother you, but have you had a chance to look at any of
> > this yet? Would like to continue moving this forward
>
> Sorry, wasn't following this thread. Have you looked at kthread_worker?
>
Hi, thanks for the response! And yes-I think this would actually be perfect
for what we need, I guess one question I might as well ask since I've got you
here: would patches to expose an unlocked version of kthread_queue_worker() be
accepted? With something like that I should be able to just reuse the
delayed_work_list and spinlocks that come with kthread_worker which would make
the vblank works implementation a bit easier
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/kthread.h#n71
>
> And, thanks a lot for the vblank explanation. I really enjoyed readin it. :)
>
--
Cheers,
Lyude Paul (she/her)
Associate Software Engineer at Red Hat
Powered by blists - more mailing lists