l4-hackers

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

2827 discussions

no makefile in v4_branch?
by Matthias Lange 11 Oct '05

11 Oct '05

Hi, I've checked out both the modules "fiasco" and "preprocess" from CVS. Because I am going to work on the v4_branch of Fiasco I've only checked out the v4_branch of the fiasco module. Following the build instructions on http://os.inf.tu-dresden.de/fiasco/use.html I wasn't able to locate the Makefile in l4/kernel/fiasco. Checking out the complete module "fiasco" and later updating it with "cvs update -r v4_branch" removes this Makefile. Is this intended behavior or is this Makefile just missing in the v4_branch? Regards, Matthias.

2 1

l4-ux
by Alan Grimes 10 Oct '05

10 Oct '05

Here's wut I get when trying to compile l4-ux: (ofcourse this is a second make run...) I wish I knew how you managed to get a guest kernel to run like this anyway... I wish I knew how you figured out to get a guest kernel to run when the documentation that comes with linux sucks so badly... ################# atg@leenooks ~/source/pot $ make make -r -I"/home/atg/source/l4/kernel/fiasco/src" -f "/home/atg/source/l4/kernel/fiasco/src"/Makefile srcdir="/home/atg/source/l4/kernel/fiasco/src" "all" make[1]: Entering directory `/home/atg/source/pot' make srcdir=/home/atg/source/l4/kernel/fiasco/src -f /home/atg/source/l4/kernel/fiasco/src/Makefile.sub1 make[2]: Entering directory `/home/atg/source/pot' Checking compiler config... unchanged. make[2]: Leaving directory `/home/atg/source/pot' make srcdir=/home/atg/source/l4/kernel/fiasco/src -f /home/atg/source/l4/kernel/fiasco/src/Makefile.sub2 all make[2]: Entering directory `/home/atg/source/pot' ... Making entry-ia32-ux.o ... Making sighandler.o ... Making shortcut-ia32-ux.o ==> Linking kernel.image /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../../../../i686-pc-linux-gnu/bin/ld: errno: TLS definition in /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../../../libc.a(errno.o) section .tbss mismatches non-TLS reference in boot_info-ux.o /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../../../libc.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[2]: *** [kernel.image] Error 1 make[2]: Leaving directory `/home/atg/source/pot' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/atg/source/pot' make: *** [all] Error 2 atg@leenooks ~/source/pot $ ################# -- Friends don't let friends use GCC 3.4.4 GCC 3.3.6 produces code that's twice as fast on x86! http://users.rcn.com/alangrimes/

2 1

ANNOUNCE: NICTA L4-embedded API
by Gernot Heiser 05 Oct '05

05 Oct '05

National ICT Australia and the L4Ka Team are pleased to announce the release of the L4-embedded API. It is based on the X.2 API and aims to provide better support for embedded systems. Specifically, it aims to reduce complexity and memory overhead on architectures with limited resources, while keeping the API small, clean, and mostly compatible to X.2. Reference and user manuals for the new ABI are available from the NICTA L4 site http://www.ertos.nicta.com.au/Research/L4/ and from http://l4hq.org/. A release of a first compliant kernel is planned for later this month. Gernot -- Gernot Heiser Program Leader Professor of Operating Systems Embedded, Real-Time, and Operating Systems University of New South Wales National ICT Australia (NICTA) http://gernot.web.cse.unsw.edu.au http://ertos.nicta.com.au Phone: +61 2 8306 0550 Fax: +61 2 8306 0406

1 0

Re: l4dm_mem_open call from L4Linux user process
by Julian Grizzard 05 Oct '05

05 Oct '05

All, I accidentally responded off list to this topic. Here's Adam's reply that may be helpful to others with similar questions to this thread. Adam's suggestion on where to look for example code and other comments are below. I was able to use the example code to create two linux apps, one which creates a DS and another that attaches to that DS. Julian -------- Original Message -------- Subject: Re: l4dm_mem_open call from L4Linux user process Date: Thu, 29 Sep 2005 22:05:18 +0200 From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> To: Julian Grizzard <grizzard(a)ece.gatech.edu> References: <433ABD93.2020303(a)ece.gatech.edu> <20050929074724.GL31351(a)os.inf.tu-dresden.de> <433C3AE5.4070601(a)ece.gatech.edu> On Thu Sep 29, 2005 at 15:05:09 -0400, Julian Grizzard wrote: > Adam Lackorzynski wrote: > > Hi, > > > > On Wed Sep 28, 2005 at 11:58:11 -0400, Julian Grizzard wrote: > > > >>I've been working with the dataspace calls with the L4Env running x86 > >>Fiasco. I am trying to create a dataspace from a L4Linux user process, > >>but I am having trouble getting the program to compile. Is my Makefile > >>correct for what I am trying to do? Is there any reason I shouldn't be > >>able to link to l4dm_mem_open from a L4Linux user process? Below is my > >>source, Makefile, and compiler error message. Help much appreciated! > >> > > > > > > Umm, basically it's possible to create a new DS in an L4Linux user app, > > as it is created at your DS manager (so most likely dm_phys). This has > > nothing to do with L4Linux or the user app in the first place. > > Attaching to it is a different issue altogether! > > > > Alright, so my eventual goal would be to attach to the DS as well. So, > attaching to a DS is going to be a problem? I figured I would try a > simple case first: just create the DS. The address space of a Linux user app is handled by the Linux server, so if one starts mapping stuff in there without telling Linux it may just overmap this area as it believes it is free, or in other words, no one is mapping stuff in there (which cannot happen in native Linux, so this is ok). So now one could start telling Linux about that region. I think the cleanest way would be to hack something in L4Linux to exclude/reserve a region in an address space of a task. This has not been done yet. Something cheaper could be to mmap something and then overmap it itself, or similar. Depending on what you want to do, there's a good example in l4/pkg/loader/examples/fprov-l4/main.c where a DS is opened but the attaching is done in a way that it works, i.e. some memory in BSS is allocated and unmap, and then, at this location, a page from the DS is mapped in. Just have a look, maybe this is ok for you. > >>---------- SOURCE ---------- > >>#include <l4/dm_mem/dm_mem.h> > >>#include <l4/l4rm/l4rm.h> > >> > >>#include <l4/sys/types.h> > >>#include <l4/dm_generic/types.h> > >> > >>int main(int argc, char**argv){ > >> l4dm_dataspace_t ds; > >> void *addr; > >> > >> l4dm_mem_open(L4DM_DEFAULT_DSM,8192,0,0,"L4RM example",&ds); > >> printf("hi\n"); > >> > >> return 0; > >>} > >> > >>---------- MAKEFILE ---------- > >>PKGDIR ?= ../.. > >>L4DIR ?= $(PKGDIR)/../.. > >> > >>TARGET = $(PKGNAME) > >> > >>MODE = host > > > > > > Mode 'host' has no L4 specific libs, includes etc, try 'l4linux' which > > gives you host + L4 stuff. > > > > This should basically fix your linking problem because the libs you link > > have dependencies to other libs which must be fulfilled. > > Okay, I've tried mode = l4linux. Now I get the error message below. > Looks like some libraries are still not getting pulled in. Do I need to > manually specify some L4LIBS? I tried several combinations but didn't > get anywhere. Any ideas? Whoa, looks like this was the wrong approach. This is pulling much more in which is really too low level for a Linux program. But have a look at the fprov-l4 example, it is hopefully enough for what you want to do. Cheers, Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

drops-demo from hard disk
by Shakthi Kannan 04 Oct '05

04 Oct '05

Greetings! I would like to know if its possible to dump the drops-demo-floppy.img to a primary partition of the hard disk and boot from it? I tried dumping the image to /dev/hdb3 using dd: dd if=drops-demo-floppy.img of=/dev/hdb3 bs=512 count=2880 The above worked fine. I tried to boot it from grub in the MBR using: root (hd0,3) chainloader +1 I get " root (hd0,3) Filesystem type unknown, partition type 0x83 chainloader +1 GRUB" Do we need any filesystem support in drops-demo-floppy.img for it? My GNU/Linux boot entry is: " root (hd0,2) kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hdb3 ro single initrd /boot/initrd-2.4.27-2-386 boot " My partitioning scheme is: /dev/hdb1 - fat32 (data) /dev/hdb2 - swap /dev/hdb3 - linux /dev/hdb4 - 1.44 drops image Any suggestions? Thanks, SK -- Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shakthimaan(a)yahoo.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

2 2

env.ipc_error: unknown
by Shakthi Kannan 30 Sep '05

30 Sep '05

Greetings! I have been working on the BID tutorial in writing the hiworld example. I was able to complete the exercise :) I just found one compilation error, in "4.3 Client helper library", where it said no member ipc_error for env. Declaration is as follows: CORBA_Environment env = dice_default_environment; One usage in the example is: return -env.ipc_error; I checked l4/tool/dice/include/dice/dice-corba-types.h and for l4x2 version, ipc_error is declared inside a _p union. Hence, the usage of: env._p.ipc_error worked fine. Is that correct? I tested hiclient and hiserver replacing demo-drops images with my compiled ones, and it worked fine. My documentation and the source code can be viewed from: http://www.shakthimaan.com -> fiasco Regards, SK -- Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shakthimaan(a)yahoo.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

2 1

About driver stubs for L4Linux
by Jianjun Shen 29 Sep '05

29 Sep '05

Hello, I try to run multiple L4Linux instances. Dose L4Linux-2.4 or L4Linux-2.6 implement the driver stubs for oshkosh, ide driver and bmodfs? Where can I find them? Thanks! Wei ___________________________________________________________ 雅虎邮箱超强增值服务－2G超大空间、pop3收信、无限量邮件提醒 http://cn.mail.yahoo.com

2 1

l4dm_mem_open call from L4Linux user process
by Julian Grizzard 29 Sep '05

29 Sep '05

All, I've been working with the dataspace calls with the L4Env running x86 Fiasco. I am trying to create a dataspace from a L4Linux user process, but I am having trouble getting the program to compile. Is my Makefile correct for what I am trying to do? Is there any reason I shouldn't be able to link to l4dm_mem_open from a L4Linux user process? Below is my source, Makefile, and compiler error message. Help much appreciated! ---------- SOURCE ---------- #include <l4/dm_mem/dm_mem.h> #include <l4/l4rm/l4rm.h> #include <l4/sys/types.h> #include <l4/dm_generic/types.h> int main(int argc, char**argv){ l4dm_dataspace_t ds; void *addr; l4dm_mem_open(L4DM_DEFAULT_DSM,8192,0,0,"L4RM example",&ds); printf("hi\n"); return 0; } ---------- MAKEFILE ---------- PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. TARGET = $(PKGNAME) MODE = host SYSTEMS = x86-l4v2 x86-l4x0 # list your .c files here SRC_C = main.c LIBCINCDIR = $(addprefix -I,$(L4INCDIR)) # if your server implements the server side of an idl defined in an idl-file # of your package, list the idl file name(s) here (no path needed) SERVERIDL = # list additional library paths and libraries here LIBS = -ldm_generic -ldm_mem include $(L4DIR)/mk/prog.mk ---------- COMPILER ERROR ---------- jgrizza@tomato:~/build_2.6.01/l4/pkg/create_ds/server/src$ make PWD=/home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/OBJ-x86_586-l4v2 make -C OBJ-x86_586-l4v2 -f Makefile make[1]: Entering directory `/home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/OBJ-x86_586-l4v2' ... Compiling main.o LD_PRELOAD=/home/jgrizza/build_2.6.01/l4/tool/gendep/libgendep.so GENDEP_TARGET=main.o GENDEP_BINARY=cc1 gcc -c -DRAM_BASE=0x0 -DUSE_OSKIT=y -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -I../../../idl/OBJ-x86-l4v2 -I../../../../../include/x86/l4v2 -I/home/jgrizza/build_2.6.01/drops/include/x86/l4v2 -I../../../../../include/l4v2 -I/home/jgrizza/build_2.6.01/drops/include/l4v2 -I../../../../../include/x86 -I/home/jgrizza/build_2.6.01/drops/include/x86 -I../../../../../include -I/home/jgrizza/build_2.6.01/drops/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations /home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/main.c -o main.o /home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/main.c: In function `main': /home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/main.c:12: warning: implicit declaration of function `printf' /home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/main.c:9: warning: unused variable `addr' ==> Linking create_ds LD_PRELOAD=/home/jgrizza/build_2.6.01/l4/tool/gendep/libgendep.so GENDEP_TARGET=create_ds GENDEP_BINARY=ld gcc -o create_ds main.o -L../../../../../lib/x86_586/l4v2 -L/home/jgrizza/build_2.6.01/drops/lib/x86_586/l4v2 -L../../../../../lib/x86_586 -L/home/jgrizza/build_2.6.01/drops/lib/x86_586 -L../../../../../lib -L/home/jgrizza/build_2.6.01/drops/lib -ldm_generic -ldm_mem ../../../../../lib/x86_586/l4v2/libdm_mem.a(open.o)(.text+0xba): In function `l4dm_mem_open': /home/jgrizza/build_2.6.01/l4/pkg/dm_mem/lib/clientlib/src/open.c:87: undefined reference to `LOG_logL' ../../../../../lib/x86_586/l4v2/libdm_mem.a(open.o)(.text+0xff):/home/jgrizza/build_2.6.01/l4/pkg/dm_mem/lib/clientlib/src/open.c:62: undefined reference to `l4env_get_default_dsm' ../../../../../lib/x86_586/l4v2/libdm_mem.a(open.o)(.text+0x12b):/home/jgrizza/build_2.6.01/l4/pkg/dm_mem/lib/clientlib/src/open.c:65: undefined reference to `LOG_logL' collect2: ld returned 1 exit status make[1]: *** [create_ds] Error 1 make[1]: Leaving directory `/home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/OBJ-x86_586-l4v2' make: *** [OBJ-x86_586-l4v2] Error 2 Thanks! Julian

2 1

names memory overlap error
by Shakthi Kannan 28 Sep '05

28 Sep '05

Greetings! Just started playing around with fiasco and l4env. I checked out l4env and hello from CVS, which obtained all the required files. I was able to compile it on my x86 Thinkpad (T41) running Debian Sarge 3.1r0a. I've added an entry in boot/grub/menu.lst as follows: title DROPS/Fiasco u-kernel kernel (hd0,0)/boot/fiasco/rmgr -sigma0 module (hd0,0)/boot/fiasco/main -noserial -nowait -nokdb module (hd0,0)/boot/fiasco/sigma0 module (hd0,0)/boot/fiasco/names module (hd0,0)/boot/fiasco/log module (hd0,0)/boot/fiasco/dm_phys module (hd0,0)/boot/fiasco/hello On boot, I get the following output: " RMGR: Starting tasks #OS: loading "(hd0,0)/boot/fiasco/names" from 0022b000 - 002341a4 to [ 02240000 - 00246b52 The module 02: 02240000 - 00246b52 : (hd0,0)/boot/fiasco/names overlaps with module loaded by bootloader at 00100000 - 001ca240: Rmgr 02: 0022b000 - 002341a4: (hd0,0)/boot/fiasco/names 03: 00235000 - 0023d324: (hd0,0)/boot/fiasco/log 04: 0023e000 - 00252584: (hd0,0)/boot/fiasco/dm_phys 05: 00253000 - 0025d7ef: (hd0,0)/boot/fiasco/hello The reason for this error message is that the modules as loaded by grub interface with their final position as defined by the linker. Most often you can solve this problem by inserting the command "modaddr 0x02000000" immediately as next line after the "kernel=" line of your menu.lst. Note that you have to use a special version of GRUB which is available from http://os.inf.tu-dresden.de/drops/download.html. Return reboots, "k" enters L4 kernel debugging. " I already have grub installed in the MBR of the hard disk, and I don't have a floppy drive in the laptop. 1. Is there any other way I can get these modules loaded and tested? Of course, hello module does not require the names, log, dm_phys modules. It runs fine though with rmgr, main and sigma0. 2. I am particularly interested in device drivers. Is there any documentation that covers these in DROPS other than using Linux device drivers? I'd appreciate any help in this regard. Thanks, SK -- Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shakthimaan(a)yahoo.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 6

[ANN] Fiasco 1.2 released
by Adam Lackorzynski 26 Sep '05

26 Sep '05

The operating system's group at Technische Universität Dresden is pleased to announce the release of version 1.2 of the Fiasco L4 microkernel. Since the last release Fiasco has significantly matured and is now thought to be the most stable version available. For a comprehensive list of changes please consult the CHANGES file in the distribution. Highlights are the integration of scheduling extensions targeted at real-time applications, better support for paravirtualised systems as well as numerous bug-fixes. The Fiasco kernel currently runs on the x86 and Linux/x86 platforms (UX) as well as various ARM platforms. All platform implementations are believed to be equally stable. More information is available at the Fiasco website at http://os.inf.tu-dresden.de/fiasco/ Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Jump to page:

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