l4-hackers

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

2 participants
2880 discussions

Installing problem with gcc-4.2.3
by fei li 14 May '08

14 May '08

Hi, all I have installed l4 on ubuntu8.04 these days, the compiling process is ok, but when I finished compiling the packages, i reboot and find that the grub doesn't support. Then i patch the grub-0.97-os.6.diff, there are errors when i use the gcc-4.2.3, then i turn to gcc-4.1.3, and everything is ok, but when i finished the grub installing, i find i can't enter the ubuntu 8.04, it says error 27, don't know the command, something like that. Then i uninstall the patched grub and install the grub from the source, it's ok, but i can't enter the l4, I guess you can have a test, if it's true, I guess we need a os.7 patch for gcc-4.2.3 or something else. That's all!

3 4

compile error when compiling the package 'overlap_wm'
by 盛淑蕙 14 May '08

14 May '08

Hi, 2 questions are mentioned as following 1) I can only get files in directory 'overlap_WM' (i.e., excluding directory) when i used the syntax 'svn co -N http://svn.tudos.org/repos/tudos/trunk/l4/pkg/overlap_wm' so, I manually downloaded all the files i need. Is it a bug or something? 2) It showed the compile error messages as below when I compiled this package. ==> Linking nitovlwm LD_PRELOAD=/usr/l4/build/l4/tool/gendep/libgendep.so GENDEP_TARGET=nitovlwm GENDEP_BINARY=ld GENDEP_BINARY_ALT1=ld ld -m elf_i386 -o nitovlwm /usr/l4/build/l4/lib/x86_586/crt0.o --hash-style=sysv -L/usr/l4/build/l4/lib/x86_586/l4v2 -L/usr/l4/build/l4/lib/x86_586 -L/usr/l4/build/l4/lib -L/usr/l4/drops/lib/x86_586/l4v2 -L/usr/l4/drops/lib/x86_586 -L/usr/l4/drops/lib -T/usr/l4/build/l4/lib/x86_586/main_stat.ld -lovlsrv-idl -static -lgeneric_ts -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -lsemaphore -llogserver_capsule -lnames -ll4util_root -ll4util -lsigma0 -lroot -ll4env -ll4env_err -ll4rm -ldm_generic -ldm_mem -lthread -lslab -ll4sys -nostdlib -luc_c -luclibc_support -u mmap_anon -lc_be_simple_mem -lc_be_mmap -lc_be_mmap_util -lc_be_l4env_start_stop -lc_be_minimal_log_io -luc_be_simple_sleep -ll4env -llogserver_capsule -ll4rm -ldm_generic -ldm_mem -lthread -lgeneric_ts -luc_c /usr/lib/gcc/i486-linux-gnu/4.2.3/libgcc.a -luc_c -ll4sys --warn-common -gc-sections /usr/l4/build/l4/lib/x86_586/l4v2/libl4env.a(startup.o): In function `__startup_main': /usr/l4/l4/pkg/l4env/lib/src/startup.c:80: undefined reference to `main' make[6]: *** [nitovlwm] Error 1 make[6]: Leaving directory `/usr/l4/build/l4/pkg/nitpicker/examples/nitovlwm/l4/OBJ-x86_586-l4v2' make[5]: *** [/usr/l4/build/l4/pkg/nitpicker/examples/nitovlwm/l4/OBJ-x86_586-l4v2] Error 2 make[5]: Leaving directory `/usr/l4/l4/pkg/nitpicker/examples/nitovlwm/l4' make[4]: *** [l4] Error 2 make[4]: Leaving directory `/usr/l4/l4/pkg/nitpicker/examples/nitovlwm' make[3]: *** [nitovlwm] Error 2 make[3]: Leaving directory `/usr/l4/l4/pkg/nitpicker/examples' make[2]: *** [examples] Error 2 make[2]: Leaving directory `/usr/l4/l4/pkg/nitpicker' make[1]: *** [nitpicker.bin] Error 2 make[1]: Leaving directory `/usr/l4/l4/pkg' make: *** [pkg] Error 2 make: Leaving directory `/usr/l4/l4' any help is welcomed kind regards Saya

2 1

Compiling errors on debian testing amd64
by fei li 11 May '08

11 May '08

Hi,all I have compiled l4 on my machine, my cpu type is amd64, when I compiled l4, I got errors as below. In my config file I chose the cpu type as amd64 and kept the other things not changed. Then I used the command make O=/home/licy/Desktop/trunk/build CC="gcc -disable-multilib" to compile. And I got the errors: /home/licy/Desktop/trunk/build/include/linux-24/linux/string.h:78: warning: conflicting types for built-in function '__builtin_memcmp' /tmp/cc6FM9DF.s: Assembler messages: /tmp/cc6FM9DF.s:2683: Error: suffix or operands invalid for `mov' /tmp/cc6FM9DF.s:2684: Error: Incorrect register `%rax' used with `l' suffix /tmp/cc6FM9DF.s:5510: Error: suffix or operands invalid for `and' /tmp/cc6FM9DF.s:7122: Error: suffix or operands invalid for `and' /tmp/cc6FM9DF.s:7201: Error: Incorrect register `%rax' used with `l' suffix Indeed I found http://lists.okl4.org/pipermail/developer/2007-April/000038.html who got the similar errors and at last the one gave an advice to simulate in qemu. Someone said that now we can compile l4 on amd64 machines, and I want to know what my problem is. My gcc version is Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --disable-libmudflap --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.2.3 (Debian 4.2.3-3) licy@licy:~/Desktop/trunk/l4$ ld -v GNU ld (GNU Binutils for Debian) 2.18.0.20080103 Whether it's the compiler's problem or we still can't compile l4 on amd64 machines, I hope someone give me some help and thanks a lot. Someone said that I shouldn't use the ia32 headers and just use the amd-64 headers is OK, but I still don't get the results, maybe there are patches for this problem or my compiling way is incorrect, just tell me and i'll have a try. Eh, I got the newest version of the trunk, I forgot telling you this.

2 1

switch to ipc question
by eric johnson 09 May '08

09 May '08

greetings !! i am using the the scheduler to implement some virtualisation stuff. i would really appreciate some help regarding the following stuff i need to get done. from the scheduler i need to do an upcall to a user level task . Can i use an ipc for this ? from the user task ( the receiver of the above upcall from kernel ) , i need to ( directly if possible ) switch to another task . how do i do this ? thanks !! any pointers would be really appreciated. ej

1 0

unhandled page fault
by 盛淑蕙 05 May '08

05 May '08

Hi, I tried to compile l4linux (kernel 2.6.24) under ubuntu 8.04 (The version of gcc compiler is 4.2.3) and it failed to boot under l4env with Fiasco microkernel. Here is my step to compile l4linux 1. make O=/usr/l4/build/linux x86-native_defconfig 2. enable Support for frame buffer devices and Framebuffer Console support 3. make O=/usr/l4/build/linux and then edited the menu.lst title L4Linux-2.6 root (hd0,0) kernel /boot/grub/common/bootstrap -modaddr 0x02000000 module /boot/grub/common/fiasco -nokdb -serial_esc module /boot/grub/common/sigma0 module /boot/grub/common/roottask task modname "bmodfs" attached 4 modules module /boot/grub/common/names module /boot/grub/common/log module /boot/grub/common/dm_phys --isa=0x00800000 module /boot/grub/common/simple_ts -t 300 module /boot/grub/common/rtc module /boot/grub/common/l4io module /boot/grub/common/bmodfs module /boot/grub/common/linux.cfg module /boot/grub/common/libloader.s.so module /boot/grub/common/libld-l4.s.so module /boot/grub/common/vmlinuz module /boot/grub/common/loader --fprov=BMODFS linux.cfg and linux.cfg modpath "(hd0,0)/boot/grub/common" task "vmlinuz" "earlyprint=yes mem=64M" all_sects_writable allow_vga it shows the following messages when it boots. (last screen page is shown) l4lx | Got 2048kB of ISA DMA memory l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physocal regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x04bfffff [65536 KiB] l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes l4lx | Main memory: 1: Phys: 0x18c00000 to 0x1cc00000, Size: 67108864 l4lx | Filling lower ptabs... l4lx | Done (1483 entries). l4lx | l4env_register_pointer_section: addr = 00400000 size = 4128768 l4lx | end: virt: 0x00400000 to 0x007effff [4032 KiB] l4lx | Noncontiguous region for end l4lx | end: Number of physical regions: 5, 4128768 Bytes l4lx | end: 1: Phys: 0x00a09000 to 0x00a59000, Size: 327680 l4lx | end: 2: Phys: 0x0108a000 to 0x01220000, Size: 1662976 l4lx | end: 3: Phys: 0x01419000 to 0x01500000, Size: 946176 l4lx | end: 4: Phys: 0x01347000 to 0x01400000, Size: 757760 l4lx | end: 5: Phys: 0x01296000 to 0x01300000, Size: 434176 l4lx | l4lx_thread_create: Created thread 0d.05 (timer.i0) l4lx | Jumping over 4x 'hit' at 0x71c949 l4lx | L4RM: [PF] read at 0xf0cfb000, ip 007371a6, src D.02 l4lx | [D.0] l4rm/lib/src/pagefault.c:81:__unknown_pf(): l4lx | unhandled page fault --PANIC, 'g' for exit----------------------------------------------- IP: a00b25c4 [l4lx.rm] (d.00) jdb: My l4linux config file is also attached for your reference. =========================================== I have read the document 'l4/Fiasco/L4Linux kickstart' as a guide and tried many times to reconfigure the kernel, but i got the same result. Any help is very welcomed.

2 1

Unhandled page fault (in __unknown_pf)
by Igor V. Ruzanov 25 Apr '08

25 Apr '08

Hello! There is a problem when vmlinuz-2.6.24-l4 (kernel image compiled in l4linux source tree) boots under l4env with Fiasco u-kernel (last screen page is shown below): l4lx | Got 2048kB of ISA DMA memory l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physocal regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043b000 to 0x0063b000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x10bfffff [262144 KiB] l4lx | Main memory: Number of physical regions: 1, 26843556 Bytes l4lx | Main memory: 1: Phys: 0x07000000 to 0x17000000, Size: 268435456 l4lx | Filling lower tabs... l4lx | Done (1722 entries). l4lx | l4env_register_pointer_section: addr = 00660000 size = 667648 l4lx | end: virt: 0x00660000 to 0x00702fff [652 KiB] l4lx | Noncontiguous region for end l4lx | end: Number of physical regions: 2, 667548 Bytes l4lx | end: 1: Phys: 0x01251000 to 0x01287000, Size: 221184 l4lx | end: 2: Phys: 0x00ba9000 to 0x00c16000, Size: 446464 l4lx | l4env_rd_path: initrd-2.6.24-l4.img l4lx | Loading: initrd-2.6.24-l4.img l4lx | INITRD: Size of RAMdisk is 3516 KiB l4lx | RAMdisk from 10c00000 to 10f6f200 [3516 KiB] l4lx | L4RM: [PF] read at 0xf0070000, ip 004098d8, src D.02 l4lx | [D.0] l4rm/lib/src/pagefault.c:81:__unknown_pf(): l4lx | unhandled page fault --PANIC, 'g' for exit----------------------------------------------- IP: a00b53a6 [l4lx.rm] (d.00) jdb: [...] OBJDUMP of vmlinux shows the following listing (cutted fragment): 004098a1 <rtc_cmos_read>: rtc_cmos_read(): /usr/src/kernels/2.6-24-l4/arch/l4/kernel/arch-i386/time.c:93 4098a1: 56 push %esi 4098a2: 53 push %ebx 4098a3: 83 ec 04 sub $0x4,%esp 4098a6: 8a 5c 24 10 mov 0x10(%esp),%bl /usr/src/kernels/2.6-24-l4/build/include/asm-l4/l4-arch/asm/irqflags.h:68 4098aa: e8 4a 87 ff ff call 401ff9 <l4x_global_save_flags> 4098af: 89 c6 mov %eax,%esi /usr/src/kernels/2.6-24-l4/build/include/asm-l4/l4-arch/asm/irqflags.h:78 4098b1: e8 4c 88 ff ff call 402102 <l4x_global_cli> /usr/src/kernels/2.6-24-l4/build/include/asm-l4/x86-arch/asm/mc146818rtc_32.h:45 4098b6: 0f b6 d3 movzbl %bl,%edx 4098b9: 89 d1 mov %edx,%ecx 4098bb: 80 cd 01 or $0x1,%ch /usr/src/kernels/2.6-24-l4/build/include/asm-l4/x86-arch/asm/mc146818rtc_32.h:47 4098be: a1 98 23 67 00 mov 0x672398,%eax 4098c3: 85 c0 test %eax,%eax 4098c5: 74 04 je 4098cb <rtc_cmos_read+0x2a> /usr/src/kernels/2.6-24-l4/build/include/asm-l4/l4-arch/asm/processor.h:487 4098c7: f3 90 pause 4098c9: eb f3 jmp 4098be <rtc_cmos_read+0x1d> /usr/src/kernels/2.6-24-l4/build/include/asm-l4/x86-arch/asm/cmpxchg_32.h:137 4098cb: 0f b1 0d 98 23 67 00 cmpxchg %ecx,0x672398 /usr/src/kernels/2.6-24-l4/build/include/asm-l4/x86-arch/asm/mc146818rtc_32.h:51 4098d2: 85 c0 test %eax,%eax 4098d4: 75 e8 jne 4098be <rtc_cmos_read+0x1d> /usr/src/kernels/2.6-24-l4/build/include/asm-l4/l4-arch/asm/io.h:359 4098d6: 88 d0 mov %dl,%al (***) 4098d8: e6 70 out %al,$0x70 /usr/src/kernels/2.6-24-l4/build/include/asm-l4/l4-arch/asm/io.h:273 4098da: e6 80 out %al,$0x80 [...] We can see that the instruction at (***) causes the fault of executing. I have no idea why it makes the problem. I've compared same part of object code of usual kernel (2.6.24.5 that working in 'real' environment) - there was the same semantics of the function rtc_cmos_read(). Below i provide grub.list section about loading l4linux module: title Red Hat Enterprise Linux Server (2.6.24-l4, very EXPERIMENTAL) root (hd0,0) kernel /boot/l4/linux/bin/bootstrap modaddr 0x06000000 module /boot/l4/linux/bin/fiasco -nokdb -serial_esc module /boot/l4/linux/bin/sigma0 module /boot/l4/linux/bin/roottask task modname "bmodfs" attached 5 modules module /boot/l4/linux/bin/names module /boot/l4/linux/bin/log module /boot/l4/linux/bin/dm_phys --isa=0x00800000 module /boot/l4/linux/bin/simple_ts -t 300 module /boot/l4/linux/bin/l4io --noirq module /boot/l4/linux/bin/con module /boot/l4/linux/bin/bmodfs module /boot/l4/linux/cfg/l4linux26.cfg module /boot/l4/linux/bin/libloader.s.so module /boot/l4/linux/bin/libld-l4.s.so module /boot/vmlinuz-2.6.24-l4 module /boot/initrd-2.6.24-l4.img module /boot/l4/linux/bin/loader --fprov=BMODFS l4linux26.cfg [...] All the stuff was compiled under RHEL5 with kernel-2.6.24-5 (SMP). Version of gcc compiler is 4.1.1 20070105 (Red Hat 4.1.1-52) [gcc -v] with POSIX thread model. My hardware is: - mainboard is DG33TL; - CPU Intel Pentium Dual-Core; - RAM 2048Mb I tried to load l4linux-module in cores-multiplexed enabled (for SMP) and cores-multiplexed disabled CPU modes, that i was tuning them on/off in BIOS setup. Any help is very welcomed!

2 1

some question about serial package
by Ding ying 22 Apr '08

22 Apr '08

Hi,everyone. In l4/pkg/,there is a serial package about operate on serial port under L4/fiasco.But I couldn't run it propery on my machine.From adding some test sentence,I found the programme will dead in serial/lib/src/client.c 115 sentence:l4_ipc_wait(),but before dead,it could do two run in:l_recv<--->goto l_recv part.I mean the l4_ipc_wait() could get two message and do the relevant work,but when goto third run,it dead,and client invoking function also dead.I can't find what cause the this. Is there anybody could help me? Best Regards! ying ding

2 1

Fiasco compilation with ubuntu
by Marc CHALAND 17 Apr '08

17 Apr '08

Hi, I get problem with our version of ubuntu to compile fiasco. date doesn't work exactly in a same manner as gentoo and debian. It adds "(+02.00)" at the end of output which disturbs make process. Here is the patch that we use. It works on debian and gentoo also. Regards Marc

3 3

compile error
by 盛淑蕙 14 Apr '08

14 Apr '08

Hi, I have downloaded the fiasco,l4linux and l4env as following ./repomgr co fiasco ./repomgr co hello ./repomgr co l4linux2.6-env svn co http://svn.tudos.org/repos/l4linux/trunk l4linux-2.6 It is failed to compile during building the loader package. === Building lib of "loader" === PWD=/usr/l4/pkg/loader make -C loader lib -o include -o idl make[2]: Entering directory `/usr/l4/l4/pkg/loader' test -f lib/broken -o -f lib/obsolete || \ if [ -f lib/Makefile ] ; then PWD=/usr/l4/pkg/loader/lib make -C lib ; fi make[3]: Entering directory `/usr/l4/l4/pkg/loader/lib' test -f clientlib/broken -o -f clientlib/obsolete || \ if [ -f clientlib/Makefile ] ; then PWD=/usr/l4/pkg/loader/lib/clientlib make -C clientlib ; fi make[4]: Entering directory `/usr/l4/l4/pkg/loader/lib/clientlib' PWD=/usr/l4/build/l4env/pkg/loader/lib/clientlib/OBJ-x86_586-l4v2 make -C /usr/l4/build/l4env/pkg/loader/lib/clientlib/OBJ-x86_586-l4v2 -f Makefile make[5]: Entering directory `/usr/l4/build/l4env/pkg/loader/lib/clientlib/OBJ-x86_586-l4v2' make[5]: Leaving directory `/usr/l4/build/l4env/pkg/loader/lib/clientlib/OBJ-x86_586-l4v2' make[4]: Leaving directory `/usr/l4/l4/pkg/loader/lib/clientlib' test -f runtime/broken -o -f runtime/obsolete || \ if [ -f runtime/Makefile ] ; then PWD=/usr/l4/pkg/loader/lib/runtime make -C runtime ; fi make[4]: Entering directory `/usr/l4/l4/pkg/loader/lib/runtime' PWD=/usr/l4/build/l4env/pkg/loader/lib/runtime/OBJ-x86_586-l4v2 make -C /usr/l4/build/l4env/pkg/loader/lib/runtime/OBJ-x86_586-l4v2 -f Makefile make[5]: Entering directory `/usr/l4/build/l4env/pkg/loader/lib/runtime/OBJ-x86_586-l4v2' ==> Linking to shared libloader.s.so LD_PRELOAD=/usr/l4/build/l4env/tool/gendep/libgendep.so GENDEP_TARGET=libloader.s.so GENDEP_BINARY=ld ld -m elf_i386 \ -o libloader.s.so -shared -T/usr/l4/build/l4env/lib/x86_586/main_rel.ld /usr/l4/build/l4env/lib/x86_586/crt0.s.o helper_dyn.s.o --hash-style=sysv -L/usr/l4/build/l4env/lib/x86_586/l4v2 -L/usr/l4/build/l4env/lib/x86_586 -L/usr/l4/build/l4env/lib -L/usr/l4/drops/lib/x86_586/l4v2 -L/usr/l4/drops/lib/x86_586 -L/usr/l4/drops/lib --whole-archive -lsemaphore.p -lthread.p -ldm_generic.p -ldm_mem.p -lslab.p -ll4env_err.p -ll4rm.p -ll4env.p -llogserver.p -lnames.p -lroot.p -lc_be_l4env_start_stop.p -lc_be_minimal_log_io.p -lc_be_simple_mem.p -lc_be_mmap.p -lc_be_mmap_util.p -luclibc_support.p -lgeneric_ts.p -lgeneric_fprov.p -lloaderif.p -ll4util_root.p -lsigma0.p --no-whole-archive -ll4sys.p -ll4util.p -ul4util_reboot -ugetopt_long /usr/lib/gcc/i486-linux-gnu/4.1.3/libgcc.a ld: cannot find -luclibc_support.p make[5]: *** [libloader.s.so] Error 1 make[5]: Leaving directory `/usr/l4/build/l4env/pkg/loader/lib/runtime/OBJ-x86_586-l4v2' make[4]: *** [/usr/l4/build/l4env/pkg/loader/lib/runtime/OBJ-x86_586-l4v2] Error 2 make[4]: Leaving directory `/usr/l4/l4/pkg/loader/lib/runtime' make[3]: *** [runtime] Error 2 make[3]: Leaving directory `/usr/l4/l4/pkg/loader/lib' make[2]: *** [lib] Error 2 make[2]: Leaving directory `/usr/l4/l4/pkg/loader' make[1]: *** [loader.lib] Error 2 make[1]: Leaving directory `/usr/l4/l4/pkg' make: *** [pkg] Error 2 make: Leaving directory `/usr/l4/l4' my gcc version is 4.1.3 and using xubuntu. Any other packages needed to be installed ? thank you

2 2

memory section iguana
by Anand Gore 14 Apr '08

14 Apr '08

Hi, I have a question about memory section in iguana server. I wanted to dynamically load a binary to a specific location e.g. 0x2000000 in my task/thread. Here is the code I have - mnsigned int base_address=0x200000; mm_s memsection_create_fixed(section_size, base_address); if(mm_s != 0) { memcpy(base_address, binary_buffer, sizeof(binary_buffer)); func=(func_t)base_address; func(); } The binary is built and linked to a fixed address 0x2000000, such that there will be an initialization function at 0x2000000. But I read in the document that the memsection_create_fixed is going to go away sometime down the line. I am wondering if there is going to be a replacement function for that or there is a better way to do this. Thank you. Anand

1 0

error while compiling the l4.
by l4 08 Apr '08

08 Apr '08

hi all, last time I put a error message to the l4-hacker ,and you send me a mail that ?I have cut away the first error.So I send the full infomations to you when I compiled it.By useing the cpu info,when I compile fiasco I do this: > > -------------------------------------------------- > > || Architecture (AMD64 processor family) ---> > > || Platform (PC platform) ---> > > || CPU (AMD Opteron / Athlon64) ---> > > || for scheduling) ---> > > || [*] Enables workaroud for AMD FPU security leak > > --------------------------------------- > > It sames that fiasco OK,but when I compile l4 with the following info: > > --------------------------------------- > > (x86) Target Architecture > > CPU type: "586" > > (L4.Fiasco) ABI > > -------------------------------------- > > errors comes out like this: > > ------------------------------------------------------------------------- > > ... Generating generic_ts-server.c > > CC="gcc -m32" /home/l4/tudos/l4/../dice/src/dice > > --require="3.2.0" -P-DUSE_UCLIBC=y -P-DRAM_BASE=0x0 > > -P-DSYSTEM_x86_l4v2 -P-DARCH_x86 -P-DCPUTYPE_586 -P-DL4API_l4v2 > > -P-DCONFIG_L4_CALL_SYSCALLS -P-DCONFIG_L4_ABS_SYSCALLS > > -P-I/home/l4/tudos/build/include/x86/l4v2 > > -P-I/home/l4/tudos/build/include/l4v2 > > -P-I/home/l4/tudos/build/include/x86 > > -P-I/home/l4/tudos/build/include > > -P-I/home/l4/tudos/l4/../dice/include > > -P-I/home/drops/include/x86/l4v2 -P-I/home/drops/include/l4v2 > > -P-I/home/drops/include/x86 -P-I/home/drops/include -P-nostdinc > > -P-I/home/l4/tudos/build/include/x86/uclibc > > -P-I/home/l4/tudos/build/include/uclibc > > -P-I/home/l4/tudos/build/include/uclibc++ > > -P-I/home/drops/include/x86/uclibc > > -P-I/home/drops/include/uclibc -P-I/home/drops/include/uclibc++ > > -P-I/usr/lib/gcc/x86_64-linux-gnu/4.1.3/include > > -P-I/usr/lib/gcc/x86_64-linux-gnu/4.1.3/include-fixed -Bifiasco > > -Bpia32 -MD /home/l4/tudos/l4/pkg/generic_ts/idl/generic_ts.idl > > In file included > > from /home/l4/tudos/l4/pkg/generic_ts/idl/generic_ts.idl:0, > > from l4/sys/types.h:1: > > /home/l4/tudos/build/include/x86/l4v2/l4/sys/types.h:398.20-29: > > error: value is out of range > > make[4]: *** [generic_ts-server.c] error 1 > > make[4]: Leaving directory > > `/home/l4/tudos/build/pkg/generic_ts/idl/OBJ-x86-l4v2' > > make[3]: *** > > [/home/l4/tudos/build/pkg/generic_ts/idl/OBJ-x86-l4v2] error 2 > > make[3]: Leaving directory > > `/home/l4/tudos/l4/pkg/generic_ts/idl' > > make[2]: *** [idl] error 2 > > make[2]: Leaving directory `/home/l4/tudos/l4/pkg/generic_ts' > > make[1]: *** [generic_ts.headers] error 2 > > make[1]: Leaving directory `/home/l4/tudos/l4/pkg' > > make: *** [pkg] error 2 > > ----------------------------------------------------------------------- > > firstly I think maybe I didn't do the right selecet,then I change it: > > ---------------------------------------------------------- > > (amd64) TargetArchitecture > > CPU type: "k7" > > (L4.Fiasco) > > ------------------------------------------------------------------ > > but there is another errors: > > -------------------------------- > > ... Generating generic_ts-server.c > > CC="gcc -m64" /home/l4/tudos/l4/../dice/src/dice > > --require="3.2.0" -P-DUSE_UCLIBC=y -P-DRAM_BASE=0x0 > > -P-DSYSTEM_amd64_l4v2 -P-DARCH_amd64 -P-DCPUTYPE_k7 > > -P-DL4API_l4v2 -P-DCONFIG_L4_CALL_SYSCALLS > > -P-DCONFIG_L4_ABS_SYSCALLS > > -P-I/home/l4/tudos/build/include/amd64/l4v2 > > -P-I/home/l4/tudos/build/include/l4v2 > > -P-I/home/l4/tudos/build/include/amd64 > > -P-I/home/l4/tudos/build/include > > -P-I/home/l4/tudos/l4/../dice/include > > -P-I/home/drops/include/amd64/l4v2 -P-I/home/drops/include/l4v2 > > -P-I/home/drops/include/amd64 -P-I/home/drops/include > > -P-nostdinc -P-I/home/l4/tudos/build/include/amd64/uclibc > > -P-I/home/l4/tudos/build/include/uclibc > > -P-I/home/l4/tudos/build/include/uclibc++ > > -P-I/home/drops/include/amd64/uclibc > > -P-I/home/drops/include/uclibc -P-I/home/drops/include/uclibc++ > > -P-I/usr/lib/gcc/x86_64-linux-gnu/4.1.3/include > > -P-I/usr/lib/gcc/x86_64-linux-gnu/4.1.3/include-fixed -Bifiasco > > -Bpamd64 -MD /home/l4/tudos/l4/pkg/generic_ts/idl/generic_ts.idl > > In file included > > from /home/l4/tudos/l4/pkg/generic_ts/idl/generic_ts.idl:0, > > from l4/sys/types.h:1, > > > > from /home/l4/tudos/build/include/amd64/l4v2/l4/sys/types.h:185: > > /home/l4/tudos/build/include/l4/sys/__l4_fpage-64bit.h:96.55-65: > > error: value is out of range > > make[4]: *** [generic_ts-server.c] error 1 > > make[4]: Leaving directory > > `/home/l4/tudos/build/pkg/generic_ts/idl/OBJ-amd64-l4v2' > > make[3]: *** > > [/home/l4/tudos/build/pkg/generic_ts/idl/OBJ-amd64-l4v2] error 2 > > make[3]: Leaving directory > > `/home/l4/tudos/l4/pkg/generic_ts/idl' > > make[2]: *** [idl] error 2 > > make[2]: Leaving directory `/home/l4/tudos/l4/pkg/generic_ts' > > make[1]: *** [generic_ts.headers] error 2 > > make[1]: Leaving directory `/home/l4/tudos/l4/pkg' > > make: *** [pkg] error 2 > > ---------------------------------------------------------- I think It can work on AMD64,could you help me?thank you very much! fangzhsh,

3 3

Re: error while compiling the l4.
by Martin Pohlack 07 Apr '08

07 Apr '08

Please use the mailing list! Forwarding. l4 wrote: >> You cut away the first error. Post a longer log. >> >> Cheers, >> Martin > > hi Martin, > last time I put a error message to the l4-hacker ,and you send me a mail > that I have cut away the first error.So I send the full infomations to > you when I compiled it.By useing the cpu info,when I compile fiasco I do > this: > -------------------------------------------------- > || Architecture (AMD64 processor family) ---> > || Platform (PC platform) ---> > || CPU (AMD Opteron / Athlon64) ---> > || for scheduling) ---> > || [*] Enables workaroud for AMD FPU security leak > --------------------------------------- > It sames that OK,but when I compile l4 with the following info: > --------------------------------------- > (x86) Target Architecture > │ │ CPU type: "586" > │ │ (L4.Fiasco) ABI > -------------------------------------- > errors comes out like this: > ------------------------------------------------------------------------- > ... Generating generic_ts-server.c > CC="gcc -m32" /home/l4/tudos/l4/../dice/src/dice > --require="3.2.0" -P-DUSE_UCLIBC=y -P-DRAM_BASE=0x0 > -P-DSYSTEM_x86_l4v2 -P-DARCH_x86 -P-DCPUTYPE_586 -P-DL4API_l4v2 > -P-DCONFIG_L4_CALL_SYSCALLS -P-DCONFIG_L4_ABS_SYSCALLS > -P-I/home/l4/tudos/build/include/x86/l4v2 > -P-I/home/l4/tudos/build/include/l4v2 > -P-I/home/l4/tudos/build/include/x86 > -P-I/home/l4/tudos/build/include > -P-I/home/l4/tudos/l4/../dice/include > -P-I/home/drops/include/x86/l4v2 -P-I/home/drops/include/l4v2 > -P-I/home/drops/include/x86 -P-I/home/drops/include -P-nostdinc > -P-I/home/l4/tudos/build/include/x86/uclibc > -P-I/home/l4/tudos/build/include/uclibc > -P-I/home/l4/tudos/build/include/uclibc++ > -P-I/home/drops/include/x86/uclibc > -P-I/home/drops/include/uclibc -P-I/home/drops/include/uclibc++ > -P-I/usr/lib/gcc/x86_64-linux-gnu/4.1.3/include > -P-I/usr/lib/gcc/x86_64-linux-gnu/4.1.3/include-fixed -Bifiasco > -Bpia32 -MD /home/l4/tudos/l4/pkg/generic_ts/idl/generic_ts.idl > In file included > from /home/l4/tudos/l4/pkg/generic_ts/idl/generic_ts.idl:0, > from l4/sys/types.h:1: > /home/l4/tudos/build/include/x86/l4v2/l4/sys/types.h:398.20-29: > error: value is out of range > make[4]: *** [generic_ts-server.c] error 1 > make[4]: Leaving directory > `/home/l4/tudos/build/pkg/generic_ts/idl/OBJ-x86-l4v2' > make[3]: *** > [/home/l4/tudos/build/pkg/generic_ts/idl/OBJ-x86-l4v2] error 2 > make[3]: Leaving directory > `/home/l4/tudos/l4/pkg/generic_ts/idl' > make[2]: *** [idl] error 2 > make[2]: Leaving directory `/home/l4/tudos/l4/pkg/generic_ts' > make[1]: *** [generic_ts.headers] error 2 > make[1]: Leaving directory `/home/l4/tudos/l4/pkg' > make: *** [pkg] error 2 > ----------------------------------------------------------------------- > firstly I think maybe I didn't do the right selecet,then I change it: > ---------------------------------------------------------- > (amd64) TargetArchitecture > │ │ CPU type: "k7" │ > │ > │ │ (L4.Fiasco) │ > │ > ------------------------------------------------------------------ > but there is another errors: > -------------------------------- > ... Generating generic_ts-server.c > CC="gcc -m64" /home/l4/tudos/l4/../dice/src/dice > --require="3.2.0" -P-DUSE_UCLIBC=y -P-DRAM_BASE=0x0 > -P-DSYSTEM_amd64_l4v2 -P-DARCH_amd64 -P-DCPUTYPE_k7 > -P-DL4API_l4v2 -P-DCONFIG_L4_CALL_SYSCALLS > -P-DCONFIG_L4_ABS_SYSCALLS > -P-I/home/l4/tudos/build/include/amd64/l4v2 > -P-I/home/l4/tudos/build/include/l4v2 > -P-I/home/l4/tudos/build/include/amd64 > -P-I/home/l4/tudos/build/include > -P-I/home/l4/tudos/l4/../dice/include > -P-I/home/drops/include/amd64/l4v2 -P-I/home/drops/include/l4v2 > -P-I/home/drops/include/amd64 -P-I/home/drops/include > -P-nostdinc -P-I/home/l4/tudos/build/include/amd64/uclibc > -P-I/home/l4/tudos/build/include/uclibc > -P-I/home/l4/tudos/build/include/uclibc++ > -P-I/home/drops/include/amd64/uclibc > -P-I/home/drops/include/uclibc -P-I/home/drops/include/uclibc++ > -P-I/usr/lib/gcc/x86_64-linux-gnu/4.1.3/include > -P-I/usr/lib/gcc/x86_64-linux-gnu/4.1.3/include-fixed -Bifiasco > -Bpamd64 -MD /home/l4/tudos/l4/pkg/generic_ts/idl/generic_ts.idl > In file included > from /home/l4/tudos/l4/pkg/generic_ts/idl/generic_ts.idl:0, > from l4/sys/types.h:1, > > from /home/l4/tudos/build/include/amd64/l4v2/l4/sys/types.h:185: > /home/l4/tudos/build/include/l4/sys/__l4_fpage-64bit.h:96.55-65: > error: value is out of range > make[4]: *** [generic_ts-server.c] error 1 > make[4]: Leaving directory > `/home/l4/tudos/build/pkg/generic_ts/idl/OBJ-amd64-l4v2' > make[3]: *** > [/home/l4/tudos/build/pkg/generic_ts/idl/OBJ-amd64-l4v2] error 2 > make[3]: Leaving directory > `/home/l4/tudos/l4/pkg/generic_ts/idl' > make[2]: *** [idl] error 2 > make[2]: Leaving directory `/home/l4/tudos/l4/pkg/generic_ts' > make[1]: *** [generic_ts.headers] error 2 > make[1]: Leaving directory `/home/l4/tudos/l4/pkg' > make: *** [pkg] error 2 > ---------------------------------------------------------- > I think It can work on AMD64,could you help me?thank you very much! > > > fangzhsh, > >

1 0

error while compiling the l4.
by fang zhengshu 06 Apr '08

06 Apr '08

hi all, when I compile the l4 ,errors come out like this : ------------------------------------------------------- $make[4]: *** [generic_ts-server.c] errot 1 $make[4]: Leaving directory `/home/l4/tudos/build/pkg/generic_ts/idl/OBJ-amd64-l4v2' $make[3]: *** [/home/l4/tudos/build/pkg/generic_ts/idl/OBJ-amd64-l4v2] error 2 $make[3]: Leaving directory `/home/l4/tudos/l4/pkg/generic_ts/idl' $make[2]: *** [idl] error 2 $make[2]: Leaving directory `/home/l4/tudos/l4/pkg/generic_ts' $make[1]: *** [generic_ts.headers] error 2 $make[1]: Leaving directory `/home/l4/tudos/l4/pkg' $make: *** [pkg] error 2 --------------------------------------------------------- I am now useing ubuntu 8.04,and I change the cpu info when I compile the fiasco & l4, my leader suggest me use qemu to use debian4.0. does the fiasco support the ubuntu8.04?and i put the cpuinfo following. anyone help me ?thank you! cpuinfo: l4@ubuntu:~/tudos/kernel/fiasco$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 107 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping : 2 cpu MHz : 2200.110 cache size : 512 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch bogomips : 4403.59 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc 100mhzsteps processor : 1 vendor_id : AuthenticAMD cpu family : 15 model : 107 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping : 2 cpu MHz : 2200.110 cache size : 512 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow rep_good pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch bogomips : 4400.24 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc 100mhzsteps

3 2

Re: l4-hackers Digest, Vol 60, Issue 5
by l4 06 Apr '08

06 Apr '08

hi adam, I installed ubuntu8.04 with 64bit through hetwork start(through change the BIOS),now the `uname -a` is: -------------------------------------- Linux ubuntu 2.6.24-15-generic #1 SMP Fri Apr 4 03:10:59 UTC 2008 x86_64 GNU/Linux --------------------------------------- if I don't put all the infomation,please send email to me. regards! fangzhsh > Message: 2 > Date: Sun, 6 Apr 2008 23:36:15 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: error while compiling the l4. > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20080406213615.GD4422(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Fri Apr 04, 2008 at 12:24:06 +0800, fang zhengshu wrote: > > when I compile the l4 ,errors come out like this : > > ------------------------------------------------------- > > $make[4]: *** [generic_ts-server.c] errot 1 > > $make[4]: Leaving directory > > `/home/l4/tudos/build/pkg/generic_ts/idl/OBJ-amd64-l4v2' > > $make[3]: *** [/home/l4/tudos/build/pkg/generic_ts/idl/OBJ-amd64-l4v2] error > > 2 > > $make[3]: Leaving directory `/home/l4/tudos/l4/pkg/generic_ts/idl' > > $make[2]: *** [idl] error 2 > > $make[2]: Leaving directory `/home/l4/tudos/l4/pkg/generic_ts' > > $make[1]: *** [generic_ts.headers] error 2 > > $make[1]: Leaving directory `/home/l4/tudos/l4/pkg' > > $make: *** [pkg] error 2 > > --------------------------------------------------------- > > I am now useing ubuntu 8.04,and I change the cpu info when I compile the > > fiasco & l4, my leader suggest me use qemu to use debian4.0. > > does the fiasco support the ubuntu8.04?and i put the cpuinfo following. > > Do you have a 64bit or 32bit version of Ubuntu installed? > > > Adam

1 0

Re: stpm
by ahmad kamal 06 Apr '08

06 Apr '08

but i got this error while running stpm *tpmrun | l4con/lib/src/contxt.c:63:contxt_init(): *tpmrun | Could not find con at names *tpmrun | main(): Error -3 opening contxt lib -- terminating *tpmrun | *tpmrun | Exiting with -3 this is the command ./fiasco -l names -l dm_phys -l stpm-ux -l tpmrun ----- Original Message ---- > From: Carsten Weinhold <weinhold(a)os.inf.tu-dresden.de> > To: ahmad kamal <amadkamal(a)yahoo.com> > Cc: l4-hackers(a)os.inf.tu-dresden.de > Sent: Friday, April 4, 2008 4:34:58 PM > Subject: Re: stpm > > Am Freitag April 4 2008 schrieb ahmad kamal: > > Hi! > > > thanks for the info, at the same time, i also give myself a try to port the > > codes to be able running on l4.hehe:) one more thing, in order to run > > tpmemulator on ux, does it really need con-ux server? > > con-ux is an L4 server that provides virtual graphical consoles. If you want > to run con-ux on Fiasco-UX with graphics support, you also need the ux_con > binary as Adam explained. However, the TPM emulator itself does not depend on > graphical output and you can therefore compile Fiasco-UX without support for > the virtual framebuffer. In this case, you do not need ux_con (and con-ux > won't work of course). > > Regards, > Carsten > > > ----- Original Message ---- > > > > > From: Carsten Weinhold > > > To: l4-hackers(a)os.inf.tu-dresden.de > > > Cc: ahmad kamal > > > Sent: Thursday, April 3, 2008 6:21:47 PM > > > Subject: Re: stpm > > > > > > Am Donnerstag April 3 2008 schrieb ahmad kamal: > > > > > > Hi Ahmad, > > > > > > > if stpm server able to call tpmemulator, so far as i know it can only > > > > call physical TPM chip. > > > > > > There is a STPM backend that can talk to a TPM emulator. However, this > > > backend assumes that STPM is running on top Fiasco-UX and talks to the > > > 'tpmd' daemon using sockets. In this case, tpmd runs next to Fiasco-UX on > > > the Linux host kernel. > > > > > > We are also porting the TPM emulator such that it can run directly on top > > > of L4, but this is work in progress in a very early stage. > > > > > > Regards, > > > Carsten > > > > > > ___________________________________________________________________________ > >_________ You rock. That's why Blockbuster's offering you one month of > > Blockbuster Total Access, No Cost. > > http://tc.deals.yahoo.com/tc/blockbuster/text5.com > > > ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com

2 1

where to start.
by Varghese Mathew 04 Apr '08

04 Apr '08

Hi, / Pardon me if this is a repeated question./ I recently came across L4 and Fiasco and am interested in studying and developing the same. (Particularly Fiasco as it's written in C++) Could you kindly help me by providing me pointers on how to start off. Specifically, I'm looking for documents which - describe how to build Fiasco and get it running on my machine. - how to build and get l4-linux or other custom operating systems running on top of the above. - the source code organization. Likewise, what is the current status of Fiasco? The latest update I see on the site: http://os.inf.tu-dresden.de/fiasco/ is dated 26 September 2005. Thanks in advance /varghese

2 1

Re: stpm
by ahmad kamal 04 Apr '08

04 Apr '08

thanks for the info, at the same time, i also give myself a try to port the codes to be able running on l4.hehe:) one more thing, in order to run tpmemulator on ux, does it really need con-ux server? ----- Original Message ---- > From: Carsten Weinhold <weinhold(a)os.inf.tu-dresden.de> > To: l4-hackers(a)os.inf.tu-dresden.de > Cc: ahmad kamal <amadkamal(a)yahoo.com> > Sent: Thursday, April 3, 2008 6:21:47 PM > Subject: Re: stpm > > Am Donnerstag April 3 2008 schrieb ahmad kamal: > > Hi Ahmad, > > > if stpm server able to call tpmemulator, so far as i know it can only call > > physical TPM chip. > > There is a STPM backend that can talk to a TPM emulator. However, this backend > assumes that STPM is running on top Fiasco-UX and talks to the 'tpmd' daemon > using sockets. In this case, tpmd runs next to Fiasco-UX on the Linux host > kernel. > > We are also porting the TPM emulator such that it can run directly on top of > L4, but this is work in progress in a very early stage. > > Regards, > Carsten > > ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com

2 1

[Fwd: Re: error while compiling the l4.]
by Martin Pohlack 04 Apr '08

04 Apr '08

Forwarding to group again ...

1 0

ux_con
by ahmad kamal 04 Apr '08

04 Apr '08

hi all, where to get ux_con? what i get so far only con-ux and l4con only? ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com

3 2

Re: where to start.
by ahmad kamal 04 Apr '08

04 Apr '08

hi mathew, u can try think link, http://wiki.tudos.org this pdf also give a good start, though some information is outdated http://dslab.lzu.edu.cn/docs/publications/l4_kickstart.pdf for a novice l4 hackers like me, i would say, its better to use fiasco-ux, here are the link http://os.inf.tu-dresden.de/fiasco/ux/ and also try to go to this link for a basic tutorial and distance learning lecturers http://www.inf.tu-dresden.de/index.php?node_id=1317&ln=en and don't forget to read the mailing list archive if u've got time ----- Original Message ---- From: Varghese Mathew <varghese85.lists(a)gmail.com> To: l4-hackers(a)os.inf.tu-dresden.de Sent: Thursday, April 3, 2008 2:04:51 PM Subject: where to start. Hi, Pardon me if this is a repeated question. I recently came across L4 and Fiasco and am interested in studying anddeveloping the same. (Particularly Fiasco as it's written in C++) Could you kindly help me by providing me pointers on how to start off. Specifically, I'm looking for documents which - describe how to build Fiasco and get it running on my machine. - how to build and get l4-linux or other custom operating systemsrunning on top of the above. - the source code organization. Likewise, what is the current status of Fiasco? The latest update I see on the site: http://os.inf.tu-dresden.de/fiasco/ is dated 26 September 2005. Thanks in advance /varghese ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com

1 0

stpm
by ahmad kamal 03 Apr '08

03 Apr '08

if stpm server able to call tpmemulator, so far as i know it can only call physical TPM chip. ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com

2 1

direct IPC VS Short IPC
by hazwan 30 Mar '08

30 Mar '08

Hello I have problems in understanding short ipc and direct long IPC. Just want to know that is it implementing register short IPC with direct long IPC implementation is the same. Unlike indirect long IPC, we must use the message header (strdope, send dope and size dope) . Do i must also use the message structure for implementing direct long ipc or i just use the same implementation on short register message (L4_IPC_SHORT_MSG)? Im kinda confuse and unsure of this issue due to unproper theory understanding. Like indirect IPC, i can understand that the memory that saves the message is only being reffered by both threads that wish to communicate by referring the memory address of the message. Unlike direct long IPC message, what I do understand is that each thread has a copy of the message at the threads respective user space. However, I dont know how to copy the message from one thread user space to the other threads user space using IPC call. But if the implementation of the direct long IPC is as the same as the register message(L4_IPC_SHORT_MSG), then i think I can imagine the flow. Thank you and your help is highly appreciated. -- View this message in context: http://www.nabble.com/direct-IPC-VS-Short-IPC-tp16247387p16247387.html Sent from the L4 mailing list archive at Nabble.com.

2 1

Re: run-l4 - to start another task
by ahmad kamal 30 Mar '08

30 Mar '08

hi all, i still failed to load another task using run-l4 here is my later config file #hello.cfg verbose 0 modpath "/boot/l4linux_2" task "hello" "" i alos tried #hello.cfg verbose 0 modpath "(hd0,5)/boot/l4linux_2" task "hello" "" for your info my boot partition is in extended partition. at l4linux terminal i run this command: ./run-l4 --fprov=BMODFS "hello.cfg" and ./run-l4 --fprov "BMODFS" "hello.cfg" and i also put hello in menu.lst. and it still failed to load hello as an alternative can u guys help me give an example of working: menu.lst config file to pass to bmodfs command line to execute in l4linux ----- Original Message ---- > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > To: l4-hackers(a)os.inf.tu-dresden.de > Sent: Wednesday, March 12, 2008 7:59:59 PM > Subject: Re: run-l4 - to start another task > > > On Tue Mar 11, 2008 at 20:55:51 -0700, ahmad kamal wrote: > > 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" > > When using bmodfs you do not need to specify a path. > > > 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? > > No, run-l4 is a Linux program, it only works in L4Linux. > > > do i need to load the task i would like to call using run-l4 during boot time? > > The binary needs to be available at the file provider you're using. So > when using bmodfs the binary needs to be loaded in menu.lst as a data > module for bmodfs (basically as usual). > > > 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

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

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