From: Hiraku Toyooka <hiraku.toyooka.gu@hitachi.com>
To: rostedt@goodmis.org
Cc: masami.hiramatsu.pt@hitachi.com, linux-kernel@vger.kernel.org,
yrl.pp-manager.tt@hitachi.com
Subject: [PATCH v3 -tip 0/4] tracing: make a snapshot feature available from userspace
Date: Wed, 19 Dec 2012 16:02:18 +0900 [thread overview]
Message-ID: <20121219070218.31200.64647.stgit@liselsia> (raw)
Hi, Steven,
Thank you for your review.
I applied your review comments.
These patches depend on the next patch.
tracing: Add a resize function to make one buffer equivalent to another buffer
http://lkml.kernel.org/r/20121017025616.2627.91226.stgit@falsita
v2->v3:
[1/4] tracing: add checks if tr->buffer is NULL in tracing_reset{_online_cpus}
- (new patch)
[2/4] tracing: replace static old_tracer with strcmp
- (new patch)
[3/4] tracing: make a snapshot feature available from userspace
- changed snapshot file I/F (removed "snapshot_allocate")
- changed CONFIG_TRACER_SNAPSHOT's location and description
- changed an integer flag of __tracing_open() to bool
- switched to use seq_read() directly for reading snapshot
[4/4] tracing: add description of snapshot to Documentation/trace/ftrace.txt
- updated documentation of the snapshot
ToDo:
- adding "trace_snapshot" kernel parameter to allocate spare buffer on boot.
(v1: https://lkml.org/lkml/2012/10/2/67)
(v2: https://lkml.org/lkml/2012/10/16/585)
---
Hiraku Toyooka (4):
tracing: add checks if tr->buffer is NULL in tracing_reset{_online_cpus}
tracing: replace static old_tracer with strcmp
tracing: make a snapshot feature available from userspace
tracing: add description of snapshot to Documentation/trace/ftrace.txt
Documentation/trace/ftrace.txt | 83 +++++++++++++++++++++
include/linux/ftrace_event.h | 3 +
kernel/trace/Kconfig | 10 +++
kernel/trace/trace.c | 158 ++++++++++++++++++++++++++++++++++------
kernel/trace/trace.h | 1
5 files changed, 231 insertions(+), 24 deletions(-)
--
Hiraku TOYOOKA
Linux Technology Center
Yokohama Research Laboratory
Hitachi Ltd.
next reply other threads:[~2012-12-19 7:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 7:02 Hiraku Toyooka [this message]
2012-12-19 7:02 ` [PATCH v3 -tip 1/4] tracing: add checks if tr->buffer is NULL in tracing_reset{_online_cpus} Hiraku Toyooka
2013-01-24 19:39 ` [tip:perf/core] tracing: Add checks if tr-> buffer " tip-bot for Hiraku Toyooka
2012-12-19 7:02 ` [PATCH v3 -tip 2/4] tracing: replace static old_tracer with strcmp Hiraku Toyooka
2012-12-21 3:04 ` Steven Rostedt
2012-12-21 10:55 ` Hiraku Toyooka
2012-12-19 7:02 ` [PATCH v3 -tip 3/4] tracing: make a snapshot feature available from userspace Hiraku Toyooka
2012-12-19 7:02 ` [PATCH v3 -tip 4/4] tracing: add description of snapshot to Documentation/trace/ftrace.txt Hiraku Toyooka
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=20121219070218.31200.64647.stgit@liselsia \
--to=hiraku.toyooka.gu@hitachi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=rostedt@goodmis.org \
--cc=yrl.pp-manager.tt@hitachi.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).