From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: 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 v6 01/26] tools headers uapi: Update tools's copy of linux/perf_event.h
Date: Wed, 28 Apr 2021 09:18:11 +0800 [thread overview]
Message-ID: <e6bc62d5-50e8-15cf-915f-de15b3d7b860@linux.intel.com> (raw)
In-Reply-To: <YIhk2XkvUcoIPbgc@kernel.org>
Hi Arnaldo,
On 4/28/2021 3:24 AM, Arnaldo Carvalho de Melo wrote:
> Em Tue, Apr 27, 2021 at 03:01:14PM +0800, Jin Yao escreveu:
>> To get the changes in:
>>
>> Liang Kan's patch
>> [PATCH V6 21/25] perf: Extend PERF_TYPE_HARDWARE and PERF_TYPE_HW_CACHE
>>
>> Kan's patch is upstreamed yet but perf/core branch doesn't have it
>> at this moment. But next perf tool patches need this interface for
>> hybrid support.
>>
>> This patch can be removed after Kan's patch is merged in perf/core
>> branch.
>
> Nope, it is already in tip/perf/core as:
>
> 55bcf6ef314ae8ba ("perf: Extend PERF_TYPE_HARDWARE and PERF_TYPE_HW_CACHE")
>
Oh, the perf/core mentioned here just means the "perf/core" from acme/linux.git. Sorry, I didn't say
this clearly. I guess it will be merged to acme/linux.git at some window.
> And your patch, the one below, shouldn't include the kernel file, i.e. include/uapi/linux/perf_event.h
> as tooling only uses the one in tools/include/uapi/linux/perf_event.h.
>
Yes, my fault. I only need to update the tools/include/uapi/linux/perf_event.h. You have helped me
to update the commit 7ad6382ef375 ("tools headers uapi: Update tools's copy of linux/perf_event.h")
in tmp.perf/core. Thanks so much!
> Leave the perf tool build warning there, as soon as both acme/perf/core
> and tip/perf/core hit torvalds/master, all gets solved.
>
> So I'm removing it here in addition to updating the commit log message.
>
Thanks again!
> Ah good news, the test builds passed in all my test build containers.
>
Great! :)
> I'll refresh tmp.perf/core once I update these messages, etc. So that we
> can continue from there in case you need to respin a v7.
>
I've seen the patches have been applied in tmp.perf/core now, thanks! If we need v7, we can continue
from tmp.perf/core.
Thanks
Jin Yao
> Thanks,
>
> - Arnaldo.
>
>
>
>> Signed-off-by: Jin Yao <yao.jin@linux.intel.com>
>> ---
>> v6:
>> - No update.
>>
>> v5:
>> - Update the commit message to mention that Kan's patch is
>> upstreamed but not merged to perf/core branch.
>>
>> v4:
>> - Updated by Kan's latest patch,
>> '[PATCH V6 21/25] perf: Extend PERF_TYPE_HARDWARE and PERF_TYPE_HW_CACHE'
>>
>> include/uapi/linux/perf_event.h | 15 +++++++++++++++
>> tools/include/uapi/linux/perf_event.h | 15 +++++++++++++++
>> 2 files changed, 30 insertions(+)
>>
>> diff --git a/include/uapi/linux/perf_event.h b/include/uapi/linux/perf_event.h
>> index ad15e40d7f5d..14332f4cf816 100644
>> --- a/include/uapi/linux/perf_event.h
>> +++ b/include/uapi/linux/perf_event.h
>> @@ -37,6 +37,21 @@ enum perf_type_id {
>> PERF_TYPE_MAX, /* non-ABI */
>> };
>>
>> +/*
>> + * attr.config layout for type PERF_TYPE_HARDWARE and PERF_TYPE_HW_CACHE
>> + * PERF_TYPE_HARDWARE: 0xEEEEEEEE000000AA
>> + * AA: hardware event ID
>> + * EEEEEEEE: PMU type ID
>> + * PERF_TYPE_HW_CACHE: 0xEEEEEEEE00DDCCBB
>> + * BB: hardware cache ID
>> + * CC: hardware cache op ID
>> + * DD: hardware cache op result ID
>> + * EEEEEEEE: PMU type ID
>> + * If the PMU type ID is 0, the PERF_TYPE_RAW will be applied.
>> + */
>> +#define PERF_PMU_TYPE_SHIFT 32
>> +#define PERF_HW_EVENT_MASK 0xffffffff
>> +
>> /*
>> * Generalized performance event event_id types, used by the
>> * attr.event_id parameter of the sys_perf_event_open()
>> diff --git a/tools/include/uapi/linux/perf_event.h b/tools/include/uapi/linux/perf_event.h
>> index ad15e40d7f5d..14332f4cf816 100644
>> --- a/tools/include/uapi/linux/perf_event.h
>> +++ b/tools/include/uapi/linux/perf_event.h
>> @@ -37,6 +37,21 @@ enum perf_type_id {
>> PERF_TYPE_MAX, /* non-ABI */
>> };
>>
>> +/*
>> + * attr.config layout for type PERF_TYPE_HARDWARE and PERF_TYPE_HW_CACHE
>> + * PERF_TYPE_HARDWARE: 0xEEEEEEEE000000AA
>> + * AA: hardware event ID
>> + * EEEEEEEE: PMU type ID
>> + * PERF_TYPE_HW_CACHE: 0xEEEEEEEE00DDCCBB
>> + * BB: hardware cache ID
>> + * CC: hardware cache op ID
>> + * DD: hardware cache op result ID
>> + * EEEEEEEE: PMU type ID
>> + * If the PMU type ID is 0, the PERF_TYPE_RAW will be applied.
>> + */
>> +#define PERF_PMU_TYPE_SHIFT 32
>> +#define PERF_HW_EVENT_MASK 0xffffffff
>> +
>> /*
>> * Generalized performance event event_id types, used by the
>> * attr.event_id parameter of the sys_perf_event_open()
>> --
>> 2.17.1
>>
>
next prev parent reply other threads:[~2021-04-28 1:18 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 7:01 [PATCH v6 00/26] perf tool: AlderLake hybrid support series 1 Jin Yao
2021-04-27 7:01 ` [PATCH v6 01/26] tools headers uapi: Update tools's copy of linux/perf_event.h Jin Yao
2021-04-27 19:24 ` Arnaldo Carvalho de Melo
2021-04-28 1:18 ` Jin, Yao [this message]
2021-04-27 7:01 ` [PATCH v6 02/26] perf jevents: Support unit value "cpu_core" and "cpu_atom" Jin Yao
2021-04-27 7:01 ` [PATCH v6 03/26] perf pmu: Simplify arguments of __perf_pmu__new_alias Jin Yao
2021-04-27 7:01 ` [PATCH v6 04/26] perf pmu: Save pmu name Jin Yao
2021-04-27 7:01 ` [PATCH v6 05/26] perf pmu: Save detected hybrid pmus to a global pmu list Jin Yao
2021-04-27 7:01 ` [PATCH v6 06/26] perf pmu: Add hybrid helper functions Jin Yao
2021-04-27 7:01 ` [PATCH v6 07/26] perf stat: Uniquify hybrid event name Jin Yao
2021-04-27 7:01 ` [PATCH v6 08/26] perf parse-events: Create two hybrid hardware events Jin Yao
2021-04-27 7:01 ` [PATCH v6 09/26] perf parse-events: Create two hybrid cache events Jin Yao
2021-04-27 7:01 ` [PATCH v6 10/26] perf parse-events: Create two hybrid raw events Jin Yao
2021-04-27 7:01 ` [PATCH v6 11/26] perf parse-events: Compare with hybrid pmu name Jin Yao
2021-04-27 7:01 ` [PATCH v6 12/26] perf parse-events: Support event inside hybrid pmu Jin Yao
2021-04-27 7:01 ` [PATCH v6 13/26] perf record: Create two hybrid 'cycles' events by default Jin Yao
2021-04-27 7:01 ` [PATCH v6 14/26] perf stat: Add default hybrid events Jin Yao
2021-04-27 7:01 ` [PATCH v6 15/26] perf stat: Filter out unmatched aggregation for hybrid event Jin Yao
2021-04-27 7:01 ` [PATCH v6 16/26] perf stat: Warn group events from different hybrid PMU Jin Yao
2021-04-27 7:01 ` [PATCH v6 17/26] perf record: Uniquify hybrid event name Jin Yao
2021-04-27 7:01 ` [PATCH v6 18/26] perf tests: Add hybrid cases for 'Parse event definition strings' test Jin Yao
2021-04-27 7:01 ` [PATCH v6 19/26] perf tests: Add hybrid cases for 'Roundtrip evsel->name' test Jin Yao
2021-04-27 7:01 ` [PATCH v6 20/26] perf tests: Skip 'Setup struct perf_event_attr' test for hybrid Jin Yao
2021-04-27 7:01 ` [PATCH v6 21/26] perf tests: Support 'Track with sched_switch' " Jin Yao
2021-04-27 7:01 ` [PATCH v6 22/26] perf tests: Support 'Parse and process metrics' " Jin Yao
2021-04-27 7:01 ` [PATCH v6 23/26] perf tests: Support 'Session topology' " Jin Yao
2021-04-27 7:01 ` [PATCH v6 24/26] perf tests: Support 'Convert perf time to TSC' " Jin Yao
2021-04-27 7:01 ` [PATCH v6 25/26] perf tests: Skip 'perf stat metrics (shadow stat) test' " Jin Yao
2021-04-27 7:01 ` [PATCH v6 26/26] perf Documentation: Document intel-hybrid support Jin Yao
2021-04-27 12:50 ` [PATCH v6 00/26] perf tool: AlderLake hybrid support series 1 Jiri Olsa
2021-04-27 13:14 ` Arnaldo Carvalho de Melo
2021-04-28 1:57 ` Jin, Yao
2021-04-28 7:28 ` Jiri Olsa
2021-04-28 8:01 ` Jin, Yao
2021-04-28 13:44 ` 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=e6bc62d5-50e8-15cf-915f-de15b3d7b860@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=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