2017-02-16 17:25:59 +01:00
|
|
|
/*
|
|
|
|
|
* \brief Report configuration
|
|
|
|
|
* \author Norman Feske
|
|
|
|
|
* \date 2017-01-16
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Copyright (C) 2017 Genode Labs GmbH
|
|
|
|
|
*
|
|
|
|
|
* This file is part of the Genode OS framework, which is distributed
|
2017-02-20 13:23:52 +01:00
|
|
|
* under the terms of the GNU Affero General Public License version 3.
|
2017-02-16 17:25:59 +01:00
|
|
|
*/
|
|
|
|
|
|
2020-01-09 21:23:19 +01:00
|
|
|
#ifndef _LIB__SANDBOX__REPORT_H_
|
|
|
|
|
#define _LIB__SANDBOX__REPORT_H_
|
2017-02-16 17:25:59 +01:00
|
|
|
|
|
|
|
|
#include <util/noncopyable.h>
|
|
|
|
|
#include <util/xml_node.h>
|
|
|
|
|
|
2020-01-09 21:23:19 +01:00
|
|
|
namespace Sandbox {
|
2017-02-16 17:25:59 +01:00
|
|
|
struct Report_update_trigger;
|
|
|
|
|
struct Report_detail;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2020-01-09 21:23:19 +01:00
|
|
|
class Sandbox::Report_detail : Genode::Noncopyable
|
2017-02-16 17:25:59 +01:00
|
|
|
{
|
|
|
|
|
private:
|
|
|
|
|
|
|
|
|
|
bool _children = false;
|
|
|
|
|
bool _ids = false;
|
|
|
|
|
bool _requested = false;
|
|
|
|
|
bool _provided = false;
|
|
|
|
|
bool _session_args = false;
|
|
|
|
|
bool _child_ram = false;
|
Capability quota accounting and trading
This patch mirrors the accounting and trading scheme that Genode employs
for physical memory to the accounting of capability allocations.
Capability quotas must now be explicitly assigned to subsystems by
specifying a 'caps=<amount>' attribute to init's start nodes.
Analogously to RAM quotas, cap quotas can be traded between clients and
servers as part of the session protocol. The capability budget of each
component is maintained by the component's corresponding PD session at
core.
At the current stage, the accounting is applied to RPC capabilities,
signal-context capabilities, and dataspace capabilities. Capabilities
that are dynamically allocated via core's CPU and TRACE service are not
yet covered. Also, the capabilities allocated by resource multiplexers
outside of core (like nitpicker) must be accounted by the respective
servers, which is not covered yet.
If a component runs out of capabilities, core's PD service prints a
warning to the log. To observe the consumption of capabilities per
component in detail, the PD service is equipped with a diagnostic
mode, which can be enabled via the 'diag' attribute in the target
node of init's routing rules. E.g., the following route enables the
diagnostic mode for the PD session of the "timer" component:
<default-route>
<service name="PD" unscoped_label="timer">
<parent diag="yes"/>
</service>
...
</default-route>
For subsystems based on a sub-init instance, init can be configured
to report the capability-quota information of its subsystems by
adding the attribute 'child_caps="yes"' to init's '<report>'
config node. Init's own capability quota can be reported by adding
the attribute 'init_caps="yes"'.
Fixes #2398
2017-05-08 21:35:43 +02:00
|
|
|
bool _child_caps = false;
|
2017-02-16 17:25:59 +01:00
|
|
|
bool _init_ram = false;
|
Capability quota accounting and trading
This patch mirrors the accounting and trading scheme that Genode employs
for physical memory to the accounting of capability allocations.
Capability quotas must now be explicitly assigned to subsystems by
specifying a 'caps=<amount>' attribute to init's start nodes.
Analogously to RAM quotas, cap quotas can be traded between clients and
servers as part of the session protocol. The capability budget of each
component is maintained by the component's corresponding PD session at
core.
At the current stage, the accounting is applied to RPC capabilities,
signal-context capabilities, and dataspace capabilities. Capabilities
that are dynamically allocated via core's CPU and TRACE service are not
yet covered. Also, the capabilities allocated by resource multiplexers
outside of core (like nitpicker) must be accounted by the respective
servers, which is not covered yet.
If a component runs out of capabilities, core's PD service prints a
warning to the log. To observe the consumption of capabilities per
component in detail, the PD service is equipped with a diagnostic
mode, which can be enabled via the 'diag' attribute in the target
node of init's routing rules. E.g., the following route enables the
diagnostic mode for the PD session of the "timer" component:
<default-route>
<service name="PD" unscoped_label="timer">
<parent diag="yes"/>
</service>
...
</default-route>
For subsystems based on a sub-init instance, init can be configured
to report the capability-quota information of its subsystems by
adding the attribute 'child_caps="yes"' to init's '<report>'
config node. Init's own capability quota can be reported by adding
the attribute 'init_caps="yes"'.
Fixes #2398
2017-05-08 21:35:43 +02:00
|
|
|
bool _init_caps = false;
|
2017-02-16 17:25:59 +01:00
|
|
|
|
|
|
|
|
public:
|
|
|
|
|
|
|
|
|
|
Report_detail() { }
|
|
|
|
|
|
|
|
|
|
Report_detail(Genode::Xml_node report)
|
|
|
|
|
{
|
|
|
|
|
_children = true;
|
|
|
|
|
_ids = report.attribute_value("ids", false);
|
|
|
|
|
_requested = report.attribute_value("requested", false);
|
|
|
|
|
_provided = report.attribute_value("provided", false);
|
|
|
|
|
_session_args = report.attribute_value("session_args", false);
|
|
|
|
|
_child_ram = report.attribute_value("child_ram", false);
|
Capability quota accounting and trading
This patch mirrors the accounting and trading scheme that Genode employs
for physical memory to the accounting of capability allocations.
Capability quotas must now be explicitly assigned to subsystems by
specifying a 'caps=<amount>' attribute to init's start nodes.
Analogously to RAM quotas, cap quotas can be traded between clients and
servers as part of the session protocol. The capability budget of each
component is maintained by the component's corresponding PD session at
core.
At the current stage, the accounting is applied to RPC capabilities,
signal-context capabilities, and dataspace capabilities. Capabilities
that are dynamically allocated via core's CPU and TRACE service are not
yet covered. Also, the capabilities allocated by resource multiplexers
outside of core (like nitpicker) must be accounted by the respective
servers, which is not covered yet.
If a component runs out of capabilities, core's PD service prints a
warning to the log. To observe the consumption of capabilities per
component in detail, the PD service is equipped with a diagnostic
mode, which can be enabled via the 'diag' attribute in the target
node of init's routing rules. E.g., the following route enables the
diagnostic mode for the PD session of the "timer" component:
<default-route>
<service name="PD" unscoped_label="timer">
<parent diag="yes"/>
</service>
...
</default-route>
For subsystems based on a sub-init instance, init can be configured
to report the capability-quota information of its subsystems by
adding the attribute 'child_caps="yes"' to init's '<report>'
config node. Init's own capability quota can be reported by adding
the attribute 'init_caps="yes"'.
Fixes #2398
2017-05-08 21:35:43 +02:00
|
|
|
_child_caps = report.attribute_value("child_caps", false);
|
2017-02-16 17:25:59 +01:00
|
|
|
_init_ram = report.attribute_value("init_ram", false);
|
Capability quota accounting and trading
This patch mirrors the accounting and trading scheme that Genode employs
for physical memory to the accounting of capability allocations.
Capability quotas must now be explicitly assigned to subsystems by
specifying a 'caps=<amount>' attribute to init's start nodes.
Analogously to RAM quotas, cap quotas can be traded between clients and
servers as part of the session protocol. The capability budget of each
component is maintained by the component's corresponding PD session at
core.
At the current stage, the accounting is applied to RPC capabilities,
signal-context capabilities, and dataspace capabilities. Capabilities
that are dynamically allocated via core's CPU and TRACE service are not
yet covered. Also, the capabilities allocated by resource multiplexers
outside of core (like nitpicker) must be accounted by the respective
servers, which is not covered yet.
If a component runs out of capabilities, core's PD service prints a
warning to the log. To observe the consumption of capabilities per
component in detail, the PD service is equipped with a diagnostic
mode, which can be enabled via the 'diag' attribute in the target
node of init's routing rules. E.g., the following route enables the
diagnostic mode for the PD session of the "timer" component:
<default-route>
<service name="PD" unscoped_label="timer">
<parent diag="yes"/>
</service>
...
</default-route>
For subsystems based on a sub-init instance, init can be configured
to report the capability-quota information of its subsystems by
adding the attribute 'child_caps="yes"' to init's '<report>'
config node. Init's own capability quota can be reported by adding
the attribute 'init_caps="yes"'.
Fixes #2398
2017-05-08 21:35:43 +02:00
|
|
|
_init_caps = report.attribute_value("init_caps", false);
|
2017-02-16 17:25:59 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
bool children() const { return _children; }
|
|
|
|
|
bool ids() const { return _ids; }
|
|
|
|
|
bool requested() const { return _requested; }
|
|
|
|
|
bool provided() const { return _provided; }
|
|
|
|
|
bool session_args() const { return _session_args; }
|
|
|
|
|
bool child_ram() const { return _child_ram; }
|
Capability quota accounting and trading
This patch mirrors the accounting and trading scheme that Genode employs
for physical memory to the accounting of capability allocations.
Capability quotas must now be explicitly assigned to subsystems by
specifying a 'caps=<amount>' attribute to init's start nodes.
Analogously to RAM quotas, cap quotas can be traded between clients and
servers as part of the session protocol. The capability budget of each
component is maintained by the component's corresponding PD session at
core.
At the current stage, the accounting is applied to RPC capabilities,
signal-context capabilities, and dataspace capabilities. Capabilities
that are dynamically allocated via core's CPU and TRACE service are not
yet covered. Also, the capabilities allocated by resource multiplexers
outside of core (like nitpicker) must be accounted by the respective
servers, which is not covered yet.
If a component runs out of capabilities, core's PD service prints a
warning to the log. To observe the consumption of capabilities per
component in detail, the PD service is equipped with a diagnostic
mode, which can be enabled via the 'diag' attribute in the target
node of init's routing rules. E.g., the following route enables the
diagnostic mode for the PD session of the "timer" component:
<default-route>
<service name="PD" unscoped_label="timer">
<parent diag="yes"/>
</service>
...
</default-route>
For subsystems based on a sub-init instance, init can be configured
to report the capability-quota information of its subsystems by
adding the attribute 'child_caps="yes"' to init's '<report>'
config node. Init's own capability quota can be reported by adding
the attribute 'init_caps="yes"'.
Fixes #2398
2017-05-08 21:35:43 +02:00
|
|
|
bool child_caps() const { return _child_caps; }
|
2017-02-16 17:25:59 +01:00
|
|
|
bool init_ram() const { return _init_ram; }
|
Capability quota accounting and trading
This patch mirrors the accounting and trading scheme that Genode employs
for physical memory to the accounting of capability allocations.
Capability quotas must now be explicitly assigned to subsystems by
specifying a 'caps=<amount>' attribute to init's start nodes.
Analogously to RAM quotas, cap quotas can be traded between clients and
servers as part of the session protocol. The capability budget of each
component is maintained by the component's corresponding PD session at
core.
At the current stage, the accounting is applied to RPC capabilities,
signal-context capabilities, and dataspace capabilities. Capabilities
that are dynamically allocated via core's CPU and TRACE service are not
yet covered. Also, the capabilities allocated by resource multiplexers
outside of core (like nitpicker) must be accounted by the respective
servers, which is not covered yet.
If a component runs out of capabilities, core's PD service prints a
warning to the log. To observe the consumption of capabilities per
component in detail, the PD service is equipped with a diagnostic
mode, which can be enabled via the 'diag' attribute in the target
node of init's routing rules. E.g., the following route enables the
diagnostic mode for the PD session of the "timer" component:
<default-route>
<service name="PD" unscoped_label="timer">
<parent diag="yes"/>
</service>
...
</default-route>
For subsystems based on a sub-init instance, init can be configured
to report the capability-quota information of its subsystems by
adding the attribute 'child_caps="yes"' to init's '<report>'
config node. Init's own capability quota can be reported by adding
the attribute 'init_caps="yes"'.
Fixes #2398
2017-05-08 21:35:43 +02:00
|
|
|
bool init_caps() const { return _init_caps; }
|
2017-02-16 17:25:59 +01:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
2020-01-09 21:23:19 +01:00
|
|
|
struct Sandbox::Report_update_trigger : Interface
|
2017-02-16 17:25:59 +01:00
|
|
|
{
|
2018-06-01 13:55:07 +02:00
|
|
|
/**
|
|
|
|
|
* Trigger regular (rate-limited) report update
|
|
|
|
|
*/
|
2017-02-16 17:25:59 +01:00
|
|
|
virtual void trigger_report_update() = 0;
|
2018-06-01 13:55:07 +02:00
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Trigger immediate report update
|
|
|
|
|
*
|
|
|
|
|
* This method is intended for situations that require a timely response of
|
|
|
|
|
* the consumer of the report. This is particularly important for resource
|
|
|
|
|
* requests that would otherwise unnecessarily stall the execution of the
|
|
|
|
|
* respective child.
|
|
|
|
|
*/
|
|
|
|
|
virtual void trigger_immediate_report_update() = 0;
|
2017-02-16 17:25:59 +01:00
|
|
|
};
|
|
|
|
|
|
2020-01-09 21:23:19 +01:00
|
|
|
#endif /* _LIB__SANDBOX__REPORT_H_ */
|