From: Javi Merino <javi.merino@arm.com>
To: acme@redhat.com, jolsa@redhat.com
Cc: linux-kernel@vger.kernel.org, Javi Merino <javi.merino@arm.com>
Subject: [RESEND PATCH v8 0/2] Add array printing support to libtraceevent
Date: Fri, 20 Mar 2015 18:12:54 +0000 [thread overview]
Message-ID: <1426875176-30244-1-git-send-email-javi.merino@arm.com> (raw)
This series add support to libtraceevent for dynamic arrays in traces.
The kernel learned to create this traces in 6ea22486ba46 ("tracing: Add
array printing helper"), which was merged for v4.0-rc1.
Changes since v7[0]:
- Call the fields of the struct print_arg_int_array "field", "count"
and "el_size" to match the definition of __print_array as Namhyung
Kim suggests. Incorporate his Acked-by.
Changes since v6[1]:
- s/alloc_and_process_arg/alloc_and_process_delim/ as Steven
Rostedt suggests
[0] http://thread.gmane.org/gmane.linux.kernel/1897935
[1] http://thread.gmane.org/gmane.linux.kernel/1896232
Javi Merino (2):
tools lib traceevent: factor out allocating and processing args
tools lib traceevent: Add support for __print_array()
tools/lib/traceevent/event-parse.c | 158 +++++++++++++++++++++++++++++--------
tools/lib/traceevent/event-parse.h | 8 ++
2 files changed, 135 insertions(+), 31 deletions(-)
--
1.9.1
next reply other threads:[~2015-03-20 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 18:12 Javi Merino [this message]
2015-03-20 18:12 ` [RESEND PATCH v8 1/2] tools lib traceevent: factor out allocating and processing args Javi Merino
2015-03-24 16:31 ` [tip:perf/core] tools lib traceevent: Factor " tip-bot for Javi Merino
2015-03-20 18:12 ` [RESEND PATCH v8 2/2] tools lib traceevent: Add support for __print_array() Javi Merino
2015-03-23 16:20 ` Arnaldo Carvalho de Melo
2015-03-24 11:07 ` [PATCH v9] " Javi Merino
2015-03-24 15:48 ` Arnaldo Carvalho de Melo
2015-03-24 16:35 ` [tip:perf/core] " tip-bot for Javi Merino
2015-03-23 16:18 ` [RESEND PATCH v8 0/2] Add array printing support to libtraceevent Arnaldo Carvalho de Melo
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=1426875176-30244-1-git-send-email-javi.merino@arm.com \
--to=javi.merino@arm.com \
--cc=acme@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.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®