- l4-hackers - example.com Site

Re: Porting libtiff library
by Irvanda Kurniadi 16 Jan '14

16 Jan '14

> > TLS definition in libuc_c.a(errno.o) section .tbss mismatches non-TLS > reference in libtiff.so > libuc_c.a: could not read symbols: Bad value > I found the source of the problem. I compiled, assambled, and linked libtiff and libtiff program with different toolchain (libtiff using gcc, libtiff program using uClibc). regards, Irvanda

1 0

Re: Porting libtiff library
by Irvanda Kurniadi 16 Jan '14

16 Jan '14

On Sun, 12 Jan 2014 23:17:12 +0100, Adam Lackorzynski wrote: > > After I ported libtiff library then I tried to compile simple tiff > > program, I found this error: > > > > TLS definition in libuc_c.a(errno.o) section .tbss mismatches non-TLS > > reference in libtiff.so > > > > libuc_c.a: could not read symbols: Bad value > > > > > > What does it mean? > > Looks like a shared libtiff is being linked to an otherwise static > program. How does the Makefile of your libtiff program look like? > This is the Makefile of my libtiff program: PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. DEPENDS_PKGS = libtiff REQUIRES_LIBS = libtiff TARGET = tiff_test SRC_C = tiff_test.c LDFLAGS = -ltiff include $(L4DIR)/mk/prog.mk regards, Irvanda

1 0

Writing to TTBCR on ARM9 causes fault
by Martin Schröder 14 Jan '14

14 Jan '14

I am trying to get L4 running on the freescale i.MX28 EVK. During startup it stops with a fault at fiasco/src/kern/arm/bootstrap.cpp:236 asm volatile("mcr p15, 0, %[ttbcr], c2, c0, 2" // TTBCR : : [ttbcr] "r" (Page::Ttbcr_bits)); Unlike ARM11, the ARM9 does not know about TTBCR. [http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0198e/I10149…] So maybe this might be omitted on ARM9? Martin

2 1

NOVA, NUL, snapshotting
by Sartakov A. Vasily 13 Jan '14

13 Jan '14

Hello. Does the NOVA/NUL support snapshotting of VMes? -- Sartakov A. Vasily

5 21

about the alien thread
by Wei Jin 12 Jan '14

12 Jan '14

Hello! I'm tring to understand how the alien thread works. I'm not confident in what I have got. Please correct me: When an alien thread invokes an IPC call, it raises an exception, which would be caught by the excenption handler as configured. The exception handler could get the status of the alien thread by reading exception regs in UTCB ( l4_utcb_exc<http://os.inf.tu-dresden.de/L4Re/doc/group__l4__utcb__exc__api.html#ga3d957…> () ). The exception handler could also set this IPC call allowed or not. If this IPC call is allowed, the alien thread acts like a non-alien thread the performs the IPC call. // This is what I doubt since the alien example does not provide a valid IPC call. If this IPC call is not allowed, the alien thread executes from where it raise the exception.

2 1

Porting libtiff library
by Irvanda Kurniadi 12 Jan '14

12 Jan '14

Thanks Adam, > >* I've put the revision of jpegv9a and it solved the problem of true and > *>* false. But now I'm having another problem. I compiled libtiff library and > *>* got this error message: > *> >* lib/contrib/contrib/dbs/tiff-bi.s.o: In function `main': > *>* /home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/dbs/tiff-bi.c:36: > *>* multiple definition of `main' > *>* lib/contrib/contrib/addtiffo/addtiffo.s.o:/home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/addtiffo/addtiffo.c:73: > *>* first defined here > *>* lib/contrib/contrib/dbs/tiff-grayscale.s.o: In function `main': > *>* /home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/dbs/tiff-grayscale.c:42: > *>* multiple definition of `main' > *>* lib/contrib/contrib/addtiffo/addtiffo.s.o:/home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/addtiffo/addtiffo.c:73: > *>* first defined here > * > I think you included too many files in your Makefile. libtiff also > contains programs (e.g. for testing purposes) which are not part of the > library itself. You must not include those when building the library. > Also, including files with 'win32' in the file name does not seem good > to me. I recommend to only include those files that are part of a > library build on Linux (display with "ar t libtiff.a"). > > After I ported libtiff library then I tried to compile simple tiff program, I found this error: TLS definition in libuc_c.a(errno.o) section .tbss mismatches non-TLS > reference in libtiff.so libuc_c.a: could not read symbols: Bad value > What does it mean? I found a solution for the problem which is similar to mine. http://os.inf.tu-dresden.de/pipermail/l4-hackers/2006/002126.html They said,"The errno.h file declares errno as global rather than per-thread, which is bogus on a TLS system. Official fix is to remove that errno.h file completely". But I don't know which errno.h that I should remove. Or maybe you have different solution for this problem? Regards, Irvanda

2 1

Porting libtiff library
by Irvanda Kurniadi 09 Jan '14

09 Jan '14

Thanks Adam, I've put the revision of jpegv9a and it solved the problem of true and false. But now I'm having another problem. I compiled libtiff library and got this error message: lib/contrib/contrib/dbs/tiff-bi.s.o: In function `main': /home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/dbs/tiff-bi.c:36: multiple definition of `main' lib/contrib/contrib/addtiffo/addtiffo.s.o:/home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/addtiffo/addtiffo.c:73: first defined here lib/contrib/contrib/dbs/tiff-grayscale.s.o: In function `main': /home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/dbs/tiff-grayscale.c:42: multiple definition of `main' lib/contrib/contrib/addtiffo/addtiffo.s.o:/home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/addtiffo/addtiffo.c:73: first defined here ... ... ... lib/contrib/contrib/addtiffo/addtiffo.s.o:/home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/addtiffo/addtiffo.c:73: first defined here lib/contrib/tools/tiffsplit.s.o: In function `main': /home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/tools/tiffsplit.c:59: multiple definition of `main' lib/contrib/contrib/addtiffo/addtiffo.s.o:/home/irvanda/l4linux_test/src/l4/pkg/libtiff/lib/contrib/contrib/addtiffo/addtiffo.c:73: first defined here make[8]: *** [libtiff.so] Error 1 make[7]: *** [/home/irvanda/l4linux_test/obj/l4/x86/pkg/libtiff/lib/build/OBJ-x86_586] Error 2 make[6]: *** [build] Error 2 make[5]: *** [lib] Error 2 make[4]: *** [libtiff] Error 2 make[3]: *** [pkg] Error 2 make[2]: *** [x] Error 2 ^Cmake[1]: *** [build_all] Interrupt make: *** [all] Interrupt This is my Makefile in build directory: PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. TARGET = libtiff.a libtiff.so DEPENDS_PKGS = libjpeg SYSTEMS = $(SYSTEMS_PLAIN) LIBS = $(GCCLIB) include $(L4DIR)/mk/Makeconf REQUIRES_LIBS = libjpeg zlib CONTRIB_INCDIR = libtiff SRC_C = $(patsubst $(PKGDIR)/%.c, %.c, $(filter-out $(PKGDIR)/lib/contrib/libtiff/tif_win32.c $(PKGDIR)/lib/contrib/libtiff/mkg3states.c, $(wildcard $(PKGDIR)/lib/contrib/libtiff/*.c))) \ $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard $(PKGDIR)/lib/contrib/contrib/addtiffo/*.c)) \ $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard $(PKGDIR)/lib/contrib/contrib/dbs/*.c)) \ $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard $(PKGDIR)/lib/contrib/contrib/iptcutil/*.c)) \ $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard $(PKGDIR)/lib/contrib/contrib/mfs/*.c)) \ $(patsubst $(PKGDIR)/%.c, %.c, $(wildcard $(PKGDIR)/lib/contrib/port/*.c)) \ $(patsubst $(PKGDIR)/%.c, %.c, $(filter-out $(PKGDIR)/lib/contrib/tools/sgi2tiff.c $(PKGDIR)/lib/contrib/tools/sgisv.c $(PKGDIR)/lib/contrib/tools/tiffgt.c $(PKGDIR)/lib/contrib/tools/sgisv.c $(PKGDIR)/lib/contrib/tools/ycbcr.c, $(wildcard $(PKGDIR)/lib/contrib/tools/*.c))) PRIVATE_INCDIR = $(PKGDIR)/lib/contrib/libtiff \ $(PKGDIR)/lib/contrib/contrib/addtiffo \ $(PKGDIR)/lib/contrib/contrib/dbs \ $(PKGDIR)/lib/contrib/contrib/iptcutil \ $(PKGDIR)/lib/contrib/contrib/mfs \ $(PKGDIR)/lib/contrib/port \ $(PKGDIR)/lib/contrib/tools \ vpath %.c $(PKGDIR) include $(L4DIR)/mk/lib.mk # prevent warnings CFLAGS := $(filter-out -Wextra -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wimplicit-function-declaration -Wformat,$(CFLAGS)) I hope some of hackers here can help me solving this problem. best regards, Irvanda

2 1

IRQ request from server to client and server.loop()
by cem akpolat 21 Dec '13

21 Dec '13

Dear all, I am quite new to the microkernel concept and I am trying to somehow build an IRQ mechanism between client and server. There are two questions that I want to ask: 1- Is it possible to receive an IRQ message being sent by Server on the client and handle it? I tried to apply that on the shared_ds examples. However what I see is the IRQ registration could be done only on the server side. How can a client, in a shared memory case,receive an IRQ request from server and how can a server send an IRQ request (in other words trigger an IRQ) to the client. 2- How can we remove or disable the server.loop mechanism? What is the role of this function? I appreciate that you can answer these questions. Best regards, Cem

2 7

Error while compiling program in l4re
by Irvanda Kurniadi 20 Dec '13

20 Dec '13

Hi, I was trying to compile my program which contains libtiff and libgomp. But I got this error message when I compiled my program. ld: errno: TLS reference in ..../l4linux_test/obj/l4/x86/lib/x86_586/l4f/libpthread.a(semaphore.o) mismatches non-TLS reference in ..../l4linux_test/obj/l4/x86/lib/x86_586/libtiff.so ..../l4linux_test/obj/l4/x86/lib/x86_586/l4f/libpthread.a: could not read symbols: Bad value Previously, I ported the libtiff library by myself. Is it happen because I didn't port it properly? Regards, Irvanda

1 0

L4RE compile error in file rt_sched-proto.h
by Wei Jin 19 Dec '13

19 Dec '13

Hi all! I got several errors while compiling L4RE(r59). It's about real-time scheduling extension headers in L4RE(file 'pkg/l4sys/ARCH-x86/rt_sched.h', 'pkg/l4sys/ARCH-x86/rt_sched-proto.h'). Here's the mesage: In file included from /home/soap/project/L4-Build/x86/l4re/include/x86/l4/sys/rt_sched.h:29:0, from /home/soap/project/L4/l4/pkg/rtdemo/server/src/rtdemo.c:13: /home/soap/project/L4-Build/x86/l4re/include/x86/l4/sys/rt_sched-proto.h:30:29: fatal error: l4/sys/syscalls.h: No such file or directory I can't find any header named "syscalls.h" in pkg/l4sys, so I comment it. Then I got more errors: In file included from /home/soap/project/L4-Build/x86/l4re/include/x86/l4/sys/rt_sched.h:29:0, from /home/soap/project/L4/l4/pkg/rtdemo/server/src/rtdemo.c:13: /home/soap/project/L4-Build/x86/l4re/include/x86/l4/sys/rt_sched-proto.h:57:5: error: unknown type name ‘l4_low_high_t’ /home/soap/project/L4-Build/x86/l4re/include/x86/l4/sys/rt_sched-proto.h:79:16: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘slice’ /home/soap/project/L4-Build/x86/l4re/include/x86/l4/sys/rt_sched-proto.h:105:19: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘slice’ /home/soap/project/L4-Build/x86/l4re/include/x86/l4/sys/rt_sched-proto.h:127:31: error: unknown type name ‘l4_threadid_t’ I can't find the definition of 'l4_low_high_t' and 'l4_threadid_t' in L4RE, but instead I found them in the legacy l4env: typedef struct { l4_umword_t low; l4_umword_t high; } l4_low_high_t; tyoedef union { l4_uint32_t raw; l4_threadid_struct_t id; } l4_threadid_t; Should I define them the same as l4env? The declairation 'L4_INLINE int l4_rt_add_time slice(l4_threadid_t dest, int prio, int time)", which also appears in the online doc( http://os.inf.tu-dresden.de/L4Re/doc/group__api__calls__rt__sched.html) seems strange. Is it a typo? "l4_rt_add_time_slice" seems reasonable. I'm not sure whether these are proper ways to fix so I need some help. Any advice would be appreciated. Soap

2 1

Assertion failed on FPU
by Wei Jin 16 Dec '13

16 Dec '13

Hi all, I'm trying to get L4Linux running on my raspberry pi(model B) but there is something wrong that I couldn't figure out. The error message is: Assertion failed: 'Fpu::fpu.current().owner() == current()' [ret=0xf0013544] /home/soap/project/L4/kernel/fiasco/src/kern/arm/thread-arm.cpp:800 at f0012b7c The value of "Fpu::fpu.current().owner()" is 0 which seems to be the value set when fpu initialized. Can anyone help me to fix it? FPU is enabled in Fiasco config and the hello example works. All the components are at latest revision(l4linux:41, fiasco:59, l4re:59) Please let me know if something is missing. Here's the full log: ------------------------------------------- L4 Bootstrapper Build: #37 Sun Dec 15 22:03:04 CST 2013, 4.7.2 Scanning up to 256 MB RAM Memory size is 256MB (00000000 - 0fffffff) RAM: 0000000000000000 - 000000000fffffff: 262144kB Total RAM: 256MB mod09: 0151b000-0181b000: ramdisk-arm.rd mod08: 01229000-0151a4b8: vmlinuz.arm mod07: 01228000-012280bd: arm-rv.io mod06: 01112000-01227740: io mod05: 01111000-01111173: l4lx.cfg mod04: 010be000-01110bec: ned mod03: 010a4000-010bd498: l4re mod02: 01072000-010a3664: moe mod01: 01068000-010713b0: sigma0 mod00: 01016000-0106787c: fiasco Moving up to 10 modules behind 1100000 moving module 00 { 1016000-106787b } -> { 1905000-195687b } [333948] moving module 01 { 1068000-10713af } -> { 1957000-19603af } [37808] moving module 02 { 1072000-10a3663 } -> { 1961000-1992663 } [202340] moving module 03 { 10a4000-10bd497 } -> { 181b000-1834497 } [103576] moving module 04 { 10be000-1110beb } -> { 1835000-1887beb } [338924] moving module 05 { 1111000-1111172 } -> { 1100000-1100172 } [371] moving module 06 { 1112000-122773f } -> { 1101000-121673f } [1136448] moving module 07 { 1228000-12280bc } -> { 1217000-12170bc } [189] moving module 08 { 1229000-151a4b7 } -> { 1218000-15094b7 } [3085496] moving module 09 { 151b000-181afff } -> { 150a000-1809fff } [3145728] moving module 03 { 181b000-1834497 } -> { 180a000-1823497 } [103576] moving module 04 { 1835000-1887beb } -> { 1824000-1876beb } [338924] Scanning fiasco -serial_esc Scanning sigma0 Scanning moe rom/l4lx.cfg Relocated mbi to [0x100f000-0x100f15d] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list 'regions' [ 1000, 19ff] { a00} Kern fiasco [ 2000, 5efff] { 5d000} Kern fiasco [ 90000, 968cf] { 68d0} Sigma0 sigma0 [ 98000, 9e17b] { 617c} Sigma0 sigma0 [ 140000, 16d58b] { 2d58c} Root moe [ 170000, 186f0f] { 16f10} Root moe [ 1000000, 10153f7] { 153f8} Boot bootstrap [ 100f000, 100f25a] { 25b} Root Multiboot info [ 1100000, 1876beb] { 776bec} Root Module API Version: (87) experimental Sigma0 config ip:00090100 sp:01014de4 Roottask config ip:00140260 sp:00000000 Starting kernel fiasco at 000011ec Hello from Startup::stage2 Cache config: ON ID_PFR[01]: 00000111 00000011 ID_[DA]FR0: 00000033 00000000 ID_MMFR[04]: 01130003 10030302 01222100 00000000 FPU0: Arch: VFPv2(1), Part: VFP11(20), r: 5, v: b, i: 41, t: hard, p: dbl/sngl SERIAL ESC: allocated IRQ 57 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: r59 compiled with gcc 4.7.2 for Broadcom 2835 [] Build: #18 Sun Dec 15 21:36:50 CST 2013 Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 2000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:0;fff] [0:5f000;8ffff] [0:97000;97fff] [0:9f000;13ffff] [4:140000;16dfff] [0:16e000;16ffff] [4:170000;186fff] [0:187000;100efff] [4:100f000;100ffff] [0:1010000;10fffff] [4:1100000;1876fff] [0:1877000;effffff] IOMEM:---------------------- [0:10000000;ffffffff] MOE: Hello world MOE: found 237400 KByte free memory MOE: found RAM from 5f000 to f000000 MOE: allocated 239 KByte for the page array @0x9f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [180a000-1823498] [C:503000] l4re BOOTFS: [1824000-1876bec] [C:504000] ned BOOTFS: [1100000-1100173] [C:505000] l4lx.cfg BOOTFS: [1101000-1216740] [C:506000] io BOOTFS: [1217000-12170bd] [C:507000] arm-rv.io BOOTFS: [1218000-15094b8] [C:508000] vmlinuz.arm BOOTFS: [150a000-180a000] [C:509000] ramdisk-arm.rd MOE: cmdline: moe rom/l4lx.cfg MOE: Starting: rom/ned rom/l4lx.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx.cfg' l4linux | libio: Warning: Query of 'vbus' failed! l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=0235af1c l4linux | phys=02000000 ephys=0235af1c l4linux | f_sz=002d93b6 memsz=0035af1c flgs=rwx l4linux | PH 1 (t: 4) offs=0029b3f4 vaddr=022933f4 vend=02293418 l4linux | phys=022933f4 ephys=02293418 l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x2000298, argc=7 argv=0x80007f8c *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa80007a0 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.11.0-l4-svn41 (soap@soap-quantal) (gcc version 4.7.2 (Sourcery CodeBench Lite 2012.09-64) ) #5 Sun Dec 15 21:56:56 CST 2013 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (6 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=2048 init=/bin/sh l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 02000000 - 02400000 [4096 KiB]. l4linux | Areas: Text: 02000000 - 022b2000 [2760kB] (a bit longer) l4linux | Data: 022b2000 - 022d4100 [136kB] l4linux | Initdata: 02294000 - 022b053c [113kB] l4linux | BSS: 022d93b6 - 0235af1c [518kB] l4linux | Device scan: l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:022b3fa4) l4linux | main thread will be 413 l4linux | l4x_register_pointer_section: addr = 02000000 size = 3518464 l4linux | section-with-init: Virt: 0x2000000 to 0x235af1b [3435 KiB] l4linux | section-with-init: Phys: 0x0024f000 to 0x005a9f1b, [3435 KiB] l4linux | Main thread running, waiting... l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 02000000 l4linux | Main memory: Virt: 0x2400000 to 0x63fffff [65536 KiB] l4linux | Main memory: Phys: 0x01900000 to 0x058fffff, [65536 KiB] l4linux | l4x: vmalloc area: 06400000 - 0e400000 l4linux | l4x_register_pointer_section: addr = 02000000 size = 3518464 l4linux | text: Virt: 0x2000000 to 0x235af1b [3435 KiB] l4linux | text: Phys: 0x0024f000 to 0x005a9f1b, [3435 KiB] l4linux | l4x_rd_path: rom/ramdisk-arm.rd l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] l4linux | l4lx_thread_create: Created thread 418 (timer) (u:b3000a00, v:00000000, sp:022f5fa0) Booting Linux on physical CPU 0x0 Linux version 3.11.0-l4-svn41 (soap@soap-quantal) (gcc version 4.7.2 (Sourcery CodeBench Lite 2012.09-64) ) #5 Sun Dec 15 21:56:56 CST 2013 CPU: Fiasco [410fb767] revision 7 (ARMv7), cr=00000000 CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: L4 Memory policy: ECC disabled, Data cache writeback INITRD: 00002000 - 00302000 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 17209 Kernel command line: mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=2048 init=/bin/sh PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 64804K/69636K available (2033K kernel code, 136K rwdata, 604K rodata, 113K init, 518K bss, 4832K reserved) Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) vmalloc : 0x06400000 - 0x0e400000 ( 128 MB) lowmem : 0x00000000 - 0x06400000 ( 100 MB) modules : Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) vmalloc : 0x06400000 - 0x0e400000 ( 128 MB) lowmem : 0x00000000 - 0x06400000 ( 100 MB) moNR_IRQS:220 l4timer: Using IRQ210 sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms Console: colour dummy device 80x30 console [ttyLv0] enabled Calibrating delay loop... 464.48 BogoMIPS (lpj=2322432) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok Setting up static identity map for 0x021e7cb8 - 0x021e7cb8 NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations bio: create slab <bio-0> at 0 Switched to clocksource l4kipclk NET: Registered protocol family 2 TCP established hash table entries: 1024 (order: 1, 8192 bytes) TCP bind hash table entries: 1024 (order: 0, 4096 bytes) TCP: Hash tables configured (established 1024 bind 1024) TCP: reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (junk in compressed archive); looks like an initrd INITRD: Freeing memory. l4x: Checks passed. msgmni has been set to 126 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) L4 serial driver ttyLv0 at MMIO 0x1 (irq = 211) is a L4 l4ser_shm: L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded l4bdds: No name given, not starting. mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 0x00000000, 0xf1199000 // these are values of 'Fpu::fpu.current().owner()' and 'current()' Assertion failed: 'Fpu::fpu.current().owner() == current()' [ret=0xf0013544] /home/soap/project/L4/kernel/fiasco/src/kern/arm/thread-arm.cpp:800 at f0012b7c ------------------------------------------------------- # end of log Thank you for any help! Soap

2 3

Porting libtiff library
by Irvanda Kurniadi 15 Dec '13

15 Dec '13

Hi hackers, I'm trying to port libtiff by following the structure of libjpeg, but I couldn't fix the error in porting libtiff. This is the tree of libjpeg: libjpeg: Control Makefile Lib Lib: build contrib include Makefile build: jconfig.h Makefile contrib: the source file of jpeg-9 library include: Makefile *What is the function of Control file?* libjpeg/Control: provides: libjpeg requires: libc libjpeg/Makefile: PKGDIR = . L4DIR ?= $(PKGDIR)/../.. include $(L4DIR)/mk/subdir.mk *I think this Makefile only for generate the other Makefile in sub-directory. * libjpeg/lib/Makefile: PKGDIR ?= .. L4DIR ?= $(PKGDIR)/../.. TARGET = include build include $(L4DIR)/mk/subdir.mk *This Makefile also only for generating the other Makefile in targeted directories.* libjpeg/lib/include/Makefile: PKGDIR = ../.. L4DIR ?= $(PKGDIR)/../.. CONTRIB_HEADERS = y INCSRC_DIR = $(PKGDIR_ABS)/lib/contrib TARGET = jpeglib.h jmorecfg.h jerror.h \ $(PKGDIR_ABS)/lib/build/jconfig.h include $(L4DIR)/mk/include.mk *What is the function of this Makefile in include directory?* libjpeg/lib/build/Makefile: PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. TARGET = libjpeg.a libjpeg.so SYSTEMS = $(SYSTEMS_PLAIN) LIBS = $(GCCLIB) CONTRIB_INCDIR = libjpeg SRC_C = jaricom.c jcapimin.c jcapistd.c jcarith.c jccoefct.c jccolor.c jcdctmgr.c jchuff.c \ jcinit.c jcmainct.c jcmarker.c jcmaster.c jcomapi.c jcparam.c \ jcprepct.c jcsample.c jctrans.c jdapimin.c jdapistd.c \ jdatadst.c jdatasrc.c jdcoefct.c jdcolor.c jddctmgr.c jdhuff.c \ jdinput.c jdmainct.c jdmarker.c jdmaster.c jdmerge.c \ jdpostct.c jdsample.c jdtrans.c jerror.c jfdctflt.c jfdctfst.c \ jfdctint.c jidctflt.c jidctfst.c jidctint.c jquant1.c \ jquant2.c jutils.c jmemmgr.c jmemnobs.c jdarith.c vpath %.c $(SRC_DIR)/../contrib include $(L4DIR)/mk/lib.mk # prevent warnings CFLAGS := $(filter-out -Wextra -Wall,$(CFLAGS)) *I think this Makefile is used for compiling all c file in source lib. Is it true that this jconfig.h is obtained by manual configure?* *From this understanding I tried to port libtiff with the same way:* libtiff: Control lib Makefile lib: build contrib include Makefile build: Makefile tiffconf.h contrib: the source file of tiff-4.0.3 include: Makefile libtiff/Control: provides: libtiff requires: zlib libc l4re_c libjpeg libtiff/Makefile: PKGDIR = . L4DIR ?= $(PKGDIR)/../.. include $(L4DIR)/mk/subdir.mk libtiff/lib/Makefile: PKGDIR ?= .. L4DIR ?= $(PKGDIR)/../.. TARGET = include build include $(L4DIR)/mk/subdir.mk libtiff/lib/include/Makefile: PKGDIR = ../.. L4DIR ?= $(PKGDIR)/../.. CONTRIB_HEADERS = y INCSRC_DIR = $(PKGDIR_ABS)/lib/contrib/libtiff TARGET = tif_config.h \ $(PKGDIR_ABS)/lib/build/tiffconf.h include $(L4DIR)/mk/include.mk *I got the tiffconf.h after manual ./configure, then I put the tiffconf.h in build directory.* libtiff/lib/build/Makefile: PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. TARGET = libtiff.a libtiff.so REQUIRES_LIBS = libjpeg SYSTEMS = $(SYSTEMS_PLAIN) LIBS = $(GCCLIB) CONTRIB_INCDIR = libtiff SRC_C = tif_aux.c tif_close.c tif_codec.c tif_color.c \ tif_compress.c tif_dir.c tif_dirinfo.c tif_dirread.c tif_dirwrite.c \ tif_dumpmode.c tif_error.c tif_extension.c tif_fax3.c tif_fax3sm.c \ tif_flush.c tif_getimage.c tif_jbig.c tif_jpeg_12.c tif_jpeg.c \ tif_luv.c tif_lzma.c tif_lzw.c tif_next.c tif_ojpeg.c tif_open.c \ tif_packbits.c tif_pixarlog.c tif_predict.c tif_print.c tif_read.c \ tif_read.c tif_strip.c tif_swab.c tif_thunder.c tif_tile.c tif_unix.c \ tif_version.c tif_warning.c tif_win32.c tif_write.c tif_zip.c vpath %.c $(SRC_DIR)/../contrib/libtiff include $(L4DIR)/mk/lib.mk # prevent warnings CFLAGS := $(filter-out -Wextra -Wall,$(CFLAGS)) *After I compiled the pkg, then I got this error message:* In file included from ~/l4linux_test/obj/l4/x86/include/contrib/libjpeg/jpeglib.h:27:0, from ~/l4linux_test/src/l4/pkg/libtiff/lib/contrib/libtiff/tif_jpeg.c:88: ~/l4linux_test/obj/l4/x86/include/contrib/libjpeg/jmorecfg.h:263:16: error: expected identifier before numeric constant ... make[8]: *** [tif_jpeg.o] Error 1 please help me to find out this problem, thanks Regards, Irvanda

2 1

Dynamic creation and passing of IPC channels
by Robert Kaiser 13 Dec '13

13 Dec '13

Hi all, I have two tasks running and communicating through an IPC connection (basically the clntsrv demo). Now I would like to extend this a bit: Using an ipc_call(), the client (actually: multiple clients) should be able to register with a server to receive a wakeup IPC at individually different points in time in the future. (First, flawed idea to do this was to *not* use the combined reply_and_wait call on the server side but instead to only do a wait() call and then postpone the corresponding reply() until when the client should be woken up. However, I learned that this will not work because the implicit reply capability will be lost as soon as another ipc call is done by the server.) Next idea now is to create another IPC channel in the client and to pass (via IPC) the send capability for that channel to the server. The client shall than block in an ipc_receive() on that channel and the server can wake it by sending to that channel. I guess this should be possible and for a seasoned Fiasco.OC/L4Re expert it is probably quite easy to do, but I can't seem to find how to: - create an IPC channel at client/server run time (so far, all IPC channels I used were prepared by Ned through lua scripts) - pass the send capability for such a channel to another task via IPC Can anyone point me to some helpful documentation or maybe an example I could cannibalize to implement this (preferably in C, but C++ code would surely be helpful too)? Thanks in advance for any help! Robert

4 6

Re: Request for information on l4 fiasco
by Matthias Lange 10 Dec '13

10 Dec '13

Hi, On 12/10/2013 04:05 PM, Viswa Sekar wrote: > Hello Sir, > thank you for your reply. > > that is really good to hear. > > is there any possibility that i can know the steps for it? > any manuals, or process for it. First, you'll need a proper cross toolchain. One configured for PPC750 should be fine. In the L4Re snapshot archive there is also a README which provides some information on how to build everything. You can adapt the hints given for ARM. Following up the hints Sebastian gave: do you already have a target hardware for your project? Matthias. > > kindly help me. > > thanks in advance > > > On Tue, Dec 10, 2013 at 3:59 PM, Matthias Lange > <mlange(a)sec.t-labs.tu-berlin.de <mailto:mlange@sec.t-labs.tu-berlin.de>> > wrote: > > Hi, > > On Tue, Dec 10, 2013 at 09:51:10AM +0100, Viswa Sekar wrote: > > Hello Sir, > > > > I am on a project on porting l4 fiasco.oc to power pc architecture. > > i am totally new to this. > > kindly provide me documentation/information on the same. > > it will be very useful. > > Fiasco has already been ported to PowerPC. The current state is, that it > compiles but functionality might be broken due to the lack of > testing hardware > on our side. > > Matthias. > > > > > -- > With warm regards, > *VISWA SUBRAMANIAN SEKAR* > Final Year B.E Computer Science and Engineering > PSG COLLEGE OF TECHNOLOGY > Coimbatore. > Phone: +91 94427 94420 > Email: viswasekarsubramanian(a)gmail.com > <mailto:viswasekarsubramanian@gmail.com> > > > -- Matthias Lange, matthias.lange(a)kernkonzept.com, +49 - 351 - 41 88 86 14 Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129. Geschäftsführer: Dr.-Ing. Michael Hohmuth

1 0

Request for information on l4 fiasco
by Viswa Sekar 10 Dec '13

10 Dec '13

Hello Sir, I am on a project on porting l4 fiasco.oc to power pc architecture. i am totally new to this. kindly provide me documentation/information on the same. it will be very useful. thanks in advance! : -- With warm regards, *VISWA SUBRAMANIAN SEKAR* Final Year B.E Computer Science and Engineering PSG COLLEGE OF TECHNOLOGY Coimbatore. Phone: +91 94427 94420 Email: viswasekarsubramanian(a)gmail.com

3 2

Microkernel Devroom Accepted Talks and Preliminary Schedule
by Julian Stecklina 06 Dec '13

06 Dec '13

Hello fellow hackers, the microkernel devroom at FOSDEM is packed full with talks! Here is a list of accepted talks and the very preliminary(!) schedule for Feb 2nd. I have changed the requested length of time slots slightly where it made sense. 09:00 - 09:05 Welcoming and Introduction 09:05 - 09:50 Rump Kernels, Just Components Antti Kantee 09:55 - 10:40 Genode as general-purpose OS - Progress report and demonstration Norman Feske 10:45 - 11:30 HelenOS annual update Jakub Jermář 11:35 - 12:05 The microkernel OS Escape Nils Asmussen 13:00 - 13:45 State of the Union: What's new in the L4Re Microkernel System t.b.d. 13:50 - 14:20 Secure applications on top of L4 Sartakov A. Vasily 14:25 - 14:55 GNU/Hurd DDE userland device drivers Samuel Thibault 15:00 - 15:30 Virtualization Dungeon on ARM Stefan Kalkowski 15:40 - 16:25 Read-Copy-Update for HelenOS Martin Děcký 16:30 - 17:00 Rethinking Resource Control Michael Engel I hope those whose talks didn't make it will attend anyway. Julian

1 0

Porting libraries to l4linux
by Irvanda Kurniadi 06 Dec '13

06 Dec '13

Hi hackers, I have read some question about adding libraries to l4/fiasco, but I don't get how to do it exactly. I need to port libtiff and openmpi to compile my program over l4/fiasco. Do you have any documentation about it? I have another question related to running application on top l4linux. Is it possible to run my application on top l4linux; like, if I want to run hello world application over l4linux (not just booting it over l4/fiasco)? I tried to run it by using this configuration: -- Start Hello loader:start( { caps = {}, l4re_bdg = L4.Dbg.Warn, log = {"hello","red"}, }, "rom/hello"); -- Start Linux loader:start( { caps = { log = L4.Env.log:m("rws"), fb = mag_svc:create(L4.Proto.Goos, "g=640x480"); vbus = vbus_l4linux; }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, }, "rom/" .. lxname .. " mem=64M console=tty0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 ramdisk_size=4000 init=linuxrc"); But I think it only run two different applications over l4/fiasco. Do you have any idea how to run the hello application over l4linux? Best regards, Irvanda

2 1

serial_drv failed
by Raja Sekhar 28 Nov '13

28 Nov '13

Hello all, I'm trying to run serial_drv on x86 . But I'm getting the following error...... *serial-drv: virtual base at:0x3000* *L4Re[rm]: mapping for page fault failed with -34 @3030 pc=10008e8* *L4Re: unhandled exception: pc=0x10008e8* What migh be the reason....... *Thanks,* Raja Sekhar

2 1

FOSDEM microkernel devroom submission deadline nears (Dec 1st)
by Julian Stecklina 27 Nov '13

27 Nov '13

Hello fellow microkernel hackers, the deadline for submitting talks to our devroom in Brussels is December 1st. If you haven't already, consider submitting a talk. Details are in the original CfP mail: https://os.inf.tu-dresden.de/pipermail/l4-hackers/2013/006068.html Submissions are done via FOSDEM's Pentabarf: https://penta.fosdem.org/submission/ If Pentabarf doesn't work for you, please send your proposal or any other questions regarding the devroom to: microkernel-devroom(a)lists.fosdem.org See you in Brussels, Julian

1 0

[ASK] Make L4 + Fiasco ISO to boot in pandaboard
by Erry Pradana Darajati 25 Nov '13

25 Nov '13

Hello L4hackers, I have a project from my college to build and configure fiasco with l4re to boot and run in Pandaboard. So far i have already build the kernel and l4. But i am having trouble to making ISO for l4re. i follow the instruction using *grub2iso *but it unsuccessful. The Error says : *This mode can only be used with architectures x86 and amd64*. My question is, how can i make ISO for Pandaboard ARM. Thank you for the answer, i am really new for this subject, so i am really appreciate any help -- *Regards,* *Erry Pradana Darajati | Student of Computer Engineering* *Politeknik Elektronika Negeri Surabaya*

2 1

Using Trustzone on mx53 and L4Linux
by panton 21 Nov '13

21 Nov '13

Hello Hackers, I am trying to run the example on l4/examples/sys/vm-tz on my imx53 qsb. I get something running but I am pretty sure it is not correct. I have found a message called "Full virtualization with Trustzone" that make me wonder several questions and I hope you can help me. 1- The vm-tz example is supposed to run a L4Linux on NS world. What I don't understand in which format should be the linux-image (or any other app you want to run). I use a gz compress linux image (the same I use for running "L4Linux ARM" example), but I think it should be a bin file (not even a ELF). 2- The vm-tz example make use of l4sigma0_map_iomem() to request a memory mapping, but why not a l4sigma0_map_mem() if what you want is RAM mapping? The serial exit I get is: SIGMA0: Dump of all resource maps RAM:------------------------ [0:70000000;70000fff] [0:70063000;7008ffff] [0:70097000;70097fff] [0:7009f000;7013ffff] [4:70140000;7016cfff] [0:7016d000;7016ffff] [4:70170000;70186fff] [0:70187000;7100cfff] [4:7100d000;7100dfff] [0:7100e000;710fffff] [4:71100000;7182cfff] [0:7182d000;8effffff] IOMEM:---------------------- [0:0;6fffffff] [0:90000000;ffffffff] MOE: Hello world MOE: found 499832 KByte free memory MOE: found RAM from 70000000 to 8f000000 MOE: allocated 496 KByte for the page array @0x7009f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [716eb000-71704494] [C:503000] l4re BOOTFS: [71705000-7171e674] [C:504000] vm-tz BOOTFS: [7171f000-7182c73c] [C:505000] io BOOTFS: [71100000-711000bd] [C:506000] arm-rv.io BOOTFS: [71101000-713ea4b4] [C:507000] vmlinuz.arm (My gz compressed linux image) BOOTFS: [713eb000-716eb000] [C:508000] ramdisk-arm.rd MOE: cmdline: moe --init=rom/vm-tz MOE: Starting: rom/vm-tz MOE: loading 'rom/vm-tz' And next is repeated forever without change. VM run VM exit pc:20007000 cpsr:00000013 r0:00000000 r1:0000033b r2:20007100 r3:00000000 r4:00000000 r5:00000000 r6:00000000 r7:00000000 r8:00000000 r9:00000000 r10:00000000 r11:00000000 r12:00000000 lr_svc:00000000 sp_svc:00000000 spsr_svc:00000000 Thanks in advanced for your answers, if any :). Pablo Anton.

2 1

Cons
by Daniel Müller 11 Nov '13

11 Nov '13

Hi, Can someone please explain in a few sentences what the purpose of the cons application (l4/pkg/cons) is? Is it (just) a multiplexer for output? Thanks, Daniel

2 1

question about process generation
by Alexander Aring 08 Nov '13

08 Nov '13

Hi all, I like to implement two processes(if this is the correct word for l4). I want to implement two elf binaries, each of them have a main function. These two processes should communicate over IPC. Is this possible? I have in my modules.list: entry krusty kernel fiasco -serial_esc roottask moe rom/krusty.cfg module foo ... so my init process is 'moe' which should start one than more processes, how can I do that if it possible? In l4 examples of 'ipc' I only saw solution with threads, is this the correct way to initiate new processes? - Alex

2 1

about the snd-base/hot-spot of flexpage mapping
by 冯希顺 08 Nov '13

08 Nov '13

hello everbody. I have a question about the snd-base/hot-spot of flexpage mapping feature. in many l4 documents, there are a lot of words about the snd-base/hot-spot concept, it seem that are a complex mechanism to calculate the send base when the sender's flexpage have different size compares to receiver's flexpage, I have read a lot of documents(l4 user manual/l4 reference manual etc.) about this mechanism, but I can not figure out it... Could you tell why l4 needs this mechanism, and what situation that this mechanism adapt to? And I have another question to Dresden University guys: what is the l4 version of Fiasco.OC based? Thank for your help! Naus

2 1

some question bout L4 memory management
by yakijahn 07 Nov '13

07 Nov '13

Hello L4 hackers Now a days I am studying the memory manage Mechanisms of fiasco kernel and L4RE, and I have some questions: 1) I see that when a process need some memory, a dataspace will be invoked and MOE will retrieve pages from alloc_list as kernel mapping sender, and attach region to region map. if process free a region of memory , the region will be dettached from region map and link the memory back to alloc_list, right? The problem I hold is when and how memory be recycled when a process terminated ? Cause I didn't see system use alloc_list :: free() function when a process had ended, in the process I malloc() about 1 MB memory and didn't free them, but it seems that the memory pre-allocated not been link back to alloc list, could you please tell me when and how will system recycle these memory? If possible, please tell me which code folders is it there. 2) Could you please tell me where are codes(files) that responsible for process virtual memory space management, such as how vitual address be assigned to a variable or pointer. Sometimes i fell to an unhandled page fault when I free pointers, because the page fault address cant be find in region map. Thank you very much for kindly answering Best Reguard YuFen Chang National Tsing-Hua University

2 1