From: mhiramat at kernel.org (Masami Hiramatsu)
Subject: [PATCH v3 15/18] tracing: probeevent: Add array type support
Date: Mon, 26 Feb 2018 19:16:45 +0900 [thread overview]
Message-ID: <20180226191645.3b1f5b529b6c876dd279cb37@kernel.org> (raw)
In-Reply-To: <20180226014532.GB1972@sejong>
On Mon, 26 Feb 2018 10:45:32 +0900
Namhyung Kim <namhyung at kernel.org> wrote:
> On Sat, Feb 24, 2018 at 02:35:40PM +0900, Masami Hiramatsu wrote:
> > Add array type support for probe events.
> > This allows user to get arraied types from memory address.
> > The array type syntax is
> >
> > TYPE[N]
> >
> > Where TYPE is one of types (u8/16/32/64,s8/16/32/64,
> > x8/16/32/64, symbol, string) and N is a fixed value less
> > than 64.
> >
> > The string array type is a bit different from other types. For
> > other base types, <base-type>[1] is equal to <base-type>
> > (e.g. +0(%di):x32[1] is same as +0(%di):x32.) But string[1] is not
> > equal to string. The string type itself represents "char array",
> > but string array type represents "char * array". So, for example,
> > +0(%di):string[1] is equal to +0(+0(%di)):string.
> >
> > Signed-off-by: Masami Hiramatsu <mhiramat at kernel.org>
> > ---
> > Changes in v2:
> > - Add array description in README file
> > - Fix to init s3 code out of loop.
> > - Fix to proceed code when the last code is OP_ARRAY.
> > - Add string array type and bitfield array type.
> > ---
>
> [SNIP]
> > @@ -546,11 +610,16 @@ int traceprobe_define_arg_fields(struct trace_event_call *event_call,
> > /* Set argument names as fields */
> > for (i = 0; i < tp->nr_args; i++) {
> > struct probe_arg *parg = &tp->args[i];
> > -
> > - ret = trace_define_field(event_call, parg->type->fmttype,
> > - parg->name,
> > + const char *fmt = parg->type->fmttype;
> > + int size = parg->type->size;
> > +
> > + if (parg->fmt)
> > + fmt = parg->fmt;
> > + if (parg->count)
> > + size *= parg->count;
> > + ret = trace_define_field(event_call, fmt, parg->name,
> > offset + parg->offset,
> > - parg->type->size,
> > + parg->type->size * parg->count,
>
> It should use the 'size' variable, otherwise scalar types will have 0 size.
Oops, good catch! I forgot to use it at the main point...
Thank you so much!
>
> Thanks,
> Namhyung
>
>
> > parg->type->is_signed,
> > FILTER_OTHER);
--
Masami Hiramatsu <mhiramat at kernel.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: mhiramat@kernel.org (Masami Hiramatsu)
Subject: [PATCH v3 15/18] tracing: probeevent: Add array type support
Date: Mon, 26 Feb 2018 19:16:45 +0900 [thread overview]
Message-ID: <20180226191645.3b1f5b529b6c876dd279cb37@kernel.org> (raw)
Message-ID: <20180226101645.-eiJaYAqEwT8enHaoJCv-3uxAE9RANt9nZprZ1sRAcg@z> (raw)
In-Reply-To: <20180226014532.GB1972@sejong>
On Mon, 26 Feb 2018 10:45:32 +0900
Namhyung Kim <namhyung@kernel.org> wrote:
> On Sat, Feb 24, 2018@02:35:40PM +0900, Masami Hiramatsu wrote:
> > Add array type support for probe events.
> > This allows user to get arraied types from memory address.
> > The array type syntax is
> >
> > TYPE[N]
> >
> > Where TYPE is one of types (u8/16/32/64,s8/16/32/64,
> > x8/16/32/64, symbol, string) and N is a fixed value less
> > than 64.
> >
> > The string array type is a bit different from other types. For
> > other base types, <base-type>[1] is equal to <base-type>
> > (e.g. +0(%di):x32[1] is same as +0(%di):x32.) But string[1] is not
> > equal to string. The string type itself represents "char array",
> > but string array type represents "char * array". So, for example,
> > +0(%di):string[1] is equal to +0(+0(%di)):string.
> >
> > Signed-off-by: Masami Hiramatsu <mhiramat at kernel.org>
> > ---
> > Changes in v2:
> > - Add array description in README file
> > - Fix to init s3 code out of loop.
> > - Fix to proceed code when the last code is OP_ARRAY.
> > - Add string array type and bitfield array type.
> > ---
>
> [SNIP]
> > @@ -546,11 +610,16 @@ int traceprobe_define_arg_fields(struct trace_event_call *event_call,
> > /* Set argument names as fields */
> > for (i = 0; i < tp->nr_args; i++) {
> > struct probe_arg *parg = &tp->args[i];
> > -
> > - ret = trace_define_field(event_call, parg->type->fmttype,
> > - parg->name,
> > + const char *fmt = parg->type->fmttype;
> > + int size = parg->type->size;
> > +
> > + if (parg->fmt)
> > + fmt = parg->fmt;
> > + if (parg->count)
> > + size *= parg->count;
> > + ret = trace_define_field(event_call, fmt, parg->name,
> > offset + parg->offset,
> > - parg->type->size,
> > + parg->type->size * parg->count,
>
> It should use the 'size' variable, otherwise scalar types will have 0 size.
Oops, good catch! I forgot to use it at the main point...
Thank you so much!
>
> Thanks,
> Namhyung
>
>
> > parg->type->is_signed,
> > FILTER_OTHER);
--
Masami Hiramatsu <mhiramat at kernel.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-02-26 10:16 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 5:28 [PATCH v3 00/18] tracing: probeevent: Improve fetcharg features mhiramat
2018-02-24 5:28 ` Masami Hiramatsu
2018-02-24 5:28 ` [PATCH v3 01/18] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol mhiramat
2018-02-24 5:28 ` Masami Hiramatsu
2018-02-26 0:38 ` namhyung
2018-02-26 0:38 ` Namhyung Kim
2018-02-27 5:23 ` mhiramat
2018-02-27 5:23 ` Masami Hiramatsu
2018-02-24 5:29 ` [PATCH v3 02/18] selftests: ftrace: Add probe event argument syntax testcase mhiramat
2018-02-24 5:29 ` Masami Hiramatsu
2018-02-24 5:29 ` [PATCH v3 03/18] selftests: ftrace: Add a testcase for string type with kprobe_event mhiramat
2018-02-24 5:29 ` Masami Hiramatsu
2018-02-24 5:30 ` [PATCH v3 04/18] tracing: probeevent: Cleanup print argument functions mhiramat
2018-02-24 5:30 ` Masami Hiramatsu
2018-02-24 5:30 ` [PATCH v3 05/18] tracing: probeevent: Cleanup argument field definition mhiramat
2018-02-24 5:30 ` Masami Hiramatsu
2018-02-24 5:31 ` [PATCH v3 06/18] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions mhiramat
2018-02-24 5:31 ` Masami Hiramatsu
2018-02-24 5:31 ` [PATCH v3 07/18] tracing: probeevent: Introduce new argument fetching code mhiramat
2018-02-24 5:31 ` Masami Hiramatsu
2018-02-24 5:32 ` [PATCH v3 08/18] tracing: probeevent: Unify fetch type tables mhiramat
2018-02-24 5:32 ` Masami Hiramatsu
2018-02-24 5:32 ` [PATCH v3 09/18] tracing: probeevent: Return consumed bytes of dynamic area mhiramat
2018-02-24 5:32 ` Masami Hiramatsu
2018-02-24 5:33 ` [PATCH v3 10/18] tracing: probeevent: Append traceprobe_ for exported function mhiramat
2018-02-24 5:33 ` Masami Hiramatsu
2018-02-24 5:33 ` [PATCH v3 11/18] tracing: probeevent: Unify fetch_insn processing common part mhiramat
2018-02-24 5:33 ` Masami Hiramatsu
2018-02-24 5:34 ` [PATCH v3 12/18] tracing: probeevent: Add symbol type mhiramat
2018-02-24 5:34 ` Masami Hiramatsu
2018-02-24 5:34 ` [PATCH v3 13/18] x86: ptrace: Add function argument access API mhiramat
2018-02-24 5:34 ` Masami Hiramatsu
2018-02-24 5:35 ` [PATCH v3 14/18] tracing: probeevent: Add $argN for accessing function args mhiramat
2018-02-24 5:35 ` Masami Hiramatsu
2018-02-24 5:35 ` [PATCH v3 15/18] tracing: probeevent: Add array type support mhiramat
2018-02-24 5:35 ` Masami Hiramatsu
2018-02-26 1:45 ` namhyung
2018-02-26 1:45 ` Namhyung Kim
2018-02-26 10:16 ` mhiramat [this message]
2018-02-26 10:16 ` Masami Hiramatsu
2018-02-24 5:36 ` [PATCH v3 16/18] selftests: ftrace: Add a testcase for symbol type mhiramat
2018-02-24 5:36 ` Masami Hiramatsu
2018-02-24 5:36 ` [PATCH v3 17/18] selftests: ftrace: Add a testcase for $argN with kprobe_event mhiramat
2018-02-24 5:36 ` Masami Hiramatsu
2018-02-24 5:37 ` [PATCH v3 18/18] selftests: ftrace: Add a testcase for array type " mhiramat
2018-02-24 5:37 ` Masami Hiramatsu
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=20180226191645.3b1f5b529b6c876dd279cb37@kernel.org \
--to=linux-kselftest@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