public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Tom Zanussi <tom.zanussi@linux.intel.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	linux-trace-users@vger.kernel.org,
	linux-kselftest@vger.kernel.org, shuah@kernel.org,
	kernel-team@lge.com
Subject: Re: [PATCH v3 15/18] tracing: probeevent: Add array type support
Date: Mon, 26 Feb 2018 10:45:32 +0900	[thread overview]
Message-ID: <20180226014532.GB1972@sejong> (raw)
In-Reply-To: <151945054003.27508.54078842635361756.stgit@devbox>

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@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.

Thanks,
Namhyung


>  					 parg->type->is_signed,
>  					 FILTER_OTHER);

  reply	other threads:[~2018-02-26  1:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-24  5:28 [PATCH v3 00/18] tracing: probeevent: Improve fetcharg features Masami Hiramatsu
2018-02-24  5:28 ` [PATCH v3 01/18] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol Masami Hiramatsu
2018-02-26  0:38   ` Namhyung Kim
2018-02-27  5:23     ` Masami Hiramatsu
2018-02-24  5:29 ` [PATCH v3 02/18] selftests: ftrace: Add probe event argument syntax testcase Masami Hiramatsu
2018-02-24  5:29 ` [PATCH v3 03/18] selftests: ftrace: Add a testcase for string type with kprobe_event Masami Hiramatsu
2018-02-24  5:30 ` [PATCH v3 04/18] tracing: probeevent: Cleanup print argument functions Masami Hiramatsu
2018-02-24  5:30 ` [PATCH v3 05/18] tracing: probeevent: Cleanup argument field definition Masami Hiramatsu
2018-02-24  5:31 ` [PATCH v3 06/18] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions Masami Hiramatsu
2018-02-24  5:31 ` [PATCH v3 07/18] tracing: probeevent: Introduce new argument fetching code Masami Hiramatsu
2018-02-24  5:32 ` [PATCH v3 08/18] tracing: probeevent: Unify fetch type tables Masami Hiramatsu
2018-02-24  5:32 ` [PATCH v3 09/18] tracing: probeevent: Return consumed bytes of dynamic area Masami Hiramatsu
2018-02-24  5:33 ` [PATCH v3 10/18] tracing: probeevent: Append traceprobe_ for exported function Masami Hiramatsu
2018-02-24  5:33 ` [PATCH v3 11/18] tracing: probeevent: Unify fetch_insn processing common part Masami Hiramatsu
2018-02-24  5:34 ` [PATCH v3 12/18] tracing: probeevent: Add symbol type Masami Hiramatsu
2018-02-24  5:34 ` [PATCH v3 13/18] x86: ptrace: Add function argument access API Masami Hiramatsu
2018-02-24  5:35 ` [PATCH v3 14/18] tracing: probeevent: Add $argN for accessing function args Masami Hiramatsu
2018-02-24  5:35 ` [PATCH v3 15/18] tracing: probeevent: Add array type support Masami Hiramatsu
2018-02-26  1:45   ` Namhyung Kim [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 Masami Hiramatsu
2018-02-24  5:36 ` [PATCH v3 17/18] selftests: ftrace: Add a testcase for $argN with kprobe_event Masami Hiramatsu
2018-02-24  5:37 ` [PATCH v3 18/18] selftests: ftrace: Add a testcase for array type " 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=20180226014532.GB1972@sejong \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=kernel-team@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-trace-users@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    --cc=tom.zanussi@linux.intel.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