Messages in this thread | | | Date | Thu, 5 Dec 2013 18:54:49 -0500 | Subject | Re: [PATCH 0/3] ARM Coresight: Enhance ETM tracing control | From | Adrien Vergé <> |
| |
Hi Greg and Christopher,
Thank you for your feedback.
2013/12/4 Greg Kroah-Hartman <gregkh@linuxfoundation.org> > What is it's purpose then? At first glance, this seems to be exactly > what 'perf' provides already. Doesn't perf work on ARM today?
On ARM, perf is unable to trace every instruction, and certainly not recording the number of cycles taken by every of them. Also, ETM is not just tracing the execution flow. It can trace data, trigger tracing on events such as address matching, data matching, context ID change, monitor CPRT... It would be sad not to use these capabilities.
If we want perf to use ETM's full functionality, its framework clearly needs to be extended. Future Intel processors will embed Processor Trace [1], which seems to have similar capabilities as ETM on ARM. At that point, it will be easier to decide what should be in the kernel or in perf.
I the meantime, while ETM is not supported elsewhere than in sysfs, it should at least be configurable. The current implementation is almost not usable.
> Well, these patches were incorrect, so that's not really a valid > question :)
Should I correct the pid size and send them again?
Thanks,
Adrien
[1]: http://software.intel.com/en-us/blogs/2013/09/18/processor-tracing
| |