On 31 Aug 2015, at 18:57 , Raymond Jennings <[email protected]<mailto:[email protected]>> wrote:
Is there an easy way for one task to share address space with another task directly or does it have to go through the kernel/os and be emulated? there’s nothing stopping you mapping the same frame into two different address spaces (provided you have the rights to do so). I noticed that support for mapping memory is mostly low level assignment of physical frames to virtual frames via page tables, unlike Mach which uses memory objects. Yes, a microkernel’s job is to provide low-level abstractions. Mach-style memory objects isn’t one of them. See https://ssrg.nicta.com.au/publications/nictaabstracts/Elphinstone_Heiser_13.abstract.pml for an explanation of the philosophy. Gernot ________________________________ The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.
_______________________________________________ Devel mailing list [email protected] https://sel4.systems/lists/listinfo/devel
