[okl4-developer] OKL4 v2.1.1

[Guanghui, Cheng]

Hello:
	I try to answer your question. Normally i think the behaviour of OKL4 v2.1.1
is reasonable and it should be that when the main thread exits all the threads 
you created before in the same application should be reclaimed by the system
so your threads are not in the queue.
	For OKL4 when the main app exits the system will have page fault which will
handled by iguana pager. The code is in iguana/server/src/iguana_server.c and 
function is iguana_ex_pagefault_impl().
	So I think the different behaviour for different OKL4 version is caused by
different iguana_ex_pagefault_impl(). I don't have the older OKl4 version than 
OKL4 2.1.1. But you can see what is happening about iguana_ex_pagefault_impl
in your two versions.
	Regards.
								Cheng Guanghui



loop in the end of L4 app and that means you are in the same environment
> In implementing an iguana server, I have noticed that when when i
> execute iguana with an example app eg. dining philisophers, once the
> app finishes, all of the threads I have created in my server are not
> on the queue. Yet when I put a loop at the end of the app, my threads
> are in the queue. In previous versions of OKL4, my threads are still
> on the scheduling queue, regardless of whether the iguana app i'm
> executing has finished, which should be the case. Is anyone able to
> shed any light as to why this is happening on version 2 of OKL4.
>
> Thanks
> -----------------------------------------------------
> Peter Nguyen
> Jacaranda Research Group
>
>
>
>
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer