From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org, linux-btrace@vger.kernel.org
Subject: [PATCH tip][0/2] ftrace interface for blktrace
Date: Fri, 23 Jan 2009 14:06:17 +0000 [thread overview]
Message-ID: <20090123140617.GB21737@ghostprotocols.net> (raw)
Hi Jens,
Here is a third version, that also implements blk_add_trace_msg,
using ftrace_vprintk.
As soon as the TRACE_ITER_CONTEXT_INFO option is implemented
I'll provide the struct trace_event->bin() callback to synthesize the
old blktrace record format so that we can test the output of trace_pipe
with blkparse -i -.
Please let me know if this is acceptable for inclusion on
linux-tip.
Best Regards,
- Arnaldo
block/blktrace.c | 651 ++++++++++++++++++++++++++++++++++++++++++++++++-
fs/partitions/check.c | 7
include/linux/ftrace.h | 8
kernel/trace/trace.c | 9
kernel/trace/trace.h | 1
5 files changed, 671 insertions(+), 5 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org, linux-btrace@vger.kernel.org
Subject: [PATCH tip][0/2] ftrace interface for blktrace
Date: Fri, 23 Jan 2009 12:06:17 -0200 [thread overview]
Message-ID: <20090123140617.GB21737@ghostprotocols.net> (raw)
Hi Jens,
Here is a third version, that also implements blk_add_trace_msg,
using ftrace_vprintk.
As soon as the TRACE_ITER_CONTEXT_INFO option is implemented
I'll provide the struct trace_event->bin() callback to synthesize the
old blktrace record format so that we can test the output of trace_pipe
with blkparse -i -.
Please let me know if this is acceptable for inclusion on
linux-tip.
Best Regards,
- Arnaldo
block/blktrace.c | 651 ++++++++++++++++++++++++++++++++++++++++++++++++-
fs/partitions/check.c | 7
include/linux/ftrace.h | 8
kernel/trace/trace.c | 9
kernel/trace/trace.h | 1
5 files changed, 671 insertions(+), 5 deletions(-)
next reply other threads:[~2009-01-23 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 14:06 Arnaldo Carvalho de Melo [this message]
2009-01-23 14:06 ` [PATCH tip][0/2] ftrace interface for blktrace Arnaldo Carvalho de Melo
2009-01-26 11:42 ` Jens Axboe
2009-01-26 11:42 ` Jens Axboe
2009-01-26 13:43 ` Ingo Molnar
2009-01-26 13:43 ` Ingo Molnar
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=20090123140617.GB21737@ghostprotocols.net \
--to=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-btrace@vger.kernel.org \
--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 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.