public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Jin Yao <yao.jin@linux.intel.com>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
	mingo@redhat.com, alexander.shishkin@linux.intel.com,
	Linux-kernel@vger.kernel.org, ak@linux.intel.com,
	kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v4 0/2] perf header: Support HYBRID_TOPOLOGY and HYBRID_CPU_PMU_CAPS
Date: Sat, 15 May 2021 23:18:26 +0200	[thread overview]
Message-ID: <YKA6oqfP0niinZkD@krava> (raw)
In-Reply-To: <20210514122948.9472-1-yao.jin@linux.intel.com>

On Fri, May 14, 2021 at 08:29:46PM +0800, Jin Yao wrote:
> AlderLake uses a hybrid architecture utilizing Golden Cove cores
> (core cpu) and Gracemont cores (atom cpu). It would be useful to let user
> know the hybrid topology, the HYBRID_TOPOLOGY feature in header indicates
> which cpus are core cpus, and which cpus are atom cpus.
> 
> On hybrid platform, it may have several cpu pmus, such as, "cpu_core" and
> "cpu_atom". The HYBRID_CPU_PMU_CAPS feature in perf header is created to
> support multiple cpu pmus.
> 
> v4:
> ---
> - Only minor update in '[PATCH v4 2/2] perf header: Support HYBRID_CPU_PMU_CAPS feature'.
>   1. Directly return process_per_cpu_pmu_caps() in process_cpu_pmu_caps.
>      Remove the variable 'ret'.
>   2. Set 'ret = -1' if (!n->pmu_name) in process_hybrid_cpu_pmu_caps().

Acked-by: Jiri Olsa <jolsa@redhat.com>

thanks,
jirka

> 
> v3:
> ---
> - For "[PATCH v3 1/2] perf header: Support HYBRID_TOPOLOGY feature",
>   update HEADER_HYBRID_TOPOLOGY format in perf.data-file-format.txt.
> 
> - For "[PATCH v3 2/2] perf header: Support HYBRID_CPU_PMU_CAPS feature",
>   Don't extend the original CPU_PMU_CAPS to support hybrid cpu pmus.
>   Instead, create a new feature 'HYBRID_CPU_PMU_CAPS' in header.
> 
> v2:
> ---
> - In "perf header: Support HYBRID_TOPOLOGY feature", don't use the n->map
>   to print the cpu list, just use n->cpus.
> 
> - Separate hybrid CPU_PMU_CAPS support into two patches:
>   perf header: Write hybrid CPU_PMU_CAPS
>   perf header: Process hybrid CPU_PMU_CAPS
> 
> - Add some words to perf.data-file-format.txt for HYBRID_TOPOLOGY and
>   hybrid CPU_PMU_CAPS.
> 
> Jin Yao (2):
>   perf header: Support HYBRID_TOPOLOGY feature
>   perf header: Support HYBRID_CPU_PMU_CAPS feature
> 
>  .../Documentation/perf.data-file-format.txt   |  33 +++
>  tools/perf/util/cputopo.c                     |  80 ++++++
>  tools/perf/util/cputopo.h                     |  13 +
>  tools/perf/util/env.c                         |  12 +
>  tools/perf/util/env.h                         |  16 ++
>  tools/perf/util/header.c                      | 249 ++++++++++++++++--
>  tools/perf/util/header.h                      |   2 +
>  tools/perf/util/pmu-hybrid.h                  |  11 +
>  8 files changed, 397 insertions(+), 19 deletions(-)
> 
> -- 
> 2.17.1
> 


  parent reply	other threads:[~2021-05-15 21:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14 12:29 [PATCH v4 0/2] perf header: Support HYBRID_TOPOLOGY and HYBRID_CPU_PMU_CAPS Jin Yao
2021-05-14 12:29 ` [PATCH v4 1/2] perf header: Support HYBRID_TOPOLOGY feature Jin Yao
2021-05-14 12:29 ` [PATCH v4 2/2] perf header: Support HYBRID_CPU_PMU_CAPS feature Jin Yao
2021-05-15 21:18 ` Jiri Olsa [this message]
2021-05-18  1:40   ` [PATCH v4 0/2] perf header: Support HYBRID_TOPOLOGY and HYBRID_CPU_PMU_CAPS Jin, Yao

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=YKA6oqfP0niinZkD@krava \
    --to=jolsa@redhat.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --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