Re: [RFC PATCH 01/12] locking/lockdep: Rework lockdep_set_novalidate_class()

2018-11-10 Thread Peter Zijlstra
On Sat, Nov 10, 2018 at 07:26:51PM -0500, Waiman Long wrote: > On 11/10/2018 09:14 AM, Peter Zijlstra wrote: > > On Thu, Nov 08, 2018 at 03:34:17PM -0500, Waiman Long wrote: > >> The current lockdep_set_novalidate_class() implementation is like > >> a hack. It assigns a special class key for that l

Re: [RFC PATCH 01/12] locking/lockdep: Rework lockdep_set_novalidate_class()

2018-11-10 Thread Waiman Long
On 11/10/2018 09:14 AM, Peter Zijlstra wrote: > On Thu, Nov 08, 2018 at 03:34:17PM -0500, Waiman Long wrote: >> The current lockdep_set_novalidate_class() implementation is like >> a hack. It assigns a special class key for that lock and calls >> lockdep_init_map() twice. > Ideally it would go away

Re: [RFC PATCH 01/12] locking/lockdep: Rework lockdep_set_novalidate_class()

2018-11-10 Thread Peter Zijlstra
On Thu, Nov 08, 2018 at 03:34:17PM -0500, Waiman Long wrote: > The current lockdep_set_novalidate_class() implementation is like > a hack. It assigns a special class key for that lock and calls > lockdep_init_map() twice. Ideally it would go away.. it is not thing that should be used. > This patc