ehmry/genode
ehmry/genode
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

init.run: lower timing sensitivity

Browse Source 
Instead of relying on init's delayed reporting, we explicitly force init
to produce a new report with the up-to-date child-RAM information.
This commit is contained in:
Norman Feske 2017-06-27 11:34:33 +02:00
parent ce01fd5321
commit a9da97bc4a
1 changed files with 22 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
repos/os/run/init.run
View File

@ -716,7 +716,6 @@ append config {
<!-- let child consume quota -->
<init_config version="consumed">
<report init_ram="yes" child_ram="yes" delay_ms="1500"/>
<parent-provides>
<service name="ROM"/>
<service name="CPU"/>
@ -736,7 +735,28 @@ append config {
</init_config>
<expect_log string="[init -> test] config 7: consume 2 MiB"/>
<expect_log string="[init -> test] consume 2M bytes of memory"/>
<sleep ms="1600"/>
<sleep ms="1000"/>
<!-- activate child_ram report -->
<init_config version="report consumed">
<report child_ram="yes"/>
<parent-provides>
<service name="ROM"/>
<service name="CPU"/>
<service name="PD"/>
<service name="LOG"/>
</parent-provides>
<default caps="100"/>
<start name="test">
<binary name="dummy"/>
<resource name="RAM" quantum="4M"/>
<config version="consume 2 MiB">
<handle_yield_requests/>
<consume_ram amount="2M"/>
</config>
<route> <any-service> <parent/> </any-service> </route>
</start>
</init_config>
<sleep ms="200"/>
<expect_init_state>
<node name="child"> <attribute name="name" value="test"/>
<node name="ram">