From: Namhyung Kim <namhyung@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: bookjovi@gmail.com, acme@ghostprotocols.net,
a.p.zijlstra@chello.nl, mingo@redhat.com, paulus@samba.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] perf, tool: Fix hw breakpoint's type modifier parsing
Date: Fri, 29 Jun 2012 09:40:47 +0900 [thread overview]
Message-ID: <87hatvx84w.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1340918329-3012-2-git-send-email-jolsa@redhat.com> (Jiri Olsa's message of "Thu, 28 Jun 2012 23:18:48 +0200")
On Thu, 28 Jun 2012 23:18:48 +0200, Jiri Olsa wrote:
> Fixing the hw breakpoint's type modifier parsing to allow all
> possible combinations of 'rwx' characters.
>
> Adding automated tests to the parsing test suite.
>
You might need this too:
Reported-by: Zovi Zhang <bookzovi@gmail.com>
Thanks,
Namhyung
> Original-patch-by: Namhyung Kim <namhyung@kernel.org>
> Signed-off-by: Jiri Olsa <jolsa@redhat.com>
> ---
> tools/perf/util/parse-events-test.c | 37 +++++++++++++++++++++++++++++++++++
> tools/perf/util/parse-events.c | 16 ++++++++++++--
> tools/perf/util/parse-events.l | 2 +-
> 3 files changed, 51 insertions(+), 4 deletions(-)
>
> diff --git a/tools/perf/util/parse-events-test.c b/tools/perf/util/parse-events-test.c
> index 229af6d..50e6a94 100644
> --- a/tools/perf/util/parse-events-test.c
> +++ b/tools/perf/util/parse-events-test.c
> @@ -181,6 +181,22 @@ static int test__checkevent_breakpoint_w(struct perf_evlist *evlist)
> return 0;
> }
>
> +static int test__checkevent_breakpoint_rw(struct perf_evlist *evlist)
> +{
> + struct perf_evsel *evsel = list_entry(evlist->entries.next,
> + struct perf_evsel, node);
> +
> + TEST_ASSERT_VAL("wrong number of entries", 1 == evlist->nr_entries);
> + TEST_ASSERT_VAL("wrong type",
> + PERF_TYPE_BREAKPOINT == evsel->attr.type);
> + TEST_ASSERT_VAL("wrong config", 0 == evsel->attr.config);
> + TEST_ASSERT_VAL("wrong bp_type",
> + (HW_BREAKPOINT_R|HW_BREAKPOINT_W) == evsel->attr.bp_type);
> + TEST_ASSERT_VAL("wrong bp_len",
> + HW_BREAKPOINT_LEN_4 == evsel->attr.bp_len);
> + return 0;
> +}
> +
> static int test__checkevent_tracepoint_modifier(struct perf_evlist *evlist)
> {
> struct perf_evsel *evsel = list_entry(evlist->entries.next,
> @@ -352,6 +368,19 @@ static int test__checkevent_breakpoint_w_modifier(struct perf_evlist *evlist)
> return test__checkevent_breakpoint_w(evlist);
> }
>
> +static int test__checkevent_breakpoint_rw_modifier(struct perf_evlist *evlist)
> +{
> + struct perf_evsel *evsel = list_entry(evlist->entries.next,
> + struct perf_evsel, node);
> +
> + TEST_ASSERT_VAL("wrong exclude_user", evsel->attr.exclude_user);
> + TEST_ASSERT_VAL("wrong exclude_kernel", !evsel->attr.exclude_kernel);
> + TEST_ASSERT_VAL("wrong exclude_hv", evsel->attr.exclude_hv);
> + TEST_ASSERT_VAL("wrong precise_ip", evsel->attr.precise_ip);
> +
> + return test__checkevent_breakpoint_rw(evlist);
> +}
> +
> static int test__checkevent_pmu(struct perf_evlist *evlist)
> {
>
> @@ -584,6 +613,14 @@ static struct test__event_st test__events[] = {
> .name = "instructions:H",
> .check = test__checkevent_exclude_guest_modifier,
> },
> + [26] = {
> + .name = "mem:0:rw",
> + .check = test__checkevent_breakpoint_rw,
> + },
> + [27] = {
> + .name = "mem:0:rw:kp",
> + .check = test__checkevent_breakpoint_rw_modifier,
> + },
> };
>
> #define TEST__EVENTS_CNT (sizeof(test__events) / sizeof(struct test__event_st))
> diff --git a/tools/perf/util/parse-events.c b/tools/perf/util/parse-events.c
> index 0cc27da..7ae76af 100644
> --- a/tools/perf/util/parse-events.c
> +++ b/tools/perf/util/parse-events.c
> @@ -383,21 +383,31 @@ parse_breakpoint_type(const char *type, struct perf_event_attr *attr)
> if (!type || !type[i])
> break;
>
> +#define CHECK_SET_TYPE(bit) \
> +do { \
> + if (attr->bp_type & bit) \
> + return -EINVAL; \
> + else \
> + attr->bp_type |= bit; \
> +} while (0)
> +
> switch (type[i]) {
> case 'r':
> - attr->bp_type |= HW_BREAKPOINT_R;
> + CHECK_SET_TYPE(HW_BREAKPOINT_R);
> break;
> case 'w':
> - attr->bp_type |= HW_BREAKPOINT_W;
> + CHECK_SET_TYPE(HW_BREAKPOINT_W);
> break;
> case 'x':
> - attr->bp_type |= HW_BREAKPOINT_X;
> + CHECK_SET_TYPE(HW_BREAKPOINT_X);
> break;
> default:
> return -EINVAL;
> }
> }
>
> +#undef CHECK_SET_TYPE
> +
> if (!attr->bp_type) /* Default */
> attr->bp_type = HW_BREAKPOINT_R | HW_BREAKPOINT_W;
>
> diff --git a/tools/perf/util/parse-events.l b/tools/perf/util/parse-events.l
> index 488362e..a066894 100644
> --- a/tools/perf/util/parse-events.l
> +++ b/tools/perf/util/parse-events.l
> @@ -76,7 +76,7 @@ num_hex 0x[a-fA-F0-9]+
> num_raw_hex [a-fA-F0-9]+
> name [a-zA-Z_*?][a-zA-Z0-9_*?]*
> modifier_event [ukhpGH]{1,8}
> -modifier_bp [rwx]
> +modifier_bp [rwx]{1,3}
>
> %%
next prev parent reply other threads:[~2012-06-29 0:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 8:39 [PATCH] perf: fix wrong hw_breakpoint documentation Jovi Zhang
2012-06-27 8:59 ` Namhyung Kim
2012-06-27 13:40 ` Jovi Zhang
2012-06-27 16:15 ` Arnaldo Carvalho de Melo
2012-06-27 19:07 ` Jiri Olsa
2012-06-27 19:58 ` Peter Zijlstra
2012-06-27 20:19 ` Jiri Olsa
2012-06-28 1:30 ` Namhyung Kim
2012-06-28 10:32 ` Jiri Olsa
2012-06-28 21:18 ` [PATCH 0/2] perf, tool: Hw breakpoint events parsing fixes Jiri Olsa
2012-06-28 21:18 ` [PATCH 1/2] perf, tool: Fix hw breakpoint's type modifier parsing Jiri Olsa
2012-06-29 0:40 ` Namhyung Kim [this message]
2012-06-29 1:01 ` Jovi Zhang
2012-06-29 1:34 ` Namhyung Kim
2012-06-29 7:22 ` [PATCHv2 " Jiri Olsa
2012-07-06 10:57 ` [tip:perf/core] perf tools: Fix hw breakpoint' s " tip-bot for Jiri Olsa
2012-06-28 21:18 ` [PATCH 2/2] perf, tool: Handle hw breakpoints event names via perf_evsel__name Jiri Olsa
2012-07-06 10:58 ` [tip:perf/core] perf evsel: Handle hw breakpoints event names in perf_evsel__name() tip-bot for Jiri Olsa
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=87hatvx84w.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=bookjovi@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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