From: David Smith <dsmith@redhat.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC PATCH v2] Tracepoint: add exec tracepoint
Date: Mon, 07 Nov 2011 09:57:30 -0600 [thread overview]
Message-ID: <4EB7FFEA.6070409@redhat.com> (raw)
In-Reply-To: <1320670609.18053.32.camel@twins>
On 11/07/2011 06:56 AM, Peter Zijlstra wrote:
> On Thu, 2011-11-03 at 10:59 -0500, David Smith wrote:
>> Added general purpose exec tracepoint. The 'bprm' argument gives
>> details of the exec.
>>
> This 'changelog' if one can call it that, is completely devoid of
> rationale, why should we care and why should we merge.
Sorry for being too terse.
Exec is an important major event in the life of a task (like fork or
exit). If you want to watch a task start up, when it gets exec'ed is a
good place to start. With the addition of this tracepoint, we can
monitor exec's and get a better picture of system activity in general.
This will also enable better process tracking, allowing you to answer
questions like "what process keeps starting up process X?".
This tracepoint can also be useful in ftrace filtering (i.e. starting or
stopping filtering when exec is called)
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
prev parent reply other threads:[~2011-11-07 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 15:59 [RFC PATCH v2] Tracepoint: add exec tracepoint David Smith
2011-11-04 12:08 ` Pedro Alves
2011-11-04 15:24 ` David Smith
2011-11-07 12:56 ` Peter Zijlstra
2011-11-07 15:57 ` David Smith [this message]
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=4EB7FFEA.6070409@redhat.com \
--to=dsmith@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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