From: Namhyung Kim <namhyung@kernel.org>
To: Javi Merino <javi.merino@arm.com>
Cc: acme@redhat.com, jolsa@redhat.com, rostedt@goodmis.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 2/2] tools lib traceevent: Add support for __print_array()
Date: Tue, 3 Mar 2015 23:12:38 +0900 [thread overview]
Message-ID: <20150303141238.GC27046@danjae> (raw)
In-Reply-To: <1425320262-7096-3-git-send-email-javi.merino@arm.com>
Hi Javi,
On Mon, Mar 02, 2015 at 06:17:42PM +0000, Javi Merino wrote:
> Since 6ea22486ba46 ("tracing: Add array printing helper") trace can
> traces with variable element size arrays. Add support to parse them.
I just have a nitpick below - otherwise both patches look good, so
Acked-by: Namhyung Kim <namhyung@kernel.org>
[SNIP]
> diff --git a/tools/lib/traceevent/event-parse.h b/tools/lib/traceevent/event-parse.h
> index 7a3873ff9a4f..5ac3e3c00389 100644
> --- a/tools/lib/traceevent/event-parse.h
> +++ b/tools/lib/traceevent/event-parse.h
> @@ -245,6 +245,12 @@ struct print_arg_hex {
> struct print_arg *size;
> };
>
> +struct print_arg_int_array {
> + struct print_arg *field;
> + struct print_arg *size;
I think it'd be better to call this field as 'count' rather than
'size' since it's clearer and consistent with the in-kernel
__print_array() function.
Thanks,
Namhyung
> + struct print_arg *el_size;
> +};
> +
> struct print_arg_dynarray {
> struct format_field *field;
> struct print_arg *index;
> @@ -273,6 +279,7 @@ enum print_arg_type {
> PRINT_FLAGS,
> PRINT_SYMBOL,
> PRINT_HEX,
> + PRINT_INT_ARRAY,
> PRINT_TYPE,
> PRINT_STRING,
> PRINT_BSTRING,
> @@ -292,6 +299,7 @@ struct print_arg {
> struct print_arg_flags flags;
> struct print_arg_symbol symbol;
> struct print_arg_hex hex;
> + struct print_arg_int_array int_array;
> struct print_arg_func func;
> struct print_arg_string string;
> struct print_arg_bitmask bitmask;
> --
> 1.9.1
>
prev parent reply other threads:[~2015-03-03 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 18:17 [PATCH v7 0/2] Add array printing support to libtraceevent Javi Merino
2015-03-02 18:17 ` [PATCH v7 1/2] tools lib traceevent: factor out allocating and processing args Javi Merino
2015-03-02 18:17 ` [PATCH v7 2/2] tools lib traceevent: Add support for __print_array() Javi Merino
2015-03-03 14:12 ` Namhyung Kim [this message]
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=20150303141238.GC27046@danjae \
--to=namhyung@kernel.org \
--cc=acme@redhat.com \
--cc=javi.merino@arm.com \
--cc=jolsa@redhat.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