Antonin,<br><br>Also, If you want to check out by code following what happens, the linux entry point is at: linux/kernel/arch/l4/kernel/main.c,<br><br>There you'll understand it clear,<br><br>Cheers,<br><br>Jorge<br><br>
<br><div class="gmail_quote">On Tue, Apr 1, 2008 at 11:10 AM, Jorge Torres <<a href="mailto:jorge.torres.maldonado@gmail.com">jorge.torres.maldonado@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Antonin,<br><br>You'll get a nicer look of priorities at any stage if you use the KDB, you can enter there at any time under wombat execution with Ctrl+k, you'll get KDB terminal output, then choose 'q' option, and you'll see whats going on, the two usermode Linux kernel threads are, L_timer and L_syscall. you can also tag your threads for the KDB env if you: L4_KDB_SetThreadName(L4_Myself(), "yourname");<br>
<br>All the best,<br><font color="#888888"><br>Jorge</font><div><div></div><div class="Wj3C7c"><br><br><div class="gmail_quote">On Tue, Apr 1, 2008 at 10:48 AM, Abi Nourai <<a href="mailto:anourai@ok-labs.com" target="_blank">anourai@ok-labs.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Antonin,<br>
<br>
I've noticed you're digging deeper into the belly of the beast that is<br>
OKL4 every day. Keep it up !<br>
<br>
I'll answer the easy questions for you immediately, and leave the more<br>
tricky ones for tomorrow.<br>
<br>
255 is highest priority. 0 is the lowest priority.<br>
<br>
Wombat actually consists of two threads, a thread that receives device<br>
interrupts (including timer ticks), and another thread that<br>
effectively does 99% of the work (sometimes called the worker thread<br>
or the syscall thread).<br>
<br>
FYI one reason for the existence of threads is so that the syscall<br>
thread (think of it as *the* linux kernel thread) can simulate<br>
disabling interrupts by telling the interrupt thread 'hey, when you<br>
get an interrupt, I don't want to know about it - so keep track of it<br>
internally, and deliver it to me by exreg only when I 'enable'<br>
interrupts' .<br>
<br>
In this model, the interrupt thread effectively servers fulfills the<br>
function of the hardware in a non-virtualized environment. It takes<br>
the interrupt trap, and delivers it to the OS (syscall thread) when<br>
interrupts are enabled. Hence the interrupt thread runs at a higher<br>
priority (100) than the syscall thread (99).<br>
<br>
Regards<br>
Abi<br>
<div><br>
On 02/04/2008, at 1:34 AM, Antonin SUBTIL wrote:<br>
</div><div><div></div><div>> Hello,<br>
><br>
><br>
> I had a look to Sconscript in Iguana, and here is my question :<br>
> "weaver = env.WeaverIguanaProgramServer(server_name =<br>
> "OKL4_HELLO_SERVER", priority=50)"<br>
> Are priorities on 0-255 ? Is 255 big or low priority?<br>
> What's Wombat priority? (If I'm trying to put some real-time server,<br>
> I should know it... yet I was able too find it)<br>
><br>
> Do anyone have a doc of this function? There's other arguments for<br>
> Linux I would like to understand...<br>
><br>
><br>
> Thanks<br>
><br>
><br>
> --<br>
> Antonin Subtil,<br>
> 35 rue Donissan<br>
> FR-33000 Bordeaux<br>
> +33 (0)6.77.40.17.69<br>
</div></div>> _______________________________________________<br>
> Developer mailing list<br>
> <a href="mailto:Developer@okl4.org" target="_blank">Developer@okl4.org</a><br>
> <a href="https://lists.okl4.org/mailman/listinfo/developer" target="_blank">https://lists.okl4.org/mailman/listinfo/developer</a><br>
<br>
<br>
_______________________________________________<br>
Developer mailing list<br>
<a href="mailto:Developer@okl4.org" target="_blank">Developer@okl4.org</a><br>
<a href="https://lists.okl4.org/mailman/listinfo/developer" target="_blank">https://lists.okl4.org/mailman/listinfo/developer</a><br>
</blockquote></div><br>
</div></div></blockquote></div><br>