From: Peter Zijlstra <peterz@infradead.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: torvalds@linux-foundation.org, mingo@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/9] liblockdep: Wrap kernel/lockdep.c to allow usage from userspace
Date: Wed, 22 May 2013 11:14:49 +0200 [thread overview]
Message-ID: <20130522091449.GD18810@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1368674141-10796-3-git-send-email-sasha.levin@oracle.com>
On Wed, May 15, 2013 at 11:15:34PM -0400, Sasha Levin wrote:
> kernel/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/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!
>
> +
> +#ifndef CALLER_ADDR0
> +#define _THIS_IP_ CALLER_ADDR0
> +#define CALLER_ADDR0 ((unsigned long)__builtin_return_address(0))
> +#endif
Why are you making _THIS_IP_ equal to _RET_IP_ ?
next prev parent reply other threads:[~2013-05-22 9:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 3:15 [PATCH v4 0/9] liblockdep: userspace lockdep Sasha Levin
2013-05-16 3:15 ` [PATCH v4 1/9] lockdep: Be nice about building from userspace Sasha Levin
2013-05-16 7:32 ` Pekka Enberg
2013-05-16 3:15 ` [PATCH v4 2/9] liblockdep: Wrap kernel/lockdep.c to allow usage " Sasha Levin
2013-05-22 9:14 ` Peter Zijlstra [this message]
2013-05-22 9:17 ` Peter Zijlstra
2013-05-28 19:30 ` Sasha Levin
2013-05-29 11:11 ` Peter Zijlstra
2013-05-16 3:15 ` [PATCH v4 3/9] liblockdep: Add public headers for pthread_mutex_t implementation Sasha Levin
2013-05-22 9:22 ` Peter Zijlstra
2013-05-28 19:33 ` Sasha Levin
2013-05-29 11:14 ` Peter Zijlstra
2013-05-16 3:15 ` [PATCH v4 4/9] liblockdep: Add pthread_mutex_t test suite Sasha Levin
2013-05-16 3:15 ` [PATCH v4 5/9] liblockdep: Add public headers for pthread_rwlock_t implementation Sasha Levin
2013-05-22 9:23 ` Peter Zijlstra
2013-05-16 3:15 ` [PATCH v4 6/9] liblockdep: Add pthread_rwlock_t test suite Sasha Levin
2013-05-16 3:15 ` [PATCH v4 7/9] liblockdep: Support using LD_PRELOAD Sasha Levin
2013-05-22 9:24 ` Peter Zijlstra
2013-05-28 19:35 ` Sasha Levin
2013-05-29 11:15 ` Peter Zijlstra
2013-05-22 9:27 ` Peter Zijlstra
2013-05-28 19:38 ` Sasha Levin
2013-05-29 11:16 ` Peter Zijlstra
2013-05-16 3:15 ` [PATCH v4 8/9] liblockdep: Add the 'lockdep' user-space utility Sasha Levin
2013-05-22 9:27 ` Peter Zijlstra
2013-05-16 3:15 ` [PATCH v4 9/9] liblockdep: Add a MAINTAINERS entry Sasha Levin
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=20130522091449.GD18810@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sasha.levin@oracle.com \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.