genode/repos/os/run/init.run
Norman Feske fcf25c22d1 init: respond to binary-name changes
This patch covers the resolution of the ROM route for child binaries
via the generic label-rewriting mechanics. Now, the <binary> node has
become merely sytactic sugar for a route like the following:

<start name="test"/>
  <route>
    <service name="ROM" unscoped_label="test">
      <parent label="test-binary-name"/> </service>
      ...
  </route>
  ...
</start>

A change of the binary name has an effect on the child's ROM route to
the binary and thereby implicitly triggers a child restart due to the
existing re-validation of the routing.
2017-03-24 16:19:55 +01:00

385 lines
12 KiB
Plaintext

#
# Build
#
set build_components { core init drivers/timer app/dummy test/init }
build $build_components
create_boot_directory
#
# Generate config
#
append config {
<config>
<parent-provides>
<service name="ROM"/>
<service name="RAM"/>
<service name="CPU"/>
<service name="PD"/>
<service name="LOG"/>
<service name="IRQ"/>
<service name="IO_MEM"/>
<service name="IO_PORT"/>
</parent-provides>
<default-route>
<any-service> <parent/> <any-child/> </any-service>
</default-route>
<start name="timer">
<resource name="RAM" quantum="1M"/>
<provides><service name="Timer"/></provides>
</start>
<start name="report_rom">
<resource name="RAM" quantum="2M"/>
<provides> <service name="ROM"/> <service name="Report"/> </provides>
<config verbose="no">
<policy label="init -> init.config" report="test-init -> init.config"/>
<policy label="test-init -> state" report="init -> state"/>
</config>
</start>
<start name="test-init">
<resource name="RAM" quantum="4M"/>
<provides> <service name="LOG"/> </provides>
<config>
<!-- let init settle, processing the initially invalid config -->
<sleep ms="150"/>
<message string="test state reporting"/>
<init_config version="initial">
<report init_ram="yes" ids="yes" child_ram="yes" requested="yes"/>
<parent-provides>
<service name="ROM"/>
<service name="RAM"/>
<service name="CPU"/>
<service name="PD"/>
<service name="LOG"/>
</parent-provides>
<start name="application">
<binary name="dummy"/>
<resource name="RAM" quantum="1G"/>
<config>
<log string="started"/>
</config>
<route> <any-service> <parent/> </any-service> </route>
</start>
</init_config>
<expect_log string="[init -> application] started"/>
<sleep ms="200"/>
<expect_init_state>
<attribute name="version" value="initial"/>
<node name="child">
<attribute name="name" value="application"/>
<attribute name="binary" value="dummy"/>
<node name="requested">
<node name="session">
<attribute name="service" value="PD"/>
<attribute name="label" value="application"/>
<attribute name="state" value="CAP_HANDED_OUT"/>
</node>
</node>
</node>
</expect_init_state>
<message string="routing to custom log service"/>
<init_config version="chained log services">
<report ids="yes" requested="yes" provided="yes"/>
<parent-provides>
<service name="ROM"/>
<service name="RAM"/>
<service name="CPU"/>
<service name="PD"/>
<service name="LOG"/>
</parent-provides>
<start name="server">
<binary name="dummy"/>
<resource name="RAM" quantum="1M"/>
<provides> <service name="LOG"/> </provides>
<config> <log_service/> </config>
<route> <any-service> <parent/> </any-service> </route>
</start>
<start name="indirect_server">
<binary name="dummy"/>
<resource name="RAM" quantum="1M"/>
<provides> <service name="LOG"/> </provides>
<config> <log_service/> </config>
<route>
<service name="LOG"> <child name="server"/> </service>
<any-service> <parent/> </any-service>
</route>
</start>
<start name="client">
<binary name="dummy"/>
<resource name="RAM" quantum="1M"/>
<config> <log string="client started"/> </config>
<route>
<service name="LOG"> <child name="indirect_server"/> </service>
<any-service> <parent/> </any-service>
</route>
</start>
</init_config>
<expect_log string="[init -> server] [indirect_server] [client] client started"/>
<sleep ms="200"/>
<expect_init_state>
<node name="child">
<attribute name="name" value="server"/>
<attribute name="id" value="2"/>
</node>
<node name="child">
<attribute name="name" value="client"/>
<attribute name="id" value="4"/>
</node>
</expect_init_state>
<sleep ms="150"/>
<message string="changing route of indirect server"/>
<!-- Because the route to the LOG session of the 'indirect_server'
is re-directed to the parent, the 'indirect_server' must be
restarted. As the 'client' depends on the 'indirect_server'
for its LOG session, the client must implicitly be restarted
as well. -->
<init_config version="restarted indirect server">
<report ids="yes" requested="yes" provided="yes"/>
<parent-provides>
<service name="ROM"/>
<service name="RAM"/>
<service name="CPU"/>
<service name="PD"/>
<service name="LOG"/>
</parent-provides>
<start name="server">
<binary name="dummy"/>
<resource name="RAM" quantum="1M"/>
<provides> <service name="LOG"/> </provides>
<config> <log_service/> </config>
<route> <any-service> <parent/> </any-service> </route>
</start>
<start name="indirect_server">
<binary name="dummy"/>
<resource name="RAM" quantum="1M"/>
<provides> <service name="LOG"/> </provides>
<config> <log_service/> </config>
<route> <any-service> <parent/> </any-service> </route>
</start>
<start name="client">
<binary name="dummy"/>
<resource name="RAM" quantum="1M"/>
<config> <log string="client started"/> </config>
<route>
<service name="LOG"> <child name="indirect_server"/> </service>
<any-service> <parent/> </any-service>
</route>
</start>
</init_config>
<!-- the output of the new 'client' does no longer go via 'server' -->
<expect_log string="[init -> indirect_server] [client] client started"/>
<sleep ms="150"/>
<expect_init_state>
<node name="child">
<attribute name="name" value="server"/>
<attribute name="id" value="2"/>
</node>
<node name="child">
<attribute name="name" value="client"/>
<attribute name="id" value="6"/> <!-- client was restarted -->
</node>
</expect_init_state>
<sleep ms="100"/>
<message string="update child config"/>
<init_config>
<report ids="yes"/>
<parent-provides>
<service name="ROM"/> <service name="RAM"/>
<service name="CPU"/> <service name="PD"/>
<service name="LOG"/>
</parent-provides>
<start name="application">
<binary name="dummy"/>
<resource name="RAM" quantum="1M"/>
<config version="Version A"/>
<route> <any-service> <parent/> </any-service> </route>
</start>
</init_config>
<expect_log string="[init -> application] config 1: Version A"/>
<init_config>
<report ids="yes"/>
<parent-provides>
<service name="ROM"/> <service name="RAM"/>
<service name="CPU"/> <service name="PD"/>
<service name="LOG"/>
</parent-provides>
<start name="application">
<binary name="dummy"/>
<resource name="RAM" quantum="1M"/>
<config version="Version B"/>
<route> <any-service> <parent/> </any-service> </route>
</start>
</init_config>
<expect_log string="[init -> application] config 2: Version B"/>
<sleep ms="100"/>
<message string="test label rewritiong and binary-name update"/>
<init_config>
<parent-provides>
<service name="ROM"/> <service name="RAM"/>
<service name="CPU"/> <service name="PD"/>
<service name="LOG"/>
</parent-provides>
<start name="test">
<binary name="dummy"/>
<resource name="RAM" quantum="1M"/>
<config version="binary-name test"/>
<route>
<any-service> <parent/> </any-service>
</route>
</start>
</init_config>
<expect_log string="[init -> test] config 1: binary-name test"/>
<!-- We change the binary name, but also use the label-rewriting
feature of init to produce the same route as the original
binary. Consequently, init does not need to restart the
child. Instead the original child merely prints a new
config version (count 2). -->
<init_config>
<parent-provides>
<service name="ROM"/> <service name="RAM"/>
<service name="CPU"/> <service name="PD"/>
<service name="LOG"/>
</parent-provides>
<start name="test">
<binary name="renamed_dummy"/>
<resource name="RAM" quantum="1M"/>
<config version="binary re-routed to same route"/>
<route>
<service name="ROM" unscoped_label="renamed_dummy">
<parent label="dummy"/> </service>
<any-service> <parent/> </any-service>
</route>
</start>
</init_config>
<expect_log string="[init -> test] config 2: binary re-routed to same route"/>
<!-- We change the binary name in a way that results in a
different route for the binary ROM request, which requires
restart of the child. The config version printed by the
new child will have a count of 1. -->
<init_config>
<parent-provides>
<service name="ROM"/> <service name="RAM"/>
<service name="CPU"/> <service name="PD"/>
<service name="LOG"/>
</parent-provides>
<start name="test">
<binary name="another_dummy"/>
<resource name="RAM" quantum="1M"/>
<config version="binary re-routed to other route"/>
<route>
<service name="ROM" unscoped_label="renamed_dummy">
<parent label="dummy"/> </service>
<any-service> <parent/> </any-service>
</route>
</start>
</init_config>
<expect_log string="[init -> test] config 1: binary re-routed to other route"/>
<sleep ms="100"/>
<message string="test RAM preservation"/>
<init_config>
<report init_ram="yes"/>
<resource name="RAM" preserve="2M"/>
<parent-provides>
<service name="ROM"/> <service name="RAM"/>
<service name="CPU"/> <service name="PD"/>
<service name="LOG"/>
</parent-provides>
<start name="regular">
<binary name="dummy"/>
<resource name="RAM" quantum="1M"/>
<config> <log string="regular component started"/> </config>
<route> <any-service> <parent/> </any-service> </route>
</start>
<start name="greedy">
<binary name="dummy"/>
<resource name="RAM" quantum="1G"/>
<config> <log string="greedy component started"/> </config>
<route> <any-service> <parent/> </any-service> </route>
</start>
</init_config>
<sleep ms="250"/>
<!-- wait until both children are started -->
<expect_init_state>
<node name="child"> <attribute name="name" value="regular"/> </node>
<node name="child"> <attribute name="name" value="greedy"/> </node>
</expect_init_state>
<expect_init_state>
<node name="ram"> <attribute name="avail" higher="2M"/> </node>
</expect_init_state>
<sleep ms="100"/>
</config>
<route>
<service name="Report"> <child name="report_rom"/> </service>
<service name="ROM" label="state"> <child name="report_rom"/> </service>
<service name="Timer"> <child name="timer"/> </service>
<any-service> <parent/> </any-service>
</route>
</start>
<start name="init">
<binary name="init"/>
<resource name="RAM" quantum="16M"/>
<configfile name="init.config"/>
<route>
<service name="ROM" label="init.config"> <child name="report_rom"/> </service>
<service name="Report"> <child name="report_rom"/> </service>
<service name="LOG"> <child name="test-init"/> </service>
<service name="Timer"> <child name="timer"/> </service>
<!-- alias for the binary as requested by the binary-name update test -->
<service name="ROM" label="another_dummy">
<parent label="dummy"/> </service>
<any-service> <parent/> </any-service>
</route>
</start>
</config>}
install_config $config
#
# Boot modules
#
set boot_modules { core ld.lib.so init timer report_rom test-init dummy }
build_boot_image $boot_modules
append qemu_args " -nographic "
run_genode_until {.*child "test-init" exited with exit value 0.*} 60