Hi Denis,
> Now I understand. You mean, I can propagate information from the target
> component through its capability space. For a simple example, I could
> create an (unbound) IPC gate, store a pointer into the label, and use a
> capability space slot to reference it. I could take one from th
Hello Norman,
thank you for the confirmation of my thoughts and for the
correction/clarification of my misunderstandings.
> This won't work that easily. The AVL tree contains pointers that point
> to some place within the target's address space. A function call would
> ultimately de-reference t
Hi Denis,
> I created a simple figure [1] to illustrate my thoughts. [...]
>
> [1]
> https://github.com/702nADOS/genode-CheckpointRestore-SharedMemory/blob/b78f529818d01b42f0b35845e36e4e1d08b22eba/drawio_genode_capability_foc.png
the figure is good except for the detail that the capability map
Hello Norman,
you are right, it is quite complicated, but I think I understand the
capability concept in Genode with Fiasco.OC. Let me recap it:
I created a simple figure [1] to illustrate my thoughts. A component has
a capability map and a kernel-intern capability space. Each managed RPC
obje
Hello Denis,
let me start with the questions raised at the end of your posting:
> I also have some general questions about Genode capabilities in
> Fiasco.OC: In the Genode Foundations book, on page 37, there is a
> figure (figure 2) with an RPC object and its object identity. What is
> an object
Hello Norman,
thanks again for your explanation.
It sounds good, that I do not have to checkpoint the component-intern
session capabilities, if they are not used by the same component. What
about the locally created capabilities which are created during
Entrypoint creation?
In particular, whe
Hi Denis,
> The target application could create its own service with a root and
> session Rpc_object and manage requests through an Entrypoint. Although
> the Entrypoint creates new Capabilities through the PD session which the
> Checkpoint/Restore intercepts (PD::alloc_rpc_cap). The
> Checkpo
Hello Stefan,
thank you for the descriptive explanation :) I found out, that it does
not suffice to map the (kernel) Capability from the target application
to the Checkpoint/Restore application, because the Checkpoint/Restore
application knows only already existing (Genode) Capabilities (kcap a
Hello Denis,
On 09/21/2016 05:42 PM, Denis Huber wrote:
> Hello again,
>
> I have two small problems where I need some guidance from you :)
>
> 1. I am trying to understand the mechanism of l4_task_map [1]. Are the
> following thoughts correct?
>
> * The destination and source task cap (first
Hello again,
I have two small problems where I need some guidance from you :)
1. I am trying to understand the mechanism of l4_task_map [1]. Are the
following thoughts correct?
* The destination and source task cap (first 2 args of l4_task_map) can
be retrieved through Pd_session::native_pd()
Hello Norman,
thank you for your great answer. I will follow your advise and
virtualize all necessary services that a target component uses.
Kind regards,
Denis
On 09.09.2016 10:58, Norman Feske wrote:
> Hi Denis,
>
>> The child component shall be migrated from one ECU to another. The
>> Genod
Hi Denis,
> The child component shall be migrated from one ECU to another. The
> Genode system on the other ECU may have the Rpc_objects, which the child
> needs (e.g. shared dataspaces), but their object identities are
> different (e.g. other addresses in memory) or the Rpc_objects do not
> e
Hello Norman,
your approach sounds really good and promising. But I have a problem
when storing the Capabilities from the Cap Space of the child:
The child component shall be migrated from one ECU to another. The
Genode system on the other ECU may have the Rpc_objects, which the child
needs (e
Hello Denis,
> After a restore of a component the capability space shall be the "same"
> as before the checkpoint:
> 1) The capabilities after the restore shall point to corresponding
> object identities.
> 2) Also the capabilities after the restore shall be on the same slot
> (have the same ad
14 matches
Mail list logo
