From: mhiramat at kernel.org (Masami Hiramatsu)
Subject: [PATCH v5 16/19] tracing: probeevent: Add array type support
Date: Thu, 15 Mar 2018 16:23:03 +0900 [thread overview]
Message-ID: <20180315162303.1250dea1500aea420ecd85c6@kernel.org> (raw)
In-Reply-To: <20180315161840.71d524a73307881febfe34c2@kernel.org>
Hi Ravi,
On Thu, 15 Mar 2018 16:18:40 +0900
Masami Hiramatsu <mhiramat at kernel.org> wrote:
> On Thu, 15 Mar 2018 11:18:19 +0530
> Ravi Bangoria <ravi.bangoria at linux.vnet.ibm.com> wrote:
>
> > Hi Masami,
> >
> > On 03/08/2018 02:20 PM, 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.
> >
> > I was trying to test this patch. But I'm not getting proper data.
> > Here is what I'm doing...
> >
> > $ cat hello.c
> > #include <stdio.h>
> >
> > void foo1(int a[])
> > {
> > printf("%d\n", a[2]);
> > }
> >
> > void foo(int a[])
> > {
> > printf("%d\n", a[1]);
> > foo1(a);
> > }
> >
> > void main()
> > {
> > int a[3] = {4, 5, 6};
> > printf("%d\n", a[0]);
> > foo(a);
> > }
> >
> > $ gcc -g hello.c -o hello
> > $ sudo ./perf probe -x ~/hello foo1 'a=a:x32[3]'
> > $ sudo cat /sys/kernel/debug/tracing/uprobe_events
> > p:probe_hello/foo1 /home/ravi/hello:0x00000000000005fc a=+96(%gpr31):x32[3]
> >
> > $ sudo ./perf record -e probe_hello:foo1 ~/hello
> > $ sudo ./perf script
> > hello 6913 [038] 2857.704470: probe_hello:foo1: (100005fc) a={0xd69e4400,0x7fff,0x0}
> >
> >
> > I don't see proper values of the 'a'? Anything wrong with my perf commands :) ?
>
> Ah, I guess since it is a pointer. in main() function, "a" is an array,
> but in foo1(), "a" is a pointer to the array.
> From the viewpoint of C source code, both pointer and array is same
> expression, but actually it is not same from memory point of view.
> perf probe has to be updated to enable it too.
>
> Could you please try to do as below?
>
> $ echo "p:probe_hello/foo1 /home/ravi/hello:0x00000000000005fc a=+0(+96(%gpr31)):x32[3]" | sudo tee /sys/kernel/debug/tracing/uprobe_events
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]'
:)
Thank you,
--
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 v5 16/19] tracing: probeevent: Add array type support
Date: Thu, 15 Mar 2018 16:23:03 +0900 [thread overview]
Message-ID: <20180315162303.1250dea1500aea420ecd85c6@kernel.org> (raw)
Message-ID: <20180315072303.MXpk0ZOb2Odi_VdZ5nUJntjslbwyF8MuMeZAnAkH8a0@z> (raw)
In-Reply-To: <20180315161840.71d524a73307881febfe34c2@kernel.org>
Hi Ravi,
On Thu, 15 Mar 2018 16:18:40 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> On Thu, 15 Mar 2018 11:18:19 +0530
> Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com> wrote:
>
> > Hi Masami,
> >
> > On 03/08/2018 02:20 PM, 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.
> >
> > I was trying to test this patch. But I'm not getting proper data.
> > Here is what I'm doing...
> >
> > $ cat hello.c
> > #include <stdio.h>
> >
> > void foo1(int a[])
> > {
> > printf("%d\n", a[2]);
> > }
> >
> > void foo(int a[])
> > {
> > printf("%d\n", a[1]);
> > foo1(a);
> > }
> >
> > void main()
> > {
> > int a[3] = {4, 5, 6};
> > printf("%d\n", a[0]);
> > foo(a);
> > }
> >
> > $ gcc -g hello.c -o hello
> > $ sudo ./perf probe -x ~/hello foo1 'a=a:x32[3]'
> > $ sudo cat /sys/kernel/debug/tracing/uprobe_events
> > p:probe_hello/foo1 /home/ravi/hello:0x00000000000005fc a=+96(%gpr31):x32[3]
> >
> > $ sudo ./perf record -e probe_hello:foo1 ~/hello
> > $ sudo ./perf script
> > hello 6913 [038] 2857.704470: probe_hello:foo1: (100005fc) a={0xd69e4400,0x7fff,0x0}
> >
> >
> > I don't see proper values of the 'a'? Anything wrong with my perf commands :) ?
>
> Ah, I guess since it is a pointer. in main() function, "a" is an array,
> but in foo1(), "a" is a pointer to the array.
> From the viewpoint of C source code, both pointer and array is same
> expression, but actually it is not same from memory point of view.
> perf probe has to be updated to enable it too.
>
> Could you please try to do as below?
>
> $ echo "p:probe_hello/foo1 /home/ravi/hello:0x00000000000005fc a=+0(+96(%gpr31)):x32[3]" | sudo tee /sys/kernel/debug/tracing/uprobe_events
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]'
:)
Thank you,
--
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-03-15 7:23 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 8:43 [PATCH v5 00/19] tracing: probeevent: Improve fetcharg features mhiramat
2018-03-08 8:43 ` Masami Hiramatsu
2018-03-08 8:44 ` [PATCH v5 01/19] [BUGFIX] tracing: probeevent: Fix to support minus offset from symbol mhiramat
2018-03-08 8:44 ` Masami Hiramatsu
2018-03-08 8:44 ` [PATCH v5 02/19] selftests: ftrace: Add probe event argument syntax testcase mhiramat
2018-03-08 8:44 ` Masami Hiramatsu
2018-03-08 8:45 ` [PATCH v5 03/19] selftests: ftrace: Add a testcase for string type with kprobe_event mhiramat
2018-03-08 8:45 ` Masami Hiramatsu
2018-03-08 8:45 ` [PATCH v5 04/19] selftests: ftrace: Add a testcase for probepoint mhiramat
2018-03-08 8:45 ` Masami Hiramatsu
2018-03-08 8:46 ` [PATCH v5 05/19] tracing: probeevent: Cleanup print argument functions mhiramat
2018-03-08 8:46 ` Masami Hiramatsu
2018-03-08 8:46 ` [PATCH v5 06/19] tracing: probeevent: Cleanup argument field definition mhiramat
2018-03-08 8:46 ` Masami Hiramatsu
2018-03-08 8:46 ` [PATCH v5 07/19] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions mhiramat
2018-03-08 8:46 ` Masami Hiramatsu
2018-03-08 8:47 ` [PATCH v5 08/19] tracing: probeevent: Introduce new argument fetching code mhiramat
2018-03-08 8:47 ` Masami Hiramatsu
2018-03-08 8:47 ` [PATCH v5 09/19] tracing: probeevent: Unify fetch type tables mhiramat
2018-03-08 8:47 ` Masami Hiramatsu
2018-03-08 8:47 ` [PATCH v5 10/19] tracing: probeevent: Return consumed bytes of dynamic area mhiramat
2018-03-08 8:47 ` Masami Hiramatsu
2018-03-08 8:48 ` [PATCH v5 11/19] tracing: probeevent: Append traceprobe_ for exported function mhiramat
2018-03-08 8:48 ` Masami Hiramatsu
2018-03-08 8:48 ` [PATCH v5 12/19] tracing: probeevent: Unify fetch_insn processing common part mhiramat
2018-03-08 8:48 ` Masami Hiramatsu
2018-03-08 8:49 ` [PATCH v5 13/19] tracing: probeevent: Add symbol type mhiramat
2018-03-08 8:49 ` Masami Hiramatsu
2018-03-08 8:49 ` [PATCH v5 14/19] x86: ptrace: Add function argument access API mhiramat
2018-03-08 8:49 ` Masami Hiramatsu
2018-03-08 8:50 ` [PATCH v5 15/19] tracing: probeevent: Add $argN for accessing function args mhiramat
2018-03-08 8:50 ` Masami Hiramatsu
2018-03-08 8:50 ` [PATCH v5 16/19] tracing: probeevent: Add array type support mhiramat
2018-03-08 8:50 ` Masami Hiramatsu
2018-03-15 5:48 ` ravi.bangoria
2018-03-15 5:48 ` Ravi Bangoria
2018-03-15 7:18 ` mhiramat
2018-03-15 7:18 ` Masami Hiramatsu
2018-03-15 7:23 ` mhiramat [this message]
2018-03-15 7:23 ` Masami Hiramatsu
2018-03-15 8:01 ` ravi.bangoria
2018-03-15 8:01 ` Ravi Bangoria
2018-03-16 14:48 ` mhiramat
2018-03-16 14:48 ` Masami Hiramatsu
2018-03-08 8:51 ` [PATCH v5 17/19] selftests: ftrace: Add a testcase for symbol type mhiramat
2018-03-08 8:51 ` Masami Hiramatsu
2018-03-08 8:51 ` [PATCH v5 18/19] selftests: ftrace: Add a testcase for $argN with kprobe_event mhiramat
2018-03-08 8:51 ` Masami Hiramatsu
2018-03-08 8:52 ` [PATCH v5 19/19] selftests: ftrace: Add a testcase for array type " mhiramat
2018-03-08 8:52 ` 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=20180315162303.1250dea1500aea420ecd85c6@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