- l4-hackers - example.com Site

Data transfer mechanisms
by Lluís Vilanova 20 Aug '13

20 Aug '13

Hi, I'd like to compare the performance of two different synchronous data transfer mechanisms: * Copies * Page maps / unmaps For the second one, it looks like I can use the streammap example (pkg/examples/libs/l4re/streammap), although I'm lacking a mechanism to unmap the page before returning control to the client. It would also be nice to be able to pass the server a read-only region. For the first one, I've only found the use of multiple send/recv operations through the limited amount of data available on the message registers. There is a "Gen_string" class in the "ipc_stream" header, which looks like it could support offline string transfers, but it's disabled at compile time and I could not find the actual code in fiasco that handles these transfers. Thanks, Lluis -- "And it's much the same thing with knowledge, for whenever you learn something new, the whole world becomes that much richer." -- The Princess of Pure Reason, as told by Norton Juster in The Phantom Tollbooth

2 4

Files that Tune Kernel
by Bryan Amato 18 Aug '13

18 Aug '13

Hello everyone, I was wondering what files are the ones that increase the performance of the kernel, besides kernel.hz. Reading in a post by L4, they say that the kernel was not tuned like the Mach Linux port. But I wanted to edit those files to increase performance and to also learn more about what that particular file does. I tried doing this once, but my whole kernel got corrupted from my lack of knowing what is able to be edited and things that had to be there so it could be booted properly. Thanks!

2 1

Desktop Environment
by Bryan Amato 17 Aug '13

17 Aug '13

Hello everyone, I have been using Linux for sometime and only recently tried a special version of BSD, named Dragonfly BSD. What I liked about Dragonfly is that the kernel is not a monolithic kernel. However BSD is not really for me, I prefer the comfort of Linux, so I began searching around the web for a non-monolithic version of the Linux kernel and I came across L4Linux. Looking at the screenshots, I don't see any modern DE's. Does L4L support those desktops like KDE, Gnome and E17? Thanks for all the work you guys are putting into this kernel!

4 3

How to write device driver
by Raja Sekhar 16 Aug '13

16 Aug '13

Hello to all, I want to write a simple character device driver.Can you please give me the procedure for writing device drivers for L4fiasco. * Thanks,* Raja Sekhar

2 1

l4linux with ide-harddisk
by Rudolf Weber 16 Aug '13

16 Aug '13

Hello, I prepared a 32 bit ubuntu system on a virtualbox and replaced the linux - Kernel through the l4re-snapshot-2013060718 - L4Linux-mag-x86 Konfiguration. First I made a disk and add it to the vm and I could mount it ! I wonder ( see later). Now I configured the Ubuntu-Linux-Root-Disk as /dev/hda and: ... piix 0000:00:03.0: IDE controller (0x8086:0x7111 rev 0x01) pci 0000:00:03.0: No interrupt pin configured for device 0000:00:03.0 piix 0000:00:03.0: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xd000-0xd007 ide1: BM-DMA at 0xd008-0xd00f hdc: VBOX CD-ROM, ATAPI CD/DVD-ROM drive hdc: UDMA/33 mode selected ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ESC[37mio | ERROR: binding irq 15, result is -1 (Operation not permitted) ESC[0m ESC[33ml4linux | Bind irq to icu failed with -1ESC[0m l4x-irq: Did not get IRQ 15 from IO service ==> I think, the interupt is not delegated from the IO-Server to l4linux My understanding is, that the io-Server manage all interrupts,ioports. But why I could mount a disk ? I dont see a device in x86-legacy.dev, so I add IDE0 and IDE1 (see attachment), and add a systembus disks => new System_bus() { IDE0 => wrap(hw-root.match("ide0")); IDE1 => wrap(hw-root.match("ide1")); } in l4lx-x86.io (see attachment) in the start-config l4lx-gfx.cfg the disks are granted to l4linux (see attachment) As result, the output is piix 0000:00:03.0: IDE controller (0x8086:0x7111 rev 0x01) pci 0000:00:03.0: No interrupt pin configured for device 0000:00:03.0 piix 0000:00:03.0: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xd000-0xd007 ide1: BM-DMA at 0xd008-0xd00f hda: VBOX HARDDISK, ATA DISK drive hda: UDMA/33 mode selected hdc: VBOX CD-ROM, ATAPI CD/DVD-ROM drive Switching to clocksource tsc hdc: UDMA/33 mode selected ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ESC[33ml4linux | Bind irq to icu failed with -1ESC[0m l4x-irq: Did not get IRQ 15 from IO service ------------[ cut here ]------------ WARNING: at /home/rw/l4exp/l4re-snapshot-2013060718/src/l4linux/arch/l4/l4lxlib/ l4env/irq_vcpu.c:106 l4lx_irq_dev_startup+0x17a/0x180() Modules linked in: Pid: 1, comm: swapper Not tainted 3.9.0-l4 #1 Call Trace: -> the ERROR "ERROR: binding irq 15, result is -1 (Operation not permitted)" don't appear, but the result is the same. The current output of the serialine is in l4ubuntu.1 The l4-linux I configured with PCI/VPCI see attatchment x86_rw_config like in my last E-mails. Summary: * How to grant the ide-Controllers to l4linux ? * Why l4Linux can't get the interrupt - what is wrong with my configuration ? HW-Question: How are the IDE-Controllers and the PCI related ? Thank you very much Rudolf Weber

2 3

issue in getting vhw_devices....................
by Raja Sekhar 13 Aug '13

13 Aug '13

Hello to all, I've downloaded l4re-core-2013041501.tar.bz2 and extracted and compiled fiasco kernel with following configuration Architecture-> IA-32 processor family, Platform -> PC Platform, CPU -> Intel Pentium Pro After that i compiled L4re env....and I just ran one example ux-vhw(which is the code for display Virtual hardware device). In that I'm getting value *'0'* for the fileld *vhw_offset *from the kernel info structure *struct l4_re_kernel_info_t.* Why It is giving zero and what does it mean....* Thanks*, Raja Sekhar

2 1

Issue in getting Virtual Hardware devices
by Raja Sekhar 10 Aug '13

10 Aug '13

Hello to all, I'm working on L4 fiasco. In that I want to read the virtual hardware devies. for tha I'm running the code from * l4/pkg/example/sys/ux-vhw/main.c *** * 10 #include <l4/sys/ipc.h> 11 #include <l4/sys/vhw.h> 12 #include <l4/util/util.h> 13 #include <l4/util/kip.h> 14 #include <l4/re/env.h> 15 16 #include <stdlib.h> 17 #include <stdio.h> 18 19 static void print_entry(struct l4_vhw_entry *e) 20 { 21 printf("type: %d mem start: %08lx end: %08lx\n" 22 "irq: %d pid %d\n", 23 e->type, e->mem_start, e->mem_size, 24 e->irq_no, e->provider_pid); 25 } 26 27 int main(void) 28 { 29 l4_kernel_info_t *kip = l4re_kip(); 30 struct l4_vhw_descriptor *vhw; 31 int i; 32 33 if (!kip) 34 { 35 36 printf("KIP not available!\n"); 37 return 1; 38 } 39 40 vhw = l4_vhw_get(kip); 41 42 if(vhw) 43 { 44 printf("kip at %p, vhw at %p\n", kip, vhw); 45 printf("magic: %08x, version: %08x, count: %02d\n", 46 vhw->magic, vhw->version, vhw->count); 47 48 for (i = 0; i < vhw->count; i++) 49 print_entry(l4_vhw_get_entry(vhw, i)); 50 } 51 return 0; 52 }** *In the above code at *line no 40* after *calling inline function l4_vhw_get(kip)* I'm getting *vhw=NULL. *and the definition of inline function is from* l4sys/include/vhw.h *is as follows* 80 enum { 81 L4_VHW_MAGIC = 0x56687765, 82 }; 83 84 static inline struct l4_vhw_descriptor * 85 l4_vhw_get(l4_kernel_info_t *kip) L4_NOTHROW 86 { 87 struct l4_vhw_descriptor *v 88 = (struct l4_vhw_descriptor *)(((unsigned long)kip) + kip->vhw_offset); 89 90 if (v->magic == L4_VHW_MAGIC) 91 return v; 92 93 return NULL; 94 } *Here* at line no 90, the v->magic *is having a value of* 0x4BE6344C *which is not equal to* L4_VHW_MAGIC *My qestion is why I'm getting different magic value Instead of 0x56687765, and how can I get correct magic value*. *If there are no virtual hardware device how can i create and integrate into my system........* * * * * *Thanks, Raja Sekhar

2 1

Setting physical CPU for a task
by Lluís Vilanova 06 Aug '13

06 Aug '13

Hi, I've been looking for a way to run some sort of ping-pong example where each task runs on either the same or different CPUs. I've been unable to see if moe's config files allow to start tasks pinned to a specific CPU, and after running the "thread_migrate" example, looks like only one CPU (CPU00) is always used: $ make -C obj/l4/amd64/ qemu E=thread_migrate QEMU_OPTIONS="-serial stdio -vnc ::59000 -smp 2" [...] Not using serial hack in slow timer handler. CPU[0]: AuthenticAMD (6:2:3:0)[00000623] Model: QEMU Virtual CPU version 1.5.1 at 3092MHz 255/512 Entry I TLB (4K pages) 255 Entry I TLB (4M pages) 255/512 Entry D TLB (4K pages) 255 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 512 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 20480 bytes (5 pages) [...] Ned says: Hi World! Ned: loading file: 'rom/thread_migrate.cfg' migrate | Found 4 CPUs. migrate | Created 12 threads. migrate | Migrated Thread00 -> CPU00 migrate | Migrated Thread01 -> CPU00 migrate | Migrated Thread02 -> CPU00 migrate | Migrated Thread03 -> CPU00 migrate | Migrated Thread04 -> CPU00 migrate | Migrated Thread05 -> CPU00 migrate | Migrated Thread06 -> CPU00 migrate | Migrated Thread07 -> CPU00 migrate | Migrated Thread08 -> CPU00 migrate | Migrated Thread09 -> CPU00 migrate | Migrated Thread10 -> CPU00 migrate | Migrated Thread11 -> CPU00 migrate | Migrated Thread00 -> CPU00 migrate | Migrated Thread01 -> CPU00 migrate | Migrated Thread02 -> CPU00 migrate | Migrated Thread03 -> CPU00 migrate | Migrated Thread04 -> CPU00 migrate | Migrated Thread05 -> CPU00 migrate | Migrated Thread06 -> CPU00 migrate | Migrated Thread07 -> CPU00 migrate | Migrated Thread08 -> CPU00 migrate | Migrated Thread09 -> CPU00 migrate | Migrated Thread10 -> CPU00 migrate | Migrated Thread11 -> CPU00 [... same output forever ...] I've modified "src/l4/conf/modules.list" to add the "thread_migrate" test, and I'm using l4re-snapshot-2013060718, with multiprocessing (with a maximum of 4) enabled on fiasco. Looks like the benchmark always detects (L4::Scheduler::info) the number of maximum CPUs configured in fiasco, but not the number of CPUs provided by QEMU (only CPU 0 is online). Am I missing some step to set all CPUs online? Is it possible to have MOE start tasks pinned to a specific CPU? Thanks a lot, Lluis -- "And it's much the same thing with knowledge, for whenever you learn something new, the whole world becomes that much richer." -- The Princess of Pure Reason, as told by Norton Juster in The Phantom Tollbooth

2 5

Re: l4-hackers Digest, Vol 124, Issue 4
by Иван Филиппов 06 Aug '13

06 Aug '13

Hi Lluis, Have pretty much the same as you sad - can't load both qemu for unknown memory address, neither for grub2 for Ubuntu 13.04, but it compiles well. I`ll ask what happens tomorrow on upcoming russian Fiasco/Virtualization school with Bjorn Doebel at al. and tell you what happens. Probably the best choose is Qemu emulator, if you don't have already written software, not to reload system every time you need. I compiled with i386 option both FiascoOC/L4RE and them works well. just as here: http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/004894.html http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/<http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/004894.html> 004894.html<http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/004894.html> I have 4.7 compiler too. Best wishes, 2013/8/5 <l4-hackers-request(a)os.inf.tu-dresden.de> > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. Unable to boot Fiasco.OC on amd64 (Llu?s Vilanova) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 04 Aug 2013 22:44:24 +0300 > From: Llu?s Vilanova <vilanova(a)ac.upc.edu> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: Unable to boot Fiasco.OC on amd64 > Message-ID: <87eha95jhj.fsf(a)fimbulvetr.bsc.es> > Content-Type: text/plain; charset="us-ascii" > > Hi there, > > After having to play with the load addresses of both fiasco and some of the > modules [1], I've been able to boot fiasco, but only to find it chokes on > some > assertion, immediately following a pager warning (see error.jpg > screenshot). > > Sorry for using a screenshot, but I've been unable to make the serial > console > work, so no copy&paste is available. > > As I'm new to L4, I don't know if the error is due to my changes or due to > some > other mis-configuration on the boot process. See the attached grub2.txt > for the > GRUB2 entries I've tried (the error corresponds to the first entry). > > I'm using the l4re-core-2013060718 tarball, all compiled on a debian > testing > (gcc 4.7.3). > > Any help on the boot or the serial console support is much appreciated. > > > Thanks a lot, > Lluis > > [1] To avoid some region overlaps, see attached l4.patch, and memory.jpg > for the > memory range configuration of the machine. > >

3 10

mmap2 on L4Linux rev 37
by Sebastian Sumpf 06 Aug '13

06 Aug '13

Hi L4 hackers, recently I started to use L4Linux r37 on ARM and experienced some issues with the 'sys_mmap_pgoff'-system call. When a user-level task tried to map a file the 'pgoff' parameter was usually bogus. Doing a little research I found that it was caused by the 'sys_mmap2' implementation in 'entry.S'. The function overwrites the 'pgoff' argument on the stack with r5 (as it is usually passed from user land), since in L4Linux this code gets called from the dispatch routine, 'pgoff' was set to whatever r5 was, and thus leading to bus errors later on. Cheers, Sebastian -- Sebastian Sumpf Genode Labs http://www.genode-labs.com · http://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

2 1

why Fiasco kernel is named as fiasco
by Raja Sekhar 05 Aug '13

05 Aug '13

Hello to all, I just want to know that why fiasco micro-kernel named as fiasco ..... can you please give me the answer....... * Thanks,* Raja Sekhar

2 1

Unable to boot Fiasco.OC on amd64
by Lluís Vilanova 04 Aug '13

04 Aug '13

Hi there, After having to play with the load addresses of both fiasco and some of the modules [1], I've been able to boot fiasco, but only to find it chokes on some assertion, immediately following a pager warning (see error.jpg screenshot). Sorry for using a screenshot, but I've been unable to make the serial console work, so no copy&paste is available. As I'm new to L4, I don't know if the error is due to my changes or due to some other mis-configuration on the boot process. See the attached grub2.txt for the GRUB2 entries I've tried (the error corresponds to the first entry). I'm using the l4re-core-2013060718 tarball, all compiled on a debian testing (gcc 4.7.3). Any help on the boot or the serial console support is much appreciated. Thanks a lot, Lluis [1] To avoid some region overlaps, see attached l4.patch, and memory.jpg for the memory range configuration of the machine. menuentry "L4" { multiboot /boot/l4/bootstrap -serial module /boot/l4/fiasco /fiasco -serial_esc module /boot/l4/l4f/sigma0 /sigma0 module /boot/l4/l4f/moe /moe module /boot/l4/l4f/hello /hello } menuentry "L4 - L4re" { multiboot /boot/l4/bootstrap -serial module /boot/l4/fiasco /fiasco -serial_esc module /boot/l4/l4f/sigma0 /sigma0 module /boot/l4/l4f/moe /moe --init=rom/hello module /boot/l4/l4f/l4re /l4re module /boot/l4/l4f/hello /hello } -- "And it's much the same thing with knowledge, for whenever you learn something new, the whole world becomes that much richer." -- The Princess of Pure Reason, as told by Norton Juster in The Phantom Tollbooth

1 0

Use of the PC value in interrupt/exception handlers
by Piyus Kedia 03 Aug '13

03 Aug '13

Dear all, We are working on developing a dynamic binary translator for the kernel. Towards this, we wanted to confirm if the interrupted PC value pushed on stack by an interrupt/exception is used by the interrupt/exception handlers? For example, is the PC value compared against a fixed address to determine the handler behaviour (like Linux's page fault handler compares the faulting PC against an exception table, to allow functions like copy_from_user to fault). Basically, we are wondering if it is safe to replace the pushed PC value on stack by another value. This would be safe if the PC value is only used for returning from interrupt, or for reading contents at that PC address (e.g., to decode the instruction at current PC). It would be unsafe if the value of the address itself is meaningful to the handler. We found that in FreeBSD segment-not-present exception handler checks the trapped PC value against some fixed kernel PC by looking at the code, except that it is only used for debugging purposes. It would be nice if somebody could also confirm this. Thanks, Piyus

2 2

l4linux: l4x_setup_memory:Cant get main memory
by Rudolf Weber 01 Aug '13

01 Aug '13

2 13

Fwd: Interrupt Handlers
by Piyus Kedia 01 Aug '13

01 Aug '13

Hi All, I am working on dynamic binary translator. Please tell me if anybody know if in L4-microkernel interrupted kernel PC is ever used in interrupt handlers? Thanks and regards, Piyus

2 1

Using the tmpfs library
by Michael Weiß 01 Aug '13

01 Aug '13

Hi, I want to do some file operations in a native l4re application. using fopen, fgetc, fprintf... from libc. I know that this is possible for the rom filesystem. However, I want to create new files during runtime which are also writable. I found the VFS implementation l4/pkg/tmpfs. but I do not really understand how that VFS stuff works, as there also is no header file for tmpfs. How can I access the tmpfs functionality within my application? For my application it would be sufficient to just have temporary files, which I think is exactly what the tmpfs lib provides. I already linked the tmpfs lib to my application and tried to use mount from sys/mount.h. However, I have no idea which parameters and how the path than has to look like for fopen. Is there some example code which shows howto use this lib in an application? Thanks, Michael

2 1

Unexpected trap while booting Fiasco
by Stefan Fritsch 01 Aug '13

01 Aug '13

Hi, sometimes I get 'Unexpected trap while booting Fiasco' when booting L4Re with grub 0.97. How often this happens seems to depend on the loaded modules, but I haven't been able to determine some rule when it will happen. It does not depend on the number or total size of the modules reaching a certain size. However, since we upgraded to l4re-snapshot-2013060718 from -2013021819, it always happen for me in the below module configuration (it only happened rarely before the upgrade). It looks like parts of fiasco are not mapped at the correct address. Do you have any idea what could cause this? Cheers, Stefan L4 Bootstrapper Build: #1 Mon Jul 29 19:27:21 CEST 2013, x86-32, 4.4.5 Limiting 'RAM' region [ 40005000, c4eb9fff] { 84eb5000} to [ 40005000, bcffffff] { 7cffb000} due to 3024 MB address limit Dropping 'RAM' region [ c50bc000, d82eefff] { 13233000} due to 3024 MB address limit Dropping 'RAM' region [ dafff000, daffffff] { 1000} due to 3024 MB address limit Dropping 'RAM' region [100000000, 11e5fffff] { 1e600000} due to 3024 MB address limit RAM: 0000000000000000 - 000000000009d7ff: 630kB RAM: 0000000000100000 - 000000001fffffff: 523264kB RAM: 0000000020200000 - 0000000040003fff: 522256kB RAM: 0000000040005000 - 00000000bcffffff: 2047980kB Total RAM: 3021MB Moving up to 22 modules behind 1100000 moving module 00 { 319000-3adc23 } -> { a669000-a6fdc23 } [609316] moving module 01 { 3ae000-3f0a71 } -> { a6fe000-a740a71 } [273010] moving module 02 { 3f1000-5be834 } -> { a741000-a90e834 } [1890357] moving module 03 { 5bf000-6ae6e5 } -> { 9882000-99716e5 } [980710] moving module 04 { 6af000-792266 } -> { 9972000-9a55266 } [930407] moving module 05 { 793000-996b94 } -> { 9a56000-9c59b94 } [2112405] moving module 06 { 997000-99802b } -> { 9c5a000-9c5b02b } [4140] moving module 07 { 999000-12e9408 } -> { 9c5c000-a5ac408 } [9765897] moving module 08 { 12ea000-12eab20 } -> { 1100000-1100b20 } [2849] moving module 09 { 12eb000-12eb547 } -> { 1101000-1101547 } [1352] moving module 10 { 12ec000-13da7a1 } -> { 1102000-11f07a1 } [976802] moving module 11 { 13db000-1a39b4e } -> { 11f1000-184fb4e } [6679375] moving module 12 { 1a3a000-7839fff } -> { 1850000-764ffff } [98566144] moving module 13 { 783a000-7c6b5ee } -> { 7650000-7a815ee } [4396527] moving module 14 { 7c6c000-8eebfff } -> { 7a82000-8d01fff } [19398656] moving module 15 { 8eec000-8eec025 } -> { 8d02000-8d02025 } [38] moving module 16 { 8eed000-8ef0f17 } -> { 8d03000-8d06f17 } [16152] moving module 17 { 8ef1000-8f5d42b } -> { 8d07000-8d7342b } [443436] moving module 18 { 8f5e000-942ca58 } -> { 8d74000-9242a58 } [5040729] moving module 19 { 942d000-9610fff } -> { 9243000-9426fff } [1982464] moving module 20 { 9611000-9880749 } -> { 9427000-9696749 } [2553674] moving module 21 { 9881000-988119e } -> { 9697000-969719e } [415] moving module 03 { 9882000-99716e5 } -> { 9698000-97876e5 } [980710] moving module 04 { 9972000-9a55266 } -> { 9788000-986b266 } [930407] moving module 05 { 9a56000-9c59b94 } -> { 986c000-9a6fb94 } [2112405] moving module 06 { 9c5a000-9c5b02b } -> { 9a70000-9a7102b } [4140] moving module 07 { 9c5c000-a5ac408 } -> { 9a72000-a3c2408 } [9765897] Scanning /l4/fiasco -serial_esc -esc -noscreen Scanning /l4/sigma0 Scanning /l4/moe rom/vs-top.cfg Bootloader MMAP: [ 0, 9d800) RAM (1) [ 9d800, a0000) reserved (2) [ e0000, 100000) reserved (2) [ 100000, 20000000) RAM (1) [ 20000000, 20200000) reserved (2) [ 20200000, 40004000) RAM (1) [ 40004000, 40005000) reserved (2) [ 40005000, c4eba000) RAM (1) [ c4eba000, c50bc000) reserved (2) [ c50bc000, d82ef000) RAM (1) [ d82ef000, daeef000) reserved (2) [ daeef000, daf9f000) ACPI NVS (4) [ daf9f000, dafff000) ACPI (3) [ dafff000, db000000) RAM (1) [ db000000, dfa00000) reserved (2) [ f8000000, fc000000) reserved (2) [ fec00000, fec01000) reserved (2) [ fed08000, fed09000) reserved (2) [ fed10000, fed18000) reserved (2) [ fed18000, fed19000) reserved (2) [ fed19000, fed1a000) reserved (2) [ fed1c000, fed20000) reserved (2) [ fee00000, fee01000) reserved (2) [ ffca0000, 100000000) reserved (2) [100000000, 11e600000) RAM (1) Relocated mbi to [0x2e0000-0x2e0304] Loading /l4/fiasco Loading /l4/sigma0 Loading /l4/moe find kernel info page... found kernel info page at 0x400000 Regions of list 'regions' [ 0, fff] { 1000} Arch BIOS [ 1000, 1fff] { 1000} Kern /l4/fiasco [ 9d800, 9ffff] { 2800} Arch BIOS [ e0000, fffff] { 20000} Arch BIOS [ 100000, 10a1b3] { a1b4} Sigma0 /l4/sigma0 [ 140000, 18c25f] { 4c260} Root /l4/moe [ 2d0000, 2e4427] { 14428} Boot bootstrap [ 2e0000, 2e0401] { 402} Root Multiboot info [ 300000, 38ffff] { 90000} Kern /l4/fiasco [ 400000, 49dfff] { 9e000} Kern /l4/fiasco [ 1100000, a3c2408] { 92c2409} Root Module [ 20000000, 201fffff] { 200000} Arch BIOS [ 40004000, 40004fff] { 1000} Arch BIOS [ c4eba000, c50bbfff] { 202000} Arch BIOS [ d82ef000, daeeefff] { 2c00000} Arch BIOS [ daeef000, daf9efff] { b0000} Arch BIOS [ daf9f000, daffefff] { 60000} Arch BIOS [ db000000, df9fffff] { 4a00000} Arch BIOS [ f8000000, fbffffff] { 4000000} Arch BIOS [ fec00000, fec00fff] { 1000} Arch BIOS [ fed08000, fed08fff] { 1000} Arch BIOS [ fed10000, fed19fff] { a000} Arch BIOS [ fed1c000, fed1ffff] { 4000} Arch BIOS [ fee00000, fee00fff] { 1000} Arch BIOS [ ffca0000, ffffffff] { 360000} Arch BIOS API Version: (87) experimental Sigma0 config ip:001001dc sp:002df150 Roottask config ip:001401c4 sp:00000000 Starting kernel /l4/fiasco at 00300834 EAX f0000000 EBX 2BADB002 ECX 00303000 EDX 00400000 ESI 00035dac EDI 002d81cf EBP 0038fd28 ESP 0038fd20 EIP f00653f0 EFLAGS 00013046 CS 0010 SS 0018 DS 0018 ES 0018 FS 0000 GS 0000 trapno 14, error 00000000, from kernel mode page fault linear address f00653f0 00300055 002dce5c 002dcfe8 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Unexpected trap while booting Fiasco! objdump shows that EIP/pagefault address is the start of init_global_kip(): f00653f0 g F .text 00000014 _ZN3Kip15init_global_kipEPS_ -- genua Gesellschaft fuer Netzwerk- und Unix-Administration mbH Domagkstrasse 7, 85551 Kirchheim bei Muenchen tel +49 89 991950-0, fax -999, www.genua.de Geschaeftsfuehrer: Dr. Magnus Harlander, Dr. Michaela Harlander, Bernhard Schneck. Amtsgericht Muenchen HRB 98238

2 2

Build errors with L4
by Bob Stewart 29 Jul '13

29 Jul '13

I pulled down revisions 56 of l4re per the l4re download instructions on an x86 platform running Ubuntu 13.04. I'm cross compiling for an ARM 8 Beaglebone platform. I created a set of tool links pointing to gcc, g++, ar, ld, etc. from the current Genode toolchain. I then followed the l4 build instructions. The build proceeded normally until is started to link in libc static libraries at which point the following errors killed the build: ... make[5]: Entering directory `/home/bob/fiasco/builds/l4/pkg/loader/server/src/OBJ-arm_armv7a-l4f' ... Compiling main.o ... Compiling slab_alloc.o ... Compiling region.o ... Compiling app_task.o ... Compiling name_space.o ... Compiling log.o ... Compiling global.o ... Compiling sched_proxy.o ... Compiling alloc.o ==> Linking loader /home/bob/fiasco/builds/l4/lib/arm_armv7a/l4f/libuc_c.a(__exit_handler.o): In function `__new_exitfn': /home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/stdlib/_atexit.c:259: undefined reference to `__emutls_v.__libc_errno' /home/bob/fiasco/builds/l4/lib/arm_armv7a/l4f/libuc_c.a(malloc.o): In function `malloc': /home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/stdlib/malloc-standard/malloc.c:1018: undefined reference to `__emutls_v.__libc_errno' /home/bob/fiasco/builds/l4/lib/arm_armv7a/l4f/libuc_c.a(fwrite.__DO_UNLOCKED.o): In function `fwrite_unlocked': /home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/stdio/fwrite.c:36: undefined reference to `__emutls_v.__libc_errno' /home/bob/fiasco/builds/l4/lib/arm_armv7a/l4f/libuc_c.a(__errno_location.o): In function `__errno_location': /home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/misc/internals/__errno_location.c:16: undefined reference to `__emutls_v.__libc_errno' /home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/misc/internals/__errno_location.c:16: undefined reference to `__emutls_v.__libc_errno' /home/bob/fiasco/builds/l4/lib/arm_armv7a/l4f/libuc_c.a(_trans2w.o):/home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/stdio/_trans2w.c:67: more undefined references to `__emutls_v.__libc_errno' follow make[5]: *** [loader] Error 1 Is there some undocumented compiler flag related to TLS I should be setting somewhere to fix these library references? Thanks you Bob Stewart

5 7

Launch of L4Linux
by Maximin Coste 29 Jul '13

29 Jul '13

Hi all, I trying to launch L4Linux over Fiasco.OC+L4RE but here is my serial output: INITRD: Freeing memory. l4x: Checks passed. NetWinder Floating Point Emulator V0.97 (double precision) 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 RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 3072KiB [1 disk] into ram disk... done. VFS: Mounted root (ext2 filesystem) readonly on device 1:0. Freeing init memory: 112K /bin/sh: can't access tty; job control turned off # io | Dev_factory: register factory for N2Hw6DeviceE io | GTF: register factory for 7Pci_dev io | GTF: register factory for N2Hw12Msi_resourceE io | Dev_factory: register factory for N2Hw11Gpio_deviceE io | Io service io | Ready. Waiting for request. [ ...Launching µC/OS-II part... ] So all I got from L4Linux is "/bin/sh: can't access tty; job control turned off" What does that mean ? I also have to say that I use the ramdisk.rd from the official website (http://os.inf.tu-dresden.de/L4/LinuxOnL4/download/drops-rd.rd) is this correct ? This is the content of my modules.list file: modaddr 0x1100000 entry l4LinuxUcos kernel fiasco -serial_esc roottask moe rom/l4lx_ucos.cfg module l4re module ned module io module l4lx_ucos.cfg module vmlinuz.arm module ramdisk-arm.rd module l4ucos module beagle.devs module beagle.io And here is my l4lx configuration file: loader:start( { caps = { log = L4.Env.log:m("rws"), calc_server = calc_server, }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, mem = L4.Env.mem_alloc:create(L4.Proto.Factory, 100*1024*1024):m("rws"), scheduler = L4.Env.user_factory:create(L4.Proto.Scheduler, 0x80, 0x70) }, "rom/" .. lxname .. " mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 ramdisk_size=17000 init=/bin/sh earlyprintk=1"); Thanks in advance, -- Maximin COSTE-LEENHARDT

2 9

Getting fiasco-ux to exit after moe's init process terminates
by John Millikin 27 Jul '13

27 Jul '13

I'm just getting started with L4 and Fiasco, and wanted to try a Hello World. The goal is to have a program which will run in fiasco-ux, print some text to the screen, and then exit back to the terminal. $ cat helloworld.c #include <stdio.h> int main(int argc, char **argv) { printf("Hello world from L4!\n"); return 1; } I'm encountering a problem where after the program runs, moe detects that it's terminated but doesn't itself exit. $ ./fiasco -R './moe --init=rom/helloworld' -l ./l4re -l ./helloworld [...] MOE: cmdline: ./moe --init=rom/helloworld MOE: Starting: rom/helloworld MOE: loading 'rom/helloworld' Hello world from L4! MOE: task 1557475 exited with 1 Looking through src/l4/pkg/moe/server/src, I can't find any obvious way to make moe exit when its init process terminates. Being able to exit seems like fairly important functionality, so I assume it's present somewhere, but I can't figure out how to enable it. moe has no flags related to exiting, and its main() appears to end in the infinite-loop server.loop_noexc() procedure. Is exiting supported? If yes, how do I enable it? If no, why, and would patches be accepted to do this?

2 1

Problem with setting up namespaces
by Johannes Schlatow 19 Jul '13

19 Jul '13

Hi, I was just trying to set up a simple application that uses L4Re namespaces. I therefore took the clntsrv example and modified it as shown in the diff below with the result that the server blocks on the bind_thread() call. Am I missing something? Cheers Johannes diff --git a/src/l4/pkg/examples/clntsrv/clntsrv.cfg b/src/l4/pkg/examples/clntsrv/clntsrv.cfg index bb2ae50..dd7dfa5 100644 --- a/src/l4/pkg/examples/clntsrv/clntsrv.cfg +++ b/src/l4/pkg/examples/clntsrv/clntsrv.cfg @@ -9,13 +9,16 @@ local ld = L4.default_loader; -- Channel for the two programs to talk to each other. local calc_server = ld:new_channel(); +local server_ns = ld:create_namespace({ calc_server = calc_server:svr()}); +local client_ns = ld:create_namespace({ calc_server = calc_server}); + -- The server program, getting the channel in server mode. -ld:start({ caps = { calc_server = calc_server:svr() }, +ld:start({ caps = { namespace = server_ns }, log = { "server", "blue" } }, "rom/ex_clntsrv-server"); -- The client program, getting the 'calc_server' channel to be able to talk -- to the server. The client will be started with a green log output. -ld:start({ caps = { calc_server = calc_server }, +ld:start({ caps = { namespace = client_ns }, log = { "client", "green" } }, "rom/ex_clntsrv-client"); diff --git a/src/l4/pkg/examples/clntsrv/server.cc b/src/l4/pkg/examples/clntsrv/server.cc index 2f2e3fc..9c4c0b9 100644 --- a/src/l4/pkg/examples/clntsrv/server.cc +++ b/src/l4/pkg/examples/clntsrv/server.cc @@ -12,6 +12,7 @@ #include <l4/re/util/cap_alloc> #include <l4/re/util/object_registry> #include <l4/cxx/ipc_server> +#include <l4/re/namespace> #include "shared.h" @@ -60,12 +61,34 @@ main() { static Calculation_server calc; - // Register calculation server - if (!server.registry()->register_obj(&calc, "calc_server").is_valid()) - { - printf("Could not register my service, is there a 'calc_server' in the caps table?\n"); - return 1; - } + L4::Cap<L4Re::Namespace> ns = L4Re::Env::env()->get_cap<L4Re::Namespace>("namespace"); + if (!ns.is_valid()) { + printf("Could not get namespace cap from cap table.\n"); + return 1; + } + L4::Cap<L4::Ipc_gate> calc_server = L4Re::Util::cap_alloc.alloc<L4::Ipc_gate>(); + + if (ns->query("calc_server", calc_server) != 0) { + printf("Could not get 'calc_server' cap from namespace\n"); + return 1; + } + + if (!calc_server.is_valid()) { + printf("calc_server cap is invalid\n"); + return 1; + } + + l4_umword_t id = l4_umword_t(0xcaffee); + L4::Cap<L4::Thread> tcap = L4Re::Env::env()->main_thread(); + + printf("bind_thread()...\n"); + int err = l4_error(calc_server->bind_thread(tcap, id)); + if (err < 0) { + printf("failed\n"); + return 1; + } + + printf("OK\n"); printf("Welcome to the calculation server!\n" "I can do substractions and negations.\n");

4 6

Fiasco.OC Kernel memory running out (I think)
by Daniel Waddington 18 Jul '13

18 Jul '13

Hi, I'm using Fiasco.OC r56 on x86_64 (with Genode). After doing quite a lot of memory mapping, mem_map finally fails. It seems that the _allocators[0]->alloc(...) fails during the Mapping_tree::new operator creation of a Mapping_tree object in the Treemap::tree method. How can I increase the available kernel memory attached to this allocator? Thanks Daniel

2 1

Error during the "ned" package build (svn revision 42)
by ggasnier31＠free.fr 16 Jul '13

16 Jul '13

Hello, I got the following error building the "ned" package for ARM architecture (Cortex-A9, Pandaboard). I use the last Linaro toolchain "gcc-linaro-arm-linux-gnueabihf-4.7-2012.12-20121214_linux". === Building package "ned" === make[1]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned' make[2]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server' make[3]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src' ... Building /home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/.general.d make[3]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src' make[3]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src' make[4]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f' ... Building .general.d ... Building Makefile.inc make[4]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f' make[4]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f' make[4]: *** No rule to make target `ned.lua.bin.o', needed by `ned'. Stop. make[4]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f' make[3]: *** [/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f] Error 2 make[3]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src' make[2]: *** [src] Error 2 make[2]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server' make[1]: *** [server] Error 2 make[1]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned' make: *** [ned] Error 2 Commenting the line "OBJS += ned.lua.bin.o" in the file l4/pkg/ned/server/src/Makefile gives this error. ==> Linking ned lua.o: In function `lua(int, char const* const*)': /home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src/lua.cc:97: undefined reference to `_binary_ned_lua_start' /home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src/lua.cc:97: undefined reference to `_binary_ned_lua_end' make[4]: *** [ned] Error 1 make[4]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f' make[3]: *** [/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f] Error 2 make[3]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src' make[2]: *** [src] Error 2 make[2]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server' make[1]: *** [server] Error 2 make[1]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned' make: *** [ned] Error 2 Regards, Guillaume GASNIER

3 3

x86_fb-example
by Rudolf Weber 15 Jul '13

15 Jul '13

Hello, I want to try out the x86-fb-example in the l4re-snapshot-2013060718. I found the following patch necessary: --- src/l4/conf/examples/x86-fb.list.vorrudi 2013-06-07 18:36:35.000000000 +0200 +++ src/l4/conf/examples/x86-fb.list 2013-07-12 18:23:39.688816451 +0200 @@ -1,5 +1,5 @@ -modaddr 0x1100000 +modaddr 0x2000000 entry x86-fb-example bootstrap bootstrap -serial @@ -13,4 +13,4 @@ module ned module fb-drv module mag -module ex_fb_spectrum +module ex_fb_spectrum_cc --- src/l4/conf/examples/x86-fb.cfg.vorrudi 2013-06-07 18:36:35.000000000 +0200 +++ src/l4/conf/examples/x86-fb.cfg 2013-07-12 18:12:30.837274646 +0200 @@ -64,5 +64,5 @@ l4re_dbg = L4.Dbg.Warn, -- scheduler = L4.Env.user_factory:create(L4.Proto.Scheduler, 0x18, 0x8), }, - "rom/ex_fb_spectrum"); + "rom/ex_fb_spectrum_cc"); print("ex_fb_spectrum exited with: " .. e:wait()); I generated a iso-Image with make grub2iso E=x86-fb-example MODULES_LIST=/home/rw/l4exp/l4re-snapshot-2013060718/src/l4/conf/examples/x86-fb.list and started with qemu-system-i386 -cdrom images/x86-fb-example.iso -serial stdio It's great to have examples ! Greetings Rudolf Weber http://www.infnet.verein.de/home/rw/index.html Computer Science and Network Club Ravensburg

2 1

Help needed
by vijay kumar godavarthy 06 Jul '13

06 Jul '13

Dear all, I am a newbie to l4re and fiasco. I would like to execute the client-server example given in the example directory. Please let me know the steps to be followed. In case I write a new server how to compile and execute it in QEMU. Best regards and many thanks -- vijay kumar

2 1