l4-hackers May 2008

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

12 participants
19 discussions

Back to UTCB IPC
by Marc CHALAND 11 Oct '09

11 Oct '09

Hi, I am back with my problem with UTCB IPC. To sum up the context : I use pure l4env applications. Here is the scenario between my server and my client : 1. client makes an UTCB IPC to manager. Manager does an l4rm_area_reserve, creates a rcv_fpage, creates worker and sends back worker thread id to client. 2. client allocates memory and associated flexpage and sends it to server. 3. UTCB IPC is sent to worker with 3 parameters : - on client side : utcb->values=0xbff00200: arg1=0x2 arg2=… [View More]

4 9

New list member Mike Jolley
by John van V. 31 May '08

31 May '08

Hi Mike (and all), I am writing about L4, its hopeful development path, and how ubiquity in systems can lead to information democracy. The goals are naturally social, but the technology layer is key. I think you have good ideas and I hope you are able to bring them to fully working level. I hope you can be verbose about your research and can supply all your resources, and perhaps images, for the pubic. I have two sites that I want use as a vehicles for this research direction, http://… [View More]

1 0

New list member Mike Jolley
by Mike Jolley 31 May '08

31 May '08

Hi all, I'm new to this mailing list but I've done a little study of the source code, history, and other things surrounding Pistachio and L4-Hurd. My knowledge of L4 is very limited. I have a goal of a drop-in Linux replacer built on much better technology, such as L4 or the kind of work being done at VPRI. I have a rough design for such a thing but a lot of major pieces are missing. On the other hand, a totally new (to me) system with enough apps to get me through the day would be … [View More]

2 1

Question about ipcmon and assembler IPC shortcut
by Marc CHALAND 30 May '08

30 May '08

Hi, I've made a little test with ipcmon. This test is a simple application launched by loader which makes an IPC to names (05) and to log server (06). With assembler IPC shortcut, I don't need to set an accept rule to names. ipcmon doesn't handle requests to names. If I activate jdb IPC monitoring, then IPC to names are handled by ipcmon. After some more checking, it seems that assembler IPC shortcut doesn't care about parity. For example, if 4 (roottask) is allowed, then 5 is also allowed … [View More]

2 1

How to eliminate echoes when loading module
by Shih-I Huang 27 May '08

27 May '08

Hi all, I am currently trying to use microkernel in our platform (X86 platform). However, I found the Fiasco returns many echoes when booting and I would like to remove them. Is there any way to remove these echoes? Besides, is there any way to display an image when booting system? (like usplash in Ubuntu) Thanks in advance. Eric.

2 1

fiasco can't start correctly
by fei li 27 May '08

27 May '08

Hi I have compiled the fiasco and l4 packages in the amd64 environment, now I get some binaries that I try to start the l4 in qemu, next is my menu.lst color 24 52 title Example entry kernel /bootstrap32 -serial -modaddr 0x2000000 module /main module /sigma0 module /roottask module /omega0 Then in the qemu, it says "Read-write (data) checksum does not match", next is the outputs in the qemu window L4 Bootstrapper move modules to 2000000 with offset ed0000 move module 4 start 126e000 -… [View More]> 213e000 move module 3 start 11d0000 -> 20a0000 move module 2 start 119c000 -> 206c000 move module 1 start 1130000 -> 2000000 Scanning /main Scanning /sigma0 Scanning /roottask Bootloader MMAP: [ 0, 9fc00) RAM (1) [ 9fc00, a0000) reserved (2) [ e8000, 100000) reserved (2) [ 100000, 7ff0000) RAM (1) [ 7ff0000, 8000000) ACPI (3) [ fffc0000, 100000000) reserved (2) Relocated mbi to [0x76000-0x760b8] Loading /main Loading /sigma0 Loading /roottask find kernel info page... found kernel info page at 0x1000 [ 1000, 75fff] Kern /main [ 76000, 761b5] Root Multiboot info [ 9fc00, 9ffff] Arch BIOS [ e8000, fffff] Arch BIOS [ 100000, 10a6df] Sigma0 /sigma0 [ 110000, 2c6fff] Root /roottask [ 2d0080, 2daf57] Boot bootstrap [ 300000, 34a8af] Kern /main [ 213e000, 2187e07] Root Modules Memory [ 7ff0000, 7ffffff] Arch BIOS [ fffc0000, ffffffff] Arch BIOS API Version: (87) experimental Sigma0 config ip:0000000000104780 sp:00000000002da990 Roottask config ip:0000000000110000 sp:0000000000000000 Starting kernel /main at 0000000000300ad0 Now i guess there are problems with the "main" binary, but i don't know what it is. # CONFIG_IA32 is not set CONFIG_AMD64=y # CONFIG_ARM is not set CONFIG_PF_PC=y # CONFIG_PF_UX is not set # CONFIG_PF_REALVIEW is not set # CONFIG_PF_INTEGRATOR is not set # CONFIG_PF_XSCALE is not set # CONFIG_PF_SA1100 is not set CONFIG_ABI_V2=y # CONFIG_ARM_PXA is not set # CONFIG_ARM_SA is not set # CONFIG_ARM_920T is not set # CONFIG_ARM_926 is not set # CONFIG_ARM_1176 is not set # CONFIG_ARM_MPCORE is not set # CONFIG_IA32_486 is not set # CONFIG_IA32_586 is not set # CONFIG_IA32_686 is not set # CONFIG_IA32_P2 is not set # CONFIG_IA32_P3 is not set # CONFIG_IA32_P4 is not set # CONFIG_IA32_PM is not set # CONFIG_IA32_K6 is not set # CONFIG_IA32_K7 is not set # CONFIG_IA32_K8 is not set CONFIG_AMD64_K8=y CONFIG_SCHED_PIT=y # CONFIG_SCHED_RTC is not set # CONFIG_SCHED_APIC is not set # CONFIG_WORKAROUND_AMD_FPU_LEAK is not set # # Kernel options # # CONFIG_PL0_HACK is not set CONFIG_TASK_CAPS=y # CONFIG_USER_LOCKS is not set CONFIG_ASSEMBLER_IPC_SHORTCUT=y CONFIG_CONTEXT_4K=y CONFIG_IO_PROT=y # CONFIG_IO_PROT_IOPL_3 is not set # # Debugging # CONFIG_INLINE=y # CONFIG_NDEBUG is not set CONFIG_NO_FRAME_PTR=y CONFIG_STACK_DEPTH=y # CONFIG_LIST_ALLOC_SANITY is not set # CONFIG_BEFORE_IRET_SANITY is not set CONFIG_SERIAL=y CONFIG_JDB=y CONFIG_JDB_MISC=y CONFIG_POWERSAVE_GETCHAR=y # CONFIG_WARN_NONE is not set CONFIG_WARN_WARNING=y # CONFIG_WARN_ANY is not set # # Compiling # CONFIG_CC="gcc" CONFIG_CXX="g++" CONFIG_HOST_CC="gcc" CONFIG_HOST_CXX="g++" CONFIG_VERBOSE=y CONFIG_MAINTAINER_MODE=y CONFIG_LABEL="" CONFIG_EXPERIMENTAL=y CONFIG_PERF_CNT=y CONFIG_BIT64=y CONFIG_WARN_LEVEL=1 CONFIG_XARCH="amd64" CONFIG_IA32_TARGET="AMD Opteron" CONFIG_ABI="v2" CONFIG_DECEIT_BIT_DISABLES_SWITCH=y I choose amd64 in the "cpu type" option, then i get the errors I have mentioned, then i keep the default config and when I start the l4 in qemu, it says Scanning /main This is an invalid binary, fix it. I don't know why, i hope someone could help me and thanks. [View Less]

2 4

the binary file come from l4 on amd64
by fangzhengshu 26 May '08

26 May '08

hi all, my system is AMD64,and by help of mailing list I have compiled l4 successfully.I have also see that the latest svn of l4 have check the pkg/bootstrap/server/src/Makefile and add -m32 after CC32.But when I do ls in /home/l4/tudos/build/bin/amd64_k8 and l4v2: ------------------- l4@fwnc:~/tudos/build/bin/amd64_k8$ ls bootstrap32 l4v2 l4@fwnc:~/tudos/build/bin/amd64_k8$ ls l4v2/ atomictest dopecmd l4io libld-l4.s.so … [View More]

2 1

Re: l4-hackers Digest, Vol 61, Issue 16
by l4 21 May '08

21 May '08

> > -Wl,-T,/home/l4/tudos/l4/pkg/bootstrap/server/src/ARCH-amd64/boot32/bootstrap32.ld,--gc-sections boot.o32 boot_idt.o32 boot_cpu.o32 boot_kernel.o32 load_elf.o32 minilibc_support.o32 bootstrap32.bin /home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a -lgcc > > /usr/bin/ld: i386 architecture of input file `boot.o32' is > > incompatible with i386:x86-64 output > > Does it help if you add -m32 to the CC32 line in > /… [View More]

1 0

Re: l4-hackers Digest, Vol 61, Issue 16
by fang zhengshu 21 May '08

21 May '08

hi , > > > > -Wl,-T,/home/l4/tudos/l4/pkg/bootstrap/server/src/ARCH-amd64/boot32/bootstrap32.ld,--gc-sections > boot.o32 boot_idt.o32 boot_cpu.o32 boot_kernel.o32 load_elf.o32 > minilibc_support.o32 bootstrap32.bin > /home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a > -lgcc > > /usr/bin/ld: i386 architecture of input file `boot.o32' is > > incompatible with i386:x86-64 output > > Does it help if you … [View More]add -m32 to the CC32 line in > /home/l4/tudos/l4/pkg/bootstrap/server/src/Makefile? like this: > CC32 = $(filter-out -m64, $(CC)) -m32 I have done it after add -m32,and the old error was handled.But when I compile l4 again , there is another error : --------------------------------------- PWD=/home/l4/tudos/l4/pkg/ipcmon make -C ipcmon all -o lib -o include -o idl make[2]: Entering directory `/home/l4/tudos/l4/pkg/ipcmon' test -f server/broken -o -f server/obsolete || \ if [ -f server/Makefile ] ; then PWD=/home/l4/tudos/l4/pkg/ipcmon/server make -C server ; fi make[3]: Entering directory `/home/l4/tudos/l4/pkg/ipcmon/server' test -f src/broken -o -f src/obsolete || \ if [ -f src/Makefile ] ; then PWD=/home/l4/tudos/l4/pkg/ipcmon/server/src make -C src ; fi make[4]: Entering directory `/home/l4/tudos/l4/pkg/ipcmon/server/src' PWD=/home/l4/tudos/build/pkg/ipcmon/server/src/OBJ-amd64_k8-l4v2 make -C /home/l4/tudos/build/pkg/ipcmon/server/src/OBJ-amd64_k8-l4v2 -f Makefile make[5]: Entering directory `/home/l4/tudos/build/pkg/ipcmon/server/src/OBJ-amd64_k8-l4v2' ==> Linking ipcmon LD_PRELOAD=/home/l4/tudos/build/tool/gendep/libgendep.so GENDEP_TARGET=ipcmon GENDEP_BINARY=ld GENDEP_BINARY_ALT1=ld ld -m elf_x86_64 -o ipcmon /home/l4/tudos/build/lib/amd64_k8/crt0.o components.o capdescriptor.o capmanager.o blacklist.o whitelist.o ipcmon-server.o -n -Ttext=0x1000000 --hash-style=sysv -L/home/l4/tudos/build/lib/amd64_k8/l4v2 -L/home/l4/tudos/build/lib/amd64_k8 -L/home/l4/tudos/build/lib -L/home/l4/tudos/lib/amd64_k8/l4v2 -L/home/l4/tudos/lib/amd64_k8 -L/home/l4/tudos/lib -T/home/l4/tudos/build/lib/amd64_k8/main_stat.ld -lparsecmdline -static -lgeneric_ts -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -lsemaphore -llogserver_capsule -lnames -ll4util_root -ll4util -lroot -ll4env -ll4env_err -ll4rm -ldm_generic -ldm_mem -lthread -lslab -ll4sys -luc_c++ -lc++start.o /usr/lib/gcc/x86_64-linux-gnu/4.2.3/libsupc++.a -lmain -lcxx_base -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 -lsigma0 -luc_c /usr/lib/gcc/x86_64-linux-gnu/4.2.3/libgcc_eh.a /usr/lib/gcc/x86_64-linux-gnu/4.2.3/libgcc.a -luc_c -ll4sys -ll4util -luc_be_minimal_io -Ttext=0x1000000 --warn-common -gc-sections /usr/lib/gcc/x86_64-linux-gnu/4.2.3/libsupc++.a(eh_alloc.o): In function `__static_initialization_and_destruction_0(int, int)': (.text._Z41__static_initialization_and_destruction_0ii+0xa2): undefined reference to `__stack_chk_fail' /usr/lib/gcc/x86_64-linux-gnu/4.2.3/libsupc++.a(cp-demangle.o): In function `d_demangle': (.text+0x4232): undefined reference to `__stack_chk_fail' make[5]: *** [ipcmon] error 1 make[5]: Leaving directory `/home/l4/tudos/build/pkg/ipcmon/server/src/OBJ-amd64_k8-l4v2' make[4]: *** [/home/l4/tudos/build/pkg/ipcmon/server/src/OBJ-amd64_k8-l4v2] error 2 make[4]: Leaving directory `/home/l4/tudos/l4/pkg/ipcmon/server/src' make[3]: *** [src] error 2 make[3]: Leaving directory `/home/l4/tudos/l4/pkg/ipcmon/server' make[2]: *** [server] error 2 make[2]: Leaving directory `/home/l4/tudos/l4/pkg/ipcmon' make[1]: *** [ipcmon.bin] error 2 make[1]: Leaving directory `/home/l4/tudos/l4/pkg' make: *** [pkg] error 2 l4@fwnc:~/tudos/l4$ --------------------------------------- I come across the stack problem last week when I reinstall grub-0.97-os.7,and handle it by add CFLAGS=-fno-stack-protector.So I think it's the same question,and add CFLAGS =-fno-stack-protector in pkg/ipcmon/server/src/Makefile but the problem cann't be handled. Could you please give some advice? much thanks! fang, [View Less]

1 0

another error while I compile l4
by l4 19 May '08

19 May '08

hi all, several days ago Cheng suggest me use qemu to virtual a 32bit system to compile l4,then i do.The l4 can work ,but the qemu is not very stable on my computer,sometimes I even can't login the qemu.So I recompile l4 on my computer again by using the latest tudos package.The error come out again : ------------------------ ==> "bootstrap" built ... Generating bootstrap32.bin objcopy -S bootstrap bootstrap64.bin chmod -x bootstrap64.bin … [View More]objcopy -B i386 -I binary -O elf32-i386 bootstrap64.bin bootstrap32.bin ==> Linking bootstrap32 gcc -o bootstrap32 -nostdlib -static \ -Wl,-T,/home/l4/tudos/l4/pkg/bootstrap/server/src/ARCH-amd64/boot32/bootstrap32.ld,--gc-sections boot.o32 boot_idt.o32 boot_cpu.o32 boot_kernel.o32 load_elf.o32 minilibc_support.o32 bootstrap32.bin /home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a -lgcc /usr/bin/ld: i386 architecture of input file `boot.o32' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `boot_idt.o32' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `boot_cpu.o32' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `boot_kernel.o32' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `load_elf.o32' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `minilibc_support.o32' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `bootstrap32.bin' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `/home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a(__assert_fail.o)' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `/home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a(memcpy.o)' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `/home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a(memset.o)' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `/home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a(printf.o)' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `/home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a(puts.o)' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `/home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a(vprintf.o)' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `/home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a(__v_printf.o)' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `/home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a(strtol.o)' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `/home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a(strtoul.o)' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `/home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a(__lltostr.o)' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `/home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a(__ltostr.o)' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `/home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a(isspace.o)' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture of input file `/home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a(memmove.o)' is incompatible with i386:x86-64 output /home/l4/tudos/build/pkg/bootstrap/server/src/ARCH-amd64/libc32/OBJ-amd64_k8/libc32.a(__lltostr.o): In function `__lltostr': /home/l4/tudos/l4/pkg/bootstrap/server/src/ARCH-amd64/libc32/__lltostr.c:29: undefined reference to `__umoddi3' /home/l4/tudos/l4/pkg/bootstrap/server/src/ARCH-amd64/libc32/__lltostr.c:30: undefined reference to `__udivdi3' collect2: ld return 1 make[5]: *** [bootstrap32] error 1 make[5]: Leaving directory `/home/l4/tudos/build/pkg/bootstrap/server/src/OBJ-amd64_k8' make[4]: *** [/home/l4/tudos/build/pkg/bootstrap/server/src/OBJ-amd64_k8] error 2 make[4]: Leaving directory `/home/l4/tudos/l4/pkg/bootstrap/server/src' make[3]: *** [src] error 2 make[3]: Leaving directory `/home/l4/tudos/l4/pkg/bootstrap/server' make[2]: *** [server] error 2 make[2]: Leaving directory `/home/l4/tudos/l4/pkg/bootstrap' make[1]: *** [bootstrap.bin] error 2 make[1]: Leaving directory `/home/l4/tudos/l4/pkg' make: *** [pkg] error 2 ------------------------ my cpu information is : ------------------------ l4@fwnc:~$ 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.104 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.55 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 ----------------------- I also check the fiasco and l4 as the AMD64 need,please see the attachments for detail .is there any problem with my lib?I google that someone suggest that: ***************************** You can install the ia32-libs, libc6-dev-i386, etc packages to get the 32bit libs on your 64bit install. Alternatively, setting up a development chroot is pretty easy, and not such a bad idea. pbuilder makes this quite easy. Install the pbuilder package, then run Code: sudo pbuilder create --distribution edgy --debootstrapopts arch --debootstrapopts i386 You can then login to your chroot with sudo pbuilder login. This won't save any changes you make in the chroot (you need to pass --save-after-login to do that), though, since it's designed for building debian packages. ****************************** Could you please give me some advice ? thank you very much! [View Less]

2 1

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 May 2008