Messages in this thread | | | Date | Thu, 7 Jul 2016 19:22:06 +0900 | From | Byungchul Park <> | Subject | Re: [PATCH 1/5] lockdep: Implement bitlock map allocator |
| |
On Mon, Jul 04, 2016 at 04:29:25PM +0900, Byungchul Park wrote: > > > 3. I think this is more general approach because _any_ random bit in > > > memory can be used as a lock. Do we need to restrict where the bit > > > is so that we can place lockdep_map explicitly around the bit? > > > > Again, yuck! > > You mean we should never provide lockdep checking mechanism tranparently, > but the user of bit-based lock must add lockdep_map manually, case by > case. Right? Do I understand correctly? If so, I wonder why?
I will stop it if it cannot provide any valuable things even I wonder. I seriously asked it since I wonder it. What do you think about my question? Is there something I missed?
Or can I proceed it after fixing my bug you pointed?
| |