From: kosaki.motohiro@jp.fujitsu.com (KOSAKI Motohiro)
Subject: [ltt-dev] [PATCH 1/2] Separate socketcall tracepoint.
Date: Tue, 10 Feb 2009 20:28:29 +0900 (JST) [thread overview]
Message-ID: <20090210202757.6FE9.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <A43B7134FC00427F85C85BDD33686946@zhaoleiwin>
> * 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
next prev parent reply other threads:[~2009-02-10 11:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 4:00 Zhaolei
2009-02-09 4:01 ` [ltt-dev] [PATCH 2/2] Make ltt support separate " Zhaolei
2009-02-10 10:30 ` [ltt-dev] [PATCH 1/2] Separate " KOSAKI Motohiro
2009-02-10 11:18 ` Zhaolei
2009-02-10 11:28 ` KOSAKI Motohiro [this message]
2009-02-10 11:43 ` [ltt-dev] [PATCH 0/2] " Zhaolei
2009-02-10 11:51 ` Zhaolei
2009-02-10 17:32 ` Mathieu Desnoyers
2009-02-10 11:45 ` [ltt-dev] [PATCH v2] " Zhaolei
2009-02-10 11:46 ` [ltt-dev] [PATCH v2 2/2] Make ltt support separate " Zhaolei
2009-02-11 5:26 ` Mathieu Desnoyers
2009-02-10 11:47 ` [ltt-dev] [PATCH v2 1/2] Separate " Zhaolei
2009-02-11 5:22 ` Mathieu Desnoyers
2009-02-10 11:47 ` [ltt-dev] [PATCH v2 0/2] " Zhaolei
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=20090210202757.6FE9.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
/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