Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1591140 > unrolled thread
| Started by | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| First post | 2017-03-02 15:40 +0100 |
| Last post | 2017-03-03 01:00 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v5 06/13] lockdep: Implement crossrelease feature Peter Zijlstra <peterz@infradead.org> - 2017-03-02 15:40 +0100
Re: [PATCH v5 06/13] lockdep: Implement crossrelease feature Byungchul Park <byungchul.park@lge.com> - 2017-03-03 01:00 +0100
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Date | 2017-03-02 15:40 +0100 |
| Subject | Re: [PATCH v5 06/13] lockdep: Implement crossrelease feature |
| Message-ID | <tgA3D-3wp-5@gated-at.bofh.it> |
On Wed, Jan 18, 2017 at 10:17:32PM +0900, Byungchul Park wrote: > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > index a6c8db1..7890661 100644 > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -1042,6 +1042,19 @@ config DEBUG_LOCK_ALLOC > spin_lock_init()/mutex_init()/etc., or whether there is any lock > held during task exit. > > +config LOCKDEP_CROSSRELEASE > + bool "Lock debugging: make lockdep work for crosslocks" > + select LOCKDEP > + select TRACE_IRQFLAGS > + 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 Does CROSSRELEASE && !PROVE_LOCKING make any sense?
[toc] | [next] | [standalone]
| From | Byungchul Park <byungchul.park@lge.com> |
|---|---|
| Date | 2017-03-03 01:00 +0100 |
| Message-ID | <tgINA-13L-29@gated-at.bofh.it> |
| In reply to | #1591140 |
On Thu, Mar 02, 2017 at 02:41:03PM +0100, Peter Zijlstra wrote: > On Wed, Jan 18, 2017 at 10:17:32PM +0900, Byungchul Park wrote: > > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > > index a6c8db1..7890661 100644 > > --- a/lib/Kconfig.debug > > +++ b/lib/Kconfig.debug > > @@ -1042,6 +1042,19 @@ config DEBUG_LOCK_ALLOC > > spin_lock_init()/mutex_init()/etc., or whether there is any lock > > held during task exit. > > > > +config LOCKDEP_CROSSRELEASE > > + bool "Lock debugging: make lockdep work for crosslocks" > > + select LOCKDEP > > + select TRACE_IRQFLAGS > > + 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 > > > Does CROSSRELEASE && !PROVE_LOCKING make any sense? No, it does not make sense. I will fix it. Thank you.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web