lkml.org 
[lkml]   [2017]   [Apr]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH v6 05/15] lockdep: Implement crossrelease feature
    On Wed, Apr 19, 2017 at 07:20:19PM +0200, Peter Zijlstra wrote:
    > On Tue, Mar 14, 2017 at 05:18:52PM +0900, Byungchul Park wrote:
    > > +config LOCKDEP_CROSSRELEASE
    > > + bool "Lock debugging: make lockdep work for crosslocks"
    > > + select PROVE_LOCKING
    >
    > depends PROVE_LOCKING
    >
    > instead ?

    OK. I will change it.

    >
    > > + default n
    > > + help
    > > + This makes lockdep work for crosslock which is a lock allowed to
    > > + be released in a different context from the acquisition context.
    > > + Normally a lock must be released in the context acquiring the lock.
    > > + However, relexing this constraint helps synchronization primitives
    > > + such as page locks or completions can use the lock correctness
    > > + detector, lockdep.
    > > +
    > > config PROVE_LOCKING
    > > bool "Lock debugging: prove locking correctness"
    > > depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
    > > --
    > > 1.9.1
    > >

    \
     
     \ /
      Last update: 2017-04-24 05:15    [W:3.088 / U:0.336 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site