genode

History

Norman Feske 9d67f9fc8e Remove Allocator_guard This patch removes old 'Allocator_guard' utility and replaces its use with the modern 'Constrained_ram_allocator'. The adjustment of core in this respect has the side effect of a more accurate capability accounting in core's CPU, TRACE, and RM services. In particular, the dataspace capabilities needed for core-internal allocations via the 'Sliced_heap' are accounted to the client now. The same goes for nitpicker and nic_dump as other former users of the allocator guard. Hence, the patch also touches code at the client and server sides related to these services. The only remaining user of the 'Allocator_guard' is the Intel GPU driver. As the adaptation of this component would be too invasive without testing, this patch leaves this component unchanged by keeping a copy of the 'allocator_guard.h' locally at the component. Fixes #3750		2020-05-18 10:16:12 +02:00
..
README	Trace-subject reporter	2015-06-22 14:43:38 +02:00
main.cc	Remove Allocator_guard	2020-05-18 10:16:12 +02:00
target.mk	Deprecate Genode::config()	2017-01-13 13:06:54 +01:00

README

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.