mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	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,
	Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
Subject: Re: [PATCH v5 16/19] tracing: probeevent: Add array type support
Date: Thu, 15 Mar 2018 13:31:29 +0530	[thread overview]
Message-ID: <d94e56c0-4096-5b8d-9e84-6a83b3daa84f@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180315162303.1250dea1500aea420ecd85c6@kernel.org>



On 03/15/2018 12:53 PM, Masami Hiramatsu wrote:
>
> Sorry, that is too complicated than enough. you should try to specify a[0] instead of a.
>
>  $ sudo ./perf probe -x ~/hello foo1 'a=a[0]:x32[3]'

Cool.. that works fine.

$ sudo ./perf script
           hello  1779 [034]    76.081971: probe_hello:foo1: (100005fc) a={0x4,0x5,0x6}

Thanks,
Ravi

> :)
>
> Thank you,
>


  reply	other threads:[~2018-03-15  7:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08  8:43 [PATCH v5 00/19] tracing: probeevent: Improve fetcharg features Masami Hiramatsu
2018-03-08  8:44 ` [PATCH v5 01/19] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol Masami Hiramatsu
2018-03-08  8:44 ` [PATCH v5 02/19] selftests: ftrace: Add probe event argument syntax testcase Masami Hiramatsu
2018-03-08  8:45 ` [PATCH v5 03/19] selftests: ftrace: Add a testcase for string type with kprobe_event Masami Hiramatsu
2018-03-08  8:45 ` [PATCH v5 04/19] selftests: ftrace: Add a testcase for probepoint Masami Hiramatsu
2018-03-08  8:46 ` [PATCH v5 05/19] tracing: probeevent: Cleanup print argument functions Masami Hiramatsu
2018-03-08  8:46 ` [PATCH v5 06/19] tracing: probeevent: Cleanup argument field definition Masami Hiramatsu
2018-03-08  8:46 ` [PATCH v5 07/19] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions Masami Hiramatsu
2018-03-08  8:47 ` [PATCH v5 08/19] tracing: probeevent: Introduce new argument fetching code Masami Hiramatsu
2018-03-08  8:47 ` [PATCH v5 09/19] tracing: probeevent: Unify fetch type tables Masami Hiramatsu
2018-03-08  8:47 ` [PATCH v5 10/19] tracing: probeevent: Return consumed bytes of dynamic area Masami Hiramatsu
2018-03-08  8:48 ` [PATCH v5 11/19] tracing: probeevent: Append traceprobe_ for exported function Masami Hiramatsu
2018-03-08  8:48 ` [PATCH v5 12/19] tracing: probeevent: Unify fetch_insn processing common part Masami Hiramatsu
2018-03-08  8:49 ` [PATCH v5 13/19] tracing: probeevent: Add symbol type Masami Hiramatsu
2018-03-08  8:49 ` [PATCH v5 14/19] x86: ptrace: Add function argument access API Masami Hiramatsu
2018-03-08  8:50 ` [PATCH v5 15/19] tracing: probeevent: Add $argN for accessing function args Masami Hiramatsu
2018-03-08  8:50 ` [PATCH v5 16/19] tracing: probeevent: Add array type support Masami Hiramatsu
2018-03-15  5:48   ` Ravi Bangoria
2018-03-15  7:18     ` Masami Hiramatsu
2018-03-15  7:23       ` Masami Hiramatsu
2018-03-15  8:01         ` Ravi Bangoria [this message]
2018-03-16 14:48   ` Masami Hiramatsu
2018-03-08  8:51 ` [PATCH v5 17/19] selftests: ftrace: Add a testcase for symbol type Masami Hiramatsu
2018-03-08  8:51 ` [PATCH v5 18/19] selftests: ftrace: Add a testcase for $argN with kprobe_event Masami Hiramatsu
2018-03-08  8:52 ` [PATCH v5 19/19] 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=d94e56c0-4096-5b8d-9e84-6a83b3daa84f@linux.vnet.ibm.com \
    --to=ravi.bangoria@linux.vnet.ibm.com \
    --cc=acme@kernel.org \
    --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=namhyung@kernel.org \
    --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
all inboxes | Powered by JetHome®