From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Ingo Molnar <mingo@elte.hu>,
Arjan van de Ven <arjan@infradead.org>,
Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: [patch 8/8] lock validator: add s390 to supported options
Date: Wed, 14 Jun 2006 16:25:03 +0200 [thread overview]
Message-ID: <20060614142503.GI1241@osiris.boeblingen.de.ibm.com> (raw)
From: Heiko Carstens <heiko.carstens@de.ibm.com>
Enable DEBUG_SPINLOCK_ALLOC, DEBUG_RWLOCK_ALLOC, DEBUG_MUTEX_ALLOC,
DEBUG_RWSEM_ALLOC and LOCKDEP for s390.
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
---
lib/Kconfig.debug | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff -purN a/lib/Kconfig.debug b/lib/Kconfig.debug
--- a/lib/Kconfig.debug 2006-06-14 12:54:17.000000000 +0200
+++ b/lib/Kconfig.debug 2006-06-14 13:46:17.000000000 +0200
@@ -175,7 +175,7 @@ config DEBUG_SPINLOCK
config DEBUG_SPINLOCK_ALLOC
bool "Spinlock debugging: detect incorrect freeing of live spinlocks"
- depends on DEBUG_SPINLOCK && X86
+ depends on DEBUG_SPINLOCK && (X86 || S390)
select LOCKDEP
help
This feature will check whether any held spinlock is incorrectly
@@ -224,7 +224,7 @@ config PROVE_SPIN_LOCKING
config DEBUG_RWLOCK_ALLOC
bool "rw-lock debugging: detect incorrect freeing of live rwlocks"
- depends on DEBUG_SPINLOCK && X86
+ depends on DEBUG_SPINLOCK && (X86 || S390)
select LOCKDEP
help
This feature will check whether any held rwlock is incorrectly
@@ -281,7 +281,7 @@ config DEBUG_MUTEXES
config DEBUG_MUTEX_ALLOC
bool "Mutex debugging: detect incorrect freeing of live mutexes"
- depends on DEBUG_MUTEXES && X86
+ depends on DEBUG_MUTEXES && (X86 || S390)
select LOCKDEP
help
This feature will check whether any held mutex is incorrectly
@@ -337,7 +337,7 @@ config DEBUG_RWSEMS
config DEBUG_RWSEM_ALLOC
bool "rwsem debugging: detect incorrect freeing of live rwsems"
- depends on DEBUG_RWSEMS && X86
+ depends on DEBUG_RWSEMS && (X86 || S390)
select LOCKDEP
help
This feature will check whether any held rwsem is incorrectly
@@ -389,7 +389,7 @@ config LOCKDEP
select FRAME_POINTER
select KALLSYMS
select KALLSYMS_ALL
- depends on X86
+ depends on X86 || S390
config DEBUG_NON_NESTED_UNLOCKS
bool "Detect non-nested unlocks"
next reply other threads:[~2006-06-14 14:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 14:25 Heiko Carstens [this message]
2006-06-19 22:05 ` Andrew Morton
2006-06-19 22:18 ` Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX Erik Ohrnberger
2006-06-20 8:20 ` Alan Cox
2006-06-20 12:52 ` Erik Ohrnberger
2006-06-21 1:19 ` Erik Ohrnberger
2006-06-21 10:51 ` Alan Cox
2006-06-21 13:09 ` Erik Ohrnberger
2006-06-21 13:34 ` Alan Cox
2006-06-21 13:34 ` Mike Snitzer
2006-06-21 14:07 ` Alan Cox
2006-06-21 15:20 ` Mike Snitzer
2006-06-21 16:10 ` Alan Cox
2006-06-21 17:47 ` Mike Snitzer
2006-06-22 22:14 ` Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driverfor PDC202XX Erik Ohrnberger
2006-06-20 7:07 ` [patch 8/8] lock validator: add s390 to supported options Arjan van de Ven
2006-06-20 7:28 ` Andrew Morton
2006-06-23 13:05 ` Heiko Carstens
2006-06-23 13:37 ` Ingo Molnar
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=20060614142503.GI1241@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=schwidefsky@de.ibm.com \
/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
Powered by JetHome