l4-hackers

l4-hackers@os.inf.tu-dresden.de

2 participants
2880 discussions

Re: l4-hackers Digest, Vol 59, Issue 14
by muhammad saufy 24 Mar '08

24 Mar '08

im using register based IPC operation to transfer string of more than two double word. (32 bit x 2). how IPC handle this? it's the register copy is loop twice to transfer the data or fiasco automatically copy that data to memory and send to the receiver? -saufy --- l4-hackers-request(a)os.inf.tu-dresden.de wrote: > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, > visit > > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body > 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it > is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. Re: Failed to create a new task (Adam > Lackorzynski) > 2. Re: porting L4linux on minix3. (Adam > Lackorzynski) > 3. Re: Compiling Fiasco UX problems under Fedora > 8 > (Adam Lackorzynski) > 4. Re: Compiling Fiasco UX problems under Fedora > 8 > (Olivier Landemarre) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 16 Mar 2008 22:37:39 +0100 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: Failed to create a new task > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: > <20080316213739.GB5636(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > Hi, > > Here's a diff of your program against a version that > works, with > comments: > > > --- x.c 2008-03-16 22:30:26.000000000 +0100 > +++ x.c 2008-03-16 22:30:26.000000000 +0100 > @@ -3,6 +3,7 @@ > #include <l4/sys/ipc.h> > #include <l4/rmgr/librmgr.h> > #include <l4/sigma0/sigma0.h> > +#include <l4/util/util.h> > > #include <stdio.h> > > @@ -41,14 +42,13 @@ > l4_addr_t map_area = 0x60000000; > l4_addr_t base; > l4_umword_t rcv_fpage; > - l4_umword_t snd_fpage; > > res = l4_ipc_call(SIGMA0_ID, > // thread id > L4_IPC_SHORT_MSG, > // send descriptor > SIGMA0_REQ_FPAGE_ANY, > // snd_dword0 > - snd_fpage, > // snd_dword1 > + l4_fpage(0, > L4_LOG2_PAGESIZE, 0, 0).fpage, // > snd_dword1 > L4_IPC_MAPMSG(map_area, > L4_WHOLE_ADDRESS_SPACE),// rcv_desc > - base, > // *rcv_dword0 > + &base, > // *rcv_dword0 > &rcv_fpage, > // *rcv_dword1 > timeout, > &result); > > Please fix compiler warnings, gcc is not issueing > them just for fun. > You've been giving an uninitialized value as an > address to l4_ipc_call, > so no wonder strange things happen. > > > @@ -75,26 +75,17 @@ > enter_kdebug("FAILED in l4_ipc_wait: > %d\n"); > } > > + while(1) { > l4_umword_t fault_addr = rcv_dword0 &~ > 0x00000003; //rcv_dword0 & 0xFFFFFFFC > > // mask lower bits for > (write/grant) flags? > l4_umword_t rw_addr = fault_addr | > 0x00000002; // mask the 2 nd lower bits to > set write flags > > - while(1) { > - > - l4_snd_fpage_t fpage; > - > - fpage.snd_base = rw_addr; // do wee need to > left shift the address??? > - > - //we can also use the function > l4_fpage(address, size, write, grant) > - fpage.fpage.fp.grant = 0; > - fpage.fpage.fp.write = 1; > - fpage.fpage.fp.page = rw_addr; > - fpage.fpage.fp.size = L4_LOG2_PAGESIZE; > //12 > + l4_touch_rw((void *)rw_addr, 1); > > Just to make sure the memory is really available. > > res = l4_ipc_reply_and_wait(src_id, > //dest_id > > L4_IPC_SHORT_FPAGE, //send descriptor > - > fpage.snd_base, //snd_dword0 > - > fpage.fpage.fpage, //snd_dword1 - might change > later to .fp > + rw_addr > & L4_PAGEMASK, //snd_dword0 > + > l4_fpage(rw_addr & L4_PAGEMASK, L4_LOG2_PAGESIZE, > L4_FPAGE_RW, L4_FPAGE_MAP).fpage, > > &src_id, //src_id > > L4_IPC_SHORT_MSG, //rcv descriptor > > &rcv_dword0, //rcv_dword0 > > I just aggregated the l4_fpage to the one line, more > compact. > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski > http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > Message: 2 > Date: Sun, 16 Mar 2008 22:54:59 +0100 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: porting L4linux on minix3. > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: > <20080316215459.GC5636(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Thu Mar 13, 2008 at 11:26:52 +0530, Pravin wrote: > > Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > wrote: > > > Hi, > > > > > > > > > On Mon Mar 10, 2008 at 19:52:53 +0530, Pravin > wrote: > > > > I wanted to ask a question regarding the > procedure followed in porting > > > > linux on L4 (L4Linux). > > > > I am exploring the possibility of porting > Linux on Minix3 on similar lines. > > > > > > I'd find it more interesting to see Minix on > L4. > > Well, I had not considered that possibility much > yet. > > I wanted to port Linux on minix to see if minix > can work as a virtualizer > > I am not very clear about the advantages of > porting minix of L4, > > can you put more light on it ? > > I think that L4 is much more of a virtualizer than > minix but that's just > my opinion. > === message truncated === ___________________________________________________________ Rise to the challenge for Sport Relief with Yahoo! For Good http://uk.promotions.yahoo.com/forgood/

2 1

Re: Failed to create a new task
by ahmad kamal 24 Mar '08

24 Mar '08

Here's a diff of your program against a version that works, with comments: --- x.c 2008-03-16 22:30:26.000000000 +0100 +++ x.c 2008-03-16 22:30:26.000000000 +0100 @@ -3,6 +3,7 @@ #include <l4/sys/ipc.h> #include <l4/rmgr/librmgr.h> #include <l4/sigma0/sigma0.h> +#include <l4/util/util.h> #include <stdio.h> @@ -41,14 +42,13 @@ l4_addr_t map_area = 0x60000000; l4_addr_t base; l4_umword_t rcv_fpage; - l4_umword_t snd_fpage; res = l4_ipc_call(SIGMA0_ID, // thread id L4_IPC_SHORT_MSG, // send descriptor SIGMA0_REQ_FPAGE_ANY, // snd_dword0 - snd_fpage, // snd_dword1 + l4_fpage(0, L4_LOG2_PAGESIZE, 0, 0).fpage, // snd_dword1 L4_IPC_MAPMSG(map_area, L4_WHOLE_ADDRESS_SPACE),// rcv_desc - base, // *rcv_dword0 + &base, // *rcv_dword0 &rcv_fpage, // *rcv_dword1 timeout, &result); Please fix compiler warnings, gcc is not issueing them just for fun. You've been giving an uninitialized value as an address to l4_ipc_call, so no wonder strange things happen. @@ -75,26 +75,17 @@ enter_kdebug("FAILED in l4_ipc_wait: %d\n"); } + while(1) { l4_umword_t fault_addr = rcv_dword0 &~ 0x00000003; //rcv_dword0 & 0xFFFFFFFC // mask lower bits for (write/grant) flags? l4_umword_t rw_addr = fault_addr | 0x00000002; // mask the 2 nd lower bits to set write flags - while(1) { - - l4_snd_fpage_t fpage; - - fpage.snd_base = rw_addr; // do wee need to left shift the address??? - - //we can also use the function l4_fpage(address, size, write, grant) - fpage.fpage.fp.grant = 0; - fpage.fpage.fp.write = 1; - fpage.fpage.fp.page = rw_addr; - fpage.fpage.fp.size = L4_LOG2_PAGESIZE; //12 + l4_touch_rw((void *)rw_addr, 1); Just to make sure the memory is really available. res = l4_ipc_reply_and_wait(src_id, //dest_id L4_IPC_SHORT_FPAGE, //send descriptor - fpage.snd_base, //snd_dword0 - fpage.fpage.fpage, //snd_dword1 - might change later to .fp + rw_addr & L4_PAGEMASK, //snd_dword0 + l4_fpage(rw_addr & L4_PAGEMASK, L4_LOG2_PAGESIZE, L4_FPAGE_RW, L4_FPAGE_MAP).fpage, &src_id, //src_id L4_IPC_SHORT_MSG, //rcv descriptor &rcv_dword0, //rcv_dword0 I just aggregated the l4_fpage to the one line, more compact. one more things, after task creation succeed, i'm a bit curious, why it doesn't run the new task, it runs the first thread n pager only. ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

2 1

Re: Failed to create a new task
by ahmad kamal 21 Mar '08

21 Mar '08

----- Original Message ---- From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> To: l4-hackers(a)os.inf.tu-dresden.de Sent: Monday, March 17, 2008 5:37:39 AM Subject: Re: Failed to create a new task Hi, Here's a diff of your program against a version that works, with comments: --- x.c 2008-03-16 22:30:26.000000000 +0100 +++ x.c 2008-03-16 22:30:26.000000000 +0100 @@ -3,6 +3,7 @@ #include <l4/sys/ipc.h> #include <l4/rmgr/librmgr.h> #include <l4/sigma0/sigma0.h> +#include <l4/util/util.h> #include <stdio.h> @@ -41,14 +42,13 @@ l4_addr_t map_area = 0x60000000; l4_addr_t base; l4_umword_t rcv_fpage; - l4_umword_t snd_fpage; res = l4_ipc_call(SIGMA0_ID, // thread id L4_IPC_SHORT_MSG, // send descriptor SIGMA0_REQ_FPAGE_ANY, // snd_dword0 - snd_fpage, // snd_dword1 + l4_fpage(0, L4_LOG2_PAGESIZE, 0, 0).fpage, // snd_dword1 L4_IPC_MAPMSG(map_area, L4_WHOLE_ADDRESS_SPACE),// rcv_desc - base, // *rcv_dword0 + &base, // *rcv_dword0 &rcv_fpage, // *rcv_dword1 timeout, &result); Please fix compiler warnings, gcc is not issueing them just for fun. You've been giving an uninitialized value as an address to l4_ipc_call, so no wonder strange things happen. @@ -75,26 +75,17 @@ enter_kdebug("FAILED in l4_ipc_wait: %d\n"); } + while(1) { l4_umword_t fault_addr = rcv_dword0 &~ 0x00000003; //rcv_dword0 & 0xFFFFFFFC // mask lower bits for (write/grant) flags? l4_umword_t rw_addr = fault_addr | 0x00000002; // mask the 2 nd lower bits to set write flags - while(1) { - - l4_snd_fpage_t fpage; - - fpage.snd_base = rw_addr; // do wee need to left shift the address??? - - //we can also use the function l4_fpage(address, size, write, grant) - fpage.fpage.fp.grant = 0; - fpage.fpage.fp.write = 1; - fpage.fpage.fp.page = rw_addr; - fpage.fpage.fp.size = L4_LOG2_PAGESIZE; //12 + l4_touch_rw((void *)rw_addr, 1); Just to make sure the memory is really available. res = l4_ipc_reply_and_wait(src_id, //dest_id L4_IPC_SHORT_FPAGE, //send descriptor - fpage.snd_base, //snd_dword0 - fpage.fpage.fpage, //snd_dword1 - might change later to .fp + rw_addr & L4_PAGEMASK, //snd_dword0 + l4_fpage(rw_addr & L4_PAGEMASK, L4_LOG2_PAGESIZE, L4_FPAGE_RW, L4_FPAGE_MAP).fpage, &src_id, //src_id L4_IPC_SHORT_MSG, //rcv descriptor &rcv_dword0, //rcv_dword0 I just aggregated the l4_fpage to the one line, more compact. >> thanks for the tips. ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping

1 0

Hacking L4 (Turaya VPN)
by Mohd Anuar Bin Mat Isa 18 Mar '08

18 Mar '08

1 0

L4_IPC_DOPE() understanding
by hazwan 17 Mar '08

17 Mar '08

Hello Currently im studying IPC for L4/fiasco. I opened the exercise solution from dresden and try to study the coding and its flow. So far, i manage to understand but there is one part that im not certain which is the L4_IPC_DOPE(). As stated in the exercise solution, the L4_IPC_DOPE is initiated as L4_IPC_DOPE(0,1) which is assigned to the l4_msgdope_t structure:- typedef struct { l4_msgdope_t size_dope; }message_t; <---there are other variables initialize in this structure but i just shorten it to the issue. message_t m; m->size_dope = L4_IPC_DOPE(0,1); I would like to know, what does this call (L4_IPC_DOPE) do and which file does this function is located. Is it in types.h? Hope anyone can assist me since im new in this field. Thanks. -- View this message in context: http://www.nabble.com/L4_IPC_DOPE%28%29-understanding-tp16091914p16091914.h… Sent from the L4 mailing list archive at Nabble.com.

3 2

Compiling Fiasco UX problems under Fedora 8
by Olivier.Landemarre＠utbm.fr 17 Mar '08

17 Mar '08

Hello I'm currently trying compil curent Fiasco UX under a Fedora 8 unfortunatly I get this: Linking test mapdb_t g++ -static -Wl,--gc-sections,-T/home/olivier/l4/kernel/fiasco/src/kernel.ux.ld \ -fno-implement-inlines -mpreferred-stack-boundary=2 -m32 -march=i686 -fno-defer-pop -freg-struct-return -g -Wall -W -Wno-parentheses -Wformat=2 -fno-stack-protector -ffunction-sections -gstabs+ -fno-rtti -fno-exceptions -fno-threadsafe-statics -Wno-non-virtual-dtor -O2 --param large-function-insns=10000 -fweb -finline-limit=10000 -frename-registers -fgcse-after-reload \ mapdb_t.o mapdb.o simpleio.o kernel_console.o panic.o warn.o buddy_alloc.o mem_layout.o mem_layout-ux.o per_cpu_data.o globals.o globals-ia32-ux.o loader.o vhw.o kip_init-ia32-amd64-ux.o kip_init-ux.o boot_info.o boot_info-ia32-amd64-ux.o boot_info-ux.o cmdline.o config.o config-ia32-ux.o config-ux.o jdb_symbol.o jdb_util.o tb_entry.o tb_entry-ia32-ux.o perf_cnt.o perf_cnt-ia32-ux.o jdb_tbuf.o x86desc.o emulation.o pic.o pic-ux.o usermode.o cpu-common.o cpu-ia32-ux.o cpu-ux.o trampoline.o cpu_lock.o cpu_lock-generic.o region.o entry_frame.o entry_frame-ia32-ux.o entry_frame-abs-timeout-hack.o kmem-ia32-ux.o kmem-ux.o mapped_alloc.o mem_unit-ux.o ram_quota.o kmem_alloc.o kmem_alloc-ia32-amd64-ux.o per_cpu_data_alloc.o slab_cache_anon.o kmem_slab_simple.o vmem_alloc.o vmem_alloc-ia32-ux.o vmem_alloc-ux.o paging.o paging-ia32-ux.o kmem_slab.o fpu_state.o fpu.o fpu-ia32-ux.o fpu-ux.o sched_context.o switch_lock.o timer.o timer-ia32-amd64-ux.o timer-ux.o timeout.o space_index.o obj_space.o cap_space.o mem_space.o mem_space-user.o mem_space-ia32-ux.o mem_space-ux.o space.o space-caps.o space-ux.o context.o context-ia32-ux.o context-ux.o helping_lock.o cap_space_alloc.o obj_space_alloc.o mapping-ia32-ux.o mapping.o mapping_tree.o libabi.a libjabi.a libdrivers.a libk.a libamm.a libcxx.a sighandler.o -o mapdb_t Running test mapdb_t ... /bin/sh: line 1: 24293 Erreur de segmentation ./mapdb_t --test --quiet > mapdb_t.out make[1]: *** [mapdb_t.ok] Erreur 139 make[1]: quittant le répertoire « /home/olivier/l4/kernel/fiasco/build » make: *** [all] Erreur 2 The Fiasco ux have been compiled but it is the same error I receive in console only an: Segmentation error Nothing more. any idea? Olivier --

3 6

porting L4linux on minix3.
by Pravin 16 Mar '08

16 Mar '08

Hi, I wanted to ask a question regarding the procedure followed in porting linux on L4 (L4Linux). I am exploring the possibility of porting Linux on Minix3 on similar lines. L4 and Minix3 are having similarities. So, in theory, with few modifications, L4Linux should be able to run on Minix also. I wanted some information regarding the approach taken in porting Linux on L4. If there are any documentation/links available about *. how to go in case of these kind of porting of linux on another kernel? *. and how L4linux works internally? *. which architecture dependent code of Linux has been modified and why? then they will be quite helpful to me. -- Thanks and Regards, Pravin Shinde

3 5

Re: Failed to create a new task
by ahmad kamal 16 Mar '08

16 Mar '08

here is my latest source codes. unfortunately i got this new error: KERNEL: nothing mapped: (Mem_space) from [4]: 00005000 size: 00001000 to [5] #include <l4/sys/types.h> #include <l4/sys/syscalls.h> #include <l4/sys/ipc.h> #include <l4/rmgr/librmgr.h> #include <l4/sigma0/sigma0.h> #include <stdio.h> #define STACK_SIZE 4096 char stack001[STACK_SIZE]; char stack002[STACK_SIZE]; static void new_task_fn(void) { l4_threadid_t cur_id = l4_myself(); enter_kdebug("new_task_fn\n"); while(1) { printf("Currently running in task id: %d, thread no: %d\n", cur_id.id.task, cur_id.id.lthread); } } static void page_handler(void) { int res; l4_timeout_t timeout = L4_IPC_NEVER; l4_msgdope_t result; /*int i = 0; while(1) { printf("page_handler, taskno: %d, thread id: %d\n", l4_myself().id.task, l4_myself().id.lthread); if (i%10 == 0) { //l4_thread_switch(new_task); l4_threadid_t switch_tid = l4_myself(); switch_tid.id.lthread -= 1; l4_thread_switch(switch_tid); enter_kdebug("i/10\n"); } i++; }*/ l4_addr_t map_area = 0x60000000; l4_addr_t base; l4_umword_t rcv_fpage; l4_umword_t snd_fpage; res = l4_ipc_call(SIGMA0_ID, // thread id L4_IPC_SHORT_MSG, // send descriptor SIGMA0_REQ_FPAGE_ANY, // snd_dword0 snd_fpage, // snd_dword1 L4_IPC_MAPMSG(map_area, L4_WHOLE_ADDRESS_SPACE),// rcv_desc base, // *rcv_dword0 &rcv_fpage, // *rcv_dword1 timeout, &result); if (res) { printf("Error in ipc_call, mapping, err no: %d\n", res); enter_kdebug("Error in ipc_call\n"); } else { enter_kdebug("successfully map fpage\n"); } l4_threadid_t src_id; // a faulting thread l4_umword_t rcv_dword0; // the faulting address l4_umword_t rcv_dword1; // the faulting eip res = l4_ipc_wait(&src_id, L4_IPC_SHORT_MSG, &rcv_dword0, &rcv_dword1, timeout, &result); enter_kdebug("Page handler handle faulting thread\n"); if (res) { //res == 0 ? SUCCESS : FAILED printf("Error occurs in l4_ipc_wait: %d\n", res); enter_kdebug("FAILED in l4_ipc_wait: %d\n"); } l4_umword_t fault_addr = rcv_dword0 &~ 0x00000003; //rcv_dword0 & 0xFFFFFFFC // mask lower bits for (write/grant) flags? l4_umword_t rw_addr = fault_addr | 0x00000002; // mask the 2 nd lower bits to set write flags while(1) { l4_snd_fpage_t fpage; fpage.snd_base = rw_addr; // do wee need to left shift the address??? //we can also use the function l4_fpage(address, size, write, grant) fpage.fpage.fp.grant = 0; fpage.fpage.fp.write = 1; fpage.fpage.fp.page = rw_addr; fpage.fpage.fp.size = L4_LOG2_PAGESIZE; //12 res = l4_ipc_reply_and_wait(src_id, //dest_id L4_IPC_SHORT_FPAGE, //send descriptor fpage.snd_base, //snd_dword0 fpage.fpage.fpage, //snd_dword1 - might change later to .fp &src_id, //src_id L4_IPC_SHORT_MSG, //rcv descriptor &rcv_dword0, //rcv_dword0 &rcv_dword1, //rcv_dword1 L4_IPC_NEVER, //timeout &result); //result if(res) {//res == 0 ? SUCCESS : FAILED printf("FAILED in reply wait: %d\n", res); enter_kdebug("FAILED in reply wait\n"); } } } int main(void) { // 1st thread l4_threadid_t first_tid; l4_umword_t first_eip, first_esp; l4_threadid_t preempter, pager_tid; l4_umword_t old_eflags, old_eip, old_esp; first_tid = l4_myself(); first_eip = first_esp = 0xFFFFFFFF; preempter = pager_tid = L4_INVALID_ID; l4_thread_ex_regs(first_tid, first_eip, first_esp, &preempter, &pager_tid, &old_eflags, &old_eip, &old_esp); // 2nd thread l4_threadid_t sec_tid; l4_umword_t sec_eip, sec_esp; l4_threadid_t sec_pager_tid; sec_tid = first_tid; sec_tid.id.lthread += 1; sec_eip = (l4_umword_t)&page_handler; sec_esp = (l4_umword_t)&stack001[STACK_SIZE-1]; sec_pager_tid = pager_tid; printf("sec_tid, task no: %d, threadid: %d\n eip: %lx esp: %lx\n", sec_tid.id.task, sec_tid.id.lthread, sec_eip, sec_esp); l4_thread_ex_regs(sec_tid, sec_eip, sec_esp, &preempter, &sec_pager_tid, &old_eflags, &old_eip, &old_esp); // new task l4_taskid_t new_task; l4_umword_t mcp; //max controlled priority, min[creator_mcp, specified_mcp] l4_umword_t new_esp; //initial stack pointer for thread000 if new task - active l4_umword_t new_eip; //entry point for thread000 if new task - active l4_threadid_t new_task_pgr; //L4_NIL_ID - inactive task. /* l4_task_new - create/delete task * create inactive/active task * active task - create a new address space with 128 threads and thread000 is started * inactive task - occupies no resources, no address space and no threads * task can be deleted by its chief or higher-level chief */ new_task = first_tid; new_task.id.task += 1; mcp = (l4_umword_t)255; new_esp = (l4_umword_t)&stack002[STACK_SIZE-1]; new_eip = (l4_umword_t)&new_task_fn; new_task_pgr = sec_tid; //printf("new task, task no: %d, threadid: %d\n", new_task.id.task, new_task.id.lthread); printf("new pager, task no: %d, threadid: %d\n eip: %lx esp: %lx\n", new_task_pgr.id.task, new_task_pgr.id.lthread, new_eip, new_esp); if (!rmgr_init()) { // zero - true/error enter_kdebug("Failed in init RMGR\n"); return 0; } if (rmgr_get_task(new_task.id.task)) { enter_kdebug("Failed in get the right of task creation\n"); return 0; } new_task = l4_task_new(new_task, mcp, new_esp, new_eip, new_task_pgr); // l4_umword_t esp2 = 0x40000000 + (new_task.id.task << 20 | new_task.id.lthread << L4_PAGESHIFT) + L4_PAGESIZE; // l4_taskid_t new_task2 = l4_task_new(new_task, 255, esp2, (l4_umword_t)&new_task_fn, new_task_pgr); l4_threadid_t nil_tid = L4_NIL_ID; if (new_task.id.task == nil_tid.id.task) { enter_kdebug("Failed to create new task\n"); return 0; } else { printf("new task, task no: %d, threadid: %d\n", new_task.id.task, new_task.id.lthread); enter_kdebug("new task is succesfully created\n"); } //continue running thread0 int i = 0; while(1) { /*if (i%10 == 0) { //l4_thread_switch(new_task); //l4_thread_switch(sec_tid); //enter_kdebug("i/10\n"); }*/ printf("Continue running thread, task id: %d, thread no: %d\n", first_tid.id.task, first_tid.id.lthread); i++; } return 0; } ----- Original Message ---- From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> To: l4-hackers(a)os.inf.tu-dresden.de Sent: Monday, March 10, 2008 7:43:17 AM Subject: Re: Failed to create a new task Hi, On Sat Mar 08, 2008 at 22:54:30 -0800, ahmad kamal wrote: > I've failed to create a new task: > > the l4_task_new in my code return 0 (L4_NIL_ID) which is indicate > either the task was create as inactive or didn't create at all. Good you have posted the source. I think the problem is that you need to get the right for creating new tasks first. Depending whether simple_ts is started or not you need to use l4ts_allocate_task2(0, &tid) or rmgr_get_task(num) before the l4_task_new. Then it should work. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/ _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

2 1

Error handling for reply in dice
by Marc Chaland 13 Mar '08

13 Mar '08

Hi, I implemented an IDL with a allow_reply_only method : start. When client calls this, it is blocked until server decides to send reply. This works fine in general. But when client thread disapears after call, I cannot get error code from reply function on server side. I tried to use error_function, but it is not called. Is there another way to get this info ? Regards Marc

2 5

error running fiasco-ux
by Lucyantie Mazalan 12 Mar '08

12 Mar '08

Hi all, need some help here. I've been trying to use my fiasco-ux to load my module. Thing is, when I try to run the module with: ~/fiasco-ux# ./fiasco -l hello Killed This is what I got. I have copied down the needed binaries ( fiasco, irq0, sigma0, roottask ) in the fiasco-ux directory. Please help. Thanks. Regards, Lucille. ------------------------------------------------------------------ - - DISCLAIMER: This e-mail (including any attachments) may contain confidential information. If you are not the intended recipient, you are hereby notified that any dealing, review, distribution, printing, copying or use of this e-mail is strictly prohibited. If you have received this email in error, please notify the sender or MIMOS Berhad immediately and delete the original message. Opinions, conclusions and other information in this e-mail that do not relate to the official business of MIMOS Berhad and/or its subsidiaries shall be understood as neither given nor endorsed by MIMOS Berhad and/or its subsidiaries and neither MIMOS Berhad nor its subsidiaries accepts responsibility for the same. All liability arising from or in connection with computer viruses and/or corrupted e-mails is excluded to the fullest extent permitted by law.

2 1

run-l4 - to start another task
by ahmad kamal 12 Mar '08

12 Mar '08

hi all, i've been trying to load another l4 task using run-l4 in l4linux, but i've got error the error is -8(cannot a find module) here is my conf file #launch.conf verbose 0 modpath "(hd0,2)/boot/l4app" task "hello" and here is the cmd i run: run-l4 --fprov "BMODFS" "(hd0,2)/boot/l4app/launch.conf" here are few question: do i need to load run-l4 during boot time, in other words do i need to define it in menu.lst? do i need to load the task i would like to call using run-l4 during boot time? Regards, Ahmad Kamal ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

2 1

about L4ka build
by ANPING WANG 12 Mar '08

12 Mar '08

sorry could you give me some help about the L4ka build i have so problem when compile the L4ka user-level application i do step by step from http://l4ka.org/projects/pistachio/ia32/gettingstarted.php when build user-level code there is a problem root@wap-desktop:~/l4ka-pistachio/ia32-user-build# ../user/configure --prefix=../ia32-user-install --with-kerneldir=../ia32-kernel-build configure: error: can not find sources in ../user or .. root@wap-desktop:~/l4ka-pistachio/ia32-user-build# that show there is no source is any thing i should to fix it thinks a lot

1 0

Re: l4-hackers Digest, Vol 59, Issue 7
by Valery V. Sedletski 12 Mar '08

12 Mar '08

On Mon, 10 Mar 2008 12:00:02 +0100, Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> wrote: >> mnt/data1/src/drops/build/include/x86/l4/util/util.h:84 >> 4019e0: 83 0a 00 orl $0x0,(%edx) >> >> So it is the function: >> >> /** Touch data areas to force mapping read-write */ >> static inline void >> l4_touch_rw(const void*addr, unsigned size) >> { >> const char *bptr, *eptr; >> >> bptr = (const char*)(((unsigned)addr) & L4_PAGEMASK); >> eptr = (const char*)(((unsigned)addr+size-1) & L4_PAGEMASK); >> for(;bptr<=eptr;bptr+=L4_PAGESIZE){ >> asm volatile("or $0,%0 \n" >> : >> : "m" (*(const unsigned*)bptr) >> ); >> } >> } >> >> And instruction "orl" is inside "asm volatile" block. >> >> So, this function touches an area (BSS in this case) to make mapping read-write. But >> why this does not work? > >I have no idea, I've never seen this before. Is there the possibility to >update the source so that we can work on the same basis? > OK, I'll try to update the sources. (First I must update a svn client as my svn client under Linux is too old (I have Red Hat 9.0)). I used an old sources from CVS, not newer SVN sources. Thank you. WBR, Valery

1 0

thread.id.lthread inquiry
by hazwan 11 Mar '08

11 Mar '08

hello Currently im studying on how to build an application using fiasco/L4. Im very new to this subject and it requires me lots of fundemental issues concerning this topic. I need to go deep in the code ie:-the roottask/sigma0/kernel implementation. So far i had try some steps to aquire answers. One of them is by printing out a thread which is initialize as l4_threadid_t. I didnt call any sys calls (l4_myself() to that particular thread. So, what i had done is :- l4_threadid_t thread; l4_threadid_t pager; printf("%x\n", thread.id.lthread); printf("%x\n", pager.id.lthread); when i print this out, the thread will print out its id as 34 in hex. Meanwhile the pager will identify as 0 for its lthread id. The question is why is this happening? If i turn back around the code, it will still print out the thread as 34 for its id and pager is 0. Is it reading some garbage value from the memory or the roottask/sigma0/kernel will identify it as 34 only if we didnt initialize any system calls. I need to study this in depth due to my yearly project which highly involves fiasco/L4 as its platform. If it is applicable, can anyone show me which file(header/*.c etc..) that locates the number of 34 happens. Thanks. p/s: Im also thinking that this is a silly question as well. :-P -- View this message in context: http://www.nabble.com/thread.id.lthread-inquiry-tp15950571p15950571.html Sent from the L4 mailing list archive at Nabble.com.

2 1

Re: Failed to create a new task
by ahmad kamal 10 Mar '08

10 Mar '08

is rmgr a roottask? why we need to rmgr_get_task(int taskno)? ----- Original Message ---- From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> To: l4-hackers(a)os.inf.tu-dresden.de Sent: Monday, March 10, 2008 7:43:17 AM Subject: Re: Failed to create a new task Hi, On Sat Mar 08, 2008 at 22:54:30 -0800, ahmad kamal wrote: > I've failed to create a new task: > > the l4_task_new in my code return 0 (L4_NIL_ID) which is indicate > either the task was create as inactive or didn't create at all. Good you have posted the source. I think the problem is that you need to get the right for creating new tasks first. Depending whether simple_ts is started or not you need to use l4ts_allocate_task2(0, &tid) or rmgr_get_task(num) before the l4_task_new. Then it should work. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/ _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping

2 1

Failed to create a new task
by ahmad kamal 10 Mar '08

10 Mar '08

Hi all, I've failed to create a new task: the l4_task_new in my code return 0 (L4_NIL_ID) which is indicate either the task was create as inactive or didn't create at all. here is my code: #include <l4/sys/types.h> #include <l4/sys/syscalls.h> #include <l4/sys/ipc.h> #include <stdio.h> #define STACK_SIZE 4096 char stack001[STACK_SIZE]; char stack002[STACK_SIZE]; #define SIGMA0_TID 0x04 static void new_task_fn(void) { l4_threadid_t cur_id = l4_myself(); enter_kdebug("new_task_fn\n"); while(1) { printf("Currently running in task id: %d, thread no: %d\n", cur_id.id.task, cur_id.id.lthread); } } static void page_handler(void) { int res; l4_threadid_t src_id; // a faulting thread l4_umword_t rcv_dword0; // the faulting address l4_umword_t rcv_dword1; // the faulting eip l4_timeout_t timeout; l4_msgdope_t result; enter_kdebug("Page handler handle faulting thread\n"); timeout = L4_IPC_NEVER; res = l4_ipc_wait(&src_id, L4_IPC_SHORT_MSG, &rcv_dword0, &rcv_dword1, timeout, &result); enter_kdebug("Page handler handle faulting thread\n"); if (res) { //res == 0 ? SUCCESS : FAILED printf("Error occurs in l4_ipc_wait: %d\n", res); enter_kdebug("FAILED in l4_ipc_wait: %d\n"); } l4_umword_t fault_addr = rcv_dword0 &~ 0x00000003; //rcv_dword0 & 0xFFFFFFFC // mask lower bits for (write/grant) flags? l4_umword_t rw_addr = fault_addr | 0x00000002; // mask the 2 nd lower bits to set write flags while(1) { l4_snd_fpage_t fpage; fpage.snd_base = rw_addr; // do wee need to left shift the address??? //we can also use the function l4_fpage(address, size, write, grant) fpage.fpage.fp.grant = 0; fpage.fpage.fp.write = 1; fpage.fpage.fp.page = rw_addr; fpage.fpage.fp.size = 12; //TODO: search the constant res = l4_ipc_reply_and_wait(src_id, //dest_id L4_IPC_SHORT_FPAGE, //send descriptor fpage.snd_base, //snd_dword0 fpage.fpage.fpage, //snd_dword1 - might change later to .fp &src_id, //src_id L4_IPC_SHORT_MSG, //rcv descriptor &rcv_dword0, //rcv_dword0 &rcv_dword1, //rcv_dword1 L4_IPC_NEVER, //timeout &result); //result if(res) {//res == 0 ? SUCCESS : FAILED printf("FAILED in reply wait: %d\n", res); enter_kdebug("FAILED in reply wait\n"); } } } int main(void) { // 1st thread l4_threadid_t first_tid; l4_umword_t first_eip, first_esp; l4_threadid_t preempter, pager_tid; l4_umword_t old_eflags, old_eip, old_esp; first_tid = l4_myself(); first_eip = first_esp = 0xFFFFFFFF; preempter = pager_tid = L4_INVALID_ID; l4_thread_ex_regs(first_tid, first_eip, first_esp, &preempter, &pager_tid, &old_eflags, &old_eip, &old_esp); // 2nd thread l4_threadid_t sec_tid; l4_umword_t sec_eip, sec_esp; l4_threadid_t sec_pager_tid; sec_tid = first_tid; sec_tid.id.lthread += 1; sec_eip = (l4_umword_t)&page_handler; sec_esp = (l4_umword_t)&stack001[STACK_SIZE-1]; sec_pager_tid = pager_tid; printf("sec_tid, task no: %d, threadid: %d\n eip: %lx esp: %lx\n", sec_tid.id.task, sec_tid.id.lthread, sec_eip, sec_esp); l4_thread_ex_regs(sec_tid, sec_eip, sec_esp, &preempter, &sec_pager_tid, &old_eflags, &old_eip, &old_esp); // new task l4_taskid_t new_task; l4_umword_t mcp; //max controlled priority, min[creator_mcp, specified_mcp] l4_umword_t new_esp; //initial stack pointer for thread000 if new task - active l4_umword_t new_eip; //entry point for thread000 if new task - active l4_threadid_t new_task_pgr; //L4_NIL_ID - inactive task. /* l4_task_new - create/delete task * create inactive/active task * active task - create a new address space with 128 threads and thread000 is started * inactive task - occupies no resources, no address space and no threads * task can be deleted by its chief or higher-level chief */ new_task = first_tid; new_task.id.task += 1; mcp = (l4_umword_t)255; new_esp = (l4_umword_t)&stack002[STACK_SIZE-1]; new_eip = (l4_umword_t)&new_task_fn; new_task_pgr = sec_tid; //printf("new task, task no: %d, threadid: %d\n", new_task.id.task, new_task.id.lthread); printf("new pager, task no: %d, threadid: %d\n eip: %lx esp: %lx\n", new_task_pgr.id.task, new_task_pgr.id.lthread, new_eip, new_esp); new_task = l4_task_new(new_task, mcp, new_esp, new_eip, new_task_pgr); printf("new task, task no: %d, threadid: %d\n", new_task.id.task, new_task.id.lthread); l4_threadid_t nil_tid = L4_NIL_ID; if (new_task.id.task == nil_tid.id.task) { enter_kdebug("Failed to create new task\n"); } //continue running thread0 int i = 0; while(1) { if (i%10 == 0) { l4_thread_switch(new_task); enter_kdebug("i/10\n"); } printf("Continue running thread, task id: %d, thread no: %d\n", first_tid.id.task, first_tid.id.lthread); i++; } return 0; } any idea? ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

2 1

Re: l4-hackers Digest, Vol 59, Issue 7
by Valery V. Sedletski 10 Mar '08

10 Mar '08

On Sat, 08 Mar 2008 12:00:01 +0100, l4-hackers-request(a)os.inf.tu-dresden.de wrote: > > Quite old but anyway. It would be interesting to know where 0x004019e0 > is in the vmlinux binary. So please look up the address with > objdump -ld vmlinux > and see what .c files and which line in there are mentioned around the > address. Then please look it up in the source and show me the function > where this happens. As 2.6.17 is quite old it probably won't match with > the current source I use. > It is around: mnt/data1/src/drops/build/include/x86/l4/util/util.h:84 4019e0: 83 0a 00 orl $0x0,(%edx) So it is the function: /** Touch data areas to force mapping read-write */ static inline void l4_touch_rw(const void*addr, unsigned size) { const char *bptr, *eptr; bptr = (const char*)(((unsigned)addr) & L4_PAGEMASK); eptr = (const char*)(((unsigned)addr+size-1) & L4_PAGEMASK); for(;bptr<=eptr;bptr+=L4_PAGESIZE){ asm volatile("or $0,%0 \n" : : "m" (*(const unsigned*)bptr) ); } } And instruction "orl" is inside "asm volatile" block. So, this function touches an area (BSS in this case) to make mapping read-write. But why this does not work? > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ >

2 1

L4Linux: pagefault at the beginning of BSS area
by Valery V. Sedletski 08 Mar '08

08 Mar '08

hi all! I compiled myself l4linux and tried to start it, but something goes wrong. When the linux server starts, a page fault occurs at the beginning of its BSS area. The log is the following: [===============================================] L4 Bootstrapper Scaning (nd)/tftpboot/drops/bin/x86_586/l4v2/fiasco -nowait -nokdb -serial -jdb_never_stop -tbuf_entries=32768 -jdb_cmd=JH Scaning (nd)/tftpboot/drops/bin/x86_586/l4v2/sigma0 Scaning (nd)/tftpboot/drops/bin/x86_586/l4v2/roottask task sigma0 boot_priority 0xA0 task roottask boot_priority 0xA0 task modname "names" boot_priority 0xA0 task modname "log" boot_priority 0xA1 task modname "dm_phys" boot_priority 0xA0 task modname "simple_ts" boot_priority 0xA0 task modname "l4io" allow_cli boot_priority 0xA3 task modname "rtc" allow_cli task modname "l4con" allow_cli task modname "l4exec" boot_priority 0xA0 task modname "loader" allow_cli boot_priority 0xA0 task modname "vmlinuz26" task modname "bmodfs" attached 4 modules Relocated mbi to [0x64000-0x64a22] Loading (nd)/tftpboot/drops/bin/x86_586/l4v2/fiasco Loading (nd)/tftpboot/drops/bin/x86_586/l4v2/sigma0 Loading (nd)/tftpboot/drops/bin/x86_586/l4v2/roottask find kernel info page... found kernel info page at 0x1000 API Version: (87) experimental Sigma0 config ip:00090000 sp:00105100 [00090000-00096d44] Roottask config ip:00120000 sp:00108528 [00120000-002bda14] [00001000-00002000) (nd)/tftpboot/drops/bin/x86_586/l4v2/fiasco [00002000-00055980) (nd)/tftpboot/drops/bin/x86_586/l4v2/fiasco [00055980-0005e290) (nd)/tftpboot/drops/bin/x86_586/l4v2/fiasco [0005f000-00062230) (nd)/tftpboot/drops/bin/x86_586/l4v2/fiasco [00062240-00064000) (nd)/tftpboot/drops/bin/x86_586/l4v2/fiasco [00090000-000948dc) (nd)/tftpboot/drops/bin/x86_586/l4v2/sigma0 [000958e0-00096d44) (nd)/tftpboot/drops/bin/x86_586/l4v2/sigma0 [0009f000-00100000) BIOS area [00100000-00108764) bootstrap [00120000-00133190) (nd)/tftpboot/drops/bin/x86_586/l4v2/roottask [00134000-0013e67e) (nd)/tftpboot/drops/bin/x86_586/l4v2/roottask [0013f680-002bda14) (nd)/tftpboot/drops/bin/x86_586/l4v2/roottask [00300000-00301a40) (nd)/tftpboot/drops/bin/x86_586/l4v2/fiasco [00302000-0038f408) (nd)/tftpboot/drops/bin/x86_586/l4v2/fiasco [02000000-036b3174) Modules Memory [10000000-ffffffff) Deep Space Starting kernel (nd)/tftpboot/drops/bin/x86_586/l4v2/fiasco at 00300878 [1;32mWelcome to Fiasco(ia32)! [0;32mDD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Mon Aug 28 08:34:51 2006 compiled with gcc 3.3.1 for Intel Pentium[0m [31mPerformance-critical config option(s) detected: CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off [m Enabling special fully nested mode for PIC Using the PIT (i8254) on IRQ 0 for scheduling Absolute KIP Syscalls using: Sysenter CPU: GenuineIntel (6:3:3:0) Model: Unknown CPU at 735 MHz 8 KB L1 I Cache (4-way associative, 32 bytes per line) Freeing init code/data: 20480 bytes (5 pages) [6nSIGMA0: Hello! Found Fiasco: KIP syscalls: yes. Allocated 132kB for maintenance structures. Roottask. Command line found: "(nd)/tftpboot/drops/bin/x86_586/l4v2/roottask task sigma0 boot_priority 0xA0 task roottask boot_priority 0xA0 task modname "names" boot_priority 0xA0 task modname "log" boot_priority 0xA1 task modname "dm_phys" boot_priority 0xA0 task modname "simple_ts" boot_priority 0xA0 task modname "l4io" allow_cli boot_priority 0xA3 task modname "rtc" allow_cli task modname "l4con" allow_cli task modname "l4exec" boot_priority 0xA0 task modname "loader" allow_cli boot_priority 0xA0 task modname "vmlinuz26" task modname "bmodfs" attached 4 modules" 261759kB ( 255MB) total RAM (reported by bootloader) 215872kB ( 211MB) received RAM from Sigma0 24376kB ( 24MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 <!2> 3 4 5 6 7 8 9 A B C D E F ] Roottask: Parsing command line config. configured task 0x02 (): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x04 (): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (names): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (log): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a1 small:ff mods:0 configured task 0x00 (dm_phys): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (simple_ts): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (l4io): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:a3 small:ff mods:0 configured task 0x00 (rtc): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:10 small:ff mods:0 configured task 0x00 (l4con): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:10 small:ff mods:0 configured task 0x00 (l4exec): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (loader): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (vmlinuz26): configured task 0x00 (bmodfs): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:10 small:ff mods:4 Roottask: Loading 14 modules. [36m#05: loading "(nd)/tftpboot/drops/bin/x86_586/l4v2/names" [m from [[37m02085000[m-[37m0208e174[m] to [002d0000-002d616a][002d7000-002e3000] entry at [37m0005f384[m via trampoline page code [36m#06: loading "(nd)/tftpboot/drops/bin/x86_586/l4v2/log --prio 0xA1" [m from [[37m0208f000[m-[37m02097354[m] to [00400000-00406c8a][00407000-00439890] entry at [37m00060390[m via trampoline page code [36m#07: loading "(nd)/tftpboot/drops/bin/x86_586/l4v2/dm_phys --isa=0x00800000" [m from [[37m02098000[m-[37m020ac174[m] to [01500000-01511dea][01512000-0151c000] entry at [37m00061398[m via trampoline page code [36m#08: loading "(nd)/tftpboot/drops/bin/x86_586/l4v2/simple_ts -t 900" [m from [[37m020ad000[m-[37m020b7354[m] to [01400000-0140854a][01409000-0141b050] entry at [37m00062390[m via trampoline page code [36m#09: loading "(nd)/tftpboot/drops/bin/x86_586/l4v2/rtc" [m from [[37m020b8000[m-[37m020bf174[m] to [01080000-01084200][01085000-0108a000] entry at [37m00063384[m via trampoline page code [36m#0a: loading "(nd)/tftpboot/drops/bin/x86_586/l4v2/l4io --noirq" [m from [[37m020c0000[m-[37m0210f174[m] to [00b80000-00ba2a32][00ba3000-00bf0000] entry at [37m0006538c[m via trampoline page code [36m#0b: loading "(nd)/tftpboot/drops/bin/x86_586/l4v2/bmodfs" [m from [[37m02110000[m-[37m02128174[m] to [01220000-012354ee][01236000-01256000] passing module (nd)/tftpboot/cfg/l4linux26.cfg [ 02129000-021290d2 ] passing module drops/bin/x86_586/l4v2/libloader.s.so [ 0212a000-021c8755 ] passing module boot/drops/bin/x86_586/l4v2/vmlinuz26 [ 021c9000-03205e3b ] passing module (nd)/tftpboot/drops/bin/rd/initrd.gz [ 03206000-03606000 ] entry at [37m00066470[m via trampoline page code [36m#0c: loading "(nd)/tftpboot/drops/bin/x86_586/l4v2/l4con --l4io" [m from [[37m03606000[m-[37m0365a174[m] to [00b00000-00b4d35e][00b4e000-00b79000] entry at [37m0006738c[m via trampoline page code [36m#0d: loading "(nd)/tftpboot/drops/bin/x86_586/l4v2/l4exec" [m from [[37m0365b000[m-[37m03689174[m] to [01100000-0112b80a][0112c000-0114e000] entry at [37m00068384[m via trampoline page code [36m#0e: loading "(nd)/tftpboot/drops/bin/x86_586/l4v2/loader --fprov=BMODFS l4linux26.cfg" [m from [[37m0368a000[m-[37m036b3174[m] to [01300000-01326272][01327000-0134f000] entry at [37m000693a4[m via trampoline page code rtc | Date:01.03.2008 Time:23:02:14 con | Using fast memcpy. simplets| parse_args(): Too many tasks (900) -- limiting to 891! simplets| Configured for 891 tasks. io | do_args(): Disabling internal IRQ handling. io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: PIIX3: Enabling Passive Release on 00:01.0 io | Limiting direct PCI/PCI transfers. io | Activating ISA DMA hang workarounds. io | 00000000-ffffffff : PCI mem io | f0000000-f1ffffff : Cirrus Logic GD 5446 io | f2000000-f2000fff : Cirrus Logic GD 5446 io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | c000-c00f : Intel Corp. 82371SB PIIX3 IDE [Natoma/Triton II] io | c100-c1ff : Realtek Semiconductor Co., Ltd. RTL-8029(AS) con | Character size is 8x14, font has 256 characters con | VESA reports 800x600@16 1600bpl (00bb) [4096kB] con | Color mapping: red=11:5 green=5:6 blue=0:5 res=0:0 con | No supported accelerated graphics card detected io | Remapping I/O memory f0000000-f0400000 cached con | Mapped I/O video mem f0000000 => 02000000+000000 [4096kB] via l4io con | Using MMXEXT for colorspace transform con | L4INPUT: !!! W A R N I N G !!! con | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. con | L4INPUT: !!! W A R N I N G !!! con | L4INPUT: Registered 0xb03c80 for callbacks. con | serio: i8042 AUX port at 0x60,0x64 irq 12 con | serio: i8042 KBD port at 0x60,0x64 irq 1 con | input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1 con | input: AT Translated Set 2 keyboard on isa0060/serio0 con | input: PC Speaker con | input: L4 input event injector con | L4 input event injector: IRQ handler up con | connect "ImExPS/2 Generic Explorer Mouse", isa0060/serio1/input0 con | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 con | connect "PC Speaker", isa0061/input0 con | connect "L4 input event injector", l4/sys con | Running as C.02. Video mode is 800x600@16. bmodfs | Passed the following modules: bmodfs | module "(nd)/tftpboot/cfg/l4linux26.cfg" (1kB) bmodfs | module "(nd)/tftpboot/drops/bin/x86_586/l4v2/libloader.s.so" (634kB bmodfs : ) bmodfs | module "(nd)/tftpboot/drops/bin/x86_586/l4v2/vmlinuz26" (16628kB) bmodfs | module "(nd)/tftpboot/drops/bin/rd/initrd.gz" (4096kB) loader | sleeping for 2000 ms exec | vmlinuz26: Loading exec | vmlinuz26: Interpreter section found, contains "/usr/lib/libc.so.1" exec | vmlinuz26: Saved 910939 bytes of symbols exec | libloader.s.so: Loading exec | libloader.s.so: Saved 26701 bytes of symbols exec | libloader.s.so: Relocating to 00010000 exec | libloader.s.so: Linking exec | libloader.s.so: Symbol mmap_normal is weak and undefined exec | libloader.s.so: Symbol munmap_normal is weak and undefined exec | libloader.s.so: Symbol mmap_normal is weak and undefined exec | libloader.s.so: Symbol munmap_normal is weak and undefined exec | libloader.s.so: Relocating entry 00005df0 => 00015df0 exec | libloader.s.so: Setting section flag 0800 exec | vmlinuz26: Setting section flag 0800 loader | vmlinuz26: Starting l4env-style application loader | [36mvmlinuz26,#f: Starting at l4loader_init (00016630)[m exec | vmlinuz26: Linking exec | vmlinuz26: Relocating entry 00400000 => 00400000 exec | vmlinuz26: Packed 737417 bytes of symbols exec | vmlinuz26: Packed 1868352 bytes of lines loader | vmlinuz26,#f: Continue at l4env_init (00016640, libloader.s.so) l4lx | [34;1m======> L4Linux 2.6 starting... <========[0m l4lx | Linux version 2.6.17-l4 (root@umas1) (gcc version 3.3.1 (Mandrake Lin l4lx : ux 9.2 3.3.1-2mdk)) #1 Thu Feb 7 22:57:26 UTC 2008 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (5 args): mem=128M load_ramdisk=1 ramdisk_size=40 l4lx : 96 root=/dev/ram l4env_rd=(nd)/tftpboot/drops/bin/rd/initrd.gz l4lx | Image: 00400000 - 0071c000 [3184 KiB]. l4lx | Areas: Text: 00400000 - 00631000 [2244kB] (a bit longer) l4lx | Data: 00631000 - 0067b5ac [297kB] l4lx | Initdata: 0067e000 - 006af000 [196kB] l4lx | BSS: 006b0000 - 0071aac0 [426kB] l4lx | L4RM: [PF] read at 0x006b0000, ip 004019e0, src F.02 l4lx | [F.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault l4lx | l4lx | Exiting with -1 simplets| Exit F.00 [===============================================] What must be mapped to the BSS area and why it may be unsuccessful? These page faults, as I understand, are handled by l4rm library and dm_phys dataspace manager, but what here can be wrong? my grub entry is: [===============================================] title loader + l4lx26 mit BMODFS kernel $(ROOT)/bootstrap -serial modaddr 0x02000000 module $(FIASCO) $(FIASCOARGS) module $(P)/sigma0 module $(P)/roottask task sigma0 boot_priority 0xA0 \ task roottask boot_priority 0xA0 \ task modname "names" boot_priority 0xA0 \ task modname "log" boot_priority 0xA1 \ task modname "dm_phys" boot_priority 0xA0 \ task modname "simple_ts" boot_priority 0xA0 \ task modname "l4io" allow_cli boot_priority 0xA3 \ task modname "rtc" allow_cli \ task modname "l4con" allow_cli \ task modname "l4exec" boot_priority 0xA0 \ task modname "loader" allow_cli boot_priority 0xA0 \ task modname "vmlinuz26" \ task modname "bmodfs" attached 4 modules module $(P)/names module $(P)/log --prio 0xA1 module $(P)/dm_phys --isa=0x00800000 module $(P)/simple_ts -t 900 module $(P)/rtc module $(P)/l4io --noirq module $(P)/bmodfs module $(CFG)/l4linux26.cfg module $(P)/libloader.s.so module $(P)/vmlinuz26 module $(S)/rd/initrd.gz module $(P)/l4con --l4io module $(P)/l4exec module $(P)/loader --fprov=BMODFS l4linux26.cfg vbeset $(VBEMODE) [===============================================] and it uses the following l4linux26.cfg: [===============================================] modpath "(nd)/tftpboot/drops/bin/x86_586/l4v2" sleep 2 task "vmlinuz26" "mem=32M load_ramdisk=1 ramdisk_size=4096 root=/dev/ram l4env_rd=(nd)/tftpboot/drops/bin/rd/initrd.gz showpfexc=1" all_sects_writable [===============================================] as you can probably see, I use a bit old l4linux and l4env sources (downloaded a year or more ago). I think I missed something simple, but I can't understand what. Please help. WBR, Valery

2 1

A pagefault at the BSS area when starting l4linux
by Valery V. Sedletski 07 Mar '08

07 Mar '08

1 0

stop thread running in fiasco/L4
by hazwan 07 Mar '08

07 Mar '08

Hello Im curious to know, how can i stop a thread from running? Is there an API call to do this process? As far as i know, there is an API call for OK/L4 to stop a thread. How about fiasco? Thanks -- View this message in context: http://www.nabble.com/stop-thread-running-in-fiasco-L4-tp15864227p15864227.… Sent from the L4 mailing list archive at Nabble.com.

2 1

need some help in okl4
by Gabi Voiculescu 05 Mar '08

05 Mar '08

Hello l4-hackers community, Does anyone have experience with okl4's distribution? I have some questions on how to make gta01 platform simulate in Skyeye starting from okl4_release_1.5.2 with lcd support. I changed machines.py in platform/s3c2410/tools to contain: lcd: state=on, type=s3c2410x, mod=gtk I know Skyeye can simulate the LCD (verified it in arm's testsuite). Gabi --------------------------------- Never miss a thing. Make Yahoo your homepage.

1 0

does l4 linux now support smp?
by Yang Xu 04 Mar '08

04 Mar '08

Hello everyone, does anybody know that whether l4 linux now already support smp or not please? As far as I know, linux 2.6.x already supports smp. So I am wondering the the l4-linux 2.6 supports smp or not. if yes, it is the linux kernel distributes the threads across the cores or the ukernel does this? Any comment is welcome :-) best regards, Yang

2 5

mysterious double fault
by Alexander Arlt 04 Mar '08

04 Mar '08

hi all, i have a mysterious double fault error while booting fiasco in qemu. the problem is that the same configuration works on a native 586 fiasco and in fiasco-ux without any problems. only with qemu a double fault is detected. i tested it with qemu 0.9.0 and qemu 0.9.1. with version 0.9.0 the boot process hangs, without any error messages. with qemu 0.9.1 fiasco says that a double fault was detected. in my configuration i boot two instances of l4linux. while the intialization of the l4linux kernel, fiasco produces the following output: DOUBLE FAULT! EAX=c02407d0 ESI=c0240000 DS=0023 EBX=c0401000 EDI=00000000 ES=0023 ECX=3fe19000 EBP=c02406b4 GS=0043 EDX=00000000 ESP=c04017cc SS=0010 ESP0=c0240800 EFL=00200087 EIP=f002ef06 CS=0008 this happens always after the "l4lx | Got 0 out of 65536 I/O ports" message. but the really confusing thing is, that sometimes also qemu can boot without any double fault. any ideas whats going wrong here? thanks alex

2 1

Linux 2.6.24 L4FB and VGA_CONSOLE
by Marc CHALAND 27 Feb '08

27 Feb '08

Hi, I made a svn up into l4linux-2.6, made an oldconfig and encountered some problems with lxevent and... cron (???). Problem with lxevent, was into rmgr_init_ping_call: _dice_msg_buffer was NULL. So I decided to purge all build directories (fiasco, build dir, install dir and l4linux). I edited a new configuration for l4linux but I encountered a problem : I cannot disable VGA_CONSOLE if I don't use EMBEDDED. So I decided to set it. But, now, I've got some stability problems : I get the following message : --------------------------------------------------------------------------------------------------------------------------------- KERNEL: set_tls: non-existing thread 003401e1 KERNEL: set_ldt: non-existing task 0. Trap: 13: 0000 [#1] Modules linked in: Pid: 1070, comm: consolechars Not tainted (2.6.24-l4 #14) EIP: ff7c:[<00405055>] EFLAGS: 00010246 CPU: 0 EIP is at l4x_switch_to+0xd0/0xd3 EAX: 1003cc60 EBX: 00000018 ECX: 00000000 EDX: 00000000 ESI: 003401e1 EDI: 1003ca80 EBP: 1081013c ESP: 108139a0 DS: 0000 ES: 4280 FS: 0023 GS: 0043 SS: 0023 Process consolechars (pid: 1070, ti=10812000 task=1003ca80 task.ti=108d0000) Stack: 108139a8 00000000 1003ca80 10810000 00000400 0054da88 005f0fbc 10810000 00000400 1003ca80 10812000 108139e8 ffff950d 00000400 0000000b 0054dd5b 108139e8 ffff950d 005f67b0 005f67b0 ffff950d 0041923c 10810000 005f5f00 Call Trace: [<0054da88>] schedule+0x171/0x1bb [<0054dd5b>] schedule_timeout+0x7b/0x99 [<0041923c>] process_timeout+0x0/0x9 [<0045672f>] do_select+0x397/0x3ee [<00456d5f>] __pollwait+0x0/0xaf [<0040eeff>] default_wake_function+0x0/0x14 [<0049f877>] __make_request+0x472/0x4a8 [<0040e891>] update_curr+0x52/0xc8 [<0040eb9b>] dequeue_entity+0xb/0x2a [<0040fbbf>] dequeue_task_fair+0x1b/0x2f [<0040f644>] finish_task_switch+0x1f/0x50 [<0054dab4>] schedule+0x19d/0x1bb [<0054dcca>] io_schedule+0xb/0x12 [<00467424>] sync_buffer+0x3b/0x40 [<0054debd>] __wait_on_bit+0x53/0x5c [<004673e9>] sync_buffer+0x0/0x40 [<004673e9>] sync_buffer+0x0/0x40 [<0054df28>] out_of_line_wait_on_bit+0x62/0x6a [<00421d9c>] wake_bit_function+0x0/0x34 [<004820b3>] __ext3_get_inode_loc+0x29e/0x2f6 [<00448a95>] kmem_cache_alloc+0x66/0x9e [<0045a1da>] __d_lookup+0x97/0xd5 [<0045a1da>] __d_lookup+0x97/0xd5 [<00451dd2>] do_lookup+0x59/0x16b [<00453837>] __link_path_walk+0x930/0xa72 [<0045a6a3>] dput+0x2a/0xe5 [<00453837>] __link_path_walk+0x930/0xa72 [<0045d5ea>] mntput_no_expire+0x1c/0x5c [<0045697e>] core_sys_select+0x1f8/0x2ae [<00454514>] __user_walk_fd+0x43/0x4c [<00449151>] kmem_cache_free+0x40/0x93 [<00452d6f>] getname+0x68/0xa2 [<0044e26d>] cp_new_stat64+0xff/0x111 [<00456eb3>] sys_select+0xa5/0x173 [<0040401b>] l4x_user_dispatcher+0x8e2/0x184c [<0040c030>] _upage_start+0x30/0x890 [<00456e0e>] sys_select+0x0/0x173 [<0044fd40>] do_execve+0x172/0x17b [<0044fd40>] do_execve+0x172/0x17b [<005c4372>] kernel_init+0x0/0x254 [<004079a3>] l4_kernelinternal_execve+0xc2/0xc9 [<00400915>] in_kernel_int80_helper+0x9/0x17 [<005c4372>] kernel_init+0x0/0x254 [<004094a3>] kernel_execve+0x17/0x1a [<00400198>] run_init_process+0x20/0x24 [<00400242>] init_post+0xa6/0xd0 [<005c45bc>] kernel_init+0x24a/0x254 [<0040f644>] finish_task_switch+0x1f/0x50 [<005c4372>] kernel_init+0x0/0x254 [<005c4372>] kernel_init+0x0/0x254 [<004072cb>] kernel_thread_start+0x28/0x2d [<00406ed2>] sys_enosys+0x0/0x6 ======================= Code: 00 00 89 04 d5 04 e0 5a 00 89 0c d5 00 e0 5a 00 8b b7 00 02 00 00 8d 87 e0 01 00 00 bb 18 00 00 00 31 c9 89 ca 0f 00 d0 5b 5e 5f <c3> 90 90 57 56 83 ec 04 8b 74 24 10 8b 7c 24 14 f6 46 0d 20 74 EIP: [<00405055>] l4x_switch_to+0xd0/0xd3 SS:ESP 0023:108139a0 ---[ end trace 10d172b22dcd8354 ]--- Fixing recursive fault but reboot is needed! ------------------------------------------------------------------------------------------------------------------------ I thought I forgot to set an option into kernel. But this happens sometimes on egrep, which, etc.. Any idea on the problem ? Regards Marc

3 10

Problem with dice when fpage are used with derivation
by Marc CHALAND 27 Feb '08

27 Feb '08

Hi, I don't have time to do more checking on L4Linux. Today, I use dice r238 of public repository of TUDOS. All my tasks are pure L4env ones. I try to process an idl which is quite long. Here is a sample : library myapp { [uuid(2)] interface connection { int syn([out] unsigned long *page_in_base); int ack([in] fpage page_in, [in] unsigned long page_out_base, [out] fpage *page_out); int rst(void); }; }; I create one interface which derives from myapp::connection : library myapp_server { interface server : myapp::configuration, myapp::connection, myapp::key { }; }; Dice generates files. One of them is very strange. On server side, file corresponding to myapp_server contains following code : inline long myapp_server_reply_and_wait (CORBA_Object _dice_corba_obj, l4_msgtag_t *_dice_tag, myapp_server_msg_buffer_t *_dice_msg_buffer, CORBA_Server_Environment *_dice_corba_env) { long _dice_opcode = 0; l4_msgtag_t tagdummy __attribute__ ((unused)) = l4_msgtag(0,0,0,0); l4_msgdope_t _dice_result = { msgdope: 0 }; if ((_dice_msg_buffer->_word._dice_send_dope.md.dwords <= 2) && (_dice_msg_buffer->_word._dice_send_dope.md.strings == 0)) [ZAP] /* clear exception if set*/ if (DICE_EXPECT_FALSE(DICE_HAS_EXCEPTION(_dice_corba_env))) CORBA_server_exception_set(_dice_corba_env, CORBA_NO_EXCEPTION, CORBA_DICE_EXCEPTION_NONE, 0); /* test for IPC errors */ if (DICE_EXPECT_FALSE(L4_IPC_IS_ERROR(_dice_result))) { _dice_opcode = 0; _dice_msg_buffer->_word._word[0] = 0; if (DICE_IS_NO_EXCEPTION(_dice_corba_env)) CORBA_server_exception_set(_dice_corba_env, CORBA_SYSTEM_EXCEPTION, CORBA_DICE_INTERNAL_IPC_ERROR, 0); return _dice_opcode; } if (l4_ipc_fpage_received(_dice_result)) _dice_opcode = _dice_msg_buffer->_word._word[2]; else _dice_opcode = _dice_msg_buffer->_word._word[0]; return _dice_opcode; } By adding some logging, I realized that when fpage is received, opcode is not into _word[2] but _word[4]. Regards Marc

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers