genode/repos/os/include/init/child_policy.h

223 lines
5.8 KiB
C
Raw Normal View History

2011-12-22 16:19:25 +01:00
/*
* \brief Policy applied to all children of the init process
* \author Norman Feske
* \date 2010-04-29
*/
/*
* Copyright (C) 2010-2016 Genode Labs GmbH
2011-12-22 16:19:25 +01:00
*
* This file is part of the Genode OS framework, which is distributed
* under the terms of the GNU General Public License version 2.
*/
#ifndef _INCLUDE__INIT__CHILD_POLICY_H_
#define _INCLUDE__INIT__CHILD_POLICY_H_
/* Genode includes */
#include <base/service.h>
#include <base/child.h>
#include <base/session_label.h>
#include <base/attached_ram_dataspace.h>
2011-12-22 16:19:25 +01:00
#include <util/arg_string.h>
#include <rom_session/connection.h>
#include <base/session_label.h>
#include <os/dynamic_rom_session.h>
2011-12-22 16:19:25 +01:00
namespace Init {
class Child_policy_ram_phys;
class Child_policy_handle_cpu_priorities;
class Child_policy_provide_rom_file;
class Child_policy_provide_dynamic_rom;
class Child_policy_redirect_rom_file;
class Traditional_child_policy;
2017-01-03 18:12:53 +01:00
using namespace Genode;
using Genode::size_t;
2017-01-03 18:12:53 +01:00
using Genode::strcmp;
using Genode::snprintf;
}
2011-12-22 16:19:25 +01:00
class Init::Child_policy_ram_phys
{
private:
2011-12-22 16:19:25 +01:00
bool _constrain_phys;
2011-12-22 16:19:25 +01:00
public:
2011-12-22 16:19:25 +01:00
Child_policy_ram_phys(bool constrain_phys)
: _constrain_phys(constrain_phys) { }
2011-12-22 16:19:25 +01:00
/**
* Filter arguments of session request
*
* This method removes phys_start and phys_size ram_session
* parameters if the child configuration does not explicitly
* permits this.
*/
void filter_session_args(const char *service, char *args,
2017-01-03 18:12:53 +01:00
size_t args_len)
{
/* intercept only RAM session requests */
2017-01-03 18:12:53 +01:00
if (strcmp(service, "RAM"))
return;
2011-12-22 16:19:25 +01:00
if (_constrain_phys)
return;
2011-12-22 16:19:25 +01:00
Arg_string::remove_arg(args, "phys_start");
Arg_string::remove_arg(args, "phys_size");
}
};
class Init::Child_policy_handle_cpu_priorities
{
/* priority parameters */
long _prio_levels_log2;
long _priority;
2011-12-22 16:19:25 +01:00
public:
2011-12-22 16:19:25 +01:00
Child_policy_handle_cpu_priorities(long prio_levels_log2, long priority)
: _prio_levels_log2(prio_levels_log2), _priority(priority) { }
2011-12-22 16:19:25 +01:00
2017-01-03 18:12:53 +01:00
void filter_session_args(const char *service, char *args, size_t args_len)
{
/* intercept only CPU session requests to scale priorities */
2017-01-03 18:12:53 +01:00
if (strcmp(service, "CPU") || _prio_levels_log2 == 0)
return;
2011-12-22 16:19:25 +01:00
unsigned long priority = Arg_string::find_arg(args, "priority").ulong_value(0);
2011-12-22 16:19:25 +01:00
/* clamp priority value to valid range */
priority = min((unsigned)Cpu_session::PRIORITY_LIMIT - 1, priority);
2011-12-22 16:19:25 +01:00
long discarded_prio_lsb_bits_mask = (1 << _prio_levels_log2) - 1;
if (priority & discarded_prio_lsb_bits_mask) {
warning("priority band too small, losing least-significant priority bits");
2011-12-22 16:19:25 +01:00
}
priority >>= _prio_levels_log2;
2011-12-22 16:19:25 +01:00
/* assign child priority to the most significant priority bits */
priority |= _priority*(Cpu_session::PRIORITY_LIMIT >> _prio_levels_log2);
2011-12-22 16:19:25 +01:00
/* override priority when delegating the session request to the parent */
char value_buf[64];
2017-01-03 18:12:53 +01:00
snprintf(value_buf, sizeof(value_buf), "0x%lx", priority);
Arg_string::set_arg(args, args_len, "priority", value_buf);
}
};
2011-12-22 16:19:25 +01:00
class Init::Child_policy_provide_rom_file
{
private:
2011-12-22 16:19:25 +01:00
2017-01-03 18:12:53 +01:00
struct Local_rom_session_component : Rpc_object<Rom_session>
{
2017-01-03 18:12:53 +01:00
Rpc_entrypoint &ep;
Dataspace_capability ds_cap;
Support for dynamic ROM sessions, fix #170 This patch introduces support for ROM sessions that update their provided data during the lifetime of the session. The 'Rom_session' interface had been extended with the new 'release()' and 'sigh()' functions, which are needed to support the new protocol. All ROM services have been updated to the new interface. Furthermore, the patch changes the child policy of init with regard to the handling of configuration files. The 'Init::Child' used to always provide the ROM dataspace with the child's config file via a locally implemented ROM service. However, for dynamic ROM sessions, we need to establish a session to the real supplier of the ROM data. This is achieved by using a new 'Child_policy_redirect_rom_file' policy to handle the 'configfile' rather than handling the 'configfile' case entirely within 'Child_config'. To see the new facility in action, the new 'os/run/dynamic_config.run' script provides a simple scenario. The config file of the test program is provided by a service, which generates and updates the config data at regular intervals. In addition, new support has been added to let slaves use dynamic reconfiguration. By using the new 'Child_policy_dynamic_rom_file', the configuration of a slave can be changed dynamically at runtime via the new 'configure()' function. The config is provided as plain null-terminated string (instead of a dataspace capability) because we need to buffer the config data anyway. So there is no benefit of using a dataspace. For buffering configuration data, a 'Ram_session' must be supplied. If no 'Ram_session' is specified at construction time of a 'Slave_policy', no config is supplied to the slave (which is still a common case). An example for dynamically reconfiguring a slave is provided by 'os/run/dynamic_config_slave.run'.
2012-04-04 17:07:19 +02:00
/**
* Constructor
*/
2017-01-03 18:12:53 +01:00
Local_rom_session_component(Rpc_entrypoint &ep,
Dataspace_capability ds)
: ep(ep), ds_cap(ds) { ep.manage(this); }
~Local_rom_session_component() { ep.dissolve(this); }
2011-12-22 16:19:25 +01:00
/***************************
** ROM session interface **
***************************/
2011-12-22 16:19:25 +01:00
2017-01-03 18:12:53 +01:00
Rom_dataspace_capability dataspace() override {
return static_cap_cast<Rom_dataspace>(ds_cap); }
2011-12-22 16:19:25 +01:00
2017-01-03 18:12:53 +01:00
void sigh(Signal_context_capability) override { }
2011-12-22 16:19:25 +01:00
} _session;
2011-12-22 16:19:25 +01:00
2017-01-03 18:12:53 +01:00
Session_label const _module_name;
2011-12-22 16:19:25 +01:00
2017-01-03 18:12:53 +01:00
typedef Local_service<Local_rom_session_component> Service;
2011-12-22 16:19:25 +01:00
Service::Single_session_factory _session_factory { _session };
Service _service { _session_factory };
Support for dynamic ROM sessions, fix #170 This patch introduces support for ROM sessions that update their provided data during the lifetime of the session. The 'Rom_session' interface had been extended with the new 'release()' and 'sigh()' functions, which are needed to support the new protocol. All ROM services have been updated to the new interface. Furthermore, the patch changes the child policy of init with regard to the handling of configuration files. The 'Init::Child' used to always provide the ROM dataspace with the child's config file via a locally implemented ROM service. However, for dynamic ROM sessions, we need to establish a session to the real supplier of the ROM data. This is achieved by using a new 'Child_policy_redirect_rom_file' policy to handle the 'configfile' rather than handling the 'configfile' case entirely within 'Child_config'. To see the new facility in action, the new 'os/run/dynamic_config.run' script provides a simple scenario. The config file of the test program is provided by a service, which generates and updates the config data at regular intervals. In addition, new support has been added to let slaves use dynamic reconfiguration. By using the new 'Child_policy_dynamic_rom_file', the configuration of a slave can be changed dynamically at runtime via the new 'configure()' function. The config is provided as plain null-terminated string (instead of a dataspace capability) because we need to buffer the config data anyway. So there is no benefit of using a dataspace. For buffering configuration data, a 'Ram_session' must be supplied. If no 'Ram_session' is specified at construction time of a 'Slave_policy', no config is supplied to the slave (which is still a common case). An example for dynamically reconfiguring a slave is provided by 'os/run/dynamic_config_slave.run'.
2012-04-04 17:07:19 +02:00
public:
Support for dynamic ROM sessions, fix #170 This patch introduces support for ROM sessions that update their provided data during the lifetime of the session. The 'Rom_session' interface had been extended with the new 'release()' and 'sigh()' functions, which are needed to support the new protocol. All ROM services have been updated to the new interface. Furthermore, the patch changes the child policy of init with regard to the handling of configuration files. The 'Init::Child' used to always provide the ROM dataspace with the child's config file via a locally implemented ROM service. However, for dynamic ROM sessions, we need to establish a session to the real supplier of the ROM data. This is achieved by using a new 'Child_policy_redirect_rom_file' policy to handle the 'configfile' rather than handling the 'configfile' case entirely within 'Child_config'. To see the new facility in action, the new 'os/run/dynamic_config.run' script provides a simple scenario. The config file of the test program is provided by a service, which generates and updates the config data at regular intervals. In addition, new support has been added to let slaves use dynamic reconfiguration. By using the new 'Child_policy_dynamic_rom_file', the configuration of a slave can be changed dynamically at runtime via the new 'configure()' function. The config is provided as plain null-terminated string (instead of a dataspace capability) because we need to buffer the config data anyway. So there is no benefit of using a dataspace. For buffering configuration data, a 'Ram_session' must be supplied. If no 'Ram_session' is specified at construction time of a 'Slave_policy', no config is supplied to the slave (which is still a common case). An example for dynamically reconfiguring a slave is provided by 'os/run/dynamic_config_slave.run'.
2012-04-04 17:07:19 +02:00
/**
* Constructor
*/
2017-01-03 18:12:53 +01:00
Child_policy_provide_rom_file(Session_label const &module_name,
Dataspace_capability ds_cap,
Rpc_entrypoint *ep)
:
_session(*ep, ds_cap), _module_name(module_name)
{ }
Support for dynamic ROM sessions, fix #170 This patch introduces support for ROM sessions that update their provided data during the lifetime of the session. The 'Rom_session' interface had been extended with the new 'release()' and 'sigh()' functions, which are needed to support the new protocol. All ROM services have been updated to the new interface. Furthermore, the patch changes the child policy of init with regard to the handling of configuration files. The 'Init::Child' used to always provide the ROM dataspace with the child's config file via a locally implemented ROM service. However, for dynamic ROM sessions, we need to establish a session to the real supplier of the ROM data. This is achieved by using a new 'Child_policy_redirect_rom_file' policy to handle the 'configfile' rather than handling the 'configfile' case entirely within 'Child_config'. To see the new facility in action, the new 'os/run/dynamic_config.run' script provides a simple scenario. The config file of the test program is provided by a service, which generates and updates the config data at regular intervals. In addition, new support has been added to let slaves use dynamic reconfiguration. By using the new 'Child_policy_dynamic_rom_file', the configuration of a slave can be changed dynamically at runtime via the new 'configure()' function. The config is provided as plain null-terminated string (instead of a dataspace capability) because we need to buffer the config data anyway. So there is no benefit of using a dataspace. For buffering configuration data, a 'Ram_session' must be supplied. If no 'Ram_session' is specified at construction time of a 'Slave_policy', no config is supplied to the slave (which is still a common case). An example for dynamically reconfiguring a slave is provided by 'os/run/dynamic_config_slave.run'.
2012-04-04 17:07:19 +02:00
Service *resolve_session_request_with_label(Service::Name const &name,
Session_label const &label)
{
return (name == "ROM" && label.last_element() == _module_name)
? &_service : nullptr;
}
2017-01-03 18:12:53 +01:00
Service *resolve_session_request(const char *service_name,
const char *args)
{
return resolve_session_request_with_label(service_name,
label_from_args(args));
}
};
Support for dynamic ROM sessions, fix #170 This patch introduces support for ROM sessions that update their provided data during the lifetime of the session. The 'Rom_session' interface had been extended with the new 'release()' and 'sigh()' functions, which are needed to support the new protocol. All ROM services have been updated to the new interface. Furthermore, the patch changes the child policy of init with regard to the handling of configuration files. The 'Init::Child' used to always provide the ROM dataspace with the child's config file via a locally implemented ROM service. However, for dynamic ROM sessions, we need to establish a session to the real supplier of the ROM data. This is achieved by using a new 'Child_policy_redirect_rom_file' policy to handle the 'configfile' rather than handling the 'configfile' case entirely within 'Child_config'. To see the new facility in action, the new 'os/run/dynamic_config.run' script provides a simple scenario. The config file of the test program is provided by a service, which generates and updates the config data at regular intervals. In addition, new support has been added to let slaves use dynamic reconfiguration. By using the new 'Child_policy_dynamic_rom_file', the configuration of a slave can be changed dynamically at runtime via the new 'configure()' function. The config is provided as plain null-terminated string (instead of a dataspace capability) because we need to buffer the config data anyway. So there is no benefit of using a dataspace. For buffering configuration data, a 'Ram_session' must be supplied. If no 'Ram_session' is specified at construction time of a 'Slave_policy', no config is supplied to the slave (which is still a common case). An example for dynamically reconfiguring a slave is provided by 'os/run/dynamic_config_slave.run'.
2012-04-04 17:07:19 +02:00
class Init::Child_policy_redirect_rom_file
{
private:
2011-12-22 16:19:25 +01:00
char const *_from;
char const *_to;
2011-12-22 16:19:25 +01:00
public:
Child_policy_redirect_rom_file(const char *from, const char *to)
: _from(from), _to(to) { }
2011-12-22 16:19:25 +01:00
void filter_session_args(const char *service,
2017-01-03 18:12:53 +01:00
char *args, size_t args_len)
{
if (!_from || !_to) return;
2011-12-22 16:19:25 +01:00
/* ignore session requests for non-ROM services */
2017-01-03 18:12:53 +01:00
if (strcmp(service, "ROM")) return;
2011-12-22 16:19:25 +01:00
/* drop out if request refers to another module name */
Session_label const label = label_from_args(args);
Session_label const from(_from);
if (from != label.last_element()) return;
/*
* The module name corresponds to the last part of the label.
* We have to replace this part with the 'to' module name.
* If the label consists of only the module name but no prefix,
* we replace the entire label with the 'to' module name.
*/
Session_label const prefix = label.prefix();
Session_label const to(_to);
Session_label const prefixed_to =
prefixed_label(prefix.valid() ? prefix : Session_label(), to);
Arg_string::set_arg_string(args, args_len, "label", prefixed_to.string());
}
};
2011-12-22 16:19:25 +01:00
#endif /* _INCLUDE__INIT__CHILD_POLICY_H_ */