Re: [PATCH 02/28] locking/lockdep: Add description and explanation in lockdep design doc

2019-04-25 Thread Yuyang Du
Thank you very much for review. You mean class can go away? Before Bart's addition, it can go away. Right? I think maybe the original point of "never go away" in that context did not intend to talk about a class's real disappearance. Anyway, the points should be made comprehensive. You want me to

Re: [PATCH 02/28] locking/lockdep: Add description and explanation in lockdep design doc

2019-04-25 Thread Peter Zijlstra
On Wed, Apr 24, 2019 at 06:19:08PM +0800, Yuyang Du wrote: > +Unlike a lock instance, a lock-class itself never goes away: when a > +lock-class's instance is used for the first time after bootup the class gets > +registered, and all (subsequent) instances of that lock-class will be mapped > +to the

[PATCH 02/28] locking/lockdep: Add description and explanation in lockdep design doc

2019-04-24 Thread Yuyang Du
More words are added to lockdep design document regarding key concepts, which should help people without lockdep experience read and understand lockdep reports. Signed-off-by: Yuyang Du --- Documentation/locking/lockdep-design.txt | 74 1 file changed, 56 inserti