Ingo Oeser wrote:
> Adeos -> Client: Use virtual interrupt vectors and use your ipipe
> for it.
>
> Client -> Adeos: Provide Emission of this virtual interrupts in
> Adeos.
>
> Also some kind of shared memory and a "commit" for this memory is
> needed in Adeos. Allocation of this memory should be up to the
> requester of this memory, so Adeos doesn't need to wait for it
> and neither does the RTOS on the other end.
>
> With that primitives (plus some atomic magic ;-)) you can build
> non-sleeping messaging.
>
> Karim, is sth. like this planned or is it senseless?
All this looks like classic nanokernel capabilities, so this is
definitely within Adeos' reach. SPACE, for instance, defines an
abstraction called "Portals" which are used for cross-domain
communication and can be implemented using exceptions (in the
SPACE papers exception == interrupt).
Karim
===================================================
Karim Yaghmour
karim@opersys.com
Embedded and Real-Time Linux Expert
===================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/