lkml.org 
[lkml]   [2010]   [Apr]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH] Add "nested" field to event of lock_release
    From
    Date
    On Sat, 2010-04-10 at 23:50 +0900, Hitoshi Mitake wrote:
    > On 04/10/10 22:59, Peter Zijlstra wrote:
    > > On Sat, 2010-04-10 at 19:41 +0900, Hitoshi Mitake wrote:
    > >> State machine of perf lock requires "nested" field of lock_release(),
    > >> so this patch adds it to event.
    > >>
    > >> Signed-off-by: Hitoshi Mitake<mitake@dcl.info.waseda.ac.jp>
    > >> Cc: Peter Zijlstra<a.p.zijlstra@chello.nl>
    > >> Cc: Paul Mackerras<paulus@samba.org>
    > >> Cc: Arnaldo Carvalho de Melo<acme@redhat.com>
    > >> Cc: Frederic Weisbecker<fweisbec@gmail.com>
    > >
    > > The nested flag only indicates if it could be nested, not if it was
    > > actually nested. So no, this doesn't make any sense at all.
    > >
    > > (in fact, pretty much every lock_release out there has nested=1)
    > >

    Just to clarify, nested=0 means the released lock needs to be at the top
    of the lock stack. This means all locking needs to be perfectly
    balanced:

    lock A
    lock B

    unlock A
    unlock B

    Would be an invalid sequence in that scenario. I think when lockdep was
    started it was thought it would be nice to be able to clean up locking
    to be always perfectly balanced, but it was found quite early to be too
    much, so it got relaxed to always nested=1, allowing the above sequence.





    \
     
     \ /
      Last update: 2010-04-10 21:23    [W:4.775 / U:1.264 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site