From mboxrd@z Thu Jan  1 00:00:00 1970
From: kosaki.motohiro@jp.fujitsu.com (KOSAKI Motohiro)
Date: Tue, 10 Feb 2009 20:28:29 +0900 (JST)
Subject: [ltt-dev] [PATCH 1/2] Separate socketcall tracepoint.
In-Reply-To: <A43B7134FC00427F85C85BDD33686946@zhaoleiwin>
References: <20090210192944.6FE0.KOSAKI.MOTOHIRO@jp.fujitsu.com>
	<A43B7134FC00427F85C85BDD33686946@zhaoleiwin>
Message-ID: <20090210202757.6FE9.KOSAKI.MOTOHIRO@jp.fujitsu.com>

> * From: "KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>
> > Hi
> > 
> >> So we can trace socket calls on arch without socketcall.
> >> And we can get detail information for socket calls.
> > 
> > The description is tooooo short.
> > Please explain why this patch is useful. Who need this?
> Hello, Kosaki-san
> 
> Now lttng trace only sys_socket_call for sys_socket, sys_bind and others.
> But on some arch(for ex, ia64) which lacks of sys_socket_call, we can't get those
> syscall traced.
> 
> This patch add separate socketcall tracers to sys_socket, sys_bind, etc.
> So people who using ia64 can trace each socket calls.
> 
> Do you agree it?

Sure.
this is good description :)


> 
> I'll add some explain to comment and send a v2 patch.
> 
> Regards
> Zhaolei