9a00ad7ae3
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'. |
||
---|---|---|
.. | ||
main.cc | ||
README | ||
target.mk |
The 'rom_tar' service obtains a TAR archive via a ROM connection and, in turn, provides the files contained in the TAR archive as individual ROM sessions. The name of the TAR archive must be specified via the 'name' attribute of an 'archive' tag, for example: ! <config> ! <archive name="archive.tar"/> ! </config> The backing store for the dataspaces exported via ROM sessions is accounted on the 'rom_tar' service (not on its clients) to make the use of 'rom_tar' transparent to the regular users of core's ROM service. Hence, this service must not be used by multiple clients that do not trust each other.