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>
16 lines
216 B
C
16 lines
216 B
C
#ifndef _LIBLOCKDEP_RCU_H_
|
|
#define _LIBLOCKDEP_RCU_H_
|
|
|
|
int rcu_scheduler_active;
|
|
|
|
static inline int rcu_lockdep_current_cpu_online(void)
|
|
{
|
|
return 1;
|
|
}
|
|
|
|
static inline int rcu_is_cpu_idle(void)
|
|
{
|
|
return 1;
|
|
}
|
|
|
|
#endif
|