public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Mathieu Desnoyers <compudj@krystal.dyndns.org>
Cc: "ltt-dev@lists.casi.polymtl.ca" <ltt-dev@lists.casi.polymtl.ca>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>,
	"rostedt@goodmis.org" <rostedt@goodmis.org>
Subject: Re: Tracing thread name
Date: Tue, 4 Aug 2009 16:06:14 +0200	[thread overview]
Message-ID: <4A784056.1020400@parrot.com> (raw)
In-Reply-To: <20090804130510.GA23396@Krystal>

Hi,

Mathieu Desnoyers a écrit :
> * Matthieu CASTET (matthieu.castet@parrot.com) wrote:
>> Hi Mathieu,
>>
>> Mathieu Desnoyers a écrit :
>> Do you know if it is possible to patch my version to add such feature ?
>>
>> I saw that the name already change in the trace before/after an exec.
>> How lltv get the new name ?
>> With "fs.exec" tracepoint ?
>> In that case I could fake a "fs.exec" tracepoint in set_task_comm.
> 
> A better solution : you add a new event in both lttng and lttv, and
> modify state.c to support your new event. The current event to brand
> thread is named "userspace.thread_brand". Look for this in LTTV to see
> all the sites that need to support the new event (there are very few).
> 
Thanks, but I want to avoid to modify too much ltt (I use an old version
for 2.6.27 and my modifications may be useless for upstream).

I added "trace_fs_exec(tsk->comm);" at the end of set_task_comm and now
the thread got the correct name :)


Matthieu

  reply	other threads:[~2009-08-04 14:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A76E42D.7010908@parrot.com>
2009-08-03 13:48 ` Tracing thread name (was: ltt comm tracking) Mathieu Desnoyers
2009-08-03 14:28   ` Peter Zijlstra
2009-08-04 10:12   ` Tracing thread name Matthieu CASTET
2009-08-04 13:05     ` Mathieu Desnoyers
2009-08-04 14:06       ` Matthieu CASTET [this message]
2009-08-13 15:57         ` [ltt-dev] " Matthieu CASTET

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=4A784056.1020400@parrot.com \
    --to=matthieu.castet@parrot.com \
    --cc=compudj@krystal.dyndns.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    --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