On Thu Aug 28, 2014 at 10:18:11 +0200, Valentin Hauner wrote:
Hi,
On 08/24/2014 11:27 PM, Adam Lackorzynski wrote:
I suggest that you first make sure you program behaves like it should with the default scheduler, and only then change over to your scheduler.
Thanks, that's a good idea.
Is there a simple way to set the name of the threads displayed in the JDB thread list from the L4Re system? I'm still creating my threads as described in my mail from August 23th and want to pass individual thread names to Fiasco. I've found a function named l4_debugger_set_object_name (e.g. moe is using it), but using it had no effect.
l4_debugger_set_object_name() is the function to use. Tried checking the return value?
Secondly, I've attached the modified l4_scheduler_run_thread_u function residing in ./l4/pkg/l4sys/include/scheduler.h. I've added an attribute named deadline to l4_sched_param_t and pass it via message register #5 to Fiasco. Initially, the second argument of the message tag for l4_ipc_call was set to 5 (5 registers to transfer), now I've set it to 6. Everything works, but I wonder where the information _which_ thread to run is passed to Fiasco? Message register #7 (previous: #6) contains information about the thread object, but it is not passed to Fiasco?
It is. It's the third parameter of the l4_msgtag (the 1) indicating this.
Adam