Latch, mutex and beyond

ksl_args.d

#!/usr/sbin/dtrace -Zs
#pragma D option quiet
pid$target::kslgetl:entry
{
printf("%s(0x%X,wait=%d,why=0x%X,whr=%d)\n",probefunc,arg0,arg1,arg2,arg3);
}

pid$target::kslgetsl:entry,
pid$target::ksl_get_shared_latch:entry
{
printf("%s(0x%X,wait=%d,why=0x%X,whr=%d,rs=%d)\n",probefunc,arg0, arg1,arg2,arg3,arg4);
}
pid$target::kslfre:entry
{
printf(" %s(0x%X)\n",probefunc,arg0);
}

1 Comment »

  1. [...] our DTrace latch tracing is to see the latch function arguments. It is easy to write such a script (ksl_args.d). Remember that Oracle acquires exclusive latches using kslgetl(laddr, wait, why, where), and [...]

    Pingback by Appetizer for DTrace « Latch, mutex and beyond — October 28, 2010 @ 3:33 pm | Reply


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

The Rubric Theme. Create a free website or blog at WordPress.com.

Follow

Get every new post delivered to your Inbox.

Join 68 other followers

%d bloggers like this: