l4-hackers

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

2827 discussions

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

25 Mar '08

hi, the problem is solved, thanks everybody :) ----- Original Message ---- > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > To: l4-hackers(a)os.inf.tu-dresden.de > Sent: Tuesday, March 25, 2008 1:08:10 AM > Subject: Re: Failed to create a new task > > > On Fri Mar 21, 2008 at 02:06:49 -0700, ahmad kamal wrote: > > 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. > > So, do you mind to post your updated program again so that I can check. > > > > 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 > ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

1 0

Debugger on top of L4
by Andrew Vadimovich 25 Mar '08

25 Mar '08

good day Im totally newbie to l4, but my aim is to develop source level debugger for our system built on top of L4. So the procedure for source level debugger is common and may be presented in following steps: 1) Cause undef exception from user task (using undef instruction) 2) Catch it by undef exception handler 3) Save CPU registers 4) Suspend running thread. Suspension must be performed by my code - not by l4 system code. 5) Continue execution with next scheduled thread But untill now i have no ideas how to suspend thead by my self. I even cant find l4 code responsible for thread suspension. Does anyone knows where can i find suspention procedure in l4 code? Probably someone has code snippets for such kind of actions? thanks in advance -- View this message in context: http://www.nabble.com/Debugger-on-top-of-L4-tp16180942p16180942.html Sent from the L4 mailing list archive at Nabble.com.

3 4

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

Jump to page:

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