On 07/11/2023 07:19, Adrian Hunter wrote:
On 6/11/23 23:52, Arnaldo Carvalho de Melo wrote:
Em Thu, Oct 19, 2023 at 01:47:15PM +0300, Adrian Hunter escreveu:
On 14/10/23 10:45, Leo Yan wrote:
An AUX trace can contain timestamp, but in some situations, the hardware trace module (e.g. Arm CoreSight) cannot decide the traced timestamp is the same source with CPU's time, thus the decoder can not use the timestamp trace for samples.
This patch introduces 'T' itrace option. If users know the platforms
"If users know" <- how would users know? Could the kernel or tools also figure it out?
Adrian, I'm trying to go all the outstanding patches, do you still have any issues with this series?
No, although the question wasn't actually answered. I presume users just have to try the 'T' option and see if it helps.
I suppose my previous answer about discoverability was more general. To answer the specific question "how would users know?", it would have to be mentioned in the reference manual of their device that this is how the timers are set up.
But I don't see this being a common use case, as I mentioned before, in newer arm platforms this is discoverable and just works.
-
James Clark