mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Wang Nan <wangnan0@huawei.com>
Cc: acme@kernel.org, masami.hiramatsu.pt@hitachi.com,
	jolsa@kernel.org, linux-kernel@vger.kernel.org, pi3orama@163.com,
	lizefan@huawei.com, He Kuang <hekuang@huawei.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH v5 05/14] perf tools: Enable BPF object configure syntax
Date: Tue, 15 Dec 2015 14:12:23 +0100	[thread overview]
Message-ID: <20151215131223.GA31734@krava.brq.redhat.com> (raw)
In-Reply-To: <1450089563-122430-6-git-send-email-wangnan0@huawei.com>

On Mon, Dec 14, 2015 at 10:39:14AM +0000, Wang Nan wrote:

SNIP

>     -e, --event <event>   event selector. use 'perf list' to list available events
> 
>  # ./perf record -e './test_bpf_map_1.c/xmaps:channel.value=10/' usleep 10
>  event syntax error: '..pf_map_1.c/xmaps:channel.value=10/'
>                                    \___ Invalid object config option
>  [SNIP]
> 
>  # ./perf record -e './test_bpf_map_1.c/maps:xchannel.value=10/' usleep 10
>  event syntax error: '..p_1.c/maps:xchannel.value=10/'
>                                    \___ Target map not exist
>  [SNIP]
> 
>  # ./perf record -e './test_bpf_map_1.c/maps:channel.xvalue=10/' usleep 10
>  event syntax error: '..ps:channel.xvalue=10/'
>                                    \___ Invalid object maps config option
>  [SNIP]
> 
>  # ./perf record -e './test_bpf_map_1.c/maps:channel.value=x10/' usleep 10
>  event syntax error: '..nnel.value=x10/'
>                                    \___ Incorrect value type for map
>  [SNIP]
> 
>  Change BPF_MAP_TYPE_ARRAY to '1':
> 
>  # ./perf record -e './test_bpf_map_1.c/maps:channel.value=10/' usleep 10
>  event syntax error: '..ps:channel.value=10/'
>                                    \___ Can't use this config term to this type of map
> 
>  Hint:	Valid config term:
>      	maps:[<arraymap>].value=[value]
>      	(add -v to see detail)
> 
> Signed-off-by: Wang Nan <wangnan0@huawei.com>
> Signed-off-by: He Kuang <hekuang@huawei.com>
> Cc: Alexei Starovoitov <ast@kernel.org>
> Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Zefan Li <lizefan@huawei.com>
> Cc: pi3orama@163.com
> ---
>  tools/perf/util/parse-events.c | 56 +++++++++++++++++++++++++++++++++++++++---
>  tools/perf/util/parse-events.h |  3 ++-
>  tools/perf/util/parse-events.l |  2 +-
>  tools/perf/util/parse-events.y | 23 ++++++++++++++---
>  4 files changed, 75 insertions(+), 9 deletions(-)

I don't understand the bpf stuff, but as far as config terms this
change look ok to me, so for bison/flex parser related changes:

Acked-by: Jiri Olsa <jolsa@kernel.org>

thanks,
jirka

  reply	other threads:[~2015-12-15 13:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14 10:39 [PATCH v5 00/14] perf tools: BPF related update and other improvements Wang Nan
2015-12-14 10:39 ` [PATCH v5 01/14] perf tests: Fix incorrect free and false TEST_OK result Wang Nan
2015-12-14 10:39 ` [PATCH v5 02/14] perf tools: Prevent calling machine__delete() on non-allocated machine Wang Nan
2015-12-15 12:36   ` Jiri Olsa
2015-12-16  1:37     ` Wangnan (F)
2015-12-16 19:49       ` Arnaldo Carvalho de Melo
2015-12-14 10:39 ` [PATCH v5 03/14] perf test: Check environment before start real BPF test Wang Nan
2015-12-14 10:39 ` [PATCH v5 04/14] perf tools: Add API to config maps in bpf object Wang Nan
2015-12-14 10:39 ` [PATCH v5 05/14] perf tools: Enable BPF object configure syntax Wang Nan
2015-12-15 13:12   ` Jiri Olsa [this message]
2015-12-14 10:39 ` [PATCH v5 06/14] perf record: Apply config to BPF objects before recording Wang Nan
2015-12-14 10:39 ` [PATCH v5 07/14] perf tools: Enable passing event to BPF object Wang Nan
2015-12-14 10:39 ` [PATCH v5 08/14] perf tools: Support perf event alias name Wang Nan
2015-12-15 13:18   ` Jiri Olsa
2015-12-16  1:50     ` Wangnan (F)
2015-12-14 10:39 ` [PATCH v5 09/14] perf tools: Support setting different slots in a BPF map separately Wang Nan
2015-12-14 10:39 ` [PATCH v5 10/14] perf tools: Enable indices setting syntax for BPF maps Wang Nan
2015-12-15 13:42   ` Jiri Olsa
2015-12-16  2:02     ` Wangnan (F)
2015-12-16  7:55       ` Jiri Olsa
2015-12-16 11:24   ` Jiri Olsa
2015-12-14 10:39 ` [PATCH v5 11/14] perf tools: Introduce bpf-output event Wang Nan
2015-12-14 10:39 ` [PATCH v5 12/14] perf data: Support converting data from bpf_perf_event_output() Wang Nan
2015-12-16 11:29   ` Jiri Olsa
2015-12-14 10:39 ` [PATCH v5 13/14] perf tools: Always give options even it not compiled Wang Nan
2015-12-14 16:00   ` Arnaldo Carvalho de Melo
2015-12-18  8:50   ` [tip:perf/core] perf tools: Make options always available, even if required libs not linked tip-bot for Wang Nan
2015-12-14 10:39 ` [PATCH v5 14/14] perf record: Support custom vmlinux path Wang Nan
2015-12-18  8:51   ` [tip:perf/core] " tip-bot for He Kuang

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=20151215131223.GA31734@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=ast@kernel.org \
    --cc=hekuang@huawei.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=namhyung@kernel.org \
    --cc=pi3orama@163.com \
    --cc=wangnan0@huawei.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

Powered by JetHome