- l4-hackers - example.com Site

Kernel configuration missing ?
by chenggh 16 May '07

16 May '07

Hi: I download the newest source page neened for L4Linux and Fiasco. The L4Dir is dice/ kernel/ l4/ l4linux-2.6/ the compilations of fiasco kernel and l4 packages is ok and when i enter the l4linux I input make menuconfig. There are some errors like this: /home/L4/tudos/l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel configuration missing. Stop. make: *** [/home/L4/tudos/l4linux-2.6/Makeconf.l4conf] Error 2 Former I downloaded the source page by cvs and all of them is ok. But this time I get it by svn there are some problem. please help me. Thanks. cheng

1 0

Simple questions
by Ernesto Bascon 16 May '07

16 May '07

Hi L4 hackers! I am very new to Fiasco and want to know several basic things: 1. Is L4Env targeted to develop OS personalities other than L4Linux? 2. Is DROPS built on top of L4Env? 3. Is there any C++ standard library implementation on top of L4Env? If not, what should be needed to have it? 4. Does Fiasco runs on AMD64/SMP machines? 5. Does Fiasco/UX runs on AMD64/SMP machines? Kind regards, Ernesto.

2 1

I have a question about L4Linux
by 차승준 15 May '07

15 May '07

Hello I’m a graduate student of CNU, in Korea My major is computer science, especially operating system(OS) May I ask some questions?? I have studied a operating system, micro kernel; l4linux So I downloaded its source code and analysis it I wonder how manage memory, in “Demand paging” Would mind please tell me where it “Demand paging” implementation and how it work in source code Best regards. SJ. Cha

5 9

Problem, when compiling Fiasco with JBD disabled.
by unruhig＠gmail.com 10 May '07

10 May '07

Hi, just checkouted Fiasco sources from SVN repo today and tried to build it. When disabling JBD in “make config”, the build fails: ... Making startup.o /usr/src/tudos/kernel/fiasco/src/kern/thread-pagefault.cpp: In member function ‘int Thread::handle_page_fault(Address, Mword, Mword, Return_frame*)’: /usr/src/tudos/kernel/fiasco/src/kern/thread-pagefault.cpp:162: error: ‘LOG_MSG_3VAL’ was not declared in this scope /usr/src/tudos/kernel/fiasco/src/kern/thread-pagefault.cpp:166: error: ‘LOG_MSG_3VAL’ was not declared in this scope make[1]: *** [startup.o] Error 1 With JBD enabled all goes ok. Can this be considered as a bug?

2 1

L4Linux without L4Loader
by Daniel Vandersee 06 May '07

06 May '07

Hi there, I wonder if it is possible to start L4Linux (possibly with some modifications) whether from GRUB directly or from a different loader than l4-loader. Is there a particular reason why L4Linux is linked against libloader.s.so? If it would not work out of the box: What has to be neccessarily provided by that (new) loader in oder to achieve that goal? Furthermore I did not manage to link L4Linux without libloader. I tried to replace libloader by those libs that were included by libloader itself, but always get undefined references: > arch/l4/kernel/built-in.o: In function `l4env_phys_to_virt': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:200: multiple definition of `l4env_infopage' > ../l4/lib/x86_586/l4v2/libl4env.p.a(startup.s.o):/home/user/src/otc_snapshot/l4/pkg/l4env/lib/src/startup.c:59: first defined here > lib/lib.a(string.o): In function `memcmp': > /home/user/src/otc_snapshot/l4linux-2.6/lib/string.c:553: multiple definition of `memcmp' > arch/l4/kernel/built-in.o:/home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/helper_dyn.c:43: first defined here > ld: Warning: size of symbol `memcmp' changed from 41 in arch/l4/kernel/built-in.o to 43 in lib/lib.a(string.o) > lib/lib.a(vsprintf.o): In function `vsnprintf': > /home/user/src/otc_snapshot/l4linux-2.6/lib/vsprintf.c:258: multiple definition of `vsnprintf' > ../l4/lib/x86_586/l4v2/liblogserver.p.a(sprintf.s.o):/home/user/src/otc_snapshot/l4/pkg/log/lib/src/sprintf.c:46: first defined here > ld: Warning: size of symbol `vsnprintf' changed from 38 in ../l4/lib/x86_586/l4v2/liblogserver.p.a(sprintf.s.o) to 1337 in lib/lib.a(vsprintf.o) > lib/lib.a(vsprintf.o): In function `snprintf': > /home/user/src/otc_snapshot/l4linux-2.6/lib/vsprintf.c:537: multiple definition of `snprintf' > ../l4/lib/x86_586/l4v2/liblogserver.p.a(sprintf.s.o):/home/user/src/otc_snapshot/l4/pkg/log/lib/src/sprintf.c:33: first defined here > ld: Warning: size of symbol `snprintf' changed from 39 in ../l4/lib/x86_586/l4v2/liblogserver.p.a(sprintf.s.o) to 40 in lib/lib.a(vsprintf.o) > lib/lib.a(vsprintf.o): In function `vsprintf': > /home/user/src/otc_snapshot/l4linux-2.6/lib/vsprintf.c:587: multiple definition of `vsprintf' > ../l4/lib/x86_586/l4v2/liblogserver.p.a(sprintf.s.o):/home/user/src/otc_snapshot/l4/pkg/log/lib/src/sprintf.c:42: first defined here > ld: Warning: size of symbol `vsprintf' changed from 35 in ../l4/lib/x86_586/l4v2/liblogserver.p.a(sprintf.s.o) to 41 in lib/lib.a(vsprintf.o) > lib/lib.a(vsprintf.o): In function `sprintf': > /home/user/src/otc_snapshot/l4linux-2.6/lib/vsprintf.c:604: multiple definition of `sprintf' > ../l4/lib/x86_586/l4v2/liblogserver.p.a(sprintf.s.o):/home/user/src/otc_snapshot/l4/pkg/log/lib/src/sprintf.c:24: first defined here > ld: Warning: size of symbol `sprintf' changed from 36 in ../l4/lib/x86_586/l4v2/liblogserver.p.a(sprintf.s.o) to 41 in lib/lib.a(vsprintf.o) > arch/l4/lib/arch-i386/built-in.o: In function `l4x_proc_init': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/lib/arch-i386/../proc.c:(.text+0x0): multiple definition of `strstr' > arch/l4/kernel/built-in.o:/home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/helper_dyn.c:134: first defined here > ld: Warning: size of symbol `strstr' changed from 112 in arch/l4/kernel/built-in.o to 48 in arch/l4/lib/arch-i386/built-in.o > ../l4/lib/x86_586/l4v2/liblogserver.p.a(doprnt.s.o): In function `LOG_doprnt': > /home/user/src/otc_snapshot/l4/pkg/log/lib/src/doprnt.c:732: undefined reference to `__umoddi3' > /home/user/src/otc_snapshot/l4/pkg/log/lib/src/doprnt.c:733: undefined reference to `__udivdi3' > arch/l4/kernel/built-in.o: In function `setup_l4env_memory': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:(.text+0x2a4): undefined reference to `l4dm_mem_allocate' > arch/l4/kernel/built-in.o: In function `free': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:291: undefined reference to `l4dm_mem_release' > arch/l4/kernel/built-in.o: In function `l4x_map_below_mainmem': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:386: undefined reference to `l4rm_lookup' > arch/l4/kernel/built-in.o: In function `l4x_map_upage_myself': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:439: undefined reference to `l4rm_lookup' > arch/l4/kernel/built-in.o: In function `l4x_map_iomemory_from_sigma0': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:1549: undefined reference to `l4sigma0_map_iomem' > arch/l4/kernel/built-in.o: In function `l4env_virt_to_phys': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:165: undefined reference to `l4dm_mem_phys_addr' > arch/l4/kernel/built-in.o: In function `__cxa_atexit': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:251: undefined reference to `l4rm_lookup' > arch/l4/kernel/built-in.o: In function `l4x_mbm_request_ghost': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:362: undefined reference to `l4rm_area_release' > arch/l4/kernel/built-in.o: In function `l4env_free_initrd_mem': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:867: undefined reference to `l4dm_ds_list_all' > arch/l4/l4lxlib/l4env/lib.a(memory.o): In function `l4lx_memory_map_virtual_page': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/l4lxlib/l4env/memory.c:23: undefined reference to `l4rm_lookup' > arch/l4/l4lxlib/l4env/lib.a(memory.o): In function `l4lx_memory_page_mapped': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/l4lxlib/l4env/memory.c:66: undefined reference to `l4rm_lookup' > arch/l4/l4lxlib/l4env/lib.a(task.o): In function `l4lx_task_number_allocate': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/l4lxlib/l4env/task.c:65: undefined reference to `l4ts_allocate_task' > arch/l4/l4lxlib/l4env/lib.a(task.o): In function `l4lx_task_number_free': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/l4lxlib/l4env/task.c:142: undefined reference to `l4ts_free_task' > arch/l4/l4lxlib/l4env/lib.a(task.o): In function `l4lx_task_create_pager': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/l4lxlib/l4env/task.c:206: undefined reference to `l4ts_create_task' > arch/l4/l4lxlib/l4env/lib.a(task.o): In function `l4lx_task_delete': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/l4lxlib/l4env/task.c:252: undefined reference to `l4ts_kill_task' > ../l4/lib/x86_586/l4v2/libio-ll.a(req_rel.o): In function `l4io_request_mem_region': > /home/user/src/otc_snapshot/l4/pkg/generic_io/lib/clientlib/req_rel.c:70: undefined reference to `l4rm_area_release' > /home/user/src/otc_snapshot/l4/pkg/generic_io/lib/clientlib/req_rel.c:70: undefined reference to `l4rm_area_release' > ../l4/lib/x86_586/l4v2/librtc.a(librtc.o): In function `init_done': > /home/user/src/otc_snapshot/l4/pkg/rtc/lib/client/librtc.c:33: undefined reference to `l4_scaler_tsc_to_ns' > /home/user/src/otc_snapshot/l4/pkg/rtc/lib/client/librtc.c:69: undefined reference to `l4_scaler_tsc_to_us' > /home/user/src/otc_snapshot/l4/pkg/rtc/lib/client/librtc.c:33: undefined reference to `l4_scaler_ns_to_tsc' > ../l4/lib/x86_586/l4v2/librtc.a(librtc.o): In function `l4rtc_get_seconds_since_1970': > /home/user/src/otc_snapshot/build/l4/include/x86/l4/util/rdtsc.h:268: undefined reference to `l4_scaler_tsc_to_ns' > /home/user/src/otc_snapshot/build/l4/include/x86/l4/util/rdtsc.h:268: undefined reference to `l4_scaler_tsc_to_ns' Especially I wasn't able to locate "__umoddi3" and "__udivdi3" in any library except of libloader. I modified l4linux-2.6/arch/l4/kernel/Makefile of the latest OTC snapshot as follows: > L4LIBS = -L$(L4OBJ)/lib/$(L4_MK_ARCH)_$(L4_MK_CPU)/$(L4_MK_API) \ > -L$(L4OBJ)/lib/$(L4_MK_ARCH)_$(L4_MK_CPU) \ > -L$(L4OBJ)/lib \ > -T../../l4/lib/x86_586/main_stat.ld --start-group -lroot.p -lsemaphore.p \ > -lgeneric_ts.p \ > -lloaderif.p \ > -ll4util_root.p \ > -ll4sys.p \ > -lthread.p \ > -ldm_generic.p \ > -ldm_mem.p \ > -ll4env_err.p \ > -ll4env.p \ > -lnames.p \ > -lgeneric_fprov.p \ > -llogserver.p \ > -lnames.p \ > -lc_be_minimal_log_io.p \ > -lc_be_simple_mem.p \ > -lc_be_mmap.p \ > -lc_be_mmap_util.p \ > -luclibc_support.p \ > -lthread.p \ > -lc_be_l4env_start_stop.p \ > -ll4rm.p \ > -lslab.p \ > -ll4util.p -lsigma0.p -llist_alloc.p --end-group \ > $(GCCLIB) Thanks in advance. Kind regards, Daniel

4 6

Fiasco built-in profiling
by Stefan Scheler 06 May '07

06 May '07

Hello, I'm currently trying to get fiasco's built-in profiling working. The problem is, as soon as roottask has been started, an error (mcount: tos overflow) occurs which apparently prevents profiling. Later on no gmon.out.uu is generated. Is that supposed to work? Or what am I doing wrong here? I attached a log showing the error message. From the JDB source code, it sounds like you can enable and disable kernel profiling from JDB. How can this be accomplished? Thanks for any help Stefan L4 Bootstrapper Scaning /bin/fiasco -profile -profstart -nokdb -nowait -serial -comport 1 -serial_esc Scaning /bin/sigma0 Scaning /bin/roottask Bootloader MMAP available [00000000,0009fc00) RAM (1) [0009fc00,000a0000) RAM (1) [000f0000,00100000) reserved (2) [ffb00000,00000000) reserved (2) [00100000,1fff0000) RAM (1) [1fff3000,20000000) ACPI (3) [1fff0000,1fff3000) ACPI NVS (4) Relocated mbi to [0x61000-0x611b3] Loading /bin/fiasco Loading /bin/sigma0 Loading /bin/roottask find kernel info page... found kernel info page at 0x1000 API Version: (87) experimental Sigma0 config ip:00094cd0 sp:00106100 Roottask config ip:00120000 sp:00109528 [00001000-00002000) /bin/fiasco [00002000-00052680) /bin/fiasco [00052680-0005add0) /bin/fiasco [0005b000-0005e861) /bin/fiasco [0005e880-00061000) /bin/fiasco [00090000-00099380) /bin/sigma0 [0009f000-00100000) BIOS area [00100000-00109764) bootstrap [00120000-001345d0) /bin/roottask [00135000-0013f9bb) /bin/roottask [001409c0-002be9f4) /bin/roottask [00300000-003017ec) /bin/fiasco [00302000-0038fce0) /bin/fiasco [03000000-03152c1d) Modules Memory [1fff0000-ffffffff) Deep Space Starting kernel /bin/fiasco at 003007e8 Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Dec 21 08:55:14 2006 compiled with gcc 4.1.1 for Pentium M Performance-critical config option(s) detected: CONFIG_SCHED_RTC is on CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_PROFILE is on CONFIG_NO_FRAME_PTR is off CONFIG_JDB_ACCOUNTING is on Enabling special fully nested mode for PIC Using the RTC on IRQ 8 (1kHz) for scheduling SERIAL ESC: allocated IRQ 4 for serial uart Absolute KIP Syscalls using: Sysenter CPU: GenuineIntel (F:2:4:9) Model: Pentium 4 (Northwood/Prestonia) at 1992 MHz 64 Entry I TLB (4K or 4M pages) 64 Entry D TLB (4k or 4M pages) 12K µ-ops T Cache (8-way associative) 8 KB L1 D Cache (4-way associative, 64 bytes per line) 512 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) Calibrating timer loop... done. SIGMA0: Hello! KIP @ 1000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures Roottask. Command line found: "/bin/roottask" mcount: tos overflow 523840kB ( 511MB) total RAM (reported by bootloader) 479676kB ( 469MB) received RAM from Sigma0 1816kB ( 2MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 <!8> 9 A B C D E F ] Roottask: Loading 1 module. #05: loading "/bin/hello" from [0312d000-03152c1d] to [01000000-01002eea][01003000-010055c0] entry at 0005b064 via trampoline page code symbols at [1d6fa000-1d6fb000] (4kB), lines at [1d6f7000-1d6fa000] (12kB) hello: My thread-id is 5.0 hello: My thread-id is 5.0 hello: My thread-id is 5.0

3 5

Typed Words
by Jonathan S. Shapiro 30 Apr '07

30 Apr '07

This is a very small issue. If I understand the L4 specifications correctly, typed words provided by the sender are copied to the recipient. This allows the recipient to know what was sent. An observation: The transfer of typed words exposes sender-side address values to the receiver. This is a small security violation, since there is no valid use that the receiver can make of this information. It is probably not an important issue, except that we noticed an interaction with cross-model calls. If the IPC transport replaces these addresses with zero, it becomes possible to re-encode a 64-bit typed item word into a 32-bit typed item word without losing any useful information. This appears (to us) to be useful in the implementation of IPCs that cross from (e.g.) 64-bit sender to 32-bit receiver. It does not appear to us that the receiver loses any useful information if the sender address is zeroed or truncated. Have we missed something? shap -- Jonathan S. Shapiro, Ph.D. Managing Director The EROS Group, LLC

2 1

Typed items and the 'C' bit
by Jonathan S. Shapiro 30 Apr '07

30 Apr '07

The L4.x2 specification states: 1. The 'C' bits of typed items and the 't' field of IPW0 redundantly encode the number of typed items. This is intentional. 2. The sender ignores the 'C' bits, but sets them for the receiver. [This is required because the sender may set the C bits incorrectly, and the path in the kernel that interprets them must have a small, bounded number of iterations. If the kernel believes the 'C' bits of the type field, a very large number of iterations could be created and the receiver-side "frame" for words could be overwritten by the sender.] 3. The specifcation *alleges* that the C bit provides a performance advantage to the receiver in parsing the arguments. I am not convinced that [3] is true. The typed items have variable length, which means that the receiver must parse the type fields in order to iterate over them. The only complex case is string items having a non-zero 'c' (continue) bit, and the specification is explicit that for these cases the "type" field of the successor stringitem is entirely ignored. Question: does the 'C' bit provide a real advantage, or is it a historical curiosity? If there is an advantage, can somebody give an example? -- Jonathan S. Shapiro, Ph.D. Managing Director The EROS Group, LLC

2 1

IPC and Multiple Execution Models
by Jonathan S. Shapiro 30 Apr '07

30 Apr '07

On amd64 (and other architectures), multiple execution models are supported by the hardware. In the case of amd64, both 64-bit and 32-bit applications can be supported simultaneously. IPC across models presents some problems. When sending from 32-bit to 64-bit, registers are widened (good), but differences in alignment rules can mean that the 64-bit receiver and the 32-bit sender do not agree about the number and lengths of indirect strings. When sending from 64-bit to 32-bit, registers are truncated, and there can be difficulties with indirect strings because of differing alignment requirements. It is definitely possible for the IDL compiler to compile for both models, and to generate cross-model calls that will avoid these problems, but I have not found any "clean" solution. On platforms that support multiple execution architectures, how do L4 systems deal with this? If this is discussed in existing documents (perhaps the IDL compiler manual?) a pointer to the document is sufficient. Thanks! -- Jonathan S. Shapiro, Ph.D. Managing Director The EROS Group, LLC

3 2

getc()
by Peter Nguyen 30 Apr '07

30 Apr '07

Hi, I'm currently messing around with L4 at the moment. More specifically, i'm providing some facilities for profiling in L4 via sampling. Right now, i'm trying to implement an exception handler for the Performance Measurement Counters on the PowerPC architecture. In providing calls to these facilities via the pingpong root-task, i seem to run into problems with input. Essentially, while the root-task is waiting for user input, it seems as if the exception is not kicking in until i enter a character. The exception that should be handled is a performance monitor exception (where one of the counters overflow). Basically, the overflow takes place such that a significant amount of instructions have been executed when theoretically it should be signalled earlier. In accepting input, the root-task (which i didn't write myself) uses getc() to obtain such input. My question is basically whether getc() blocks everything and sits there until a character is received? I suspect that this is most certainly the case. If so, does anyone know whether there are other facilities available for provide an alternative means for providing input in an application. The reason why i am asking about whether getc() is a factor or not is that in providing an infinite loop, the exception/interrupt kicks in at the right time ie. when the counter overflows, the resulting counter value is slightly above the overflow value eg. the counter overflows when the contents of the register is 0x80000000. When the exception kicks in, the "final" value is 0x80000012 as opposed to a random value in the case with a root-task that requests input. Any help would be greatly appreciated. Peter N -- View this message in context: http://www.nabble.com/getc%28%29-tf3626544.html#a10126418 Sent from the L4 mailing list archive at Nabble.com.

3 6

Re: L4Linux without L4Loader
by Bjoern Doebel 26 Apr '07

26 Apr '07

Hi, > I didn't know about that patch. I just tried it and with some > modifications it builds fine. Thank you. Cool. :) > But additionally I want to load l4linux with our loader. As Christian > Helmuth stated in that thread, the loader has to emulate(?) an > L4env-environment in order to do that. What does that mean for our loader? Basically, the Loader sets up an L4Env infopage that contains some information about the application's environment. (See l4/pkg/l4env/include/env.h). I think you will be able to find the few locations where this is done in our Loader. If you have questions, feel free to ask. Regards, Bjoern

1 0

Debian package for Dice and DICE_INCDIR
by Neal H. Walfield 24 Apr '07

24 Apr '07

When using Adam's Debian package for dice [1], Dice's include files are installed in /usr/include. For L4 ENV to make use of them, I had to override DICE_INCDIR. This has the unfortunate effect of essentially making the system header files includable. This triggers the following error: LD_PRELOAD=/home/neal/src/tudos/build/tool/gendep/libgendep.so GENDEP_TARGET=helper_dyn.s.o GENDEP_BINARY=cc1 gcc-3.4 -c -DRAM_BASE=0x0 -DUSE_UCLIBC=y -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -DCONFIG_L4_CALL_SYSCALLS -DCONFIG_L4_ABS_SYSCALLS -I/home/neal/src/tudos/build/pkg/loader/idl/OBJ-x86-l4v2 -I/home/neal/src/tudos/build/include/x86/l4v2 -I/home/neal/src/tudos/build/include/l4v2 -I/home/neal/src/tudos/build/include/x86 -I/home/neal/src/tudos/build/include -I/usr/include -I/home/neal/src/tudos/l4/../install/include/x86/l4v2 -I/home/neal/src/tudos/l4/../install/include/l4v2 -I/home/neal/src/tudos/l4/../install/include/x86 -I/home/neal/src/tudos/l4/../install/include -nostdinc -I/home/neal/src/tudos/build/include/x86/uclibc -I/home/neal/src/tudos/build/include/uclibc -I/home/neal/src/tudos/build/include/uclibc++ -I/home/neal/src/tudos/l4/../install/include/x86/uclibc -I/home/neal/src/tudos/l4/../install/include/uclibc -I/home/neal/src/tudos/l4/../install/include/uclibc++ -I/usr/lib/gcc/i486-linux-gnu/3.4.6/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -fno-common -D__PIC__ -fPIC /home/neal/src/tudos/l4/pkg/loader/lib/runtime/helper_dyn.c -o helper_dyn.s.o /home/neal/src/tudos/l4/pkg/loader/lib/runtime/helper_dyn.c:70: error: syntax error before "__extension__" /home/neal/src/tudos/l4/pkg/loader/lib/runtime/helper_dyn.c:70: error: syntax error before '&&' token ... make[6]: *** [helper_dyn.s.o] Error 1 make[6]: Leaving directory `/home/neal/src/tudos/build/pkg/loader/lib/runtime/OBJ-x86_586-l4v2' As can be seen above -I/usr/include is present on the command line. This is due to the expansion of $(DICE_INCDIR). To work around this problem, the package could be changed to instead install the dice include files under /usr/include/dice such that setting DICE_INCDIR to /usr/include/dice would cause the dice header files to be made available for inclusion. Neal [1] http://os.inf.tu-dresden.de/~adam/dice/

2 1

Automated regression test suite for L4
by seth bollinger 18 Apr '07

18 Apr '07

Hello All, Is there an automated regression test suite for L4 that covers all (or most of) the features of the l4 kernel? Is there also an automated benchmarking suite? These would be great tools to have available for people who are porting the kernel to new platforms/dev boards, or for people who are looking to tweak/play with the kernel. Thanks, Seth

4 3

Fehler beim kompilieren...
by MHaeussi＠gmx.de 18 Apr '07

18 Apr '07

Hallo liebe Entwickler, ich habe ein Problem beim kompilieren von dem Kernel. Den Kernel will ich als Schulprojekt verwenden, dass sich mit "TPM unter Linux" beschäftigt. Grundidee ist auf dem Microkernel ein "normales" Suse Linux laufen zu lassen das fast alle TPM Funktionen unterstützt die es unter Windows gibt. Hoffentlich ist das überhaupt möglich ^^ Als er den Kompilierdurchlauf beendet habe ich 2 Fehler und es befindet sich kein Kernel im Verzeichnis. Leider kann ich mit den Fehlermeldungen nichts anfangen. Diese habe ich als Anhang beigefügt. Vorgegangen bin ich laut eurer Anleitung im Internet. lg Markus Häußler -- Markus Häußler "Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail

2 1

AIM Multiuser Benchmark - Suite VII
by Eduard Benes 12 Apr '07

12 Apr '07

Hello! As a part of my research I have to run macrobenchmarks on L4Linux and native Linux. I saw few papers related to performance testing of L4Linux, where this benchmark was used. The problem is that I'm not able to find (google) working version. Could somebody provide me tested (used,working) copy of this benchmark? Or are there any similar test that could be used instead of aim7? Thank you, Eduard Benes

2 1

Writing simple "hiworld" server using L4Env packages
by Eduard Benes 10 Apr '07

10 Apr '07

Hi! My goal is to create, using l4env pkgs, some simple servers that would run on top of microkernel and compare their performance when running on native Linux and on L4 ukernel. They should run single and more paraller "processes" that would do some simple numerical algorithms (sorting, Monter Carlo, ...) So, I would like to ask for help with creation of such servers. Better said, it can be few single servers without any clients. (integer/float data types? forks? mallocs? time measurement? ...) Is there available l4env "programming tutorial", some notes from lectures provided at TU-Dresden, or some more advanced "example" server code that could be modified without much knowledge of l4env specifics? I've found the BID tutorial, but for me it would be more helpful to know what basic functions, libraries, data types can be used, and how. (e.g. the hello world example could be modified) Could someone please show me the right way to go? I'm running out of time, so I would really appreciate all help :) Right now I'm working on benchmarking L4Linux and native Linux to get idea of the overhead. And It would be interesting to get idea of the performance when apps/servers are running on L4 kernel without the L4Linux overhead. Thank you, Eduard Benes

3 2

Re: Writing simple "hiworld" server using L4Env packages
by chenggh 10 Apr '07

10 Apr '07

> Is there available l4env "programming tutorial", some notes from > lectures provided at TU-Dresden, or some more advanced "example" > server code that could be modified without much knowledge of l4env > specifics? Sorry, As i know there is not existing l4env programming tutorial. > I've found the BID tutorial, but for me it would be more helpful > to know what basic functions, libraries, data types can be used, > and how. (e.g. the hello world example could be modified) > Could someone please show me the right way to go? Yes, the BID tutorial is very helpful. But it could give you a small example about how the l4 application is created and running. > I'm running out of time, so I would really appreciate all help :) > Right now I'm working on benchmarking L4Linux and native Linux > to get idea of the overhead. And It would be interesting to > get idea of the performance when apps/servers are running on L4 > kernel without the L4Linux overhead. Do you aim at porting a Linux application on top of L4 kernel without L4Linux ? What is the function of your application? cheng

1 0

access to l4/pkg/ktest
by Hendrik Tews 08 Apr '07

08 Apr '07

Hi, would it be possible to put the ktest package into the public repository? If not, how can Erik Schierboom get access to ktest? [I suggested to Erik to put the properties that he is about to prove for the Fiasco IPC as assertions into the code and then run some IPC stress test. As IPC stress test I suggested to recompile linux inside l4linux with -j 100. However Marcus suggested to use pingpong and ktest instead. Any further suggestions for Fiasco IPC stress testing are of course most welcome.] Bye, Hendrik

2 1

Building L4Linux
by Eduard Benes 08 Apr '07

08 Apr '07

Hi, I run into problem compiling l4linux. I've been able to compile it many times before. But after few weeks while I was not with l4linux stuff, I run into problem when building it. I'm pretty sure it will be some "stupid" mistake I've made, but since I need to quickly finish some testing, I would really appreciate any advise... Here is configuration I use: Debian {sarge, etch}; gcc version: 3.{3,4}, l4linux-2.6-17 Everything is mainly based on chenggh's kickstart and tarball he provided. (http://os.inf.tu-dresden.de/pipermail/l4-hackers/2007/002732.html) < l4linux make log start > include/asm-l4/i386-arch/asm/alternative.h:7: error: syntax error before "u8" include/asm-l4/i386-arch/asm/alternative.h:7: warning: no semicolon at end of struct or union include/asm-l4/i386-arch/asm/alternative.h:8: warning: type defaults to `int' in declaration of `replacement' include/asm-l4/i386-arch/asm/alternative.h:8: warning: data definition has no type or storage class include/asm-l4/i386-arch/asm/alternative.h:9: error: syntax error before "cpuid" include/asm-l4/i386-arch/asm/alternative.h:9: warning: type defaults to `int' in declaration of `cpuid' include/asm-l4/i386-arch/asm/alternative.h:9: warning: data definition has no type or storage class include/asm-l4/i386-arch/asm/alternative.h:10: error: syntax error before "instrlen" include/asm-l4/i386-arch/asm/alternative.h:10: warning: type defaults to `int' in declaration of `instrlen' include/asm-l4/i386-arch/asm/alternative.h:10: warning: data definition has no type or storage class include/asm-l4/i386-arch/asm/alternative.h:11: error: syntax error before "replacementlen" include/asm-l4/i386-arch/asm/alternative.h:11: warning: type defaults to `int' in declaration of `replacementlen' include/asm-l4/i386-arch/asm/alternative.h:11: warning: data definition has no type or storage class include/asm-l4/i386-arch/asm/alternative.h:12: error: syntax error before "pad" include/asm-l4/i386-arch/asm/alternative.h:12: warning: type defaults to `int' in declaration of `pad' include/asm-l4/i386-arch/asm/alternative.h:12: warning: data definition has no type or storage class In file included from include/asm-l4/i386-arch/asm/thread_info.h:17, from include/linux/thread_info.h:21, from include/linux/preempt.h:10, from include/linux/interrupt.h:9, from arch/l4/l4lxlib/l4env/irq_multi.c:12: include/asm-l4/l4-arch/asm/processor.h:154: error: `cpuid' redeclared as different kind of symbol include/asm-l4/i386-arch/asm/alternative.h:9: error: previous declaration of `cpuid' include/asm-l4/l4-arch/asm/processor.h:154: warning: `cpuid' was declared `extern' and later `static' make[1]: *** [arch/l4/l4lxlib/l4env/irq_multi.o] Error 1 make: *** [arch/l4/l4lxlib/l4env] Error 2 < l4linux make log end > Thank you, Eduard Benes

2 1

Re: hda : lost interrupt
by chenggh 03 Apr '07

03 Apr '07

On Tuesday 03 April 2007 11:47, you wrote: > Linux's that I have compiled l4 and l4linux , is in > /dev/hda1. But home folder is in /dev/hda3. And the l4 > codes and build directory is in /dev/hda3 > > I did not understand the root concept in the l4linux > coniguration. The root concept in l4linux is same as in linux. A simple root file system consists of different directories including /bin /etc /lib /dev/, etc. The root file system is different from root home directory. In other words the partition which is mounted into / is your choice. For example, the /etc/fstab of my machine is : /dev/hda2 swap swap defaults 0 0 /dev/hda3 / ext3 defaults 1 1 /dev/hda4 /home/ ext3 defaults 1 2 /dev/hdd2 /home/oldsystem ext3 defaults 1 2 If i set root file system it is /dev/hda3. I think it is enough. Good luck. cheng

2 1

Re: hda : lost interrupt
by chenggh 03 Apr '07

03 Apr '07

On Tuesday 03 April 2007 10:31, Burak OGUZ wrote: > Thanks for your help, > > Now it goes over lost interrupt error but this time it > says that > > Warning : unable to open an initial console > Kernel panic - not syncing : No init found try parsing > init= option to kernel > panic : going to sleep forever bye > > What do you think about this situation? Maybe it means that you set a wrong root file system. In your linux26.cfg you set root=/dev/hda1. Are you sure your root file system is located in /dev/hda1? cheng

3 2

Re: hda : lost interrupt
by Burak OGUZ 02 Apr '07

02 Apr '07

I have started dmon log server to take logs but it gave no errors. I am totally confused about it. I think l4linux does not contain the driver for my block devices. I think that is why it gives lost interrupt error. -- burak() (ps: bf) METU CENG '06 ----- Original Message ---- From: chenggh <chenggh04(a)st.lzu.edu.cn> To: l4-hackers(a)os.inf.tu-dresden.de Sent: Monday, April 2, 2007 4:26:43 PM Subject: Re: hda : lost interrupt > l4lx | Done (1517 entries). > l4lx | l4lx_thread_create: Created thread 0f.05 > (timer.i0) > l4lx | panic: going to sleep forever, bye > > > I have booted it with 512m ram under qemu. If you have kernel panic message above it means your l4linux kernel encounters some problem. In this situation you should use a serial console to receive l4linux booting messages. These messages could help you find what is wrong. My booting log is like this: l4lx | Filling lower ptabs... l4lx | Done (1611 entries). l4lx | l4lx\_thread\_create: Created thread 10.05 (timer.i0) l4lx | l4lx\_thread\_create: Created thread 10.06 (Idler) maybe this could help you. Thank you. cheng _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ____________________________________________________________________________________ No need to miss a message. Get email on-the-go with Yahoo! Mail for Mobile. Get started. http://mobile.yahoo.com/mail

1 0

Re: hda : lost interrupt
by chenggh 02 Apr '07

02 Apr '07

> l4lx | Done (1517 entries). > l4lx | l4lx_thread_create: Created thread 0f.05 > (timer.i0) > l4lx | panic: going to sleep forever, bye > > > I have booted it with 512m ram under qemu. If you have kernel panic message above it means your l4linux kernel encounters some problem. In this situation you should use a serial console to receive l4linux booting messages. These messages could help you find what is wrong. My booting log is like this: l4lx | Filling lower ptabs... l4lx | Done (1611 entries). l4lx | l4lx\_thread\_create: Created thread 10.05 (timer.i0) l4lx | l4lx\_thread\_create: Created thread 10.06 (Idler) maybe this could help you. Thank you. cheng

1 0

Re: hda : lost interrupt
by Burak OGUZ 02 Apr '07

02 Apr '07

I have made dmon work. What should I report here? It gives no error but finally it logs : l4lx_thread_create: Created thread 0f.0a (IRQ14) l4lx_thread_create: Created thread 0f.0b (IRQ15) and it starts giving lost interrupt for hard disk and cdrom. -- burak() (ps: bf) METU CENG '06 ----- Original Message ---- From: Burak OGUZ <burakoguzs(a)yahoo.com> To: Ronald Aigner <ra3(a)os.inf.tu-dresden.de>; l4-hackers(a)os.inf.tu-dresden.de Sent: Monday, April 2, 2007 3:33:31 PM Subject: Re: hda : lost interrupt Also I have changed the l4 linux configuration file. I think I should adjust linux configuration too. After changing my linux configuration to this : verbose 0 task "vmlinuz26" "earlyprintk=yes mem=256M video=l4fb" all_sects_writable allow_cli After changing the configuration l4linux started to give this error: l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.19-l4 (root@think) (gcc version 3.4.6) #1 Wed Mar 2 l4lx : 8 15:42:40 EEST 2007 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (3 args): earlyprintk=yes mem=256M video=l4fb l4lx | Image: 00400000 - 00790000 [3648 KiB]. l4lx | Areas: Text: 00400000 - 00696000 [2648kB] (a bit longer) l4lx | Data: 00696000 - 006e408c [312kB] l4lx | Initdata: 006e8000 - 00722000 [232kB] l4lx | BSS: 00724000 - 0078e300 [424kB] l4lx | l4lx_thread_create: Created thread 0f.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0f.04 (server) l4lx | main thread will be 0f.04 l4lx | l4env_register_pointer_section: addr = 006e6000 size = 249856 l4lx | sec-w-init: virt: 0x006e6000 to 0x00722fff [244 KiB] l4lx | sec-w-init: Number of physical regions: 1, 249856 Bytes l4lx | sec-w-init: 1: Phys: 0x01191000 to 0x011ce000, Size: 249856 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 256MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x10bfffff [262144 KiB] l4lx | Main memory: Number of physical regions: 1, 268435456 Bytes l4lx | Main memory: 1: Phys: 0x0d400000 to 0x1d400000, Size: 268435456 l4lx | Filling lower ptabs... l4lx | Done (1517 entries). l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) DMphys | ds 32, client F.00, rights 0x0003, has 0x0001 DMphys | [8.0] dm_phys/server/src/map.c:620:if_l4dm_generic_fault_component(): DMphys | DMphys: bad permissions l4lx | L4RM: dataspace at 0x00400000-0x00695fff, id 32 at 8.00 l4lx | L4RM: dataspace manager call failed ("permission denied") l4lx | L4RM: [PF] write at 0x00400038, ip 004101d0, src F.02 l4lx | [F.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault --PANIC, 'g' for exit------------------------------------IP: a00b43dd (f.00) jdb: Best regards, -- burak() (ps: bf) METU CENG '06 ____________________________________________________________________________________ Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ____________________________________________________________________________________ Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html

1 0

Re: hda : lost interrupt
by chenggh 02 Apr '07

02 Apr '07

On Monday 02 April 2007 12:33, Burak OGUZ wrote: > permission What is your choice of option in Fiasco configuration? [ ] Enable I/O port protection If you enable this option only kernel has full access to all I/O ports. As a result when l4lx could access some resources it has no enough rights. So there is "bad permission" or "permission denied" message. So If you run l4linux disenble this option. It is my opinin. You can try. Thanks cheng

1 0