Re: [PATCH] PM-runtime: fix deadlock with ktime

2019-01-30 Thread Vincent Guittot
On Wed, 30 Jan 2019 at 10:39, Rafael J. Wysocki wrote: > > On Wed, Jan 30, 2019 at 10:14 AM Vincent Guittot > wrote: > > > > Hi Geert, > > > > On Wed, 30 Jan 2019 at 09:21, Geert Uytterhoeven > > wrote: > > > > > > Hi Vincent, > > > > > > On Wed, Jan 30, 2019 at 9:16 AM Vincent Guittot > > > w

Re: [PATCH] PM-runtime: fix deadlock with ktime

2019-01-30 Thread Rafael J. Wysocki
On Wed, Jan 30, 2019 at 10:14 AM Vincent Guittot wrote: > > Hi Geert, > > On Wed, 30 Jan 2019 at 09:21, Geert Uytterhoeven wrote: > > > > Hi Vincent, > > > > On Wed, Jan 30, 2019 at 9:16 AM Vincent Guittot > > wrote: > > > A deadlock has been seen when swicthing clocksources which use PM runtime

Re: [PATCH] PM-runtime: fix deadlock with ktime

2019-01-30 Thread Vincent Guittot
Hi Geert, On Wed, 30 Jan 2019 at 09:21, Geert Uytterhoeven wrote: > > Hi Vincent, > > On Wed, Jan 30, 2019 at 9:16 AM Vincent Guittot > wrote: > > A deadlock has been seen when swicthing clocksources which use PM runtime. > > The call path is: > > change_clocksource > > ... > > write_seq

Re: [PATCH] PM-runtime: fix deadlock with ktime

2019-01-30 Thread Geert Uytterhoeven
Hi Vincent, On Wed, Jan 30, 2019 at 9:16 AM Vincent Guittot wrote: > A deadlock has been seen when swicthing clocksources which use PM runtime. > The call path is: > change_clocksource > ... > write_seqcount_begin > ... > timekeeping_update > ... > sh_cmt_clocksour

[PATCH] PM-runtime: fix deadlock with ktime

2019-01-30 Thread Vincent Guittot
A deadlock has been seen when swicthing clocksources which use PM runtime. The call path is: change_clocksource ... write_seqcount_begin ... timekeeping_update ... sh_cmt_clocksource_enable ... rpm_resume pm_runtime_mark_last_b