9d67f9fc8e
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 |
||
|---|---|---|
| .. | ||
| README | ||
| main.cc | ||
| target.mk | ||
README
This component obtains the information about the existing trace subjects from
core's "TRACE" service and shows via the LOG session the highest CPU consumer
per CPU in percentage.
Configuration
-------------
The interval of output generation can be defined via the 'period_ms' attribute
of the '<config>' node. The value is specified in milliseconds.
The threads with the top most execution time are shown per CPU. The sorting
of the execution time can be shown per thread ('ec' - execution context) or,
if supported by the kernel, per scheduling context of a thread ('sc').
The following example shows the default values.
! <config period_ms="5000" sort_time="ec"/>