From: Phil Muldoon <pmuldoon@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Eugene Teo <eteo@redhat.com>, frysk@sourceware.org
Subject: Re: Extending Frysk to trace user-space lockings
Date: Thu, 23 Aug 2007 00:24:00 -0000 [thread overview]
Message-ID: <46CCD3AB.8060700@redhat.com> (raw)
In-Reply-To: <1184921481.3611.17.camel@dijkstra.wildebeest.org>
Mark Wielaard wrote:
> Hi Eugene,
>
> On Fri, 2007-07-20 at 11:08 +0800, Eugene Teo wrote:
>
>> Is it possible to extend Frysk to trace user-space lockings? I am trying to
>> write a tool that basically outputs the lock used and the backtrace showing
>> who is holding on to it. I don't really have an example output that I can show,
>> but if you have an idea to share, do let me know!
>>
>
> I am afraid I know too little about user space locking or even know how
> various user space locking mechanisms are implemented to give a real
> answer.
>
> Lets assume you are interested in pthread mutexes.
Are futex's exposed via fhpd at the moment?
Regards
Phil
next prev parent reply other threads:[~2007-08-23 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 3:08 Eugene Teo
2007-07-20 8:51 ` Mark Wielaard
2007-08-23 0:24 ` Phil Muldoon [this message]
2007-08-23 0:45 ` Phil Muldoon
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=46CCD3AB.8060700@redhat.com \
--to=pmuldoon@redhat.com \
--cc=eteo@redhat.com \
--cc=frysk@sourceware.org \
--cc=mark@klomp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).