- l4-hackers - example.com Site

How to run simple client server example
by Thang Tran 24 Jun '13

24 Jun '13

Hi, I'm new to Fiasco and L4Re. I want to write a new program in C++ which will run on L4Re. I'm looking at the simple client server example in the l4/pkg/examples/clntsrv directory for my reference. I was able to get it compiled eventually on L4Re, but I have no idea how to run it. Is there anyway that I can run examples/clntsrv package just like we run the hello package by using grub2iso and qemu? Thanks in advance, Thang Tran.

2 1

Unable to boot 64bit hello
by Daniel Müller 14 Jun '13

14 Jun '13

Hi, I tried booting a 64bit hello world program on L4/Fiasco but that fails with a region overlap: ============================================= xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->000000000019dd88 TOTAL: 0000000000000000->000000007f800000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000000 Daemon running with PID 9320 net0: 00:16:3e:72:79:e5 using rtl8139 on PCI00:04.0 (open) [Link:up, TX:0 TXE:0 RX:0 RXE:0] DHCP (net0 00:16:3e:72:79:e5)... ok net0: 192.168.178.200/255.255.255.0 gw 192.168.178.54 Booting from PXE menu boot PXEBS (net0 type 128).... ok Next server: 192.168.178.54 Filename: pxeboot.0 tftp://192.168.178.54/pxeboot.0... ok L4 Bootstrapper Build: #7 Sun Jun 9 16:51:46 CEST 2013, x86-64, 4.6.3 RAM: 0000000000000000 - 000000000009a7ff: 618kB RAM: 0000000000100000 - 000000007f7b9fff: 2087656kB Total RAM: 2039MB New region for list regions: [ 20d000, 4c62c9] { 2b92ca} Root Module overlaps with: [ 2d0080, 2e45c7] { 14548} Boot bootstrap Regions of list 'regions' [ 0, fff] { 1000} Arch BIOS [ e0000, fffff] { 20000} Arch BIOS [ 106000, 1a646f] { a0470} Root Module [ 1a7000, 20c9bd] { 659be} Root Module [ 2d0080, 2e45c7] { 14548} Boot bootstrap [ 1013000, 10a8fff] { 96000} Boot bootstrap-ptab64 [ fc000000, ffffffff] { 4000000} Arch BIOS region overlap Key press reboots... ============================================= Everything works for 32bit. I took a look at bootstrap/server/src/startup.cc. I verified that modaddr is correctly passed to boostrap in both cases (32 and 64bit; it is 0x2000000 everytime). It appears that the failure happens in the call to add_boot_modules_region(): /* we're just a GRUB-booted kernel! */ add_boot_modules_region(mbi); if (_mod_addr) move_modules(mbi, _mod_addr); I do not fully understand all this code but to me this looks like a logic error: first the move should happen to honor "-modaddr" and only then the overlap check should be done. Here is the output for 32bit: ============================================= L4 Bootstrapper Build: #3 Sun Jun 9 16:55:38 CEST 2013, x86-32, 4.6.3 RAM: 0000000000000000 - 000000000009a7ff: 618kB RAM: 0000000000100000 - 000000007f7b9fff: 2087656kB Total RAM: 2039MB Moving up to 7 modules behind 2000000 moving module 00 { 139000-1ba783 } -> { 2829000-28aa783 } [530308] moving module 01 { 1bb000-21015e } -> { 28ab000-290015e } [348511] moving module 02 { 2e5000-51f51c } -> { 2901000-2b3b51c } [2336029] moving module 03 { 520000-762e3b } -> { 2000000-2242e3b } [2371132] moving module 04 { 763000-8880c6 } -> { 2243000-23680c6 } [1200327] moving module 05 { 211000-211080 } -> { 2369000-2369080 } [129] moving module 06 { 889000-9616a6 } -> { 236a000-24426a6 } [886439] Scanning /fiasco -serial -serial_esc -comspeed 115200 -comport 1 -nokdb Scanning /sigma0 Scanning /moe rom/hello.lua Bootloader MMAP: [ 0, 9a800) RAM (1) [ e0000, 100000) reserved (2) [ 100000, 7f7ba000) RAM (1) [ fc000000, 100000000) reserved (2) Relocated mbi to [0x2e0000-0x2e043f] Loading /fiasco Loading /sigma0 Loading /moe find kernel info page... found kernel info page at 0x400000 ... ============================================= Since the module addresses are also different between the two version this might also be an issue with the linker scripts (and thus just luck that the 32bit version boots), I would guess. I am using a Xen VM for testing. Any help would be appreciated. Thanks, Daniel

3 6

How to make task run on different cores?
by Chao-Jui Chang 12 Jun '13

12 Jun '13

Hi, I start up 4 L4Linux on intel core2quad platform. In jdb, I can see 4 vmlinuz on the task list (command 's' in jdb). Next, I run 4 benchmarks, one in each L4Linux, but the experiment result shows that the 4 benchmark are running on the same core. The kernel seems not scheduling them to different cpu cores. I have enabled "Enable multi processor support" option in fiasco config menu and the jdb shows there are 4 cores: *** Cut start *** ----------------------------------------------------------------------- CPU 0 [f000d2a0]: IRQ ENTRY CPU 1 [f0022451]: Maskable Interrupt CPU 2 [f0022451]: Maskable Interrupt CPU 3 [f0022451]: Maskable Interrupt jdb: g *** Cut end *** But the running benchmarks are not showing on the task list(command 's' in jdb), is it normal? I remember in ARM L4Linux, the task list will show 'vmlinuz', 'sh', 'benchmark', ...,etc. Best Regards, Chao-Jui

2 5

How Fiasco reclaim task resources when the task exits (abnormally) ?
by BogDan 11 Jun '13

11 Jun '13

Hello, What happens with a task resources when a task crashes or it leaks resources at exit? How this resources (e.g. memory, file descriptors, any other capabilities) are reclaimed back by the o.s. ? Cheers, BogDan.

2 3

Re: Fiasco.OC with ARM TrustZone
by Chao-Jui Chang 11 Jun '13

11 Jun '13

Hi Adam, Thanks for your reply. After I change the memory to 1023, it runs but stops at ### Timer for CPU0 is at IRQ 28 Calibrating timer loop... ### By the way, how to turn on the module loading information during booting? The latest snapshot and svn only prints message starting from "Hello from Startup::stage2" ### Start cur ### Exynos4412 # run fiasco Partition1: Start Address(0x1000), Size(0x32000) reading bootstrap.raw 803080 bytes read Boot with zImage Starting kernel ... Hello from Startup::stage2 Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl Watchdog initialized SERIAL ESC: allocated IRQ 305 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rUnversioned director compiled with gcc 4.5.2 for Samsung Exynos [] Build: #22 17:15:49 CST 2013 Timer for CPU0 is at IRQ 28 Calibrating timer loop... ### End ### Thanks, Chao-Jui 2013/5/12 Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Hi, > > On Tue May 07, 2013 at 17:51:42 +0800, Chao-Jui Chang wrote: > > Is trustzone working on exynos 4412 platform? > > It is generally supposed to work but this also depends on the particular > board/system due to board configs etc. > > > I have selected the follow item in Fiasco config menu: > > * Platform Timer (Multi-core timer) > > * Use ExtGic > > * Execution Model (TrustZone normal side) > > > > But it stop at early stage. > > Same result for Execution Model (Standard mode). > > but no message for Execution Model (TrustZone secure side). > > One reason could be the configured amount of memory, is it 1023 or 1024MB? > > > If the trustzone is disabled in u-boot, the 'Standard mode' works fine. > > That could also indicate that. > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers >

2 5

Program development for L4Re
by Rahul Singhal 11 Jun '13

11 Jun '13

I have recently ported l4 fiasco + l4Re on raspberry pi. I tested the port with the sample hello world program and it works fine.Now I want to write some of my own programs (C++, C and python) and run it on this environment. All I have done as of now is modify the sample hello world code a bit and test it. How do I go about doing this and where to start from? i appreciate your help. Regards Rahul

2 1

Task threads are not killed at exit
by BogDan 10 Jun '13

10 Jun '13

Hello, Not all the task threads are killed when a task exits or it crashes. I've created a simple example here: http://paste.kde.org/760274 After application crashes (line 22), test thread is still alive, I still can see "Test thread alive" message printed. If I call exit or return instead to crash the task, the test thread is still alive . Cheers, BogDan.

2 3

Re: <http://l4ka.org/> down?
by Thomas Schwinge 08 Jun '13

08 Jun '13

Hi! As the l4ka mailing list also seems to be defunct (though, my email didn't bounce), forwarding the question to the Dresden L4 folks as well as the registrant of the l4ka.org domain: On Thu, 06 Jun 2013 10:06:02 +0200, Thomas Schwinge <thomas(a)codesourcery.com> wrote: > On Wed, 05 Jun 2013 17:10:11 +0200, I wrote: > > On Wed, 5 Jun 2013 17:02:03 +0300, Fotis Koutoulakis <fotis.koutoulakis(a)gmail.com> wrote: > > > On http://www.gnu.org/software/hurd/microkernel.html the link for the > > > paper "On Microkernel Construction" appears to be dead. This patch > > > replaces the dead link with a working one. > > > > > [ mkernelconstructionurl.patch: application/octet-stream (as text/x-diff) ] > > > 14c14 > > > < [[Liedtke]] explains in [On Microkernel Construction](http://l4ka.org/publications/paper.php?docid=642) > > > [...] > > > As it appears that <http://l4ka.org/> generally is down (»Unconfigured > > server«) Now the server completely disappeared. > > at the moment. I suggest we wait a few days and see whether it > > comes back. If not (huh...), I'd like to use a more canonical [...] > > Any comments from the l4ka list? Is this a permanent outage, or just > temporary? Grüße, Thomas

1 0

arm-linux-ld not found while compiling l4-fiasco microkernel
by Rahul Singhal 06 Jun '13

06 Jun '13

I am trying to port L4-fiasco + L4Re to raspberry pi. But when I compile fiasco, it throws an error saying arm-linux-ld not found. I found that I will need cross compiler binaries to compile the fiasco microkernel. But where to find them. Please help! Thanks in advance.

3 2

Hello scenario gets stuck
by Markus Partheymueller 05 Jun '13

05 Jun '13

Hey, I'm having trouble booting the hello example on real hardware. The following config is booted via PXE: addr 0x2000000 exec mparthey/foc/bootstrap -serial load mparthey/foc/fiasco -serial -serial_esc -esc load mparthey/foc/sigma0 load mparthey/foc/moe load mparthey/foc/l4re load mparthey/foc/hello But it hangs after "MOE: Hello world". I can still enter the Kernel debugger, listing these task and thread objects: [Objects] 1 f007e020 [Task ] {KERNEL} R=2 6 ffdc6134 [Thread ] {KERNEL} C=0 R=1 current 7 fffe8f70 [Task ] {sigma0 } R=3 8 ffd80134 [Thread ] {sigma0 } C=0 S=D:7 R=3 9 fffe8f18 [Task ] R=3 a ffd83134 [Thread ] C=0 S=D:9 R=4 Backtrace on thread a yields an address 0x143d7d in moe (?), belonging to void List_alloc::merge() { List_alloc_sanity_guard __attribute__((unused)) guard(this, __func__); Mem_block *c = _first; while (c && c->next) 143d7d: 8b 00 mov (%eax),%eax 143d7f: 85 c0 test %eax,%eax 143d81: 75 ee jne 143d71 <_ZN22Single_page_alloc_base5_freeEPvmb+0x51> _ZN22Single_page_alloc_base5_freeEPvmb(): [...]/src/l4/pkg/moe/server/src/page_alloc.cc:109 } On a different machine the exact same setup works fine. Has anyone got a clue what goes wrong here? If I should get more information out of the kernel debugger, just let me know. Cheers Markus

2 5