linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jin Yao <yao.jin@linux.intel.com>
Cc: jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com,
	alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, ak@linux.intel.com,
	kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH] perf stat: Support --cputype option for hybrid events
Date: Tue, 7 Dec 2021 11:46:17 -0300	[thread overview]
Message-ID: <Ya9zufZb+1zRl+Cj@kernel.org> (raw)
In-Reply-To: <20210909062215.10278-1-yao.jin@linux.intel.com>

Em Thu, Sep 09, 2021 at 02:22:15PM +0800, Jin Yao escreveu:
> In previous patch, we have supported the syntax which enables
> the event on a specified pmu, such as:

Fell thru the cracks :-\

Thanks, applied.

- Arnaldo

 
> cpu_core/<event>/
> cpu_atom/<event>/
> 
> While this syntax is not very easy for applying on a set of
> events or applying on a group. In following example, we have to
> explicitly assign the pmu prefix.
> 
>   # ./perf stat -e '{cpu_core/cycles/,cpu_core/instructions/}' -- sleep 1
> 
>    Performance counter stats for 'sleep 1':
> 
>            1,158,545      cpu_core/cycles/
>            1,003,113      cpu_core/instructions/
> 
>          1.002428712 seconds time elapsed
> 
> A much easier way is:
> 
>   # ./perf stat --cputype core -e '{cycles,instructions}' -- sleep 1
> 
>    Performance counter stats for 'sleep 1':
> 
>            1,101,071      cpu_core/cycles/
>              939,892      cpu_core/instructions/
> 
>          1.002363142 seconds time elapsed
> 
> For this example, the '--cputype' enables the events from specified
> pmu (cpu_core).
> 
> If '--cputype' conflicts with pmu prefix, '--cputype' is ignored.
> 
>   # ./perf stat --cputype core -e cycles,cpu_atom/instructions/ -a -- sleep 1
> 
>    Performance counter stats for 'system wide':
> 
>           21,003,407      cpu_core/cycles/
>              367,886      cpu_atom/instructions/
> 
>          1.002203520 seconds time elapsed
> 
> Signed-off-by: Jin Yao <yao.jin@linux.intel.com>
> ---
>  tools/perf/Documentation/perf-stat.txt |  4 ++++
>  tools/perf/builtin-stat.c              | 24 ++++++++++++++++++++++++
>  tools/perf/util/evlist.h               |  1 +
>  tools/perf/util/parse-events-hybrid.c  |  9 ++++++---
>  4 files changed, 35 insertions(+), 3 deletions(-)
> 
> diff --git a/tools/perf/Documentation/perf-stat.txt b/tools/perf/Documentation/perf-stat.txt
> index 4c9310be6acc..33da737161a6 100644
> --- a/tools/perf/Documentation/perf-stat.txt
> +++ b/tools/perf/Documentation/perf-stat.txt
> @@ -493,6 +493,10 @@ This option can be enabled in perf config by setting the variable
>  
>  $ perf config stat.no-csv-summary=true
>  
> +--cputype::
> +Only enable events on applying cpu with this type for hybrid platform
> +(e.g. core or atom)"
> +
>  EXAMPLES
>  --------
>  
> diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> index f6e87b7be5fa..752e2bf1029f 100644
> --- a/tools/perf/builtin-stat.c
> +++ b/tools/perf/builtin-stat.c
> @@ -1168,6 +1168,26 @@ static int parse_stat_cgroups(const struct option *opt,
>  	return parse_cgroups(opt, str, unset);
>  }
>  
> +static int parse_hybrid_type(const struct option *opt,
> +			     const char *str,
> +			     int unset __maybe_unused)
> +{
> +	struct evlist *evlist = *(struct evlist **)opt->value;
> +
> +	if (!list_empty(&evlist->core.entries)) {
> +		fprintf(stderr, "Must define cputype before events/metrics\n");
> +		return -1;
> +	}
> +
> +	evlist->hybrid_pmu_name = perf_pmu__hybrid_type_to_pmu(str);
> +	if (!evlist->hybrid_pmu_name) {
> +		fprintf(stderr, "--cputype %s is not supported!\n", str);
> +		return -1;
> +	}
> +
> +	return 0;
> +}
> +
>  static struct option stat_options[] = {
>  	OPT_BOOLEAN('T', "transaction", &transaction_run,
>  		    "hardware transaction statistics"),
> @@ -1282,6 +1302,10 @@ static struct option stat_options[] = {
>  		       "don't print 'summary' for CSV summary output"),
>  	OPT_BOOLEAN(0, "quiet", &stat_config.quiet,
>  			"don't print output (useful with record)"),
> +	OPT_CALLBACK(0, "cputype", &evsel_list, "hybrid cpu type",
> +		     "Only enable events on applying cpu with this type "
> +		     "for hybrid platform (e.g. core or atom)",
> +		     parse_hybrid_type),
>  #ifdef HAVE_LIBPFM
>  	OPT_CALLBACK(0, "pfm-events", &evsel_list, "event",
>  		"libpfm4 event selector. use 'perf list' to list available events",
> diff --git a/tools/perf/util/evlist.h b/tools/perf/util/evlist.h
> index 97bfb8d0be4f..7af5b247e319 100644
> --- a/tools/perf/util/evlist.h
> +++ b/tools/perf/util/evlist.h
> @@ -64,6 +64,7 @@ struct evlist {
>  	struct evsel *selected;
>  	struct events_stats stats;
>  	struct perf_env	*env;
> +	const char *hybrid_pmu_name;
>  	void (*trace_event_sample_raw)(struct evlist *evlist,
>  				       union perf_event *event,
>  				       struct perf_sample *sample);
> diff --git a/tools/perf/util/parse-events-hybrid.c b/tools/perf/util/parse-events-hybrid.c
> index 10160ab126f9..3875a8d086e4 100644
> --- a/tools/perf/util/parse-events-hybrid.c
> +++ b/tools/perf/util/parse-events-hybrid.c
> @@ -62,10 +62,13 @@ static int create_event_hybrid(__u32 config_type, int *idx,
>  static int pmu_cmp(struct parse_events_state *parse_state,
>  		   struct perf_pmu *pmu)
>  {
> -	if (!parse_state->hybrid_pmu_name)
> -		return 0;
> +	if (parse_state->evlist && parse_state->evlist->hybrid_pmu_name)
> +		return strcmp(parse_state->evlist->hybrid_pmu_name, pmu->name);
> +
> +	if (parse_state->hybrid_pmu_name)
> +		return strcmp(parse_state->hybrid_pmu_name, pmu->name);
>  
> -	return strcmp(parse_state->hybrid_pmu_name, pmu->name);
> +	return 0;
>  }
>  
>  static int add_hw_hybrid(struct parse_events_state *parse_state,
> -- 
> 2.17.1

-- 

- Arnaldo

      reply	other threads:[~2021-12-07 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09  6:22 [PATCH] perf stat: Support --cputype option for hybrid events Jin Yao
2021-12-07 14:46 ` Arnaldo Carvalho de Melo [this message]

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=Ya9zufZb+1zRl+Cj@kernel.org \
    --to=acme@kernel.org \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=yao.jin@intel.com \
    --cc=yao.jin@linux.intel.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).