On Thu, Apr 02, 2015 at 07:25:13PM +0200, Peter Zijlstra wrote:
> On Thu, Apr 02, 2015 at 12:03:08PM -0400, Sasha Levin wrote:
> > It's not correct.
>
> Yay for lockdep ;-)
>
> > [0.645644] debug_check_no_locks_held (kernel/locking/lockdep.c:4178)
>
> Should we also have that call in freezer
On Thu, Apr 02, 2015 at 12:03:08PM -0400, Sasha Levin wrote:
> It's not correct.
Yay for lockdep ;-)
> [0.645644] debug_check_no_locks_held (kernel/locking/lockdep.c:4178)
Should we also have that call in freezer_do_not_count() ?
--
To unsubscribe from this list: send the line "unsubscribe l
On 03/31/2015 11:07 AM, Peter Zijlstra wrote:
>>> @@ -1781,7 +1781,7 @@ schedule_hrtimeout_range_clock(ktime_t *
>>> > > t.task = NULL;
>>> > >
>>> > > if (likely(t.task))
>>> > > - schedule();
>>> > > + freezable_schedule();
>>> > >
>>> > >
On Tue, Mar 31, 2015 at 01:39:07AM +0200, Rafael J. Wysocki wrote:
> > From: Maninder Singh
> > Subject: kernel/time/hrtimer.c: restart_syscall: use freezable blocking call
> >
> > Avoid waking up every thread sleeping in a restart_syscall call during
> > suspend and resume by calling a freezable
CC more maintainers.
On Monday, March 30, 2015 03:43:51 PM Andrew Morton wrote:
> On Mon, 30 Mar 2015 11:07:35 + (GMT) Maninder Singh
> wrote:
>
> > Hello All,
> >
> > Avoid waking up every thread sleeping in a restart_syscall call during
> > suspend and resume by calling a freezable blo
On Mon, 30 Mar 2015 11:07:35 + (GMT) Maninder Singh
wrote:
> Hello All,
>
> Avoid waking up every thread sleeping in a restart_syscall call during
> suspend and resume by calling a freezable blocking call.
> Previous patches modified the freezer to avoid sending wakeups to threads
> tha
6 matches
Mail list logo
