- l4-hackers - example.com Site

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 14 Jul '13

14 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

A interprocess communication system for two l4linux instances
by Wajidali Whowe 05 Jul '13

05 Jul '13

Dear all, I am trying to implement an IPC method between two l4linux instances (lets call them as vmlinuz1 and vmlinuz2) using l4ser driver. Nevertheless both l4linux instances stuck during boot up printing, the following last sentence: "vmlinuz.| L4 serial driver" Going over the driver/tty/serial/l4ser.c file, I have seen that the stuck position line is in the function "l4ser_init_port"; "t = L4XV_FN(l4_msgtag_t, l4_icu_bind(l4ser_port[num].vcon_cap, 0, l4ser_port[num].vcon_irq_cap));" The following is my lua script: local ttyChannel = l:new_channel(); local hid = l:new_channel(); local linux_caps = { log = L4.Env.log:m("rws"); vbus = io_caps.linux_bus, rtc = rtc_caps.rtc, ev = hid:svr(), rom = L4.Env.rom, ttyMv0 = ttyChannel, }; l:start( { caps = linux_caps, }, "rom/vmlinuz1 mem=512M l4ser.add=ttyMv0 l4-input-srv.enable=1 console=ttyLv0 ramdisk=rom/myRamdisk root=1:0 ramdisk_size=190000 l4x_rd=rom/myRamdisk init=/sbin/init"); local linux_caps2 = { vbus = io_caps.linux_bus2, rtc = rtc_caps.rtc, rom = L4.Env.rom, ttyMv0 = ttyChannel, }; l:start( { caps = linux_caps2, }, "rom/vmlinuz.android mem=512M l4ser.add=ttyMv0 console=ttyLv0 ramdisk=rom/ramdisk root=1:0 ramdisk_size=190000 l4x_rd=rom/ramdisk init=/sbin/init"); How do you think that might cause the problem? Best regards and many thanks.

1 0

Thought you'd find this interesting
by Rahul Singhal 30 Jun '13

30 Jun '13

Hi! I’ve just learned about the water crisis and thought you would be interested to check out this story: https://waterforward.charitywater.org/et/xclFZthf Let me know what you think! Thanks, Rahul -- Sent via WaterForward, an initiative of charity: water WaterForward, 387 Tehama Street, San Francisco, CA 94103, USA. Click here to unsubscribe: https://waterforward.charitywater.org/opt_out?et=xclFZthf

1 0

15th Real Time Linux Workshop - Call for Papers
by Nicholas Mc Guire 25 Jun '13

25 Jun '13

15th Real Time Linux Workshop 1st Call for Papers October 28 - 31, 2013 Dipartimento tecnologie innovative Scuola universitaria professionale della Svizzera italiana Lugano-Manno Switzerland Following the meetings of academics, developers and users of real-time and embedded Linux at the previous 14 Real Time Linux Workshops held world-wide (Vienna, Orlando, Milano, Boston, Valencia, Singapore, Lille, Lanzhou, Linz, Guadalajara, Dresden, Nairobi, Prague and Chapel Hill) - the 2013 Real Time Linux Workshop will come to the Scuola Universitaria Professionale della Svizzera Italiana in Lugano-Manno, Switzerland. It will be held from October 28 to October 31, 2013. Rationale Real-time systems have evolved over the past decades in a relatively calm manner - performance has increased, one can say dramatically, but the main paradigms were pretty stable since the mid 80s. With the considerable increase of computing power, notably with multicore systems becoming mainstream in embedded devices, the requirements on RTOS are shifting and the tools are again trying to catch up. In stark contrast to 1999 (when the first RTLWS took place), Linux has a strong position in all kind of embedded systems, ranging from consumer electronics to network devices and a broad range of industrial applications including safety related systems. The technological resources suitable for high-availability, real-time, and safety critical systems have been continuously expanding and improving - allowing to cover the entire development life cycle of industrial projects based on open-source tools. At the core of this development is the availability of stable operating systems with reliable real-time properties. Extending and improving the real-time properties of Open Source RTOS is a continuous research and development effort. The OSADL has set itself the ambitious goal to document these efforts and it's most effective tool to do so is the annual Real Time Linux Workshop. Call for papers Authors from regulatory bodies, academics, industry as well as the user-community are invited to submit original work dealing with general topics related to Open Source and Free Software based real-time systems research, experiments and case studies, as well as issues of integration of open-source real-time and embedded OS. A special focus will be on industrial case studies and safety related systems. Topics of interest include, but are not limited to: - Modifications and variants of the GNU/Linux operating system and extending its real-time capabilities, - Contributions to real-time Linux variants, drivers and extensions, - Tools for the verification and validation of real-time properties, - User-mode real-time concepts, implementation and experience, - Real-time Linux applications, in academia, research and industry, - Safety related FLOSS systems, - Safety related systems using FLOSS components, - FLOSS Tools used to analyze, verify or validate safety properties, - Work in progress reports, covering recent developments, - Educational material on real-time Linux, - RTOS core concepts, RT-safe synchronization mechanisms, - RT-safe IPC mechanisms for RT and non RT components, - Analysis and benchmarking methods and results of real-time GNU/Linux variants, - Debugging techniques and tools, both for code and temporal debugging of core RTOS components, drivers and real-time applications, - Real-time related extensions to development environments Abstract submission If you wish to present a paper at the workshop, please submit an abstract using the submission page at https://www.osadl.org/RTLWS15-Abstract.submission-form.0.html. Final paper to be included into the RTLWS15 Proceedings Upon acceptance of an abstract by the RTLWS15 Program Committee, the author will be invited to submit a full paper in a form defined by https://www.osadl.org/paper.tgz. A detailed description of the editing and formatting process will be provided along with the notification email. Further information: http://www.osadl.org/RTLWS Important dates July 29, 2013 - Abstract submission deadline August 26, 2013 - Notification of acceptance September 23, 2013 - Submission of final paper October 28-31, 2013 - Workshop Organization committee: Local organizers: - Roberto Bucher, Scuola universitaria professionale della Svizzera italiana SUPSI, Switzerland OSADL/RTLF - Carsten Emde, OSADL - Nicholas Mc Guire, OSADL - Andreas Platschek, ICT, Vienna University of Technology, Austria Program committee: - Alexey Khoroshilov, ISPRAS, Russia - Andrea Bastoni, SYSGO AG, Germany - Andreas Platschek, TU-Wien, Austria - Bernhard N�lte, IQSE TueV SueD Rail, Germany - Carsten Emde, OSADL, Germany - Cheng Sheng, Beijing Shenzhou Aerospace Software Technology, China - Fans, Spectrum Sys, China - Georg Schiesser, OpenTech EDV Research, Austria - Herman H�rtig, Technische Universit�t Dresden, Germany - Julia Lawall, Inria/LIP6, France - Julien Delange, Carnegie Mellon Software Engineering Institute, USA - Klaus Reichl, Base Systems Technology Thales, Austria - Matthias Auchmann, A&R TECH, Austria - Michal Sojka, Czech Technical University in Prague, Czech Republic - Nicholas Mc Guire, OpenTech EDV Research, Austria - Paul E. McKenney, IBM Linux Technology Center, USA - Paolo Mantegazza, Politecnico di Milano, Italy - Peter Okech, University of Nairobi, Kenya - Peter Wurmsdobler, Aveillant Ltd, UK - Peter Zijlstra, RedHat, Netherlands - Philippe Gerum, Xenomai, France - Roberto Bucher, SUPSI, Switzerland - Shawn Choo, Weslab, Singapur - Stefan Schoenegger, B&R, Austria - Steven Rostedt, RedHat, USA - Thomas Gleixner, Linutronix, Germany - Yutaka Matsuno, University of Electro-Communications, Japan - Zhou Qingguo, DSLab, Lanzhou University, China Workshop organizers: - Dipartimento Tecnologie Innovative, SUPSI, Switzerland - Open Source Automation Development Lab (OSADL) Roberto Bucher Carsten Emde Nicholas Mc Guire Andreas Platschek

1 0

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