Hi Valery,
> So yes, I could be able to create the shared memory area as a single
> managed dataspace in os2exec, and
> pass it to each userland process, at its initialization. Also, reserved
> sub-regions could also be
> implemented as managed dataspaces, which will go into needed (private or
>
Hi Valery,
> With a lookup function, maintaining
> such list manually is not required. So, do I need to care about
> releasing these backing store dataspaces manually, in case of a managed
> dataspace, or is it released automatically, when a managed dataspace is
> destroyed? Would be the need in
On 20.01.2018 02:05, Valery V. Sedletski via genode-main wrote:
Also, I'm wondering, are the stack area and the linker area still
implemented as managed dataspaces
on base-linux? So, they are the same as on other platforms, but they
only couldn't be nested? (As I understand,
dataspaces on Linux
On 20.01.2018 02:05, Valery V. Sedletski via genode-main wrote:
On 19.01.2018 23:33, Norman Feske wrote:
For reference, you may take
a look at the handling of the stack area, which is a 256MiB-sized
virtual-address space window that is sparsely populated with the stacks
of the component-local
On 19.01.2018 23:33, Norman Feske wrote:
Hi Valery,
I also know, that there is a support for managed dataspaces, or nested
region maps, which could be useful here (at least, for implementing a
shared memory area), but I also know, that nested region maps are not
supported on all platforms
Hi Valery,
> I also know, that there is a support for managed dataspaces, or nested
> region maps, which could be useful here (at least, for implementing a
> shared memory area), but I also know, that nested region maps are not
> supported on all platforms (like Genode/Linux). So, it would be,
>
