tools/lib/lockdep/uinclude/linux/debug_locks.h

#ifndef _LIBLOCKDEP_DEBUG_LOCKS_H_
#define _LIBLOCKDEP_DEBUG_LOCKS_H_

#include <stddef.h>
#include <linux/compiler.h>

#define DEBUG_LOCKS_WARN_ON(x) (x)

extern bool debug_locks;
extern bool debug_locks_silent;

#endif
liblockdep: Wrap kernel/locking/lockdep.c to allow usage from userspace kernel/locking/lockdep.c deals with validating locking scenarios for various architectures supported by the kernel. There isn't anything kernel specific going on in lockdep, and when we compare userspace to other architectures that don't have to deal with irqs such as s390, they become all too similar. We wrap kernel/locking/lockdep.c and include/linux/lockdep.h with several headers which allow us to build and use lockdep from userspace. We don't touch the kernel code itself which means that any work done on lockdep in the kernel will automatically benefit userspace lockdep as well! Signed-off-by: Sasha Levin <sasha.levin@oracle.com> Signed-off-by: Peter Zijlstra <peterz@infradead.org> Cc: torvalds@linux-foundation.org Link: http://lkml.kernel.org/r/1371163284-6346-3-git-send-email-sasha.levin@oracle.com Signed-off-by: Ingo Molnar <mingo@kernel.org> 2013-06-13 18:41:17 -04:00			`#ifndef _LIBLOCKDEP_DEBUG_LOCKS_H_`
			`#define _LIBLOCKDEP_DEBUG_LOCKS_H_`

			`#include <stddef.h>`
			`#include <linux/compiler.h>`

			`#define DEBUG_LOCKS_WARN_ON(x) (x)`

			`extern bool debug_locks;`
			`extern bool debug_locks_silent;`

			`#endif`