Re: [PATCH 6/7] smp/hotplug: Differentiate the AP-work lockdep class between up and down

2017-11-30 Thread Lai Jiangshan
On Thu, Sep 21, 2017 at 1:00 AM, Peter Zijlstra wrote: > With lockdep-crossrelease we get deadlock reports that span cpu-up and > cpu-down chains. Such deadlocks cannot possibly happen because cpu-up > and cpu-down are globally serialized. > > CPU0 CPU1

Re: [PATCH 6/7] smp/hotplug: Differentiate the AP-work lockdep class between up and down

2017-11-30 Thread Lai Jiangshan
On Thu, Sep 21, 2017 at 1:00 AM, Peter Zijlstra wrote: > With lockdep-crossrelease we get deadlock reports that span cpu-up and > cpu-down chains. Such deadlocks cannot possibly happen because cpu-up > and cpu-down are globally serialized. > > CPU0 CPU1CPU2

Re: [PATCH 6/7] smp/hotplug: Differentiate the AP-work lockdep class between up and down

2017-09-25 Thread Peter Zijlstra
On Mon, Sep 25, 2017 at 05:54:59PM +0900, Byungchul Park wrote: > On Wed, Sep 20, 2017 at 07:00:20PM +0200, Peter Zijlstra wrote: > > With lockdep-crossrelease we get deadlock reports that span cpu-up and > > cpu-down chains. Such deadlocks cannot possibly happen because cpu-up > > and cpu-down

Re: [PATCH 6/7] smp/hotplug: Differentiate the AP-work lockdep class between up and down

2017-09-25 Thread Peter Zijlstra
On Mon, Sep 25, 2017 at 05:54:59PM +0900, Byungchul Park wrote: > On Wed, Sep 20, 2017 at 07:00:20PM +0200, Peter Zijlstra wrote: > > With lockdep-crossrelease we get deadlock reports that span cpu-up and > > cpu-down chains. Such deadlocks cannot possibly happen because cpu-up > > and cpu-down

Re: [PATCH 6/7] smp/hotplug: Differentiate the AP-work lockdep class between up and down

2017-09-25 Thread Byungchul Park
On Wed, Sep 20, 2017 at 07:00:20PM +0200, Peter Zijlstra wrote: > With lockdep-crossrelease we get deadlock reports that span cpu-up and > cpu-down chains. Such deadlocks cannot possibly happen because cpu-up > and cpu-down are globally serialized. > > CPU0 CPU1

Re: [PATCH 6/7] smp/hotplug: Differentiate the AP-work lockdep class between up and down

2017-09-25 Thread Byungchul Park
On Wed, Sep 20, 2017 at 07:00:20PM +0200, Peter Zijlstra wrote: > With lockdep-crossrelease we get deadlock reports that span cpu-up and > cpu-down chains. Such deadlocks cannot possibly happen because cpu-up > and cpu-down are globally serialized. > > CPU0 CPU1

[PATCH 6/7] smp/hotplug: Differentiate the AP-work lockdep class between up and down

2017-09-20 Thread Peter Zijlstra
With lockdep-crossrelease we get deadlock reports that span cpu-up and cpu-down chains. Such deadlocks cannot possibly happen because cpu-up and cpu-down are globally serialized. CPU0 CPU1CPU2 cpuhp_up_callbacks: takedown_cpu: cpuhp_thread_fun:

[PATCH 6/7] smp/hotplug: Differentiate the AP-work lockdep class between up and down

2017-09-20 Thread Peter Zijlstra
With lockdep-crossrelease we get deadlock reports that span cpu-up and cpu-down chains. Such deadlocks cannot possibly happen because cpu-up and cpu-down are globally serialized. CPU0 CPU1CPU2 cpuhp_up_callbacks: takedown_cpu: cpuhp_thread_fun: