genode/repos/os/src/app/trace_subject_reporter
Alexander Boettcher 463b39fc73 xml reporter: support different start node name
Currently the report name is used implicitly as first xml node name for the
report.  This is inconvenient if one component wants to generate various xml
reports under various names (e.g. to steer consumers/clients slightly
differently) but with the same xml node tree structure.

Fixes #1940
2016-05-09 13:09:54 +02:00
..
main.cc xml reporter: support different start node name 2016-05-09 13:09:54 +02:00
README Trace-subject reporter 2015-06-22 14:43:38 +02:00
target.mk Trace-subject reporter 2015-06-22 14:43:38 +02:00

This component obtains the information about the existing trace subjects from
core's "TRACE" service and delivers a report to a "Report" server. The report,
in turn, can be used by top-like applications to present the consumed execution
time per thread.

Configuration
-------------

The interval of report generation can be defined via the 'period_ms' attribute
of the '<config>' node. The value is specified in milliseconds.

The level of detail of the generated reports can be influenced by the
'<report>' sub node of the configuration. The following example shows the
default values.

! <config period_ms="5000" >
!   <report activity="no" affinity="no"/>
! </config>

When setting 'activity' to "yes", the report contains an '<activity>' sub node
for each subject. The sub node has the two attributes 'total' and 'recent'. The
'recent' value represents the execution time consumed in the last period.

When setting 'affinity' to "yes", the report contains an '<affinity>' sub node
for each subject. The sub node shows the thread's physical CPU affinity,
expressed via the 'xpos' and 'ypos' attributes.