From: David Ahern <dsahern@gmail.com>
To: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Tom Zanussi <tzanussi@gmail.com>,
Steven Rostedt <srostedt@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Jiri Olsa <jolsa@redhat.com>,
Masami Hiramatsu <mhiramat@redhat.com>,
Oleg Nesterov <oleg@redhat.com>,
linux-kernel@vger.kernel.org,
Denys Vlasenko <vda.linux@googlemail.com>
Subject: Re: [RFC] Full syscall argument decode in "perf trace"
Date: Wed, 18 Sep 2013 06:46:54 -0600 [thread overview]
Message-ID: <5239A0BE.7050203@gmail.com> (raw)
In-Reply-To: <52398FF1.5020502@redhat.com>
On 9/18/13 5:35 AM, Denys Vlasenko wrote:
> Therefore my question should be restated as:
>
> Would perf developers accept the "syscall pausing" feature,
> or it won't be accepted?
I have been using perf-trace a lot lately specifically because it is
effectively a 'passive' observer of the task (e.g., time-sensitive tasks
can be traced with perf but not with strace).
Also, your solution would not work if the raw_syscall events are written
to a file for later analysis where as using tracepoints to collect this
information would.
David
next prev parent reply other threads:[~2013-09-18 12:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 19:06 [RFC] Full syscall argument decode in "perf trace" Arnaldo Carvalho de Melo
2013-09-18 11:35 ` Denys Vlasenko
2013-09-18 12:46 ` David Ahern [this message]
2013-09-18 13:35 ` Ingo Molnar
2013-09-18 14:33 ` Arnaldo Carvalho de Melo
2013-09-26 7:41 ` Denys Vlasenko
2013-09-30 11:33 ` Denys Vlasenko
-- strict thread matches above, loose matches on Subject: below --
2013-09-17 15:10 Denys Vlasenko
2013-09-17 17:52 ` Arnaldo Carvalho de Melo
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=5239A0BE.7050203@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@redhat.com \
--cc=dvlasenk@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=srostedt@redhat.com \
--cc=tzanussi@gmail.com \
--cc=vda.linux@googlemail.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 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.