linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Thomas-Mich Richter <tmricht@linux.ibm.com>
Cc: Paul Clarke <pc@us.ibm.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	acme@kernel.org, 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: Fri, 15 Jun 2018 11:27:00 +0200	[thread overview]
Message-ID: <20180615092700.GH5082@krava> (raw)
In-Reply-To: <f78bbadb-047d-afad-eac6-b1236bd56c81@linux.ibm.com>

On Fri, Jun 15, 2018 at 11:09:05AM +0200, Thomas-Mich Richter wrote:
> On 06/15/2018 10:12 AM, Jiri Olsa wrote:
> > On Thu, Jun 14, 2018 at 08:53:14AM -0500, Paul Clarke wrote:
> > 
> > SNIP
> > 
> >>> +		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);
> > 
> > hum, how is newval different from val? AFAICS it's the same
> > 
> 
> Not really, depends on the platform, here is some debug output from s390:
> root@s35lp76 perf]# ./perf stat -e tx_nc_tend -- ~/mytesttx 1 >/tmp/111
> 
>  Performance counter stats for '/root/mytesttx 1':
> 
>                  1      tx_nc_tend                                                  
> 
>        0.001050150 seconds time elapsed
> 
> [root@s35lp76 perf]# fgrep -i tx_nc_tend /tmp/111
> __perf_pmu__new_alias TX_NC_TEND val:event=0x008d newval:event=0x8d
> __perf_pmu__new_alias tx_nc_tend val:event=0x8d newval:event=0x8d
> TX_NC_TEND	1 rc 8
> [root@s35lp76 perf]# 
> 
> On s390 the events in the PMU sysfs file are printed with leading zeroes.
> This means the strcmp() of alias->str differs, but the contents is logically
> identical. (Same of some files contains spaces).
> 
> Thats why I do the rewrite of val into newval.
> 
> The alias name does not match too, but we use strcasecmp() to ignore case.
> 
> Hope this helps.

yep.. should have read the full change log ;-) thanks

jirka

  reply	other threads:[~2018-06-15  9:27 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
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 [this message]
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=20180615092700.GH5082@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=brueckner@linux.vnet.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=pc@us.ibm.com \
    --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;
as well as URLs for NNTP newsgroup(s).