History log of /external/lisa/libs/utils/__init__.py
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
e77ae1847a37c6da74c0aaf4384214c8bb2ab260 25-Jan-2017 Patrick Bellasi <patrick.bellasi@arm.com> utils/android/workloads: move workloads loading at module initialisation

This "seems" to be required to make workloads plugins visible from
external python scripts.

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
/external/lisa/libs/utils/__init__.py
c278c2343c7f25083a80cb164b6bdc761d50050b 22-Nov-2016 Patrick Bellasi <patrick.bellasi@arm.com> libs: use a more configurable logging strategy

This is a big re-factoring which update all the logging statements to make
use of a more sane and consistent configuration:

- each module uses the same logger configuration but refers to a custom
logger which has the same name of the module, this should allows a
fine grained configuration of the loglevels for each module.

- a new libs/utils/conf.py::LisaLogging class allows to load the
configuration and customize the root logger level.

- loggers are configured using a single logfile (logging.conf) which is
provided by default in the LISA's root folder.

Each logger can be configured to specify:
- loglevel: INFO by default for all modules
- output channels: console and logfile (lisa.log by default) for all modules
- string format: the same by default for all modules

If logging.conf does not specify a specific configuration for a logger, than
the default logger configuration applies, which is the one defined by the
"root" logger.

Notebooks and LisaTest are required to call at least one time the
LisaLogging::setup() method to properly intialize logging.

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
/external/lisa/libs/utils/__init__.py
eca5c66709821e9c9447bfeeb34325625b94f7d4 25-Jul-2016 Patrick Bellasi <patrick.bellasi@arm.com> libs/utils/analysis: move filters APIs into TASKs module

All the functions defined from libs/utils/filters.py, in the new refactoring
of the TraceAnalysis code, they better belong to the tasks_analysis module.
Let's move this code under this module as well as refactor a big the
DataFrame getter methods to return a more complete set of tables.

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
/external/lisa/libs/utils/__init__.py
ed84c9525d40e2f35e424f3b7cd839a322d865ca 22-Jul-2016 Patrick Bellasi <patrick.bellasi@arm.com> libs/utils/trace_analysis: remove useless original module

The AnalysisRegister module provides now a support to dynamically register
all the trace analysis module available under the libs/utils/analysis folder.

The code originally part of libs/utils/trace_analysis.py has been moved
into a set of new AnalysisModules. Thus, this patch get rides of the not more
used original trace_analysis.py file.

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
/external/lisa/libs/utils/__init__.py
6721d173e18d3c56a33fd3f2eb9b50acd675ec27 22-Jul-2016 Patrick Bellasi <patrick.bellasi@arm.com> libs/utils/analysis: add base support to register trace analysis modules

A TraceModule is a LISA module which can:
a) expose new DataFrame getters
b) expose analysis functions to report/plot DataFrame data

This patch adds the basic support to add new TraceAnalysis modules which
can now be added by simply:
1) creating a new module under libs/utils/analysis
2) derive the top level class from AnalysisModule
3) prefix with "_dfg_" all its methods which generated a DataFrame

The AnalysisRegister class provides the run-time support to register
all the available trace analysis module, which are available as attributes
of this class with a name derived from the module filename.

For example:
libs/utils/analysis/frequency_analysis.py
will be registered as:
AnalysisRegister::frequency

The Trace module initialize and keep track of the AnalysisRegister in its
"analysis" attribute. Thus for example the previous module can be accessed
using:

trace = Trace(platform, trace_dir)
trace.analysis.frequency.plotClusterFrequencies()

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
/external/lisa/libs/utils/__init__.py
19477157cbabd28f6c132a28b1c7716658445589 10-May-2016 Patrick Bellasi <patrick.bellasi@arm.com> libs/utils/android: Add Screen control class

When working on an Android target, some experiments requires to properly
setup some components, especially to reduce variations on energy
consumptions. The screen is one of the most energy consuming componets.

This patch adds a Screen module which exposes some of the most common
operations to tune the Screen settings of an Android target.

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
/external/lisa/libs/utils/__init__.py
ce73ce0f78dec8da6daa7c1355b1da988f39790d 05-Feb-2016 Patrick Bellasi <patrick.bellasi@arm.com> libs/utils/executor: add a generic tests execution engine

A tests executor is a module which support the execution of a
configured set of experiments. Each experiment is composed by:
- a target configuration
- a worload to execute

The executor module can be configured to run a set of workloads
(wloads) in each different target configuration of a specified set
(confs). These wloads and confs can be specified by the "tests_config"
input dictionary.

All the results generated by each experiment will be collected a result
folder which is named according to this template:
results/<test_id>/<wltype>:<conf>:<wload>/<run_id>
where:
- <test_id> : the "tid" defined by the tests_config, or a timestamp
based folder in case "tid" is not specified
- <wltype> : the class of workload executed, e.g. rtapp or sched_perf
- <conf> : the identifier of one of the specified configurations
- <wload> : the identified of one of the specified workload
- <run_id> : the progressive execution number from 1 up to the
specified iterations

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
/external/lisa/libs/utils/__init__.py
d95e98d88a6cf4347853427dc4ef6fd0222a3881 04-Dec-2015 Patrick Bellasi <patrick.bellasi@arm.com> Add proper copyright headers to all the contributed sources

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
/external/lisa/libs/utils/__init__.py
3f169475d4849a2a9bc43583e0bdb2cf267b4c33 16-Nov-2015 Patrick Bellasi <patrick.bellasi@arm.com> libs: fix typo in trace_analysis import

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
/external/lisa/libs/utils/__init__.py
828cde6ded040fc089fe81803c6b2c2e0d428e4c 13-Nov-2015 Patrick Bellasi <patrick.bellasi@arm.com> libs: remove all external dependencies

External dependency libraries (i.e. devlib, trappy and bart) are now
expected to be installed via pip install.

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
/external/lisa/libs/utils/__init__.py
fbfa96dae9da9899bd7aac36ca3ef376e7bcf4fe 05-Nov-2015 Patrick Bellasi <patrick.bellasi@arm.com> libs/utils/env: add a test environment class

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
/external/lisa/libs/utils/__init__.py
eb467dfa2d71d93ef7c5fc2b7562a3f2286d89cd 05-Nov-2015 Patrick Bellasi <patrick.bellasi@arm.com> libs/utils/conf: add a simple JSON parser which support comments

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
/external/lisa/libs/utils/__init__.py
16d94fb008126d4c1957c07ee1a8138ea1d12e43 05-Nov-2015 Patrick Bellasi <patrick.bellasi@arm.com> libs/utils/energy: add energy meter factory class

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
/external/lisa/libs/utils/__init__.py
833b2312b5b101aef8d519580b806a4482f26203 22-Oct-2015 Patrick Bellasi <patrick.bellasi@arm.com> libs/utils/trace_analysis: add trace analysis plots

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
/external/lisa/libs/utils/__init__.py
583c618c681c9b336c00510ab56db18001a19827 21-Oct-2015 Patrick Bellasi <patrick.bellasi@arm.com> libs/utils/perf_analysis: add RTApp performance analysis plots

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
/external/lisa/libs/utils/__init__.py
1e56382fe175078251fda15f9b831b0bf04e8a74 12-Oct-2015 Patrick Bellasi <patrick.bellasi@arm.com> utils/report: properly initialize the reporting module

Signed-off-by: Patrick Bellasi <patrick.bellasi@arm.com>
/external/lisa/libs/utils/__init__.py