From: Christoph Hellwig <hch@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Zhao Lei <zhaolei@cn.fujitsu.com>
Subject: Re: [PATCH 1/2] ftrace: Add task_comm support for trace_event
Date: Sun, 24 May 2009 17:41:26 -0400 [thread overview]
Message-ID: <20090524214125.GA10195@infradead.org> (raw)
In-Reply-To: <20090521141914.208848802@goodmis.org>
On Thu, May 21, 2009 at 10:18:14AM -0400, Steven Rostedt wrote:
> From: Zhaolei <zhaolei@cn.fujitsu.com>
>
> If we use trace_event alone(without function trace, .etc),
> it can't output enough task command information.
For some reason I still only see the process name sometimes but not
always. It is more likely to appear for later entries than earlier
ones (and no, this is not an IRQ context problem as this is with
my work in progress XFS trace events, and XFS runs no major piece of
code in IRQ context)
next prev parent reply other threads:[~2009-05-24 21:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 14:18 [PATCH 0/2] [GIT PULL] tracing/events: show task comms Steven Rostedt
2009-05-21 14:18 ` [PATCH 1/2] ftrace: Add task_comm support for trace_event Steven Rostedt
2009-05-24 21:41 ` Christoph Hellwig [this message]
2009-05-21 14:18 ` [PATCH 2/2] ftrace: clean up of using ftrace_event_enable_disable() Steven Rostedt
2009-05-22 8:00 ` [PATCH 0/2] [GIT PULL] tracing/events: show task comms Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2009-05-21 7:08 [PATCH 1/2] ftrace: Add task_comm support for trace_event Zhaolei
2009-05-21 13:15 ` Steven Rostedt
2009-05-22 8:01 ` Ingo Molnar
2009-05-22 8:25 ` Ingo Molnar
2009-05-22 8:49 ` Zhaolei
2009-05-23 15:16 ` Christoph Hellwig
2009-05-23 15:18 ` Christoph Hellwig
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=20090524214125.GA10195@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=zhaolei@cn.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;
as well as URLs for NNTP newsgroup(s).