From: Javi Merino <javi.merino@arm.com>
To: linux-kernel@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>
Cc: Javi Merino <javi.merino@arm.com>
Subject: [PATCH v5 0/3] Add array printing helper to ftrace
Date: Wed, 28 Jan 2015 12:48:52 +0000 [thread overview]
Message-ID: <1422449335-8289-1-git-send-email-javi.merino@arm.com> (raw)
This series add a helper to the tracing framework to trace arrays.
Patch 1 add the helper and patches 2 and 3 update the traceevent
library to parse them. They've been tested with trace-cmd.
Changes since v4[0]:
- Specify the element size in __print_array() as bytes instead of
bits
Changes since v3:
- use %zu to print size_t
Changes since v2:
- Changed BUG() into a trace_seq_printf()
- Add BUILD_BUG_ON() to chase mistakes in element sizes on build
- Add patch 2 to avoid repeating code in patch 3.
- print a warning in traeevent if the size of the array is not valid
[0] http://thread.gmane.org/gmane.linux.kernel/1874250
Dave Martin (1):
tracing: Add array printing helper
Javi Merino (2):
tools lib traceevent: factor out allocating and processing args
tools lib traceevent: Add support for __print_array()
include/linux/ftrace_event.h | 4 +
include/trace/ftrace.h | 9 +++
kernel/trace/trace_output.c | 44 +++++++++++
tools/lib/traceevent/event-parse.c | 158 +++++++++++++++++++++++++++++--------
tools/lib/traceevent/event-parse.h | 8 ++
5 files changed, 192 insertions(+), 31 deletions(-)
--
1.9.1
next reply other threads:[~2015-01-29 2:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 12:48 Javi Merino [this message]
2015-01-28 12:48 ` [PATCH v5 1/3] tracing: Add array printing helper Javi Merino
2015-01-28 12:48 ` [PATCH v5 2/3] tools lib traceevent: factor out allocating and processing args Javi Merino
2015-01-28 12:48 ` [PATCH v5 3/3] tools lib traceevent: Add support for __print_array() Javi Merino
2015-02-27 12:32 ` Javi Merino
2015-02-27 14:15 ` Steven Rostedt
2015-02-27 14:52 ` Javi Merino
2015-06-04 14:25 ` Javi Merino
2015-06-08 16:17 ` Steven Rostedt
2015-07-13 16:06 ` Steven Rostedt
2015-07-13 16:36 ` Javi Merino
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=1422449335-8289-1-git-send-email-javi.merino@arm.com \
--to=javi.merino@arm.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®