Patrick Bellasi a7cfd28bd0 ftrace: force report CPU frequencies at trace start and stop ...

When the cpufreq module is loaded, quite likely we want to run experiments
which involve an analysis of frequencies transitions. However, if during
an experiment there are not cpu_frequency events, the generated trace
does not allows to know at which frequency the experiment has been executed.
This happens for example when we are running at constant frequency or just
because the workload is not generating a variable capacity request in the
system.

This path ensure the a "cpu_frequency" events is always generated at the
beginning and at the end of a collected trace. This support is required
for example to properly plot CPUs frequencies event when there are not
CPUFreq generated changes of OPP.

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>

2015-11-16 17:47:58 +00:00

..

bin

devlib initial commit.

2015-10-09 09:30:04 +01:00

instrument

devlib initial commit.

2015-10-09 09:30:04 +01:00

module

cpufreq: add method to trace current frequencies

2015-11-16 17:47:58 +00:00

platform

devlib initial commit.

2015-10-09 09:30:04 +01:00

trace

ftrace: force report CPU frequencies at trace start and stop

2015-11-16 17:47:58 +00:00

utils

ssh: disable commands echo

2015-11-10 18:30:48 +00:00

__init__.py

devlib initial commit.

2015-10-09 09:30:04 +01:00

exception.py

devlib initial commit.

2015-10-09 09:30:04 +01:00

host.py

devlib initial commit.

2015-10-09 09:30:04 +01:00

target.py

target: fix 'bl' module initialisation

2015-10-12 18:35:29 +01:00