2011-12-22 16:19:25 +01:00
|
|
|
/*
|
|
|
|
|
* \brief Core main program
|
|
|
|
|
* \author Norman Feske
|
|
|
|
|
* \date 2006-07-12
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/*
|
2017-02-20 13:23:52 +01:00
|
|
|
* Copyright (C) 2006-2017 Genode Labs GmbH
|
2011-12-22 16:19:25 +01:00
|
|
|
*
|
|
|
|
|
* 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.
|
2011-12-22 16:19:25 +01:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/* Genode includes */
|
|
|
|
|
#include <base/snprintf.h>
|
|
|
|
|
#include <base/sleep.h>
|
|
|
|
|
#include <base/service.h>
|
|
|
|
|
#include <base/child.h>
|
2016-05-03 16:31:17 +02:00
|
|
|
#include <base/log.h>
|
2015-05-05 08:50:16 +02:00
|
|
|
#include <rm_session/connection.h>
|
|
|
|
|
#include <pd_session/connection.h>
|
2011-12-22 16:19:25 +01:00
|
|
|
#include <rom_session/connection.h>
|
|
|
|
|
#include <cpu_session/connection.h>
|
|
|
|
|
|
2016-05-04 12:27:17 +02:00
|
|
|
/* base-internal includes */
|
|
|
|
|
#include <base/internal/globals.h>
|
|
|
|
|
|
2011-12-22 16:19:25 +01:00
|
|
|
/* core includes */
|
|
|
|
|
#include <platform.h>
|
|
|
|
|
#include <core_env.h>
|
2017-05-11 00:07:54 +02:00
|
|
|
#include <core_service.h>
|
2017-05-10 20:11:38 +02:00
|
|
|
#include <signal_transmitter.h>
|
2011-12-22 16:19:25 +01:00
|
|
|
#include <rom_root.h>
|
|
|
|
|
#include <rm_root.h>
|
|
|
|
|
#include <cpu_root.h>
|
|
|
|
|
#include <pd_root.h>
|
|
|
|
|
#include <log_root.h>
|
|
|
|
|
#include <io_mem_root.h>
|
|
|
|
|
#include <irq_root.h>
|
2013-08-10 03:44:55 +02:00
|
|
|
#include <trace/root.h>
|
2012-10-02 13:11:58 +02:00
|
|
|
#include <platform_services.h>
|
2011-12-22 16:19:25 +01:00
|
|
|
|
|
|
|
|
using namespace Genode;
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/***************************************
|
|
|
|
|
** Core environment/platform support **
|
|
|
|
|
***************************************/
|
|
|
|
|
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
Core_env &Genode::core_env()
|
2011-12-22 16:19:25 +01:00
|
|
|
{
|
|
|
|
|
/*
|
|
|
|
|
* Make sure to initialize the platform before constructing the core
|
|
|
|
|
* environment.
|
|
|
|
|
*/
|
|
|
|
|
platform();
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* By placing the environment as static object here, we ensure that its
|
|
|
|
|
* constructor gets called when this function is used the first time.
|
|
|
|
|
*/
|
|
|
|
|
static Core_env _env;
|
2017-05-10 20:11:38 +02:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Register signal-source entrypoint at core-local signal-transmitter back
|
|
|
|
|
* end
|
|
|
|
|
*/
|
|
|
|
|
static bool signal_transmitter_initialized;
|
|
|
|
|
|
|
|
|
|
if (!signal_transmitter_initialized)
|
|
|
|
|
signal_transmitter_initialized =
|
2017-11-20 15:33:25 +01:00
|
|
|
(init_core_signal_transmitter(_env.signal_ep()), true);
|
2017-05-10 20:11:38 +02:00
|
|
|
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
return _env;
|
2011-12-22 16:19:25 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
Env_deprecated *Genode::env_deprecated() {
|
|
|
|
|
return &core_env(); }
|
2011-12-22 16:19:25 +01:00
|
|
|
|
|
|
|
|
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
Platform &Genode::platform_specific()
|
2011-12-22 16:19:25 +01:00
|
|
|
{
|
|
|
|
|
static Platform _platform;
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
return _platform;
|
2011-12-22 16:19:25 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
Platform_generic &Genode::platform() { return platform_specific(); }
|
2011-12-22 16:19:25 +01:00
|
|
|
|
|
|
|
|
|
2017-05-11 00:07:54 +02:00
|
|
|
Thread_capability Genode::main_thread_cap() { return Thread_capability(); }
|
2011-12-22 16:19:25 +01:00
|
|
|
|
|
|
|
|
|
2017-06-13 13:18:11 +02:00
|
|
|
/**
|
|
|
|
|
* Dummy implementation for core that has no parent to ask for resources
|
|
|
|
|
*/
|
Follow practices suggested by "Effective C++"
The patch adjust the code of the base, base-<kernel>, and os repository.
To adapt existing components to fix violations of the best practices
suggested by "Effective C++" as reported by the -Weffc++ compiler
argument. The changes follow the patterns outlined below:
* A class with virtual functions can no longer publicly inherit base
classed without a vtable. The inherited object may either be moved
to a member variable, or inherited privately. The latter would be
used for classes that inherit 'List::Element' or 'Avl_node'. In order
to enable the 'List' and 'Avl_tree' to access the meta data, the
'List' must become a friend.
* Instead of adding a virtual destructor to abstract base classes,
we inherit the new 'Interface' class, which contains a virtual
destructor. This way, single-line abstract base classes can stay
as compact as they are now. The 'Interface' utility resides in
base/include/util/interface.h.
* With the new warnings enabled, all member variables must be explicitly
initialized. Basic types may be initialized with '='. All other types
are initialized with braces '{ ... }' or as class initializers. If
basic types and non-basic types appear in a row, it is nice to only
use the brace syntax (also for basic types) and align the braces.
* If a class contains pointers as members, it must now also provide a
copy constructor and assignment operator. In the most cases, one
would make them private, effectively disallowing the objects to be
copied. Unfortunately, this warning cannot be fixed be inheriting
our existing 'Noncopyable' class (the compiler fails to detect that
the inheriting class cannot be copied and still gives the error).
For now, we have to manually add declarations for both the copy
constructor and assignment operator as private class members. Those
declarations should be prepended with a comment like this:
/*
* Noncopyable
*/
Thread(Thread const &);
Thread &operator = (Thread const &);
In the future, we should revisit these places and try to replace
the pointers with references. In the presence of at least one
reference member, the compiler would no longer implicitly generate
a copy constructor. So we could remove the manual declaration.
Issue #465
2017-12-21 15:42:15 +01:00
|
|
|
void Genode::init_parent_resource_requests(Genode::Env &) {};
|
2017-06-13 13:18:11 +02:00
|
|
|
|
|
|
|
|
|
2011-12-22 16:19:25 +01:00
|
|
|
/****************
|
|
|
|
|
** Core child **
|
|
|
|
|
****************/
|
|
|
|
|
|
|
|
|
|
class Core_child : public Child_policy
|
|
|
|
|
{
|
|
|
|
|
private:
|
|
|
|
|
|
2016-11-06 14:26:34 +01:00
|
|
|
Registry<Service> &_services;
|
2011-12-22 16:19:25 +01: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 21:35:43 +02:00
|
|
|
Capability<Pd_session> _core_pd_cap;
|
|
|
|
|
Pd_session &_core_pd;
|
|
|
|
|
|
2016-11-06 14:26:34 +01:00
|
|
|
Capability<Cpu_session> _core_cpu_cap;
|
|
|
|
|
Cpu_session &_core_cpu;
|
2016-04-27 16:04:58 +02: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 21:35:43 +02:00
|
|
|
Cap_quota const _cap_quota;
|
2017-05-08 01:33:40 +02:00
|
|
|
Ram_quota const _ram_quota;
|
2016-04-20 21:12:57 +02:00
|
|
|
|
2013-01-30 17:00:00 +01:00
|
|
|
Child _child;
|
2011-12-22 16:19:25 +01:00
|
|
|
|
|
|
|
|
public:
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Constructor
|
|
|
|
|
*/
|
2017-05-11 20:03:28 +02:00
|
|
|
Core_child(Registry<Service> &services, Region_map &local_rm,
|
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
|
|
|
Pd_session &core_pd, Capability<Pd_session> core_pd_cap,
|
2017-05-08 19:55:54 +02:00
|
|
|
Cpu_session &core_cpu, Capability<Cpu_session> core_cpu_cap,
|
2017-08-16 16:04:41 +02:00
|
|
|
Cap_quota cap_quota, Ram_quota ram_quota,
|
|
|
|
|
Rpc_entrypoint &ep)
|
2011-12-22 16:19:25 +01:00
|
|
|
:
|
2016-11-06 14:26:34 +01:00
|
|
|
_services(services),
|
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
|
|
|
_core_pd_cap (core_pd_cap), _core_pd (core_pd),
|
2016-11-06 14:26:34 +01:00
|
|
|
_core_cpu_cap(core_cpu_cap), _core_cpu(core_cpu),
|
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
|
|
|
_cap_quota(Child::effective_quota(cap_quota)),
|
2017-05-08 01:33:40 +02:00
|
|
|
_ram_quota(Child::effective_quota(ram_quota)),
|
2017-08-16 16:04:41 +02:00
|
|
|
_child(local_rm, ep, *this)
|
|
|
|
|
{ }
|
2011-12-22 16:19:25 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
/****************************
|
|
|
|
|
** Child-policy interface **
|
|
|
|
|
****************************/
|
|
|
|
|
|
2019-02-14 22:39:08 +01:00
|
|
|
Name name() const override { return "init"; }
|
2016-11-06 14:26:34 +01:00
|
|
|
|
2019-01-30 17:53:16 +01:00
|
|
|
Route resolve_session_request(Service::Name const &name,
|
|
|
|
|
Session_label const &label) override
|
2016-11-06 14:26:34 +01:00
|
|
|
{
|
|
|
|
|
Service *service = nullptr;
|
|
|
|
|
_services.for_each([&] (Service &s) {
|
|
|
|
|
if (!service && s.name() == name)
|
|
|
|
|
service = &s; });
|
|
|
|
|
|
|
|
|
|
if (!service)
|
Streamline exception types
This patch reduces the number of exception types by facilitating
globally defined exceptions for common usage patterns shared by most
services. In particular, RPC functions that demand a session-resource
upgrade not longer reflect this condition via a session-specific
exception but via the 'Out_of_ram' or 'Out_of_caps' types.
Furthermore, the 'Parent::Service_denied', 'Parent::Unavailable',
'Root::Invalid_args', 'Root::Unavailable', 'Service::Invalid_args',
'Service::Unavailable', and 'Local_service::Factory::Denied' types have
been replaced by the single 'Service_denied' exception type defined in
'session/session.h'.
This consolidation eases the error handling (there are fewer exceptions
to handle), alleviates the need to convert exceptions along the
session-creation call chain, and avoids possible aliasing problems
(catching the wrong type with the same name but living in a different
scope).
2017-05-07 22:03:22 +02:00
|
|
|
throw Service_denied();
|
2016-11-06 14:26:34 +01:00
|
|
|
|
2019-01-30 17:53:16 +01:00
|
|
|
return Route { .service = *service,
|
|
|
|
|
.label = label,
|
|
|
|
|
.diag = Session::Diag() };
|
2016-11-06 14:26:34 +01:00
|
|
|
}
|
2013-05-08 11:10:35 +02: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 21:35:43 +02:00
|
|
|
void init(Pd_session &session, Capability<Pd_session> cap) override
|
|
|
|
|
{
|
|
|
|
|
session.ref_account(_core_pd_cap);
|
|
|
|
|
_core_pd.transfer_quota(cap, _cap_quota);
|
2017-05-11 20:03:28 +02:00
|
|
|
_core_pd.transfer_quota(cap, _ram_quota);
|
2016-11-06 14:26:34 +01:00
|
|
|
}
|
2011-12-22 16:19:25 +01:00
|
|
|
|
2016-11-06 14:26:34 +01:00
|
|
|
void init(Cpu_session &session, Capability<Cpu_session> cap) override
|
2011-12-22 16:19:25 +01:00
|
|
|
{
|
2016-11-06 14:26:34 +01:00
|
|
|
session.ref_account(_core_cpu_cap);
|
|
|
|
|
_core_cpu.transfer_quota(cap, Cpu_session::quota_lim_upscale(100, 100));
|
2011-12-22 16:19:25 +01:00
|
|
|
}
|
2016-11-06 14:26:34 +01:00
|
|
|
|
2019-01-30 17:53:16 +01:00
|
|
|
Pd_session &ref_pd() override { return _core_pd; }
|
|
|
|
|
Pd_session_capability ref_pd_cap() const override { return _core_pd_cap; }
|
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 10:31:50 +01:00
|
|
|
|
|
|
|
|
size_t session_alloc_batch_size() const override { return 128; }
|
2011-12-22 16:19:25 +01:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
2015-12-23 15:22:33 +01:00
|
|
|
/****************
|
|
|
|
|
** Signal API **
|
|
|
|
|
****************/
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* In contrast to the 'Platform_env' used by non-core components, core disables
|
|
|
|
|
* the signal thread but overriding 'Genode::init_signal_thread' with a dummy.
|
|
|
|
|
* Within core, the signal thread is not needed as core is never supposed to
|
|
|
|
|
* receive any signals. Otherwise, the signal thread would be the only
|
|
|
|
|
* non-entrypoint thread within core, which would be a problem on NOVA where
|
|
|
|
|
* the creation of regular threads within core is unsupported.
|
|
|
|
|
*/
|
|
|
|
|
|
2017-05-10 20:11:38 +02:00
|
|
|
void Genode::init_signal_thread(Env &) { }
|
|
|
|
|
void Genode::destroy_signal_thread() { }
|
2015-12-23 15:22:33 +01:00
|
|
|
|
|
|
|
|
|
2015-06-16 20:39:09 +02:00
|
|
|
/*******************
|
|
|
|
|
** Trace support **
|
|
|
|
|
*******************/
|
|
|
|
|
|
|
|
|
|
Trace::Source_registry &Trace::sources()
|
|
|
|
|
{
|
|
|
|
|
static Trace::Source_registry inst;
|
|
|
|
|
return inst;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2011-12-22 16:19:25 +01:00
|
|
|
/***************
|
|
|
|
|
** Core main **
|
|
|
|
|
***************/
|
|
|
|
|
|
2014-04-11 13:59:18 +02:00
|
|
|
namespace Genode {
|
|
|
|
|
extern bool inhibit_tracing;
|
|
|
|
|
extern char const *version_string;
|
|
|
|
|
}
|
2013-08-09 20:48:32 +02:00
|
|
|
|
2015-12-23 15:22:33 +01:00
|
|
|
|
2011-12-22 16:19:25 +01:00
|
|
|
int main()
|
|
|
|
|
{
|
2013-08-09 20:48:32 +02:00
|
|
|
/**
|
|
|
|
|
* Disable tracing within core because it is currently not fully implemented.
|
|
|
|
|
*/
|
|
|
|
|
inhibit_tracing = true;
|
|
|
|
|
|
2016-05-03 16:31:17 +02:00
|
|
|
log("Genode ", Genode::version_string);
|
2014-03-18 16:23:52 +01:00
|
|
|
|
2013-08-10 03:44:55 +02:00
|
|
|
static Trace::Policy_registry trace_policies;
|
|
|
|
|
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
static Rpc_entrypoint &ep = core_env().entrypoint();
|
|
|
|
|
static Ram_allocator &core_ram_alloc = core_env().ram_allocator();
|
|
|
|
|
static Region_map &local_rm = core_env().local_rm();
|
|
|
|
|
Pd_session &core_pd = *core_env().pd_session();
|
|
|
|
|
Capability<Pd_session> core_pd_cap = core_env().pd_session_cap();
|
2011-12-22 16:19:25 +01:00
|
|
|
|
2017-05-11 00:07:54 +02:00
|
|
|
static Registry<Service> services;
|
2016-11-06 14:26:34 +01:00
|
|
|
|
2011-12-22 16:19:25 +01:00
|
|
|
/*
|
|
|
|
|
* Allocate session meta data on distinct dataspaces to enable independent
|
|
|
|
|
* destruction (to enable quota trading) of session component objects.
|
|
|
|
|
*/
|
2017-05-08 19:55:54 +02:00
|
|
|
static Sliced_heap sliced_heap(core_ram_alloc, local_rm);
|
2011-12-22 16:19:25 +01:00
|
|
|
|
2016-01-19 20:24:22 +01:00
|
|
|
/*
|
|
|
|
|
* Factory for creating RPC capabilities within core
|
|
|
|
|
*/
|
|
|
|
|
static Rpc_cap_factory rpc_cap_factory(sliced_heap);
|
|
|
|
|
|
2016-04-15 15:19:22 +02:00
|
|
|
static Pager_entrypoint pager_ep(rpc_cap_factory);
|
|
|
|
|
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
static Rom_root rom_root (ep, ep, platform().rom_fs(), sliced_heap);
|
2020-05-05 14:27:29 +02:00
|
|
|
static Rm_root rm_root (ep, sliced_heap, core_ram_alloc, local_rm, pager_ep);
|
2019-01-30 17:53:16 +01:00
|
|
|
static Cpu_root cpu_root (core_ram_alloc, local_rm, ep, ep, pager_ep,
|
|
|
|
|
sliced_heap, Trace::sources());
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
static Pd_root pd_root (ep, core_env().signal_ep(), pager_ep,
|
|
|
|
|
platform().ram_alloc(),
|
2017-11-09 14:20:07 +01:00
|
|
|
local_rm, sliced_heap,
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
platform_specific().core_mem_alloc());
|
|
|
|
|
static Log_root log_root (ep, sliced_heap);
|
|
|
|
|
static Io_mem_root io_mem_root (ep, ep, platform().io_mem_alloc(),
|
|
|
|
|
platform().ram_alloc(), sliced_heap);
|
|
|
|
|
static Irq_root irq_root (*core_env().pd_session(),
|
|
|
|
|
platform().irq_alloc(), sliced_heap);
|
2019-01-30 17:53:16 +01:00
|
|
|
static Trace::Root trace_root (core_ram_alloc, local_rm, ep, sliced_heap,
|
|
|
|
|
Trace::sources(), trace_policies);
|
2011-12-22 16:19:25 +01:00
|
|
|
|
2016-11-06 14:26:34 +01:00
|
|
|
static Core_service<Rom_session_component> rom_service (services, rom_root);
|
|
|
|
|
static Core_service<Rm_session_component> rm_service (services, rm_root);
|
|
|
|
|
static Core_service<Cpu_session_component> cpu_service (services, cpu_root);
|
|
|
|
|
static Core_service<Pd_session_component> pd_service (services, pd_root);
|
|
|
|
|
static Core_service<Log_session_component> log_service (services, log_root);
|
|
|
|
|
static Core_service<Io_mem_session_component> io_mem_service (services, io_mem_root);
|
|
|
|
|
static Core_service<Irq_session_component> irq_service (services, irq_root);
|
|
|
|
|
static Core_service<Trace::Session_component> trace_service (services, trace_root);
|
2011-12-22 16:19:25 +01:00
|
|
|
|
2012-10-02 13:11:58 +02:00
|
|
|
/* make platform-specific services known to service pool */
|
2019-04-17 14:16:27 +02:00
|
|
|
platform_add_local_services(ep, sliced_heap, services, Trace::sources());
|
2016-11-06 14:26:34 +01:00
|
|
|
|
2017-05-11 20:03:28 +02:00
|
|
|
size_t const avail_ram_quota = core_pd.avail_ram().value;
|
|
|
|
|
size_t const avail_cap_quota = core_pd.avail_caps().value;
|
|
|
|
|
|
|
|
|
|
size_t const preserved_ram_quota = 224*1024;
|
|
|
|
|
size_t const preserved_cap_quota = 1000;
|
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
|
|
|
|
2017-05-11 20:03:28 +02:00
|
|
|
if (avail_ram_quota < preserved_ram_quota) {
|
|
|
|
|
error("core preservation exceeds platform RAM limit");
|
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
|
|
|
return -1;
|
|
|
|
|
}
|
|
|
|
|
|
2017-05-11 20:03:28 +02:00
|
|
|
if (avail_cap_quota < preserved_cap_quota) {
|
|
|
|
|
error("core preservation exceeds platform cap quota limit");
|
|
|
|
|
return -1;
|
|
|
|
|
}
|
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
|
|
|
|
2017-05-11 20:03:28 +02:00
|
|
|
Ram_quota const init_ram_quota { avail_ram_quota - preserved_ram_quota };
|
|
|
|
|
Cap_quota const init_cap_quota { avail_cap_quota - preserved_cap_quota };
|
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
|
|
|
|
|
|
|
|
/* CPU session representing core */
|
2014-10-16 11:15:46 +02:00
|
|
|
static Cpu_session_component
|
2020-05-05 14:27:29 +02:00
|
|
|
core_cpu(ep,
|
|
|
|
|
Session::Resources{{Cpu_connection::RAM_QUOTA},
|
|
|
|
|
{Cpu_session::CAP_QUOTA}},
|
|
|
|
|
"core", Session::Diag{false},
|
|
|
|
|
core_ram_alloc, local_rm, ep, pager_ep, Trace::sources(), "",
|
|
|
|
|
Affinity(), Cpu_session::QUOTA_LIMIT);
|
|
|
|
|
|
|
|
|
|
Cpu_session_capability core_cpu_cap = core_cpu.cap();
|
2016-11-06 14:26:34 +01:00
|
|
|
|
2017-05-11 20:03:28 +02:00
|
|
|
log("", init_ram_quota.value / (1024*1024), " MiB RAM and ", init_cap_quota, " caps "
|
2017-05-08 01:33:40 +02:00
|
|
|
"assigned to init");
|
2011-12-22 16:19:25 +01:00
|
|
|
|
2016-12-01 17:37:08 +01:00
|
|
|
static Reconstructible<Core_child>
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
init(services, local_rm, core_pd, core_pd_cap, core_cpu, core_cpu_cap,
|
2017-08-16 16:04:41 +02:00
|
|
|
init_cap_quota, init_ram_quota, ep);
|
2011-12-22 16:19:25 +01:00
|
|
|
|
base/core: use references instead of pointers
This patch replaces the former prominent use of pointers by references
wherever feasible. This has the following benefits:
* The contract between caller and callee becomes more obvious. When
passing a reference, the contract says that the argument cannot be
a null pointer. The caller is responsible to ensure that. Therefore,
the use of reference eliminates the need to add defensive null-pointer
checks at the callee site, which sometimes merely exist to be on the
safe side. The bottom line is that the code becomes easier to follow.
* Reference members must be initialized via an object initializer,
which promotes a programming style that avoids intermediate object-
construction states. Within core, there are still a few pointers
as member variables left though. E.g., caused by the late association
of 'Platform_thread' objects with their 'Platform_pd' objects.
* If no pointers are present as member variables, we don't need to
manually provide declarations of a private copy constructor and
an assignment operator to avoid -Weffc++ errors "class ... has
pointer data members [-Werror=effc++]".
This patch also changes a few system bindings on NOVA and Fiasco.OC,
e.g., the return value of the global 'cap_map' accessor has become a
reference. Hence, the patch touches a few places outside of core.
Fixes #3135
2019-01-24 22:00:01 +01:00
|
|
|
platform().wait_for_exit();
|
2011-12-22 16:19:25 +01:00
|
|
|
|
2016-11-06 14:26:34 +01:00
|
|
|
init.destruct();
|
2011-12-22 16:19:25 +01:00
|
|
|
return 0;
|
|
|
|
|
}
|
