mirror of
https://github.com/ARM-software/workload-automation.git
synced 2025-06-24 17:26:05 +01:00
dev_scripts
doc
source
_static
_templates
additional_topics.rst
agenda.rst
changes.rst
conf.py
configuration.rst
contributing.rst
conventions.rst
daq-wiring.png
daq_device_setup.rst
device_setup.rst
execution_model.rst
index.rst
installation.rst
instrumentation_method_map.rst
instrumentation_method_map.template
invocation.rst
quickstart.rst
resources.rst
revent.rst
wa-execution.png
writing_extensions.rst
Makefile
build_extension_docs.py
build_instrumentation_method_map.py
extras
scripts
wlauto
.gitignore
LICENSE
MANIFEST.in
README.rst
setup.py
18 lines
768 B
Plaintext
18 lines
768 B
Plaintext
Instrumentation Signal-Method Mapping
|
|
=====================================
|
|
|
|
.. _instrumentation_method_map:
|
|
|
|
Instrument methods get automatically hooked up to signals based on their names. Mostly, the method
|
|
name correponds to the name of the signal, however there are a few convienience aliases defined
|
|
(listed first) to make easier to relate instrumenation code to the workload execution model.
|
|
|
|
$signal_names
|
|
|
|
The names above may be prefixed with one of pre-defined prefixes to set the priority of the
|
|
Instrument method realive to other callbacks registered for the signal (within the same priority
|
|
level, callbacks are invoked in the order they were registered). The table below shows the mapping
|
|
of the prifix to the corresponding priority:
|
|
|
|
$priority_prefixes
|