June 2005 - l4-hackers - example.com Site

questions on L4Env and libraries for development on pistachio
by Jayesh Salvi 10 Jun '05

10 Jun '05

I am looking for libraries to do coding on pistachio. As I understand L4Env gives a bunch of libraries - memory management libraries (dm_phys,...), l4io, etc. Could someone answer these questions: 1. From L4Env's docs I see it being used only with fiasco source code. Haven't come across any project that uses L4Env with pistachio. Any dependencies that I don't know of? If not are there any examples? 2. I want libraries for some basic functions - malloc, free, printf, etc. L4Env needs oskit, l4linux2.2 and fiasco L4 kernel. Aren't there any lightweight ways of getting such libraries for L4? Can parts of L4Env used seperately in pistachio tree? 3. I came across libCLight library which is the light implementation of libc. I could get it compiled in my pistachio tree, as done in IoL4 project. Can anyone compare using malloc in libCLight and using DMPhys of L4Env? Hope these questions are not that naive. Thanks in advance. -- Jayesh

4 5

Grub problem
by fabs0028＠free.fr 09 Jun '05

09 Jun '05

Hello, i'm trying to create a l4linux system based on l4linux 2.6 and fiasco. i builded l4linux with l4env and fiasco from scratch with no problem but when i wanted to launch it i had problems with the grub version (gnu grub 0.95). I took your grub version as i was advised but i can't build it i have some problems, mainly with a reference to memcpy in some files in the stage2 directory, but what's weird is that there's no references to that fonction in the concerned files. For the record here is my grub menu.lst concerning l4linux title L4/Linux root (hd0,0) kernel /l4linux/rmgr task modname "bmodfs" module module module module /l4linux/fiasco module /l4linux/bmodfs module /l4linux/libloader.s.so module /l4linux/run-l4 module /l4linux/vmlinuz26 module /l4linux/loader --fprov=BMODFS run-l4 thanx for your help

2 3

gettimeofday(2) and time(2)
by Derick Swanepoel 09 Jun '05

09 Jun '05

Hi all, I would like to get the current time as reported by gettimeofday(2) and time(2). However, neither of these functions seem to work in L4. gettimeofday() fills in the timeval struct with random values and time() always returns -1. What is the correct way to get the time in seconds since the Epoch in L4? Thanks in advance, Derick

3 7

Re: [Fwd: Re: gettimeofday(2) and time(2)]
by Julian Grizzard 09 Jun '05

09 Jun '05

> use the RTC server. $(L4DIR)/pkg/rtc. Is $(L4DIR)/pkg/rtc part of the fiasco project CVS? If so, how do you check it out? Contents of my $(L4DIR)/pkg/ directory from 20050523 CVS: $ ls build/l4/pkg/ COPYING CVS hello l4sys Makefile rmgr crtx demangle l4lthread l4util oskit_support sigma0 Thanks! -Julian

3 7

Status of the fiasco project
by fabs0028＠free.fr 09 Jun '05

09 Jun '05

Hello everyone, i'm a bit new in the world of L4. It is really interesting but it seems a wide world as well. I'd like to know if there will be a new version of fiasco in the near future and the main goal you are wanting to achieve for this hypothetic new version. Fabien Chaillou

2 1

l4linux2.4 System Call Emulation question
by Andrew Davenport 07 Jun '05

07 Jun '05

Hi, where in l4 does an exception (int 0x80) get trapped and turned into an appropriate l4 ipc and sent to l4linux? for instance: if (from an l4linux program), i do a system call like this (in assembly) mov bx, 0x20 mov ax, 0x10 int 0x80 where will i see 0x10 and 0x20 (the syscall parameters) inside the l4 IPC ?? Thanks very much in advance -andrew

2 1

l4linux question
by Andrew Davenport 04 Jun '05

04 Jun '05

Hello, I have a fiasco l4/l4linux system setup. I want to eventually log all linux system calls from within the fiasco kernel (via thread::sys_ipc and thread::shortcut_ipc). I am curious: How does a linux system call get translated into an l4 ipc ? Thanks, Andrew Winter Davenport

2 1

TFTP server and E1000 problem
by Leon Brits 04 Jun '05

04 Jun '05

Hi all, I've just received an Intel E1000(82545GM) NIC to make work with the TFTP server. The problem is that it does not seem to receive packets when connected to a GigE switch. It does work with a Fast Ethernet switch. The switches are from the same manufacturer. I do see the initial DHCP/BOOTP message send out, so I added some debug code to the rx-polling routine and it does not ever receive anything. I've looked on the Etherboot-project's mailing list and found some comments to a similar error back in 2002 but no mention of a reason or a fix. Any suggestions? Thanks Leon

2 1

Debugging an L4 task
by Derick Swanepoel 02 Jun '05

02 Jun '05

Hi, I am trying to debug an L4 task that double pagefaults before reaching the main function. How should one use the debugger to run a task so it can be debugged without having to break into the debugger later? The backtrace doesn't seem very useful because it looks like a stack overflow due to infinite recursion. Here is the loader output: exec | testtask: Loading exec | testtask: Has no dynamic info exec | testtask: Saved 50936 bytes of symbols exec | testtask: "libloader.s.so" not in library list loader | testtask: Starting sigma0-style application exec | testtask: Packed 37981 bytes of symbols exec | testtask: Packed 60324 bytes of lines loader | testtask,#11: Entry at 00009c7c => 01600000 loader | testtask,#11: Started loader | testtask,#11: Double PF (w) at 0c776bec eip 016290bf (11.00) Here is the backtrace: backtrace (thread 11.00, fp=01629068, pc=016290bf): #1 016290bf : capdigits + 0x12 #2 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #3 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #4 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #5 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #6 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #7 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #8 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #9 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #10 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #11 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #12 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #13 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #14 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #15 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #16 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #17 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #18 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #19 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #20 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #21 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #22 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #23 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #24 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #25 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #26 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #27 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #28 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #29 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #30 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #31 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #32 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #33 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #34 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #35 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 #36 01604dca : outs + 0x2a /home/derick/DROPS/l4/pkg/log/lib/src/logliblinux.c:22 #37 01604970 : flush + 0x20 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:47 #38 01604a4f : printchar + 0xcf /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:71 #39 01604c56 : LOG_fputs + 0x26 /home/derick/DROPS/l4/pkg/log/lib/src/log_printf.c:148 --kernel-bt-follows-- (don't trust w/o frame pointer!!) #1 f0005950 #2 f0004c7e #3 f0009e01 #4 f0009e01 #5 f00053ee #6 f0009a65 #7 f000b3fa #8 f00049ce #9 f000b767 #10 f00086e3 #11 f0004084 #12 f0006931 #13 f00253a2 Thanks in advance, Derick

2 3

IPCs
by Andrew Davenport 02 Jun '05

02 Jun '05

Hello, I am trying to make a simple IPC logger in L4 (by modifying the kernel). I want to eventually log src, dest, and contents of the message. Where would be most effective place in the l4 kernel to do this, and how should I go about getting the message contents -- eg registers, flex pages or strings ? Thanks, Andrew -- Andrew Winter Davenport Georgia Institute of Technology College of Computing www.prism.gatech.edu/~gtg259m

2 1