From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.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: Tue, 18 May 2021 09:40:41 +0800 [thread overview]
Message-ID: <228cc228-464d-c4dd-039c-535f050704d5@linux.intel.com> (raw)
In-Reply-To: <YKA6oqfP0niinZkD@krava>
Hi Jiri,
On 5/16/2021 5:18 AM, Jiri Olsa wrote:
> 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
>
Thanks so much!
I have some followup patches which depend on this patchset. I will post them after this patchset is
applied.
Thanks
Jin Yao
prev parent reply other threads:[~2021-05-18 1:40 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 ` [PATCH v4 0/2] perf header: Support HYBRID_TOPOLOGY and HYBRID_CPU_PMU_CAPS Jiri Olsa
2021-05-18 1:40 ` Jin, Yao [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=228cc228-464d-c4dd-039c-535f050704d5@linux.intel.com \
--to=yao.jin@linux.intel.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=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@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