From d012e3e4bd444063e2a506ee781fb2e7be149e01 Mon Sep 17 00:00:00 2001 From: Ulf Hermann Date: Mon, 31 Oct 2016 14:23:05 +0100 Subject: [PATCH] Clarify section about broken performance counters on i.MX6 The performance counters are broken on most (all?) i.MX6 boards, not only on the ones from Boundary Devices. Task-number: QTBUG-56769 Change-Id: I9e0f291be7e00df3d9d1b98c7414dfd37e265b39 Reviewed-by: Kari Hormi Reviewed-by: Leena Miettinen --- doc/src/analyze/cpu-usage-analyzer.qdoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/src/analyze/cpu-usage-analyzer.qdoc b/doc/src/analyze/cpu-usage-analyzer.qdoc index 873abff8c08..dddea53102f 100644 --- a/doc/src/analyze/cpu-usage-analyzer.qdoc +++ b/doc/src/analyze/cpu-usage-analyzer.qdoc @@ -346,11 +346,11 @@ \li Some versions of Perf will not start recording unless given a certain minimum sampling frequency. Try with a \uicontrol {Sampling Frequency} of 1000. - \li On some devices, for example Boundary Devices i.MX6 Boards, the - Perf support is not very stable and the Linux kernel may randomly - fail to record data after some time. Perf can use different types - of events to trigger samples. You can get a list of available event - types by running \c {perf list} on the device and add + \li On some devices, in particular various i.MX6 Boards, the hardware + performance counters are dysfunctional and the Linux kernel may + randomly fail to record data after some time. Perf can use different + types of events to trigger samples. You can get a list of available + event types by running \c {perf list} on the device and add \c {-e } to the \uicontrol {Additional arguments} field to change the event type to be used. The choice of event type affects the performance and stability of the sampling.