From d4c22654e1b04c69aa238d4ba2347af0e10d515d Mon Sep 17 00:00:00 2001 From: Norman Feske Date: Tue, 12 Jun 2018 11:18:44 +0200 Subject: [PATCH] init test: reduce RAM demand of app/dummy The addition of the 'Cap_consumer' feature to app/dummy increased the static RAM demand of the component to a point where 1 MiB no longer suffices on sel4 (on this kernel, the base library uses a larger amount of statically allocated data compared to the others). The tweaks enable init.run and init_loop.run to work on sel4 on x86-64. --- repos/os/src/app/dummy/main.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/repos/os/src/app/dummy/main.cc b/repos/os/src/app/dummy/main.cc index 25784d0d76..9df645753e 100644 --- a/repos/os/src/app/dummy/main.cc +++ b/repos/os/src/app/dummy/main.cc @@ -36,7 +36,7 @@ struct Dummy::Log_service { Env &_env; - Heap _heap { _env.ram(), _env.rm() }; + Sliced_heap _heap { _env.ram(), _env.rm() }; bool const _verbose; @@ -208,7 +208,7 @@ struct Dummy::Cap_consumer * Statically allocate an array of RPC objects to avoid RAM allocations * as side effect during the cap-consume step. */ - static constexpr size_t MAX = 200; + static constexpr size_t MAX = 100; Constructible _objects[MAX];