From: Paul Clarke <pc@us.ibm.com>
To: Thomas Richter <tmricht@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
acme@kernel.org, jolsa@redhat.com
Cc: brueckner@linux.vnet.ibm.com, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com
Subject: Re: [PATCH 2/3] perf alias: Rebuild alias expression string to make it comparable
Date: Thu, 14 Jun 2018 08:53:14 -0500 [thread overview]
Message-ID: <809ff562-511d-26e9-bac3-e8f7b84666e5@us.ibm.com> (raw)
In-Reply-To: <20180614114845.41221-2-tmricht@linux.ibm.com>
On 06/14/2018 06:48 AM, Thomas Richter wrote:
> PMU alias definitions in sysfs files may have spaces, newlines
> and number with leading zeroes. Same alias definitions may
> also appear in JSON files without spaces, etc.
>
> Scan alias definitions and remove leading zeroes, spaces,
> newlines, etc and rebuild string to make alias->str member
> comparable.
>
> s390 for example has terms specified as
> event=0x0091 (read from files ../<PMU>/events/<FILE>
> and terms specified as event=0x91 (read from JSON files).
>
> Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
> ---
> tools/perf/util/pmu.c | 25 ++++++++++++++++++++++++-
> 1 file changed, 24 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c
> index 26c79a9c4142..da8f243743d3 100644
> --- a/tools/perf/util/pmu.c
> +++ b/tools/perf/util/pmu.c
> @@ -241,9 +241,11 @@ static int __perf_pmu__new_alias(struct list_head *list, char *dir, char *name,
> char *metric_expr,
> char *metric_name)
> {
> + struct parse_events_term *term;
> struct perf_pmu_alias *alias;
> int ret;
> int num;
> + char newval[256];
How was 256 chosen?
>
> alias = malloc(sizeof(*alias));
> if (!alias)
> @@ -262,6 +264,27 @@ static int __perf_pmu__new_alias(struct list_head *list, char *dir, char *name,
> return ret;
> }
>
> + /* Scan event and remove leading zeroes, spaces, newlines, some
> + * platforms have terms specified as
> + * event=0x0091 (read from files ../<PMU>/events/<FILE>
> + * and terms specified as event=0x91 (read from JSON files).
> + *
> + * Rebuild string to make alias->str member comparable.
> + */
> + memset(newval, 0, sizeof(newval));
> + ret = 0;
> + list_for_each_entry(term, &alias->terms, list) {
> + if (ret)
> + ret += scnprintf(newval + ret, sizeof(newval) - ret,
> + ",");
> + if (term->type_val == PARSE_EVENTS__TERM_TYPE_NUM)
> + ret += scnprintf(newval + ret, sizeof(newval) - ret,
> + "%s=%#x", term->config, term->val.num);
> + else if (term->type_val == PARSE_EVENTS__TERM_TYPE_STR)
> + ret += scnprintf(newval + ret, sizeof(newval) - ret,
> + "%s=%s", term->config, term->val.str);
If we exceed 256, we just suddenly terminate the rebuilding without reporting any issues.
> + }
> +
> alias->name = strdup(name);
> if (dir) {
> /*
> @@ -285,7 +308,7 @@ static int __perf_pmu__new_alias(struct list_head *list, char *dir, char *name,
> snprintf(alias->unit, sizeof(alias->unit), "%s", unit);
> }
> alias->per_pkg = perpkg && sscanf(perpkg, "%d", &num) == 1 && num == 1;
> - alias->str = strdup(val);
> + alias->str = strdup(newval);
>
> list_add_tail(&alias->list, list);
>
PC
next prev parent reply other threads:[~2018-06-14 13:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 11:48 [PATCH 1/3] perf alias: Remove trailing newline when reading sysfs files Thomas Richter
2018-06-14 11:48 ` [PATCH 2/3] perf alias: Rebuild alias expression string to make it comparable Thomas Richter
2018-06-14 13:53 ` Paul Clarke [this message]
2018-06-14 14:16 ` Thomas-Mich Richter
2018-06-15 8:12 ` Jiri Olsa
2018-06-15 9:09 ` Thomas-Mich Richter
2018-06-15 9:27 ` Jiri Olsa
2018-06-14 11:48 ` [PATCH 3/3] perf stat: Remove duplicate event counting Thomas Richter
2018-06-15 8:21 ` Jiri Olsa
2018-06-15 8:56 ` Thomas-Mich Richter
2018-06-19 15:17 ` Arnaldo Carvalho de Melo
2018-06-19 18:24 ` Jiri Olsa
2018-06-14 13:17 ` [PATCH 1/3] perf alias: Remove trailing newline when reading sysfs files Paul Clarke
2018-06-14 14:10 ` Thomas-Mich Richter
2018-06-15 9:10 ` David Laight
2018-06-14 14:05 ` Arnaldo Carvalho de Melo
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=809ff562-511d-26e9-bac3-e8f7b84666e5@us.ibm.com \
--to=pc@us.ibm.com \
--cc=acme@kernel.org \
--cc=brueckner@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=tmricht@linux.ibm.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