feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

Clarify section about broken performance counters on i.MX6

Browse Source 
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 <kari.hormi@qt.io>
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
This commit is contained in:
Ulf Hermann
2016-10-31 14:23:05 +01:00
parent 4325f4facb
commit d012e3e4bd
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/analyze/cpu-usage-analyzer.qdoc
View File

@@ -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 <event type>} 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.