Re: [RFC 05/12] lockdep: Implement crossrelease feature

2016-06-30 Thread Byungchul Park
On Thu, Jun 30, 2016 at 03:03:57PM +0200, Peter Zijlstra wrote: > On Mon, Jun 20, 2016 at 01:55:20PM +0900, Byungchul Park wrote: > > +struct cross_lock { > > + unsigned intgen_id; > > 4 byte hole > > > + struct list_headxlock_entry; > > + > > + /* > > +* Seperated

Re: [RFC 05/12] lockdep: Implement crossrelease feature

2016-06-30 Thread Byungchul Park
On Thu, Jun 30, 2016 at 03:03:57PM +0200, Peter Zijlstra wrote: > On Mon, Jun 20, 2016 at 01:55:20PM +0900, Byungchul Park wrote: > > +struct cross_lock { > > + unsigned intgen_id; > > 4 byte hole > > > + struct list_headxlock_entry; > > + > > + /* > > +* Seperated

Re: [RFC 05/12] lockdep: Implement crossrelease feature

2016-06-30 Thread Peter Zijlstra
On Mon, Jun 20, 2016 at 01:55:20PM +0900, Byungchul Park wrote: > +struct cross_lock { > + unsigned intgen_id; 4 byte hole > + struct list_headxlock_entry; > + > + /* > + * Seperated hlock instance. This will be used when > + * building a dependency

Re: [RFC 05/12] lockdep: Implement crossrelease feature

2016-06-30 Thread Peter Zijlstra
On Mon, Jun 20, 2016 at 01:55:20PM +0900, Byungchul Park wrote: > +struct cross_lock { > + unsigned intgen_id; 4 byte hole > + struct list_headxlock_entry; > + > + /* > + * Seperated hlock instance. This will be used when > + * building a dependency

[RFC 05/12] lockdep: Implement crossrelease feature

2016-06-19 Thread Byungchul Park
Crossrelease feature calls a lock which is releasable by a different context from the context having acquired the lock, crosslock. For crosslock, all locks having been held in the context unlocking the crosslock, until eventually the crosslock will be unlocked, have dependency with the crosslock.

[RFC 05/12] lockdep: Implement crossrelease feature

2016-06-19 Thread Byungchul Park
Crossrelease feature calls a lock which is releasable by a different context from the context having acquired the lock, crosslock. For crosslock, all locks having been held in the context unlocking the crosslock, until eventually the crosslock will be unlocked, have dependency with the crosslock.