From: Ingo Molnar <mingo@kernel.org>
To: torvalds@linux-foundation.org, peterz@infradead.org,
tglx@linutronix.de, linux-kernel@vger.kernel.org,
byungchul.park@lge.com, hpa@zytor.com
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:locking/core] locking/lockdep: Make CONFIG_LOCKDEP_CROSSRELEASE part of CONFIG_PROVE_LOCKING
Date: Thu, 17 Aug 2017 12:45:44 +0200 [thread overview]
Message-ID: <20170817104544.p5vvdx2zrvjgpflh@gmail.com> (raw)
In-Reply-To: <tip-d0541b0fa64b36665d6261079974a26943c75009@git.kernel.org>
* tip-bot for Byungchul Park <tipbot@zytor.com> wrote:
> Commit-ID: d0541b0fa64b36665d6261079974a26943c75009
> Gitweb: http://git.kernel.org/tip/d0541b0fa64b36665d6261079974a26943c75009
> Author: Byungchul Park <byungchul.park@lge.com>
> AuthorDate: Thu, 17 Aug 2017 17:57:39 +0900
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitDate: Thu, 17 Aug 2017 11:38:54 +0200
>
> locking/lockdep: Make CONFIG_LOCKDEP_CROSSRELEASE part of CONFIG_PROVE_LOCKING
>
> Crossrelease support added the CONFIG_LOCKDEP_CROSSRELEASE and CONFIG_LOCKDEP_COMPLETE
> options. It makes little sense to enable them when PROVE_LOCKING is disabled.
>
> Make them non-interative options and part of PROVE_LOCKING to simplify the UI.
>
> Signed-off-by: Byungchul Park <byungchul.park@lge.com>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: kernel-team@lge.com
> Link: http://lkml.kernel.org/r/1502960261-16206-1-git-send-email-byungchul.park@lge.com
> Signed-off-by: Ingo Molnar <mingo@kernel.org>
> ---
> lib/Kconfig.debug | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index ebd40d3..1ad7f1b 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1081,6 +1081,8 @@ config PROVE_LOCKING
> select DEBUG_MUTEXES
> select DEBUG_RT_MUTEXES if RT_MUTEXES
> select DEBUG_LOCK_ALLOC
> + select LOCKDEP_CROSSRELEASE
> + select LOCKDEP_COMPLETE
> select TRACE_IRQFLAGS
> default n
> help
> @@ -1152,8 +1154,6 @@ config LOCK_STAT
>
> config LOCKDEP_CROSSRELEASE
> bool "Lock debugging: make lockdep work for crosslocks"
> - depends on PROVE_LOCKING
> - 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.
> @@ -1164,9 +1164,6 @@ config LOCKDEP_CROSSRELEASE
>
> config LOCKDEP_COMPLETE
> bool "Lock debugging: allow completions to use deadlock detector"
> - depends on PROVE_LOCKING
> - select LOCKDEP_CROSSRELEASE
> - default n
> help
Yeah, so I only noticed this after committing the patches, but this change does
not make the option non-interactive. The way to do that is to remove the "" help
text, i.e. make it a simple 'bool'.
I'll do that and re-push.
Thanks,
Ingo
next prev parent reply other threads:[~2017-08-17 10:45 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 8:57 [PATCH v3 1/3] lockdep: Make LOCKDEP_CROSSRELEASE configs all part of PROVE_LOCKING Byungchul Park
2017-08-17 8:57 ` [PATCH v3 2/3] lockdep: Reword title of LOCKDEP_CROSSRELEASE config Byungchul Park
2017-08-17 10:21 ` [tip:locking/core] locking/lockdep: " tip-bot for Byungchul Park
2017-08-17 8:57 ` [PATCH v3 3/3] lockdep: Rename LOCKDEP_COMPLETE config Byungchul Park
2017-08-17 10:22 ` [tip:locking/core] locking/lockdep: Rename CONFIG_LOCKDEP_COMPLETE to CONFIG_LOCKDEP_COMPLETIONS tip-bot for Byungchul Park
2017-08-17 10:21 ` [tip:locking/core] locking/lockdep: Make CONFIG_LOCKDEP_CROSSRELEASE part of CONFIG_PROVE_LOCKING tip-bot for Byungchul Park
2017-08-17 10:45 ` Ingo Molnar [this message]
2017-08-18 5:33 ` Byungchul Park
2017-08-21 15:46 ` [PATCH v3 1/3] lockdep: Make LOCKDEP_CROSSRELEASE configs all part of PROVE_LOCKING Peter Zijlstra
2017-08-22 5:14 ` Byungchul Park
2017-08-22 7:52 ` Peter Zijlstra
2017-08-22 8:51 ` Byungchul Park
2017-08-22 9:21 ` Peter Zijlstra
2017-08-22 9:33 ` Byungchul Park
2017-08-22 10:08 ` Peter Zijlstra
2017-08-22 13:49 ` Peter Zijlstra
2017-08-22 14:46 ` Peter Zijlstra
2017-08-22 15:10 ` Peter Zijlstra
2017-08-22 15:59 ` Oleg Nesterov
2017-08-22 16:35 ` Peter Zijlstra
2017-08-23 16:39 ` Oleg Nesterov
2017-08-23 17:47 ` Peter Zijlstra
2017-08-24 6:11 ` Byungchul Park
2017-08-24 7:37 ` Byungchul Park
2017-08-24 8:11 ` Byungchul Park
2017-08-25 1:14 ` Byungchul Park
2017-08-29 15:52 ` Oleg Nesterov
2017-08-29 17:07 ` lockdep && recursive-read Oleg Nesterov
2017-08-29 17:30 ` Peter Zijlstra
2017-08-29 17:51 ` [PATCH v3 1/3] lockdep: Make LOCKDEP_CROSSRELEASE configs all part of PROVE_LOCKING Peter Zijlstra
2017-08-23 2:43 ` Byungchul Park
2017-08-23 6:31 ` Byungchul Park
2017-08-23 10:26 ` Peter Zijlstra
2017-08-24 5:07 ` Byungchul Park
2017-08-22 5:46 ` Dave Chinner
2017-08-22 9:06 ` Peter Zijlstra
2017-08-22 9:22 ` Byungchul Park
2017-08-22 9:37 ` Peter Zijlstra
2017-08-22 9:42 ` Peter Zijlstra
2017-08-23 2:12 ` Byungchul Park
2017-08-23 6:03 ` Byungchul Park
2017-08-23 10:20 ` Peter Zijlstra
2017-08-24 2:02 ` Byungchul Park
2017-08-24 7:30 ` Byungchul Park
2017-08-22 21:19 ` Dave Chinner
2017-08-23 2:31 ` Byungchul Park
2017-08-23 6:11 ` Byungchul Park
2017-08-23 10:46 ` Peter Zijlstra
2017-08-24 5:06 ` Byungchul Park
2017-08-23 1:56 ` Byungchul Park
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170817104544.p5vvdx2zrvjgpflh@gmail.com \
--to=mingo@kernel.org \
--cc=byungchul.park@lge.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®