2011-12-22 15:19:25 +00:00
|
|
|
/*
|
|
|
|
|
* \brief Launchpad interface
|
|
|
|
|
* \author Norman Feske
|
|
|
|
|
* \date 2006-09-01
|
|
|
|
|
*
|
|
|
|
|
* This class is a convenience-wrapper for starting and killing
|
|
|
|
|
* child processes. To support the Launchpad application, is
|
|
|
|
|
* also provides an interface to glues the child handling and
|
|
|
|
|
* the GUI together.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/*
|
2017-02-20 12:23:52 +00:00
|
|
|
* Copyright (C) 2006-2017 Genode Labs GmbH
|
2011-12-22 15:19:25 +00:00
|
|
|
*
|
|
|
|
|
* This file is part of the Genode OS framework, which is distributed
|
2017-02-20 12:23:52 +00:00
|
|
|
* under the terms of the GNU Affero General Public License version 3.
|
2011-12-22 15:19:25 +00:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef _INCLUDE__LAUNCHPAD__LAUNCHPAD_H_
|
|
|
|
|
#define _INCLUDE__LAUNCHPAD__LAUNCHPAD_H_
|
|
|
|
|
|
2017-03-03 15:54:45 +00:00
|
|
|
#include <util/xml_node.h>
|
2011-12-22 15:19:25 +00:00
|
|
|
#include <base/allocator.h>
|
|
|
|
|
#include <base/service.h>
|
|
|
|
|
#include <base/lock.h>
|
2017-03-03 15:54:45 +00:00
|
|
|
#include <base/child.h>
|
2011-12-22 15:19:25 +00:00
|
|
|
#include <timer_session/timer_session.h>
|
2016-04-15 13:19:22 +00:00
|
|
|
#include <pd_session/client.h>
|
2017-03-03 15:54:45 +00:00
|
|
|
#include <init/child_policy.h>
|
|
|
|
|
#include <os/session_requester.h>
|
2011-12-22 15:19:25 +00:00
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
class Launchpad;
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
class Launchpad_child : public Genode::Child_policy,
|
|
|
|
|
public Genode::List<Launchpad_child>::Element,
|
2017-05-08 14:49:00 +00:00
|
|
|
public Genode::Async_service::Wakeup
|
2011-12-22 15:19:25 +00:00
|
|
|
{
|
2016-11-23 16:07:49 +00:00
|
|
|
public:
|
|
|
|
|
|
|
|
|
|
typedef Genode::Child_policy::Name Name;
|
|
|
|
|
|
|
|
|
|
typedef Genode::Registered<Genode::Child_service> Child_service;
|
|
|
|
|
typedef Genode::Registered<Genode::Parent_service> Parent_service;
|
|
|
|
|
|
|
|
|
|
typedef Genode::Registry<Child_service> Child_services;
|
|
|
|
|
typedef Genode::Registry<Parent_service> Parent_services;
|
|
|
|
|
|
2015-03-16 13:56:29 +00:00
|
|
|
private:
|
|
|
|
|
|
|
|
|
|
Name const _name;
|
|
|
|
|
|
2017-01-18 08:29:52 +00:00
|
|
|
Binary_name const _elf_name;
|
|
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
Genode::Env &_env;
|
|
|
|
|
|
base: remove Child::heap
This patch improves the accounting for the backing store of
session-state meta data. Originally, the session state used to be
allocated by a child-local heap partition fed from the child's RAM
session. However, whereas this approach was somehow practical from a
runtime's (parent's) point of view, the child component could not count
on the quota in its own RAM session. I.e., if the Child::heap grew at
the parent side, the child's RAM session would magically diminish. This
caused two problems. First, it violates assumptions of components like
init that carefully manage their RAM resources (and giving most of them
away their children). Second, if a child transfers most of its RAM
session quota to another RAM session (like init does), the child's RAM
session may actually not allow the parent's heap to grow, which is a
very difficult error condition to deal with.
In the new version, there is no Child::heap anymore. Instead, session
states are allocated from the runtime's RAM session. In order to let
children pay for these costs, the parent withdraws the local session
costs from the session quota donated from the child when the child
initiates a new session. Hence, in principle, all components on the
route of the session request take a small bite from the session quota to
pay for their local book keeping
Consequently, the session quota that ends up at the server may become
depleted more or less, depending on the route. In the case where the
remaining quota is insufficient for the server, the server responds with
'QUOTA_EXCEEDED'. Since this behavior must generally be expected, this
patch equips the client-side 'Env::session' implementation with the
ability to re-issue session requests with successively growing quota
donations.
For several of core's services (ROM, IO_MEM, IRQ), the default session
quota has now increased by 2 KiB, which should suffice for session
requests to up to 3 hops as is the common case for most run scripts. For
longer routes, the retry mechanism as described above comes into effect.
For the time being, we give a warning whenever the server-side quota
check triggers the retry mechanism. The warning may eventually be
removed at a later stage.
2017-02-19 09:31:50 +00:00
|
|
|
Genode::Allocator &_alloc;
|
|
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
Genode::Ram_session_capability _ref_ram_cap;
|
|
|
|
|
Genode::Ram_session_client _ref_ram { _ref_ram_cap };
|
2017-05-07 23:33:40 +00:00
|
|
|
|
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 19:35:43 +00:00
|
|
|
Genode::Cap_quota const _cap_quota;
|
2017-05-07 23:33:40 +00:00
|
|
|
Genode::Ram_quota const _ram_quota;
|
2016-11-23 16:07:49 +00:00
|
|
|
|
|
|
|
|
Parent_services &_parent_services;
|
|
|
|
|
Child_services &_child_services;
|
|
|
|
|
|
|
|
|
|
Genode::Dataspace_capability _config_ds;
|
|
|
|
|
|
|
|
|
|
Genode::Session_requester _session_requester;
|
|
|
|
|
|
|
|
|
|
Init::Child_policy_provide_rom_file _config_policy;
|
|
|
|
|
|
|
|
|
|
Genode::Child _child;
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Child_service::Wakeup callback
|
|
|
|
|
*/
|
2017-05-08 14:49:00 +00:00
|
|
|
void wakeup_async_service() override
|
2016-11-23 16:07:49 +00:00
|
|
|
{
|
|
|
|
|
_session_requester.trigger_update();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
template <typename T>
|
|
|
|
|
static Genode::Service *_find_service(Genode::Registry<T> &services,
|
|
|
|
|
Genode::Service::Name const &name)
|
|
|
|
|
{
|
|
|
|
|
Genode::Service *service = nullptr;
|
|
|
|
|
services.for_each([&] (T &s) {
|
|
|
|
|
if (!service && (s.name() == name))
|
|
|
|
|
service = &s; });
|
|
|
|
|
return service;
|
|
|
|
|
}
|
2015-03-16 13:56:29 +00:00
|
|
|
|
2011-12-22 15:19:25 +00:00
|
|
|
public:
|
|
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
Launchpad_child(Genode::Env &env,
|
base: remove Child::heap
This patch improves the accounting for the backing store of
session-state meta data. Originally, the session state used to be
allocated by a child-local heap partition fed from the child's RAM
session. However, whereas this approach was somehow practical from a
runtime's (parent's) point of view, the child component could not count
on the quota in its own RAM session. I.e., if the Child::heap grew at
the parent side, the child's RAM session would magically diminish. This
caused two problems. First, it violates assumptions of components like
init that carefully manage their RAM resources (and giving most of them
away their children). Second, if a child transfers most of its RAM
session quota to another RAM session (like init does), the child's RAM
session may actually not allow the parent's heap to grow, which is a
very difficult error condition to deal with.
In the new version, there is no Child::heap anymore. Instead, session
states are allocated from the runtime's RAM session. In order to let
children pay for these costs, the parent withdraws the local session
costs from the session quota donated from the child when the child
initiates a new session. Hence, in principle, all components on the
route of the session request take a small bite from the session quota to
pay for their local book keeping
Consequently, the session quota that ends up at the server may become
depleted more or less, depending on the route. In the case where the
remaining quota is insufficient for the server, the server responds with
'QUOTA_EXCEEDED'. Since this behavior must generally be expected, this
patch equips the client-side 'Env::session' implementation with the
ability to re-issue session requests with successively growing quota
donations.
For several of core's services (ROM, IO_MEM, IRQ), the default session
quota has now increased by 2 KiB, which should suffice for session
requests to up to 3 hops as is the common case for most run scripts. For
longer routes, the retry mechanism as described above comes into effect.
For the time being, we give a warning whenever the server-side quota
check triggers the retry mechanism. The warning may eventually be
removed at a later stage.
2017-02-19 09:31:50 +00:00
|
|
|
Genode::Allocator &alloc,
|
2016-11-23 16:07:49 +00:00
|
|
|
Genode::Session_label const &label,
|
2017-01-18 08:29:52 +00:00
|
|
|
Binary_name const &elf_name,
|
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 19:35:43 +00:00
|
|
|
Genode::Cap_quota cap_quota,
|
2017-05-07 23:33:40 +00:00
|
|
|
Genode::Ram_quota ram_quota,
|
2016-11-23 16:07:49 +00:00
|
|
|
Parent_services &parent_services,
|
|
|
|
|
Child_services &child_services,
|
|
|
|
|
Genode::Dataspace_capability config_ds)
|
2011-12-22 15:19:25 +00:00
|
|
|
:
|
2017-01-18 08:29:52 +00:00
|
|
|
_name(label), _elf_name(elf_name),
|
base: remove Child::heap
This patch improves the accounting for the backing store of
session-state meta data. Originally, the session state used to be
allocated by a child-local heap partition fed from the child's RAM
session. However, whereas this approach was somehow practical from a
runtime's (parent's) point of view, the child component could not count
on the quota in its own RAM session. I.e., if the Child::heap grew at
the parent side, the child's RAM session would magically diminish. This
caused two problems. First, it violates assumptions of components like
init that carefully manage their RAM resources (and giving most of them
away their children). Second, if a child transfers most of its RAM
session quota to another RAM session (like init does), the child's RAM
session may actually not allow the parent's heap to grow, which is a
very difficult error condition to deal with.
In the new version, there is no Child::heap anymore. Instead, session
states are allocated from the runtime's RAM session. In order to let
children pay for these costs, the parent withdraws the local session
costs from the session quota donated from the child when the child
initiates a new session. Hence, in principle, all components on the
route of the session request take a small bite from the session quota to
pay for their local book keeping
Consequently, the session quota that ends up at the server may become
depleted more or less, depending on the route. In the case where the
remaining quota is insufficient for the server, the server responds with
'QUOTA_EXCEEDED'. Since this behavior must generally be expected, this
patch equips the client-side 'Env::session' implementation with the
ability to re-issue session requests with successively growing quota
donations.
For several of core's services (ROM, IO_MEM, IRQ), the default session
quota has now increased by 2 KiB, which should suffice for session
requests to up to 3 hops as is the common case for most run scripts. For
longer routes, the retry mechanism as described above comes into effect.
For the time being, we give a warning whenever the server-side quota
check triggers the retry mechanism. The warning may eventually be
removed at a later stage.
2017-02-19 09:31:50 +00:00
|
|
|
_env(env), _alloc(alloc),
|
2017-05-07 23:33:40 +00:00
|
|
|
_ref_ram_cap(env.ram_session_cap()),
|
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 19:35:43 +00:00
|
|
|
_cap_quota(Genode::Child::effective_quota(cap_quota)),
|
2017-05-07 23:33:40 +00:00
|
|
|
_ram_quota(Genode::Child::effective_quota(ram_quota)),
|
2015-03-16 13:56:29 +00:00
|
|
|
_parent_services(parent_services),
|
|
|
|
|
_child_services(child_services),
|
2016-11-23 16:07:49 +00:00
|
|
|
_session_requester(env.ep().rpc_ep(), _env.ram(), _env.rm()),
|
|
|
|
|
_config_policy("config", config_ds, &_env.ep().rpc_ep()),
|
|
|
|
|
_child(_env.rm(), _env.ep().rpc_ep(), *this)
|
2011-12-22 15:19:25 +00:00
|
|
|
{ }
|
|
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
~Launchpad_child()
|
|
|
|
|
{
|
|
|
|
|
using namespace Genode;
|
|
|
|
|
|
|
|
|
|
/* unregister services */
|
|
|
|
|
_child_services.for_each(
|
|
|
|
|
[&] (Child_service &service) {
|
|
|
|
|
if (service.has_id_space(_session_requester.id_space()))
|
base: remove Child::heap
This patch improves the accounting for the backing store of
session-state meta data. Originally, the session state used to be
allocated by a child-local heap partition fed from the child's RAM
session. However, whereas this approach was somehow practical from a
runtime's (parent's) point of view, the child component could not count
on the quota in its own RAM session. I.e., if the Child::heap grew at
the parent side, the child's RAM session would magically diminish. This
caused two problems. First, it violates assumptions of components like
init that carefully manage their RAM resources (and giving most of them
away their children). Second, if a child transfers most of its RAM
session quota to another RAM session (like init does), the child's RAM
session may actually not allow the parent's heap to grow, which is a
very difficult error condition to deal with.
In the new version, there is no Child::heap anymore. Instead, session
states are allocated from the runtime's RAM session. In order to let
children pay for these costs, the parent withdraws the local session
costs from the session quota donated from the child when the child
initiates a new session. Hence, in principle, all components on the
route of the session request take a small bite from the session quota to
pay for their local book keeping
Consequently, the session quota that ends up at the server may become
depleted more or less, depending on the route. In the case where the
remaining quota is insufficient for the server, the server responds with
'QUOTA_EXCEEDED'. Since this behavior must generally be expected, this
patch equips the client-side 'Env::session' implementation with the
ability to re-issue session requests with successively growing quota
donations.
For several of core's services (ROM, IO_MEM, IRQ), the default session
quota has now increased by 2 KiB, which should suffice for session
requests to up to 3 hops as is the common case for most run scripts. For
longer routes, the retry mechanism as described above comes into effect.
For the time being, we give a warning whenever the server-side quota
check triggers the retry mechanism. The warning may eventually be
removed at a later stage.
2017-02-19 09:31:50 +00:00
|
|
|
Genode::destroy(_alloc, &service); });
|
2016-11-23 16:07:49 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/****************************
|
|
|
|
|
** Child_policy interface **
|
|
|
|
|
****************************/
|
|
|
|
|
|
|
|
|
|
Name name() const override { return _name; }
|
|
|
|
|
|
2017-01-18 08:29:52 +00:00
|
|
|
Binary_name binary_name() const override { return _elf_name; }
|
|
|
|
|
|
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 19:35:43 +00:00
|
|
|
Genode::Pd_session &ref_pd() override { return _env.pd(); }
|
|
|
|
|
Genode::Pd_session_capability ref_pd_cap() const override { return _env.pd_session_cap(); }
|
|
|
|
|
|
2017-05-08 14:49:00 +00:00
|
|
|
Genode::Ram_session &ref_ram() override { return _ref_ram; }
|
2016-11-23 16:07:49 +00:00
|
|
|
Genode::Ram_session_capability ref_ram_cap() const override { return _ref_ram_cap; }
|
|
|
|
|
|
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 19:35:43 +00:00
|
|
|
void init(Genode::Pd_session &session,
|
|
|
|
|
Genode::Pd_session_capability cap) override
|
|
|
|
|
{
|
|
|
|
|
session.ref_account(_env.pd_session_cap());
|
|
|
|
|
_env.pd().transfer_quota(cap, _cap_quota);
|
|
|
|
|
}
|
|
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
void init(Genode::Ram_session &session,
|
|
|
|
|
Genode::Ram_session_capability cap) override
|
|
|
|
|
{
|
|
|
|
|
session.ref_account(_ref_ram_cap);
|
|
|
|
|
_ref_ram.transfer_quota(cap, _ram_quota);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
Genode::Id_space<Genode::Parent::Server> &server_id_space() override {
|
|
|
|
|
return _session_requester.id_space(); }
|
2015-03-16 13:56:29 +00:00
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
Genode::Service &resolve_session_request(Genode::Service::Name const &service_name,
|
|
|
|
|
Genode::Session_state::Args const &args) override
|
2011-12-22 15:19:25 +00:00
|
|
|
{
|
2016-11-23 16:07:49 +00:00
|
|
|
Genode::Service *service = nullptr;
|
2011-12-22 15:19:25 +00:00
|
|
|
|
|
|
|
|
/* check for config file request */
|
2016-11-23 16:07:49 +00:00
|
|
|
if ((service = _config_policy
|
|
|
|
|
.resolve_session_request(service_name.string(), args.string())))
|
|
|
|
|
return *service;
|
2011-12-22 15:19:25 +00:00
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
/* check for "session_requests" ROM request */
|
|
|
|
|
Genode::Session_label const label(Genode::label_from_args(args.string()));
|
|
|
|
|
if (service_name == Genode::Rom_session::service_name()
|
|
|
|
|
&& label.last_element() == Genode::Session_requester::rom_name())
|
|
|
|
|
return _session_requester.service();
|
2011-12-22 15:19:25 +00:00
|
|
|
|
|
|
|
|
/* if service is provided by one of our children, use it */
|
2016-11-23 16:07:49 +00:00
|
|
|
if ((service = _find_service(_child_services, service_name)))
|
|
|
|
|
return *service;
|
2011-12-22 15:19:25 +00:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Handle special case of the demo scenario when the user uses
|
|
|
|
|
* a nested Launchad for starting another Nitpicker instance
|
|
|
|
|
* before starting Liquid_fb. In this case, we do not want to
|
|
|
|
|
* delegate Nitpicker's session requests to the parent. The
|
|
|
|
|
* parent may be a launchpad again trying to apply the same
|
|
|
|
|
* policy. This instance will recognise that the session is not
|
|
|
|
|
* available at init (because the actual input and framebuffer
|
|
|
|
|
* drivers are singletons, and would therefore block for
|
|
|
|
|
* Framebuffer or Input to become available at one of its own
|
|
|
|
|
* children. The launchpad with which the user originally
|
|
|
|
|
* interacted, however, would block at the parent interface
|
|
|
|
|
* until this condition gets satisfied.
|
|
|
|
|
*/
|
2016-11-23 16:07:49 +00:00
|
|
|
if (service_name != "Input"
|
|
|
|
|
&& service_name != "Framebuffer"
|
|
|
|
|
&& ((service = _find_service(_parent_services, service_name))))
|
|
|
|
|
return *service;
|
|
|
|
|
|
|
|
|
|
Genode::warning(name(), ": service ", service_name, " not available");
|
|
|
|
|
throw Genode::Parent::Service_denied();
|
2011-12-22 15:19:25 +00:00
|
|
|
}
|
2015-03-16 13:56:29 +00:00
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
void announce_service(Genode::Service::Name const &service_name) override
|
2015-03-16 13:56:29 +00:00
|
|
|
{
|
2016-11-23 16:07:49 +00:00
|
|
|
if (_find_service(_child_services, service_name)) {
|
|
|
|
|
Genode::warning(name(), ": service ", service_name, " is already registered");
|
|
|
|
|
return;
|
2015-03-16 13:56:29 +00:00
|
|
|
}
|
|
|
|
|
|
base: remove Child::heap
This patch improves the accounting for the backing store of
session-state meta data. Originally, the session state used to be
allocated by a child-local heap partition fed from the child's RAM
session. However, whereas this approach was somehow practical from a
runtime's (parent's) point of view, the child component could not count
on the quota in its own RAM session. I.e., if the Child::heap grew at
the parent side, the child's RAM session would magically diminish. This
caused two problems. First, it violates assumptions of components like
init that carefully manage their RAM resources (and giving most of them
away their children). Second, if a child transfers most of its RAM
session quota to another RAM session (like init does), the child's RAM
session may actually not allow the parent's heap to grow, which is a
very difficult error condition to deal with.
In the new version, there is no Child::heap anymore. Instead, session
states are allocated from the runtime's RAM session. In order to let
children pay for these costs, the parent withdraws the local session
costs from the session quota donated from the child when the child
initiates a new session. Hence, in principle, all components on the
route of the session request take a small bite from the session quota to
pay for their local book keeping
Consequently, the session quota that ends up at the server may become
depleted more or less, depending on the route. In the case where the
remaining quota is insufficient for the server, the server responds with
'QUOTA_EXCEEDED'. Since this behavior must generally be expected, this
patch equips the client-side 'Env::session' implementation with the
ability to re-issue session requests with successively growing quota
donations.
For several of core's services (ROM, IO_MEM, IRQ), the default session
quota has now increased by 2 KiB, which should suffice for session
requests to up to 3 hops as is the common case for most run scripts. For
longer routes, the retry mechanism as described above comes into effect.
For the time being, we give a warning whenever the server-side quota
check triggers the retry mechanism. The warning may eventually be
removed at a later stage.
2017-02-19 09:31:50 +00:00
|
|
|
new (_alloc)
|
2017-05-08 14:49:00 +00:00
|
|
|
Child_service(_child_services, service_name,
|
|
|
|
|
_session_requester.id_space(),
|
|
|
|
|
_child.session_factory(), *this,
|
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 19:35:43 +00:00
|
|
|
_child.ram_session_cap(),
|
|
|
|
|
_child.pd_session_cap());
|
2015-03-16 13:56:29 +00:00
|
|
|
}
|
2011-12-22 15:19:25 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
class Launchpad
|
2011-12-22 15:19:25 +00:00
|
|
|
{
|
|
|
|
|
private:
|
|
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
Genode::Env &_env;
|
2016-04-27 14:04:58 +00:00
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
Genode::Heap _heap { _env.ram(), _env.rm() };
|
2011-12-22 15:19:25 +00:00
|
|
|
|
|
|
|
|
unsigned long _initial_quota;
|
|
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
Launchpad_child::Parent_services _parent_services;
|
|
|
|
|
Launchpad_child::Child_services _child_services;
|
2011-12-22 15:19:25 +00:00
|
|
|
|
|
|
|
|
Genode::Lock _children_lock;
|
|
|
|
|
Genode::List<Launchpad_child> _children;
|
|
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
bool _child_name_exists(Launchpad_child::Name const &);
|
2011-12-22 15:19:25 +00:00
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
Launchpad_child::Name _get_unique_child_name(Launchpad_child::Name const &);
|
2011-12-22 15:19:25 +00:00
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
Genode::Sliced_heap _sliced_heap;
|
2011-12-22 15:19:25 +00:00
|
|
|
|
|
|
|
|
protected:
|
|
|
|
|
|
|
|
|
|
int _ypos;
|
|
|
|
|
|
|
|
|
|
public:
|
|
|
|
|
|
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 19:35:43 +00:00
|
|
|
typedef Genode::Cap_quota Cap_quota;
|
2017-05-07 23:33:40 +00:00
|
|
|
typedef Genode::Ram_quota Ram_quota;
|
|
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
Launchpad(Genode::Env &env, unsigned long initial_quota);
|
2011-12-22 15:19:25 +00:00
|
|
|
|
|
|
|
|
unsigned long initial_quota() { return _initial_quota; }
|
|
|
|
|
|
|
|
|
|
virtual ~Launchpad() { }
|
|
|
|
|
|
2014-08-06 15:43:40 +00:00
|
|
|
/**
|
|
|
|
|
* Process launchpad XML configuration
|
|
|
|
|
*/
|
2016-11-25 15:54:49 +00:00
|
|
|
void process_config(Genode::Xml_node);
|
2011-12-22 15:19:25 +00:00
|
|
|
|
2015-03-16 13:56:29 +00:00
|
|
|
|
2011-12-22 15:19:25 +00:00
|
|
|
/*************************
|
|
|
|
|
** Configuring the GUI **
|
|
|
|
|
*************************/
|
|
|
|
|
|
|
|
|
|
virtual void quota(unsigned long quota) { }
|
|
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
virtual void add_launcher(Launchpad_child::Name const &binary_name,
|
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 19:35:43 +00:00
|
|
|
Cap_quota caps, unsigned long default_quota,
|
2011-12-22 15:19:25 +00:00
|
|
|
Genode::Dataspace_capability config_ds) { }
|
|
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
virtual void add_child(Launchpad_child::Name const &,
|
2011-12-22 15:19:25 +00:00
|
|
|
unsigned long quota,
|
2016-11-23 16:07:49 +00:00
|
|
|
Launchpad_child &,
|
|
|
|
|
Genode::Allocator &) { }
|
2011-12-22 15:19:25 +00:00
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
virtual void remove_child(Launchpad_child::Name const &,
|
|
|
|
|
Genode::Allocator &) { }
|
2011-12-22 15:19:25 +00:00
|
|
|
|
2016-11-23 16:07:49 +00:00
|
|
|
Launchpad_child *start_child(Launchpad_child::Name const &binary_name,
|
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 19:35:43 +00:00
|
|
|
Cap_quota cap_quota, Ram_quota ram_quota,
|
2011-12-22 15:19:25 +00:00
|
|
|
Genode::Dataspace_capability config_ds);
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Exit child and close all its sessions
|
|
|
|
|
*/
|
2016-11-23 16:07:49 +00:00
|
|
|
void exit_child(Launchpad_child &child);
|
2011-12-22 15:19:25 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
#endif /* _INCLUDE__LAUNCHPAD__LAUNCHPAD_H_ */
|
