Hi Kent, Thank you, your suggestions are helpful. I didn't realize we could use a separate CNode to save the reply cap with seL4_CNode_SaveCaller.
Do you think this is an acceptable use of seL4_Call? There is a sequence diagram here: https://github.com/sid-agrawal/OSmosis/blob/fd3aa0be5baa29684b9872c83e73de906665ea0f/images/seL4_Call_diagram.png. I want to make sure that we're not breaking any design principles by moving the reply cap to the root task and having the root task reply on behalf of Process 2. Best, Arya _______________________________________________ Devel mailing list -- devel@sel4.systems To unsubscribe send an email to devel-leave@sel4.systems
