Initialising Camkes App before another dependent Camkes app
Hi, I have a Camkes app (app1) which depends on another Camkes app (app2), which means my app1 must start only after app2 is completely initialized. For this currently I use a signal RPC wait in app1 and the corresponding RPC emit from app2 after app2 is completely initialized. Is there any other way in CamkES which will ensure that app1 starts only after app2 is completely initialized without using RPC signalling (emit and wait) ? How can this dependency be built ? Regards yk
Is there any other way in CamkES which will ensure that app1 starts only after app2 is completely initialized without using RPC signalling (emit and wait) ? How can this dependency be built ? Explicitly ordering components via signalling connectors is currently the main way for ordering component startups. We've considered adding better built in support for this in the past but it isn't currently on our upcoming roadmap.
Kent, I think this Q/A should be added to the FAQ at https://sel4.systems/Info/CAmkES/FAQ.pml Axel
Is there any other way in CamkES which will ensure that app1 starts only after app2 is completely initialized without using RPC signalling (emit and wait) ? How can this dependency be built ?
Explicitly ordering components via signalling connectors is currently the main way for ordering component startups. We've considered adding better built in support for this in the past but it isn't currently on our upcoming roadmap.
participants (3)
-
Axel Heider -
Mcleod, Kent (Data61, Kensington NSW) -
yogidk .