From: Sasha Levin <sasha.levin@oracle.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: penberg@kernel.org, mingo@redhat.com, peterz@infradead.org,
asias.hejun@gmail.com, tglx@linutronix.de, gorcunov@openvz.org,
kvm@vger.kernel.org
Subject: Re: [RFC 2/3] lockdep: be nice about compiling from userspace
Date: Thu, 25 Oct 2012 15:17:15 -0400 [thread overview]
Message-ID: <5089903B.2060508@oracle.com> (raw)
In-Reply-To: <20121025170616.GA1267@gmail.com>
On 10/25/2012 01:06 PM, Ingo Molnar wrote:
> * Sasha Levin <sasha.levin@oracle.com> wrote:
>> Yes, we can wrap both static_obj() and debug_show_all_locks()
>> with #ifndefs and let kvmtool provide it's own version of
>> those two.
>
> Only static_obj() - I see no immediate reason why you shouldn't
> be able to utilize debug_show_all_locks(). 'vm debug -a' already
> lists all backtraces on all vcpus - so 'vm debug lockdep -a'
> could list all current locks and indicate which one is held and
> by whom.
I'm not sure how we'd make debug_show_all_locks() work in userspace
since it would require us to wrap do_each_thread() & friends to iterate
over all our task_structs.
I was thinking about writing a corresponding debug_show_all_locks() that
would simply iterate a list of our dummy task_structs.
Thanks,
Sasha
next prev parent reply other threads:[~2012-10-25 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 17:00 [RFC 1/3] kvm tools: use mutex abstraction instead of pthread mutex Sasha Levin
2012-10-24 17:00 ` [RFC 2/3] lockdep: be nice about compiling from userspace Sasha Levin
2012-10-25 8:05 ` Ingo Molnar
2012-10-25 16:58 ` Sasha Levin
2012-10-25 17:06 ` Ingo Molnar
2012-10-25 19:17 ` Sasha Levin [this message]
2012-10-24 17:00 ` [RFC 3/3] kvm tools: use lockdep to detect locking issues Sasha Levin
2012-10-25 6:50 ` [RFC 1/3] kvm tools: use mutex abstraction instead of pthread mutex Pekka Enberg
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=5089903B.2060508@oracle.com \
--to=sasha.levin@oracle.com \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@openvz.org \
--cc=kvm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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.