From: Ingo Molnar <mingo@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Davidlohr Bueso <dave@stgolabs.net>
Subject: Re: [PATCH v4 2/2] locking/debug: Restructure the lock debugging menu
Date: Fri, 30 Mar 2018 13:17:56 +0200 [thread overview]
Message-ID: <20180330111756.jvikchnxaeqkojao@gmail.com> (raw)
In-Reply-To: <1522246852-17501-3-git-send-email-longman@redhat.com>
* Waiman Long <longman@redhat.com> wrote:
> Two config options in the lock debugging menu that are probably the most
> frequently used, as far as I am concerned, is the PROVE_LOCKING and
> LOCK_STAT. From a UI perspective, they should be front and center. So
> these two options are now moved to the top of the lock debugging menu.
>
> The DEBUG_WW_MUTEX_SLOWPATH option is also added to the PROVE_LOCKING
> umbrella.
>
> Signed-off-by: Waiman Long <longman@redhat.com>
> ---
> lib/Kconfig.debug | 146 ++++++++++++++++++++++++++++--------------------------
> 1 file changed, 76 insertions(+), 70 deletions(-)
>
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index 6aad28c..dc9ffe2 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1034,6 +1034,79 @@ config DEBUG_PREEMPT
>
> menu "Lock Debugging (spinlocks, mutexes, etc...)"
>
> +config LOCK_DEBUGGING_SUPPORT
> + bool
> + depends on TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
> + default y
Ok, this patch is a nice reorganization - but could we please split this into two
patches, the first one adds the LOCK_DEBUGGING_SUPPORT helper, the other does the
reordering of the entries (without changing anything in the entries)?
It's hard to review when the two steps are mixed up.
Thanks,
Ingo
prev parent reply other threads:[~2018-03-30 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 14:20 [PATCH v4 0/2] locking/rwsem: Add DEBUG_RWSEMS Waiman Long
2018-03-28 14:20 ` [PATCH v4 1/2] locking/rwsem: Add DEBUG_RWSEMS to look for lock/unlock mismatches Waiman Long
2018-03-29 1:32 ` Davidlohr Bueso
2018-03-29 14:55 ` Waiman Long
2018-03-29 15:01 ` Davidlohr Bueso
2018-03-29 15:17 ` Waiman Long
2018-03-28 14:20 ` [PATCH v4 2/2] locking/debug: Restructure the lock debugging menu Waiman Long
2018-03-29 1:35 ` Davidlohr Bueso
2018-03-30 11:17 ` Ingo Molnar [this message]
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=20180330111756.jvikchnxaeqkojao@gmail.com \
--to=mingo@kernel.org \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.