On Thursday, 28 April 2022 23:21:46 CEST Adam Lackorzynski wrote:
On Mon Apr 25, 2022 at 17:55:45 +0200, Paul Boddie wrote:
I didn't really understand this when looking through the existing code. It seemed that the memory was reserved, and that seemed to involve telling a region manager/mapper about it, such as in Remote_app_model where the prog_reserve_utcb_area method appears to attach an invalid dataspace (obtained from the reserved_area method) to an existing RM.
Generally, the RM API has a reserve_area call which should be used for this.
Thanks once again for the clarification! I suppose I should ask the more general question of whether the different L4Re mechanisms are documented in a manual or something of that nature. Although the reference documentation covers some of the concepts, along with APIs for use by applications, but not necessarily various framework-level abstractions (like Remote_app_model), it would be informative to be able to read something that discusses the techniques involved in building a system on top of Fiasco.
At the moment, I am just trying to persuade a program to run in a new task, which will hopefully only be a matter of properly initialising the details of the program environment. As well as paging in the appropriate segments of the binary in the right places, of course.
Paul