Hi
On Mon, Nov 13, 2023 at 08:39:42AM +0100, Daniel Vetter wrote:
> This conflicts with the kthread change in 6.7-rc1 6309727ef271
> ("kthread: add kthread_stop_put")
>
> Please double-check that the conflict resolution I've done in drm-tip
> is correct and then ask drm-misc/accel maintainers to
This conflicts with the kthread change in 6.7-rc1 6309727ef271
("kthread: add kthread_stop_put")
Please double-check that the conflict resolution I've done in drm-tip
is correct and then ask drm-misc/accel maintainers to backmerge -rc2
to bake this in properly. Adding them as fyi.
-Sima
On Sat,
On 10/28/2023 9:59 AM, Stanislaw Gruszka wrote:
Stop job_done thread when going to suspend. Use kthread_park() instead
of kthread_stop() to avoid memory allocation and potential failure
on resume.
Use separate function as thread wake up condition. Use spin lock to assure
rx_msg_list is properly
Stop job_done thread when going to suspend. Use kthread_park() instead
of kthread_stop() to avoid memory allocation and potential failure
on resume.
Use separate function as thread wake up condition. Use spin lock to assure
rx_msg_list is properly protected against concurrent access.
Reviewed-by:
