l4-hackers April 2014

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

16 participants
27 discussions

Do L4 Linux lack source code about Freescale i.MX6 Quad ?
by Taeung 04 Aug '14

04 Aug '14

Hello , L4 hackers I always appreciate L4 hackers. I've succeed boot "helloworld + L4/Fiasco" on Freescale i.MX6q_sabre_sd. So, I've try to build L4 linux (|Repository : svn co http://svn.tudos.org/repos/oc/l4linux/trunk l4linux|). I've configured for build L4 Linux such as.. ====================================================== System type ---> ARM system type (Allow multiple platforms to be selected) Multiple platform selection ---> ARMv7 based platforms (Cortex-A, PJ4, Scorpion, Krait) Build type Freescale i.MX family Freescale i.MX support ---> i.MX6 Quad/DualLite support ====================================================== But I've meet errors even so often. such as .. 1. ERROR: CONFIG_ARM_PATCH_PHYS_VIRT must not be enabled. => So, I've force to change CONFIG_ARM_PATCH_PHYS_VIRT=y to =n . 2. irq.c:16:26: error: 'L4X_NR_IRQS_V_DYN' undeclared here irq.c:46:14: error: 'L4X_IRQS_V_DYN_BASE' undeclared and irq.c:48:14: error: 'NR_IRQS_HW' undeclared => So, I've included "#include <asm/generic/irq-vectors.h>" and "#include <asm/mach-arm/generic/mach/irqs.h>". 3. l4.c:57:13: error: 'L4X_IRQS_V_STATIC_BASE' undeclared ...etc. => So, I've included "#include <asm/generic/irq-vectors.h>" and "#include <asm/mach-arm/generic/mach/irqs.h>". 4. drivers/built-in.o: In function `clk_disable': clk.c:867: multiple definition of `clk_disable' arch/l4/built-in.o:/home/taeung/workspace/l4linux/arch/l4/kernel/arch-arm/l4.c:73: first defined here drivers/built-in.o: In function `clk_enable': clk.c:919: multiple definition of `clk_enable' arch/l4/built-in.o:/home/taeung/workspace/l4linux/arch/l4/kernel/arch-arm/l4.c:65: first defined here make[1]: *** [vmlinux] Error 1 make: *** [sub-make] Error 2 => So, I delete this lines in l4linux/drivers/clk/clk.c. 7. undefined reference to `__pv_phys_offset' from signal.c , init.c, mm.h ....etc. My question is.... Is it's problem that my config is wrong or l4 linux lack source code about Freescale i.MX6 Quad ? * Refer to > /home/taeung/workspace/l4linux/arch/l4/kernel/*irq.c* /home/taeung/workspace/l4linux/arch/l4/include/asm/generic/*irq-vectors.h* /home/taeung/workspace/l4linux/arch/l4/kernel/*pm.c */home/taeung/workspace/l4linux/arch/l4/kernel/arch-arm/*l4.c** */home/taeung/workspace/l4linux/arch/l4/l4lxlib/generic/*irq_gen.c* /home/taeung/workspace/l4linux/drivers/clk/*clk.c */home/taeung/workspace/l4linux/arch/l4/kernel/arch-arm/*signal.c */home/taeung/workspace/l4linux/arch/l4/mm/arch-arm/*init.c */home/taeung/workspace/l4linux/include/linux/*mm.h *

3 2

OKL4 vs L4::Pistachio
by Taylor Bioniks 15 May '14

15 May '14

How does OKL4 compare with L4::Pistachio as far as speed, security, responsiveness? L4::Pistachio uses kickstart to load it, the core kernel is contained in kernel, and the physical memory manager is stored in sigma0, I'm not even sure if it has a virtual memory manager. Does OKL4 have a built in memory manager, and does it handle virtual memory? Thank you.

3 3

How to enable 'CONFIG_COMMON_CLK' ?
by Taeung 30 Apr '14

30 Apr '14

Hello, L4 Hackers :-) I'm trying to build L4 Linux with added option of MMC device driver. When I've tried to compile L4 Linux , I've failed it with error log such as.. ============== drivers/built-in.o: In function `sdhci_pltfm_clk_get_max_clock': /home/taeung/test/source/l4linux/drivers/mmc/host/sdhci-pltfm.c:43: undefined reference to `clk_get_rate' make[1]: *** [vmlinux] Error 1 make: *** [sub-make] Error 2 ============== After I saw the log , I've guessed the cause is that 'drivers/clk/clk.c' was not built. So, I must enable 'CONFIG_COMMON_CLK' , to build 'drivers/clk/clk.c' How to enable 'CONFIG_COMMON_CLK' ? For reference, I've tried to compile L4 Linux with options as follows.. =================================== --- MMC/SD/SDIO card support [ ] MMC debugging [*] Assume MMC/SD cards are non-removable (DANGEROUS) [ ] MMC host clock gating *** MMC/SD/SDIO Card Drivers *** <*> MMC block device driver (8) Number of minors per block device [*] Use bounce buffer for simple hosts < > SDIO UART/GPS class support < > MMC host test driver *** MMC/SD/SDIO Host Controller Drivers *** < > ARM AMBA Multimedia Card Interface support -*- Secure Digital Host Controller Interface support -*- SDHCI platform and OF driver helper <*> Marvell MMP2 SD Host Controller support (PXAV3) < > Marvell PXA9XX SD Host Controller support (PXAV2) < > Synopsys DesignWare Memory Card Interface ==================================== -Taeung -

2 2

L4Linux on amd64 arch
by Irvanda Kurniadi 28 Apr '14

28 Apr '14

Hi hackers, Is there anyone who has tried to build l4linux on amd64? I compiled the new snapshot of L4re, but there is no l4linux for amd64. Can I barely compile this l4linux in l4re-amd64? thanks, Irvanda

2 3

L4linux: cpu and core [comprehension question]
by Irvanda Kurniadi 28 Apr '14

28 Apr '14

Hi hackers, I am a little bit confused about the term of cpu and core in l4linux. I have a system with 8 processor intel xeon E5606 with 4 cores in each cpu. I'm going to maximize it to become the maximum number of cores in all cpus. But I am confused in determining the l4x_cpus that what is the term cpu in here? Is it literally cpu or the number of threads that can be handled in each core? I run an openmp hello world apps over l4linux. I call the omp_get_thread_num() and I got 4 threads in the result. Are these 4 threads obtained from 4 cores in single cpu? So, if I'm right, how can I optimize to use all of the cpu existed in the system? I've tried to use l4x_cpus=8 and l4x_cpus=32, but those commands doesn't work for me. In my opinion, if I can maximize until the maximum number of cores and I have 32 threads that run concurrently, then it will be served by each core in those 8 cpus. In fiasco configuration, there is maximal supported number of CPUs. So referring to my case, the maximum is supposed to be 8, am I right? In case of thread migration in example ex_thread_migrate, I create 16 threads and will be migrated to each cpu. Here is the result: migrate | Migrated Thread00 -> CPU02 migrate | Migrated Thread01 -> CPU03 migrate | Migrated Thread02 -> CPU04 migrate | Migrated Thread03 -> CPU05 migrate | Migrated Thread04 -> CPU06 migrate | Migrated Thread05 -> CPU07 migrate | Migrated Thread06 -> CPU00 migrate | Migrated Thread07 -> CPU01 migrate | Migrated Thread08 -> CPU02 migrate | Migrated Thread09 -> CPU03 migrate | Migrated Thread10 -> CPU04 migrate | Migrated Thread11 -> CPU05 migrate | Migrated Thread12 -> CPU06 migrate | Migrated Thread13 -> CPU07 migrate | Migrated Thread14 -> CPU00 migrate | Migrated Thread15 -> CPU01 My question is do the thread00 and thread08 share the same core in CPU02 or they use different core in CPU02 which run concurrently? And also, is it normal to get the output like cpu[1] to cpu[7] goes to idle loop? Thanks, Irvanda

2 3

Re: L4Linux and L4Re communication
by Björn Döbel 25 Apr '14

25 Apr '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 25.04.2014 10:24, Irvanda Kurniadi wrote: > On Fri, Apr 25, 2014 at 4:24 PM, Björn Döbel > <doebel(a)os.inf.tu-dresden.de <mailto:doebel@os.inf.tu-dresden.de>> > wrote: > > -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > Hi, > >> In term of running hello world in L4Linux, I can run it by >> passing -m32 -static in the compilation process. But, now I'm >> having a problem in running the mpi-based application on L4Linux >> which this apps needs the mpi library to be able to run. I have >> ported the mpi library and run the apps over L4Re by using Ned. >> So, based on the explanation above, I don't understand how to run >> the mpi-based program on top L4Linux in which the L4Linux >> definitely doesn't have mpi-library because the mpi-library is >> existed in L4Re. Is it like this, the l4linux kernel needs the >> device driver to communicate with external L4 apps (in my case >> mpi-base apps), then to trigger the communication we should make >> the kernel module (linux program to talk to the l4linux kernel). >> Am I right? Can you point one example, which is similar with my >> case, that can be followed by me? > > I see two different scenarios here: > > > 1. Your MPI application is supposed to run as a Linux application > in L4Linux - -> In this case all you need is an MPI library > installed in the Linux distribution that you boot L4Linux into. > E.g., if you are using some custom ramdisk, simply add a (Linux) > MPI library to this disk and your program will then use it. No L4 > magic necessary at all. > > > 2. Your MPI application is supposed to run directly on L4Re - -> In > this case you don't need any Linux or L4Linux in the setup. You > build your L4Re program and link it with your ported MPI library > and then it should run. > > Does that answer your question or am I missing your point? > > > Yes it does. In my case I think I only need to run my application > on L4linux, but since the beginning I misunderstood that I have to > port the library on L4. I have wasted so much time in doing > scenario 2. Sorry to hear that. > What is the differences between running application over L4linux > and running application as a task in L4Re? Good question. Let me try to explain from bottom up. 1. It all starts with Fiasco.OC, our microkernel. Fiasco runs directly on the hardware in the CPU's privileged mode. It provides kernel mechanisms, such as threads, tasks, inter-process communication and scheduling. - - - - - - - - - - - - - - - - - - - - - - - - - - - - +-------------+ Privileged CPU Mode | Fiasco.OC | +-------------+ 2. On top of Fiasco.OC we have the L4 Runtime Environment. L4Re is a set of libraries and applications that run in non-privileged (aka "user") mode and implement basic operating system services, such as memory management, device drivers etc. +------------------------+ | L4 Runtime Environment | Non-privileged +------------------------+ CPU mode - - - - - - - - - - - - - - - - - - - - - - - - - - - - +-------------+ Privileged CPU Mode | Fiasco.OC | +-------------+ 3. On top of L4Re you are free to implement your own software using L4Re's and Fiasco's primitives. This is where scenario #2 (MPI on L4Re) comes in. +-----------------+ +---------------------+ | MPI Application | | Another Application | +-----------------+ +---------------------+ +------------------------+ | L4 Runtime Environment | Non-privileged +------------------------+ CPU mode - - - - - - - - - - - - - - - - - - - - - - - - - - - +-------------+ Privileged CPU Mode | Fiasco.OC | +-------------+ In contrast to Linux this is a completely different operating system. You mostly don't see that because L4Re provides you with interfaces that are similar to Linux (e.g., a POSIX C library, a virtual file system etc.). With respect to MPI the difference here is that you have to adapt any kind of load balancing, process distribution etc. to use the respective Fiasco and L4Re services. 4. Now we have a special usage scenario: We can slightly adapt the Linux kernel and run it as an application on top of L4Re. This is called L4Linux and the approach is what we call virtualization. +----------------+ | L4Linux Kernel | +----------------+ +------------------------+ | L4 Runtime Environment | Non-privileged +------------------------+ CPU mode - - - - - - - - - - - - - - - - - - - - - - - - - - - +-------------+ Privileged CPU Mode | Fiasco.OC | +-------------+ 5. A single (L4)Linux kernel does not help you very much, because you want to run applications on top of Linux. Here the virtualization magic steps in and as a result you can run standard Linux applications on top of L4Linux without the need for any modification. Technically, these applications are L4 applications with the difference that their system calls are not sent to the Fiasco kernel but to the L4Linux kernel. The combination of the L4Linux kernel and all Linux applications running on top of it is what we call a virtual machine (VM). Linux VM .............................. . +-------------------+ . . | Linux Application | . . +-------------------+ . . +----------------+ . . | L4Linux Kernel | . . +----------------+ . .............................. +------------------------+ | L4 Runtime Environment | Non-privileged +------------------------+ CPU mode - - - - - - - - - - - - - - - - - - - - - - - - - - - +-------------+ Privileged CPU Mode | Fiasco.OC | +-------------+ This setup is how scenario #1 works. Your Linux MPI application believes it is running on a real Linux kernel and Fiasco's virtualization makes sure that everything works as expected. Kind regards, Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlNaJo8ACgkQP5ijxgQLUNmSfgCgkQUPRGJ/Vyq0DIQkEi/Dm9+2 gAcAnRdS9hHkIIp9qBYCfHHL1+Uuy2Fi =zFBP -----END PGP SIGNATURE-----

1 0

L4Linux and L4Re communication
by Irvanda Kurniadi 25 Apr '14

25 Apr '14

Hi, This thread is just a sequel from http://os.inf.tu-dresden.de/pipermail/l4-hackers/2013/006108.html > > Is it possible to run my application on top l4linux; like, > > if I want to run hello world application over l4linux (not just > > booting it over l4/fiasco)? I tried to run it by using this > > configuration: > > > > -- Start Hello loader:start( { caps = {}, l4re_bdg = L4.Dbg.Warn, > > log = {"hello","red"}, }, "rom/hello"); > > > > -- Start Linux loader:start( { caps = { log = L4.Env.log:m("rws"), > > fb = mag_svc:create(L4.Proto.Goos, "g=640x480"); vbus = > > vbus_l4linux; }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", > > "yellow" }, }, "rom/" .. lxname .. " mem=64M console=tty0 > > l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 > > ramdisk_size=4000 init=linuxrc"); > > > > But I think it only run two different applications over l4/fiasco. > > > > Do you have any idea how to run the hello application over > > l4linux? > Bjoern said: > > The idea behind L4Linux is to run native Linux applications, so hello > world in L4Linux works just as the version you would write in your > local Linux. > > Running an application that communicates with both L4 and Linux is a > bit more involved. L4Linux applications don't talk to L4 apps > directly. The L4Linux kernel is an L4 app though, so it can do this > talking for you. The missing link then is to write a Linux device > driver that allows your Linux program to talk to the L4Linux kernel, > which then in turn communicates with an external L4 application. > > In term of running hello world in L4Linux, I can run it by passing -m32 -static in the compilation process. But, now I'm having a problem in running the mpi-based application on L4Linux which this apps needs the mpi library to be able to run. I have ported the mpi library and run the apps over L4Re by using Ned. So, based on the explanation above, I don't understand how to run the mpi-based program on top L4Linux in which the L4Linux definitely doesn't have mpi-library because the mpi-library is existed in L4Re. Is it like this, the l4linux kernel needs the device driver to communicate with external L4 apps (in my case mpi-base apps), then to trigger the communication we should make the kernel module (linux program to talk to the l4linux kernel). Am I right? Can you point one example, which is similar with my case, that can be followed by me? Thanks, Irvanda

2 2

build error: [kobject_mapdb.o] error
by Irvanda Kurniadi 25 Apr '14

25 Apr '14

Hi hackers, I have a problem in building l4/fiasco for arm. I'm using ubuntu 11.10 64-bit and want to build l4/fiasco for arm9. For cross compiler, I'm using Sourcery_G++_Lite. For the snapshot, I'm using current snapshot l4re-snapshot-2014022818. Then, when I tried to build the l4/fiasco, I got the error message shown in [1.error message]. Have you ever built l4/fiasco for arm9 over ubuntu 11.10 64-bit? I think this is just a compiler problem. If you know about this problem, please let me know to solve this problem. Thanks, Irvanda [1.error message] make[3]: Entering directory `/home/l4re-arm/obj/fiasco/arm-mp-rv-pb11mp' ... Generating version information ... Making kip.o ... Making kip-debug.o ... Making kip-arm.o ... Making l4_types.o ... Making l4_types-debug.o ... Making l4_fpage.o ... Making l4_msg_item.o ... Making l4_buf_desc.o ... Making l4_error.o ==> Archiving into libabi.a ... Making kernel.arm.lds ... Making crt0.o ... Making bootstrap.o ... Making bootstrap-arm-realview.o ==> Linking bootstrap.fiasco.o ... Making kernel_panic.o ... Making libc_backend_lock.o ... Making cpu_mask.o ... Making rcupdate.o ... Making kobject_mapdb.o In file included from /home/l4re-arm/src/kernel/fiasco/src/kern/context.cpp:22, from /home/l4re-arm/src/kernel/fiasco/src/kern/switch_lock.cpp:85, from /home/l4re-arm/src/kernel/fiasco/src/kern/helping_lock.cpp:4, from /home/l4re-arm/src/kernel/fiasco/src/kern/lock.cpp:3, from /home/l4re-arm/src/kernel/fiasco/src/kern/kobject.cpp:3, from /home/l4re-arm/src/kernel/fiasco/src/kern/kobject_mapdb.cpp:5, from auto/kobject_mapdb.cc:3: /home/l4re-arm/src/kernel/fiasco/src/lib/libk/cxx/function:34: error: 'cxx::functor<Res(Args ...)>::functor(cxx::functor<Res(Args ...)>&&)' cannot be defaulted make[3]: *** [kobject_mapdb.o] Error 1 make[3]: Leaving directory `/home/l4re-arm/obj/fiasco/arm-mp-rv-pb11mp' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/l4re-arm/obj/fiasco/arm-mp-rv-pb11mp'

2 4

Keyboard Input in L4Re Pandaboard ARM
by Erry Pradana Darajati 24 Apr '14

24 Apr '14

Hello L4 hackers I have a question about accessing standard I/O Is it possible to access keyboard using L4Re. If it's possible, can i access it using USB keyboard or do i need to access the std input from serial ? The idea of this question because i want to make a simple calculator to practice study the stdio of L4Re I am really sorry for the basic question And i am appreciating any helps and answer Thanks L4 Hackers -- *Regards,* *Erry Pradana Darajati | Student of Computer Engineering* *Politeknik Elektronika Negeri Surabaya / EEPIS, Indonesia*

2 1

Can you confirm whether or not I secure devices on L4 Linux ?
by Taeung 24 Apr '14

24 Apr '14

Hello, L4 hackers and Wei Jin :-) I'm trying to secure devices which are 'SD card' and 'Ethernet' on L4 Linux. Can you confirm whether or not I secure devices on L4 Linux ? Sorry for long my mail.. The try I've done is as follows .. 1) 'l4lx-vbus.io' file I've modified ==================== # vim:set ft=ioconfig: # configuration file for io l4linux => new System_bus() { NIC => wrap(hw-root.NIC); FLASHMEMORY => wrap(hw-root.FLASHMEMORY); } ==================== 2) 'arm-rv-eb-mc.devs' file I've modified using IRQ and MMIO information in my board's DataSheet . (My board is 'Freescale imx6 Quad SABRE SD') ==================== local Hw = Io.Hw local Res = Io.Res Io.hw_add_devices { FLASHMEMORY = Hw.Device { hid = "flashmemory"; Res.mmio(0x02198000 , 0x0219BFFF); Res.irq(56); }, NIC = Hw.Device { hid = "freescale"; Res.mmio(0x02188000, 0x0218BFFF); Res.irq(150); Res.irq(151); }, } ==================== 3) l4lx_xs.cfg I've modified. ==================== local lxname = "vmlinuz"; if L4.Info.arch() == "arm" then lxname = "vmlinuz.arm"; end loader = L4.default_loader; vbus_l4linux = loader:new_channel(); -- Start io & flash memory loader:start( { caps = { sigma0 = L4.cast(L4.Proto.Factory,L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; l4linux = vbus_l4linux:svr(); }, log = { "IO", "y" }, l4re_dbg = L4.Dbg.Warn, }, "rom/io rom/arm-rv-eb-mc.devs rom/l4lx-vbus.io"); L4.default_loader:start( { caps = { log = L4.Env.log:m("rws"), vbus = vbus_l4linux; }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, }, "rom/" .. lxname .. " mem=64M vmalloc=4M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 rw ramdisk_size=20480 init=/linuxrc debug"); ==================== 4) I've modified 'modules.list' 5) I found something about device on L4 Linux booting log as follows.. ==================== |Starting kernel ... L4 Bootstrapper Build: #8 Tue Apr 22 16:33:35 JST 2014, 4.6.2 20110630 (prerelease) Scanning up to 1024 MB RAM ...(omitted) l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.13.0-l4-svn46 (taeung@taeung-MS-7798) (gcc version 4.6.2 20110630 (prerelease) (Freescale MAD -- Linaro 2011.07 -4 l4linux | Binary name: rom/vmlinuz.arm | ||...(omitted) l4linux | Device scan: l4linux | Device: (noname) l4linux | Device: NIC l4linux | MEM: 02188000 - 0218bfff l4linux | IRQ: 00000096 - 00000096 l4linux | IRQ: 00000097 - 00000097 l4linux | Device: FLASHMEMORY l4linux | MEM: 02198000 - 0219bfff l4linux | IRQ: 00000038 - 00000038 l4linux | Device scan done. || ||||...(omitted) |||DMA: preallocated 256 KiB pool for atomic coherent allocations Added static device '(noname)' with 0 resources. Added static device 'NIC' with 3 resources. Added static device 'FLASHMEMORY' with 2 resources. ...(|||omitted|) mmcblk driver (I've added 'pr_info("|||mmcblk driver|");' in __init function of mmc device driver source code.) ...(|||omitted|)| |mount: mounting /dev/mmcblk0p2 on /mnt failed: No such device or address /etc/init.d/S10getconf: Couldnt mount /dev/mmcblk0p2 Initializing random number generator... random: dd urandom read with 1 bits of entropy available done. Loading libertas firmware... /lib/firmware/libertas not found! /etc/init.d/S30libertas_fw: exit: line 46: Illegal number: -2 Starting network... Cannot find device "usb0" Cannot find device "usb0" Cannot find device "wlan0" Cannot find device "wlan0" Starting dropbear sshd: OK Loading iptables rules... /etc/iptables not found! dnsmasq: unknown interface usb0 Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Invalid argument. Cannot read /proc/net/wireless Error for wireless request "Set ESSID" (8B1A) : SET failed on device wlan0 ; Invalid argument. net.ipv4.ip_forward = 1 / # |==================== I guess that devices is secured through being registered in io server but network could not be run because there is not FEC ethernet driver. (For reference, my board's ethernet use 'FEC Ethernet Driver' ) However I don't know why could not run 'mount /dev/mmcblk0p1 /mnt '. Do I secure devices on L4 Linux successfully ? If I only make drivers for its to run successfully , can I access 'SD card' and 'Ethernet' on L4Linux ? Or is my guess wrong ? I would appreciate if anyone answer. - Taeung -

2 1

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 April 2014