[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44e87647-d64e-ee24-0046-06bb15f5a1f4@arm.com>
Date: Fri, 6 Jan 2023 09:54:23 +0000
From: Suzuki K Poulose <suzuki.poulose@....com>
To: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
linux-perf-users@...r.kernel.org,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>
Cc: mathieu.poirier@...aro.org, leo.yan@...aro.org,
quic_jinlmao@...cinc.com, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, coresight@...ts.linaro.org,
Mike Leach <mike.leach@...aro.org>,
Adrian Hunter <adrian.hunter@...el.com>
Subject: Re: [PATCH v6 11/14] kernel: events: Export
perf_report_aux_output_id()
Peter, Ingo, Arnaldo
On 13/12/2022 10:08, Suzuki K Poulose wrote:
> Peter,
>
> On 24/11/2022 11:04, Suzuki Kuruppassery Poulose wrote:
>> Peter
>>
>>
>> On 23/11/2022 19:50, Mike Leach wrote:
>>> CoreSight trace being updated to use the perf_report_aux_output_id()
>>> in a similar way to intel-pt.
>>>
>>> This function in needs export visibility to allow it to be called from
>>> kernel loadable modules, which CoreSight may configured to be built as.
>>>
>>> Signed-off-by: Mike Leach <mike.leach@...aro.org>
>>> Acked-by: Suzuki K Poulose <suzuki.poulose@....com>
>>> ---
>>> kernel/events/core.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/kernel/events/core.c b/kernel/events/core.c
>>> index 4ec3717003d5..ad388552f1d5 100644
>>> --- a/kernel/events/core.c
>>> +++ b/kernel/events/core.c
>>> @@ -9231,6 +9231,7 @@ void perf_report_aux_output_id(struct
>>> perf_event *event, u64 hw_id)
>>> perf_output_end(&handle);
>>> }
>>> +EXPORT_SYMBOL_GPL(perf_report_aux_output_id);
>>
>> Are you happy with me picking up this change through the coresight
>> tree ?
>>
>> Suzuki
>>
>
> Please could you let me know your thoughts on this ? Coresight PMU would
> use this to inform the dynamically allocated trace id for a CPU to the
> perf via this HWID packet.
>
> If you are happy with the above change, I could pick it up via the
> coresight tree with your Ack. Otherwise, please could you pick it
> up ?
>
Please could you let us know if this is acceptable and if so, how can
this be pushed ? CoreSight PMU (which can be built as a module) is using
these packets to advertise the traceID allocated for a given CPU bound
ETM (which is made dynamic due to the limited number of ids available).
The perf tool can use these packets to then decode and separate the
trace data from shared buffer.
As of now, the series to enable the dynamic trace id allocation is
blocked on this change.
Kind regards
Suzuki
> Suzuki
>
Powered by blists - more mailing lists