From: Rob Clark <robdclark@gmail.com>
Date: Wed, 27 Aug 2014 15:19:26 +0000 (-0400)
Subject: ww-mutex: clarify help text for DEBUG_WW_MUTEX_SLOWPATH
X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=4d6923733f158e7f8f0695b43c30c22a59ec0a34;p=GitHub%2Fmoto-9609%2Fandroid_kernel_motorola_exynos9610.git

ww-mutex: clarify help text for DEBUG_WW_MUTEX_SLOWPATH

We really don't want distro's enabling this in their kernels.  Try and
make that more clear.

Signed-off-by: Rob Clark <robdclark@gmail.com>
Acked-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
---

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 07c28323f88f..1b233fc67466 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -892,6 +892,10 @@ config DEBUG_WW_MUTEX_SLOWPATH
 	 the full mutex checks enabled with (CONFIG_PROVE_LOCKING) this
 	 will test all possible w/w mutex interface abuse with the
 	 exception of simply not acquiring all the required locks.
+	 Note that this feature can introduce significant overhead, so
+	 it really should not be enabled in a production or distro kernel,
+	 even a debug kernel.  If you are a driver writer, enable it.  If
+	 you are a distro, do not.
 
 config DEBUG_LOCK_ALLOC
 	bool "Lock debugging: detect incorrect freeing of live locks"