The doc comment for the instrument mentions the option to select the
trace_cmd_mode ('start' or 'record'). As far as I can tell this was
never implemented. This commit adds the support for passing
trace_cmd_mode to the FtraceCollector in devlib.
While at it, it also does some slight cleanup aronud the instrument,
e.g. in the teardown() implementation which should be folded
inside the collector instead of reimplemented here.
Signed-off-by: Kajetan Puchalski <kajetan.puchalski@arm.com>
Allow optionally setting the top level ftrace buffer size separately
from the devlib buffer size. The parameter will be passed to the devlib
FtraceCollector and take effect there.
Signed-off-by: Kajetan Puchalski <kajetan.puchalski@arm.com>
- Add copyright headers to files that did not already have them
- Update the year to the last year the file was modified in files with
existing headers.
Extracting trace and pulling the trace file from the target can take a
relatively long time, as the trace file can be tens, and even hundreds,
of MB. Add an info-level log message to inform the user why WA execution
appears to have paused for a few seconds.
Both the instrument and utility functions were called `trace-cmd.py`.
`"-"`'s are not valid python identifiers therefore when trying to import
the `trace-cmd` module this causes an error.
