gma500: allow the creation of 'stolen' memory objects
[linux-2.6/linux-acpi-2.6/ibm-acpi-2.6.git] / lib / debug_locks.c
blobb1c17730767745f81d9990effd5078cdc769dc08
1 /*
2 * lib/debug_locks.c
4 * Generic place for common debugging facilities for various locks:
5 * spinlocks, rwlocks, mutexes and rwsems.
7 * Started by Ingo Molnar:
9 * Copyright (C) 2006 Red Hat, Inc., Ingo Molnar <mingo@redhat.com>
11 #include <linux/rwsem.h>
12 #include <linux/mutex.h>
13 #include <linux/module.h>
14 #include <linux/spinlock.h>
15 #include <linux/debug_locks.h>
18 * We want to turn all lock-debugging facilities on/off at once,
19 * via a global flag. The reason is that once a single bug has been
20 * detected and reported, there might be cascade of followup bugs
21 * that would just muddy the log. So we report the first one and
22 * shut up after that.
24 int debug_locks = 1;
25 EXPORT_SYMBOL_GPL(debug_locks);
28 * The locking-testsuite uses <debug_locks_silent> to get a
29 * 'silent failure': nothing is printed to the console when
30 * a locking bug is detected.
32 int debug_locks_silent;
35 * Generic 'turn off all lock debugging' function:
37 int debug_locks_off(void)
39 if (__debug_locks_off()) {
40 if (!debug_locks_silent) {
41 console_verbose();
42 return 1;
45 return 0;