Messages in this thread | | | From | Yuyang Du <> | Date | Fri, 26 Apr 2019 13:41:45 +0800 | Subject | Re: [PATCH 02/28] locking/lockdep: Add description and explanation in lockdep design doc |
| |
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 resend the patch or you modify it?
On Thu, 25 Apr 2019 at 22:01, Peter Zijlstra <peterz@infradead.org> wrote: > > 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 lock-class. > > That's not entirely accurate anymore. Bart van Assche recently added > lockdep_{,un}register_key().
| |