From: James Clark <james.clark@arm.com>
To: Mike Leach <mike.leach@linaro.org>
Cc: mathieu.poirier@linaro.org, peterz@infradead.org,
mingo@redhat.com, acme@kernel.org,
linux-perf-users@vger.kernel.org, quic_jinlmao@quicinc.com,
suzuki.poulose@arm.com, coresight@lists.linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 09/13] perf: cs-etm: Update record event to use new Trace ID protocol
Date: Tue, 23 Aug 2022 10:11:01 +0100 [thread overview]
Message-ID: <35d01f5c-6167-497a-ddb9-5882025cc42b@arm.com> (raw)
In-Reply-To: <CAJ9a7Vi63XxDXtT8KD2-3=n5+de6_ZfD+X=jtPK+puM7f4koNw@mail.gmail.com>
On 09/08/2022 17:13, Mike Leach wrote:
> Hi James
>
> On Wed, 20 Jul 2022 at 15:41, James Clark <james.clark@arm.com> wrote:
>>
>>
>>
>> On 04/07/2022 09:11, Mike Leach wrote:
>>> Trace IDs are now dynamically allocated.
>>>
>>> Previously used the static association algorithm that is no longer
>>> used. The 'cpu * 2 + seed' was outdated and broken for systems with high
>>> core counts (>46). as it did not scale and was broken for larger
>>> core counts.
>>>
>>> Trace ID is as unknown in AUXINFO record, and the ID / CPU association
>>> will now be sent in PERF_RECORD_AUX_OUTPUT_HW_ID record.
>>>
>>> Remove legacy Trace ID allocation algorithm.
>>>
>>> Signed-off-by: Mike Leach <mike.leach@linaro.org>
>>> ---
>>> include/linux/coresight-pmu.h | 19 +++++++------------
>>> tools/include/linux/coresight-pmu.h | 19 +++++++------------
>>
>> I usually see mentions that these header updates need to be separate commits
>> because they are merged through different trees.
>>
>>> tools/perf/arch/arm/util/cs-etm.c | 21 ++++++++++++---------
>>> 3 files changed, 26 insertions(+), 33 deletions(-)
>>>
>>> diff --git a/include/linux/coresight-pmu.h b/include/linux/coresight-pmu.h
>>> index 4ac5c081af93..9f7ee380266b 100644
>>> --- a/include/linux/coresight-pmu.h
>>> +++ b/include/linux/coresight-pmu.h
>>> @@ -8,7 +8,13 @@
>>> #define _LINUX_CORESIGHT_PMU_H
>>>
>>> #define CORESIGHT_ETM_PMU_NAME "cs_etm"
>>> -#define CORESIGHT_ETM_PMU_SEED 0x10
>>> +
>>> +/*
>>> + * Metadata now contains an unused trace ID - IDs are transmitted using a
>>> + * PERF_RECORD_AUX_OUTPUT_HW_ID record.
>>> + * Value architecturally defined as reserved in CoreSight.
>>> + */
>>> +#define CS_UNUSED_TRACE_ID 0x7F
>>>
>>> /*
>>> * Below are the definition of bit offsets for perf option, and works as
>>> @@ -32,15 +38,4 @@
>>> #define ETM4_CFG_BIT_RETSTK 12
>>> #define ETM4_CFG_BIT_VMID_OPT 15
>>>
>>> -static inline int coresight_get_trace_id(int cpu)
>>> -{
>>> - /*
>>> - * A trace ID of value 0 is invalid, so let's start at some
>>> - * random value that fits in 7 bits and go from there. Since
>>> - * the common convention is to have data trace IDs be I(N) + 1,
>>> - * set instruction trace IDs as a function of the CPU number.
>>> - */
>>> - return (CORESIGHT_ETM_PMU_SEED + (cpu * 2));
>>> -}
>>> -
>>> #endif
>>> diff --git a/tools/include/linux/coresight-pmu.h b/tools/include/linux/coresight-pmu.h
>>> index 6c2fd6cc5a98..31d007fab3a6 100644
>>> --- a/tools/include/linux/coresight-pmu.h
>>> +++ b/tools/include/linux/coresight-pmu.h
>>> @@ -8,7 +8,13 @@
>>> #define _LINUX_CORESIGHT_PMU_H
>>>
>>> #define CORESIGHT_ETM_PMU_NAME "cs_etm"
>>> -#define CORESIGHT_ETM_PMU_SEED 0x10
>>> +
>>> +/*
>>> + * Metadata now contains an unused trace ID - IDs are transmitted using a
>>> + * PERF_RECORD_AUX_OUTPUT_HW_ID record.
>>> + * Value architecturally defined as reserved in CoreSight.
>>> + */
>>> +#define CS_UNUSED_TRACE_ID 0x7F
>>>
>>
>> minor nit: this isn't used in the kernel so only needs to be defined on the
>> tools side.
>>
>
> Unfortunately if the two versions of coresight-pmu.h are different,
> the build process for perf throws out a warning. So they have to be
> identical.
I was thinking more along the lines of putting it in a header that is
only present on the perf side, rather than only having it in one version
of a shared header.
>
> Thanks
>
> Mike
>
>>> /*
>>> * Below are the definition of bit offsets for perf option, and works as
>>> @@ -34,15 +40,4 @@
>>> #define ETM4_CFG_BIT_RETSTK 12
>>> #define ETM4_CFG_BIT_VMID_OPT 15
>>>
>>> -static inline int coresight_get_trace_id(int cpu)
>>> -{
>>> - /*
>>> - * A trace ID of value 0 is invalid, so let's start at some
>>> - * random value that fits in 7 bits and go from there. Since
>>> - * the common convention is to have data trace IDs be I(N) + 1,
>>> - * set instruction trace IDs as a function of the CPU number.
>>> - */
>>> - return (CORESIGHT_ETM_PMU_SEED + (cpu * 2));
>>> -}
>>> -
>>> #endif
>>> diff --git a/tools/perf/arch/arm/util/cs-etm.c b/tools/perf/arch/arm/util/cs-etm.c
>>> index 1b54638d53b0..2d68e6a722ed 100644
>>> --- a/tools/perf/arch/arm/util/cs-etm.c
>>> +++ b/tools/perf/arch/arm/util/cs-etm.c
>>> @@ -421,13 +421,16 @@ static int cs_etm_recording_options(struct auxtrace_record *itr,
>>> evlist__to_front(evlist, cs_etm_evsel);
>>>
>>> /*
>>> - * In the case of per-cpu mmaps, we need the CPU on the
>>> - * AUX event. We also need the contextID in order to be notified
>>> + * get the CPU on the sample - need it to associate trace ID in the
>>> + * AUX_OUTPUT_HW_ID event, and the AUX event for per-cpu mmaps.
>>> + */
>>> + evsel__set_sample_bit(cs_etm_evsel, CPU);
>>> +
>>> + /*
>>> + * Also the case of per-cpu mmaps, need the contextID in order to be notified
>>> * when a context switch happened.
>>> */
>>> if (!perf_cpu_map__empty(cpus)) {
>>> - evsel__set_sample_bit(cs_etm_evsel, CPU);
>>> -
>>> err = cs_etm_set_option(itr, cs_etm_evsel,
>>> BIT(ETM_OPT_CTXTID) | BIT(ETM_OPT_TS));
>>> if (err)
>>> @@ -633,8 +636,9 @@ static void cs_etm_save_etmv4_header(__u64 data[], struct auxtrace_record *itr,
>>>
>>> /* Get trace configuration register */
>>> data[CS_ETMV4_TRCCONFIGR] = cs_etmv4_get_config(itr);
>>> - /* Get traceID from the framework */
>>> - data[CS_ETMV4_TRCTRACEIDR] = coresight_get_trace_id(cpu);
>>> + /* traceID set to unused */
>>> + data[CS_ETMV4_TRCTRACEIDR] = CS_UNUSED_TRACE_ID;
>>> +
>>> /* Get read-only information from sysFS */
>>> data[CS_ETMV4_TRCIDR0] = cs_etm_get_ro(cs_etm_pmu, cpu,
>>> metadata_etmv4_ro[CS_ETMV4_TRCIDR0]);
>>> @@ -681,9 +685,8 @@ static void cs_etm_get_metadata(int cpu, u32 *offset,
>>> magic = __perf_cs_etmv3_magic;
>>> /* Get configuration register */
>>> info->priv[*offset + CS_ETM_ETMCR] = cs_etm_get_config(itr);
>>> - /* Get traceID from the framework */
>>> - info->priv[*offset + CS_ETM_ETMTRACEIDR] =
>>> - coresight_get_trace_id(cpu);
>>> + /* traceID set to unused */
>>> + info->priv[*offset + CS_ETM_ETMTRACEIDR] = CS_UNUSED_TRACE_ID;
>>> /* Get read-only information from sysFS */
>>> info->priv[*offset + CS_ETM_ETMCCER] =
>>> cs_etm_get_ro(cs_etm_pmu, cpu,
>
>
>
next prev parent reply other threads:[~2022-08-23 10:53 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 8:11 [PATCH v2 00/13] coresight: Add new API to allocate trace source ID values Mike Leach
2022-07-04 8:11 ` [PATCH v2 01/13] coresight: trace-id: Add API to dynamically assign Trace " Mike Leach
2022-07-19 17:30 ` Suzuki K Poulose
2022-08-09 16:11 ` Mike Leach
2022-07-04 8:11 ` [PATCH v2 02/13] coresight: trace-id: update CoreSight core to use Trace ID API Mike Leach
2022-07-19 17:36 ` Suzuki K Poulose
2022-07-04 8:11 ` [PATCH v2 03/13] coresight: stm: Update STM driver " Mike Leach
2022-07-19 17:51 ` Suzuki K Poulose
2022-07-04 8:11 ` [PATCH v2 04/13] coresight: etm4x: Update ETM4 " Mike Leach
2022-07-19 21:41 ` Suzuki K Poulose
2022-07-04 8:11 ` [PATCH v2 05/13] coresight: etm3x: Update ETM3 " Mike Leach
2022-07-19 21:45 ` Suzuki K Poulose
2022-07-04 8:11 ` [PATCH v2 06/13] coresight: etmX.X: stm: Remove unused legacy source Trace ID ops Mike Leach
2022-07-19 21:47 ` Suzuki K Poulose
2022-07-04 8:11 ` [PATCH v2 07/13] coresight: perf: traceid: Add perf notifiers for Trace ID Mike Leach
2022-07-19 21:49 ` Suzuki K Poulose
2022-07-04 8:11 ` [PATCH v2 08/13] perf: cs-etm: Move mapping of Trace ID and cpu into helper function Mike Leach
2022-07-19 14:54 ` James Clark
2022-07-20 10:22 ` Mike Leach
2022-07-20 12:57 ` James Clark
2022-07-20 16:19 ` Arnaldo Carvalho de Melo
2022-07-04 8:11 ` [PATCH v2 09/13] perf: cs-etm: Update record event to use new Trace ID protocol Mike Leach
2022-07-20 14:41 ` James Clark
2022-08-09 16:13 ` Mike Leach
2022-08-09 16:19 ` Arnaldo Carvalho de Melo
2022-08-23 9:11 ` James Clark [this message]
2022-07-04 8:11 ` [PATCH v2 10/13] kernel: events: Export perf_report_aux_output_id() Mike Leach
2022-07-19 21:50 ` Suzuki K Poulose
2022-07-04 8:11 ` [PATCH v2 11/13] perf: cs-etm: Handle PERF_RECORD_AUX_OUTPUT_HW_ID packet Mike Leach
2022-07-20 16:07 ` James Clark
2022-07-21 12:38 ` Mike Leach
2022-07-22 9:30 ` James Clark
2022-07-04 8:11 ` [PATCH v2 12/13] coresight: events: PERF_RECORD_AUX_OUTPUT_HW_ID used for Trace ID Mike Leach
2022-07-20 9:30 ` Suzuki K Poulose
2022-07-20 10:53 ` Mike Leach
2022-07-04 8:11 ` [PATCH v2 13/13] coresight: trace-id: Add debug & test macros to Trace ID allocation Mike Leach
2022-07-20 9:41 ` Suzuki K Poulose
2022-07-21 10:27 ` [PATCH v2 00/13] coresight: Add new API to allocate trace source ID values James Clark
2022-07-21 13:54 ` Mike Leach
2022-07-22 12:10 ` James Clark
2022-07-25 8:19 ` Mike Leach
2022-07-26 13:53 ` James Clark
2022-07-26 14:57 ` Mike Leach
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=35d01f5c-6167-497a-ddb9-5882025cc42b@arm.com \
--to=james.clark@arm.com \
--cc=acme@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=quic_jinlmao@quicinc.com \
--cc=suzuki.poulose@arm.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
all inboxes | Powered by JetHome®