[okl4-developer] Okl4_notify_wait() use

[Xavier.LANGELLIER at fr.thalesgroup.com]

Thanks for the answer,

In fact I changed Linux module to.
I rewrited the function cross_cell_write() to use message instead of
notification so I don't need any interrupt.
Should I change other things in this module to make message passing works?
(I suppose I don't need L_timer thread for synchronous messages) or is my
OKL4 cell incorrect?

I attach source of my OKL4 cell and the write function of the Linux module.

Xavier Langellier.


-----Message d'origine-----
De : developer-bounces at okl4.org [mailto:developer-bounces at okl4.org]De la
part de Hannes Payer
Envoyé : jeudi 28 mai 2009 16:44
À : developer at okl4.org
Objet : Re: [okl4-developer] Okl4_notify_wait() use



Hi,

the Linux L_timer thread expects asynchronous IPC communication so it throws
an error if you try to replace the IPC mechanism in the decrypt cell. The
decrypt cell sends asynchronous messages to Linux which trigger in the Linux
kernel an interrupt. This interrupt is handled in the cross cell demo kernel
module.

What you could do is the following: create a special thread in Linux which
waits for synchronous IPC messages and send the decrypt messages to this
thread. Don't forget to set up the capabilities for this communication.

Best,
Hannes


XavierL wrote:
> 
> Hi,
> 
> I'm trying to modify the decrypt cell example to test IPC communication
> and security policy with OKL4 and I have a problem.
> I replaced the asynchronous notification by synchronous IPC in the decrypt
> cell with okl4_message_wait() but with this function my system crashes at
> startup. (if I put okl4_notify_wait() i have no problem to start)
> 
> SETUP_SEGMENT: P:0x418a000..0x418b000, rwx:6, attrib:ff
> MAP_MEMORY: V:0x80215000 O:0x0 (P=418a000) S:0x1000 N:0xf A=0x3 R=0x6
> SETUP_SEGMENT: P:0x4cb8000..0x4cb9000, rwx:6, attrib:ff
> MAP_MEMORY: V:0x80208000 O:0x0 (P=4cb8000) S:0x1000 N:0x10 A=0x3 R=0x6
> CREATE IPC CAP: clist_ref=24, cap_slot=1, thread_ref=18c
> CREATE IPC CAP: clist_ref=138, cap_slot=1, thread_ref=48
> --- KD# User: L4_Rootserver abort()ed ---
> 
> What can I do to solve this problem?
> Thanks.
> 
> Xavier Langellier.
> 
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer
> 
> 

-- 
View this message in context:
http://n2.nabble.com/Okl4_notify_wait%28%29-use-tp2987813p2988065.html
Sent from the OKL4 Community Forum mailing list archive at Nabble.com.


_______________________________________________
Developer mailing list
Developer at okl4.org
https://lists.okl4.org/mailman/listinfo/developer

-------------- next part --------------
A non-text attachment was scrubbed...
Name: okl4_decrypt_cell.c
Type: application/octet-stream
Size: 767 bytes
Desc: not available
Url : http://lists.okl4.org/pipermail/developer/attachments/20090529/8b289048/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: okl4_linux_module.c
Type: application/octet-stream
Size: 456 bytes
Desc: not available
Url : http://lists.okl4.org/pipermail/developer/attachments/20090529/8b289048/attachment-0001.obj