- l4-hackers - example.com Site

Implementing a few real time scheduling algorithms on Fiasco.OC
by Biermans Joeri 30 May '15

30 May '15

Hi everyone, I'm a student at the university of Antwerp and I'm currently working on my master's thesis. My project is about comparing the performance of a few global multicore scheduling algorithms (G-RM, G-EDF, ...) on an embedded system. A part of my thesis is to make an implementation on a real embedded system equipped with a quadcore processor (i.MX6). To do that I need an RTOS. Fiasco with the l4re at a first sight seems an interesting candidate. To test the performance of the above algorithms I will schedule a bunch of randomly generated tasksets comprising some periodic tasks having implicit deadlines* with each of the algorithms and try to detect if any deadlines are missed. * Such a task is executed repeatedly after a fixed amount of time and its deadline is equal to its period, which is the point of time when the next invocation of the task takes place. This brings me to my first question: Would this be achievable with the fiasco kernel? I've been trying to interpret the project of the fiasco kernel during the last days, but this seems easier said than done. As a first step I've been trying to figure out how the scheduler works and how exactly the scheduling policies are implemented. (I have read somewhere the current scheduling policy is fixed priority round robin) Is there perhaps a more documented version of the code or an overview of the different classes, their functions and the way they interact available? It's really hard to figure out a bunch of code without any leads on how exactly the project has been implemented. Besides that I don't really have a clue about how to start developing on the fiasco kernel. Some tips about how to start working on the kernel are always welcome. Has anyone got experience with developing on the fiasco kernel? It would be nice to get some directions on this matter because I'm quite stuck on this. Thanks in advance! Kind regards, Joeri

3 2

Booting error of L4Linux enabled SMP surpport
by Xiefeng (Stephen) 29 May '15

29 May '15

Hi all, I use entry L4Linux-mag-x86 in modules.list to start a L4Linux on L4Re successfully. The codes is l4re-snapshot-2014092821. L4Linux use x86-native_deconfig complie, use l4lx-gfx.cfg to start L4Linux. This config is just set one cpu for L4Linux. If I set l4x_cpus=2 in l4lx-gfx.cfg, use x86-mp_vPCI_defconfig and set CONFIG_NR_CPUS=2 to compile the L4Linux, when I start L4Linux, a kernel panic happened: l4linux | Loading: rom/ramdisk-x86.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 88d70000 to 89070000 [3072KiB] l4linux | rtc not found l4linux | l4lx_thread_create: Created thread 41f (timer0) (u:b3000a00, v:00000000, sp:008e1fa8) l4linux | WARNING: Unknown wrmsr: 0000008b at 0x414bad l4linux | WARNING: Unknown rdmsr: 00000186 at 0x85e1d6 l4linux | WARNING: Unknown rdmsr: 00000187 at 0x85e1d6 l4linux | WARNING: Unknown wrmsr: 000000c1 at 0x85e2a7 l4linux | Launching cpu1 on pcpu 1 at 0x4024e0 l4linux | l4lx_thread_create: Created thread 420 (cpu1) (u:b3000800, v:b3000600, sp:008c7fa8) l4linux | WARNING: Unknown wrmsr: 0000008b at 0x414bad l4linux | l4lx_thread_create: Created thread 424 (timer1) (u:b3000400, v:00000000, sp:008e3fa8) l4linux | Spurious IPI on CPU0: 4 l4linux | panic: going to sleep forever, bye Has anyone encountered this problem? Stephen

3 4

Boot L4Linux Error
by 刘海剑 28 May '15

28 May '15

Hello everyone, after building l4re-snapshot-2014092821 on my Ubuntu-14.04(32bit), I run L4Linux-mag-x86, and get some errors. The information is as follows: qemu-system-i386 -kernel /home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/bootstrap -append "bootstrap -modaddr 0x01100000" -initrd "/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco -serial_esc,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/sigma0 ,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/l4re ,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/ned ,/home/lhj/L4Linux/l4re-snapshot-2014092821/src/l4/conf/examples/l4lx-gfx.cfg ,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/io ,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/fb-drv ,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/mag ,/home/lhj/L4Linux/l4re-snapshot-2014092821/files/cfg/x86-legacy.devs ,/home/lhj/L4Linux/l4re-snapshot-2014092821/src/l4/conf/examples/l4lx-x86.io ,/tmp/QEVRyiQlKD/vmlinuz ,/home/lhj/L4Linux/l4re-snapshot-2014092821/files/ramdisk-x86.rd " -m 256 -serial stdio L4 Bootstrapper Build: #1 Tue May 26 16:48:47 CST 2015, x86-32, 4.8.2 RAM: 0000000000000000 - 000000000009fbff: 639kB RAM: 0000000000100000 - 000000000fffdfff: 261112kB Total RAM: 255MB Scanning /home/lhj/L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco -serial_esc Scanning /home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/sigma0 Scanning /home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg need 1368 bytes to copy MBI reserved 1368 bytes at 0x2000 Moving up to 13 modules behind 1100000 moving module 12 { 2266400-25663ff } -> { 3085000-3384fff } [3145728] moving module 11 { 1e8e400-2265919 } -> { 2cad000-3084519 } [4027674] moving module 10 { 1e8d400-1e8d626 } -> { 2cac000-2cac226 } [551] moving module 09 { 1e8c400-1e8c63e } -> { 2cab000-2cab23e } [575] moving module 08 { 1a29400-1e8ba0b } -> { 2848000-2caa60b } [4597260] moving module 07 { 189f400-1a28598 } -> { 26be000-2847198 } [1610137] moving module 06 { 98e400-189ee03 } -> { 17ad000-26bda03 } [15796740] moving module 05 { 98d400-98d96a } -> { 17ac000-17ac56a } [1387] moving module 04 { 736400-98ce09 } -> { 1555000-17aba09 } [2451978] moving module 03 { 5fc400-735b2c } -> { 141b000-155472c } [1283885] moving module 02 { 3a9400-5fb7eb } -> { 11c8000-141a3eb } [2434028] moving module 01 { 353400-3a928a } -> { 1172000-11c7e8a } [351883] moving module 00 { 2e1400-352677 } -> { 1100000-1171277 } [463480] Loading /L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco Loading re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/sigma0 Loading /l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/moe find kernel info page... found kernel info page at 0x400000 Regions of list 'regions' [ 0, fff] { 1000} Arch BIOS [ 1000, 1fff] { 1000} Kern /L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco [ 2000, 2557] { 558} Root mbi_rt [ 9fc00, 9ffff] { 400} Arch BIOS [ f0000, fffff] { 10000} Arch BIOS [ 100000, 10b193] { b194} Sigma0 re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/sigma0 [ 140000, 193363] { 53364} Root /l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/moe [ 2d0400, 2df43f] { f040} Boot bootstrap [ 300000, 38ffff] { 90000} Kern /L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco [ 400000, 475fff] { 76000} Kern /L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco [ 141b000, 3384fff] { 1f6a000} Root Module [ fffe000, fffffff] { 2000} Arch BIOS [ fffc0000, ffffffff] { 40000} Arch BIOS API Version: (87) experimental Sigma0 config ip:0010021c sp:00000000 Roottask config ip:001401f6 sp:00000000 Starting kernel /L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco at 003007b8 Welcome to Fiasco.OC (ia32)! L4/Fiasco.OC ia32 microkernel (C) 1998-2013 TU Dresden Rev: unknown compiled with gcc 4.8.2 for Intel Pentium [] Build: #1 Tue May 26 16:33:03 CST 2015 Performance-critical config option(s) detected: CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off Superpages: yes Kmem:: cpu page at fffd000 (4096Bytes) ACPI-Init ACPI: RSDP[0xf09e0]r00 OEM:BOCHS. ACPI: RSDT[0x203ffbc1]r01 OEM:BOCHS. OEMTID:BXPCRSDT ACPI: FACP[0x203ff1c0]r01 OEM:BOCHS. OEMTID:BXPCFACP ACPI: SSDT[0x203ff234]r01 OEM:BOCHS. OEMTID:BXPCSSDT ACPI: APIC[0x203ffb11]r01 OEM:BOCHS. OEMTID:BXPCAPIC ACPI: HPET[0x203ffb89]r01 OEM:BOCHS. OEMTID:BXPCHPET IO-APIC: MADT = 0x203ffb11 IO-APIC[ 0]: struct: 0x203ffb45 adr=fec00000 IO-APIC[ 0]: pins 24 PIN[ 0m]: vector=20, del=0, dm=physical, dest=0 (high, edge) PIN[ 1m]: vector=21, del=0, dm=physical, dest=0 (high, edge) PIN[ 2m]: vector=22, del=0, dm=physical, dest=0 (high, edge) PIN[ 3m]: vector=23, del=0, dm=physical, dest=0 (high, edge) PIN[ 4m]: vector=24, del=0, dm=physical, dest=0 (high, edge) PIN[ 5m]: vector=25, del=0, dm=physical, dest=0 (high, edge) PIN[ 6m]: vector=26, del=0, dm=physical, dest=0 (high, edge) PIN[ 7m]: vector=27, del=0, dm=physical, dest=0 (high, edge) PIN[ 8m]: vector=28, del=0, dm=physical, dest=0 (high, edge) PIN[ 9m]: vector=29, del=0, dm=physical, dest=0 (high, edge) PIN[10m]: vector=2a, del=0, dm=physical, dest=0 (high, edge) PIN[11m]: vector=2b, del=0, dm=physical, dest=0 (high, edge) PIN[12m]: vector=2c, del=0, dm=physical, dest=0 (high, edge) PIN[13m]: vector=2d, del=0, dm=physical, dest=0 (high, edge) PIN[14m]: vector=2e, del=0, dm=physical, dest=0 (high, edge) PIN[15m]: vector=2f, del=0, dm=physical, dest=0 (high, edge) PIN[16m]: vector=30, del=0, dm=physical, dest=0 (high, edge) PIN[17m]: vector=31, del=0, dm=physical, dest=0 (high, edge) PIN[18m]: vector=32, del=0, dm=physical, dest=0 (high, edge) PIN[19m]: vector=33, del=0, dm=physical, dest=0 (high, edge) PIN[20m]: vector=34, del=0, dm=physical, dest=0 (high, edge) PIN[21m]: vector=35, del=0, dm=physical, dest=0 (high, edge) PIN[22m]: vector=36, del=0, dm=physical, dest=0 (high, edge) PIN[23m]: vector=37, del=0, dm=physical, dest=0 (high, edge) IO-APIC: dual 8259: yes IO-APIC: ovr[ 0] 00 -> 2 0 IO-APIC: ovr[ 1] 05 -> 5 d IO-APIC: ovr[ 2] 09 -> 9 d IO-APIC: ovr[ 3] 0a -> a d IO-APIC: ovr[ 4] 0b -> b d Allocate cpu_mem @ 0xfdbf9400 FPU0: SSE Local APIC[00]: version=11 max_lvt=5 APIC ESR value before/after enabling: 00000000/00000000 Using the Local APIC timer on vector 90 (Periodic Mode) for scheduling ACPI: FACS phys=fffe000 virt=0x203fe000 ACPI: HW sig=0 SERIAL ESC: allocated IRQ 4 for serial uart Absolute KIP Syscalls using: Sysenter Enable MSI support: chained IRQ mgr @ 0xfdbf9150 SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. CPU[0]: GenuineIntel (6:6:3:0)[00000663] Model: QEMU Virtual CPU version 2.0.0 at 2507MHz 32 KB L1 I Cache (8-way associative, 64 bytes per line) 32 KB L1 D Cache (8-way associative, 64 bytes per line) 2048 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) Calibrating timer loop... done. MDB: use page size: 22 MDB: use page size: 12 SIGMA0: Hello! KIP @ 400000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:2000;2fff] [0:3000;9efff] [0:10c000;13ffff] [4:140000;193fff] [0:194000;3fffff] [0:470000;141afff] [4:141b000;3384fff] [0:3385000;eb8afff] IOMEM:---------------------- [0:0;fff] [0:9f000;fffff] [0:fffe000;febfffff] [0:fec01000;fedfffff] [0:fee01000;ffffffff] IO PORTS-------------------------- [0:0;fffffff] MOE: Hello world MOE: found 207796 KByte free memory MOE: found RAM from 2000 to eb8b000 MOE: allocated 235 KByte for the page array @0x3000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [141b000-155472d] [C:503000] l4re BOOTFS: [1555000-17aba0a] [C:504000] ned BOOTFS: [17ac000-17ac56b] [C:505000] l4lx-gfx.cfg BOOTFS: [17ad000-26bda04] [C:506000] io BOOTFS: [26be000-2847199] [C:507000] fb-drv BOOTFS: [2848000-2caa60c] [C:508000] mag BOOTFS: [2cab000-2cab23f] [C:509000] x86-legacy.devs BOOTFS: [2cac000-2cac227] [C:50a000] l4lx-x86.io BOOTFS: [2cad000-308451a] [C:50b000] vmlinuz BOOTFS: [3085000-3385000] [C:50c000] ramdisk-x86.rd MOE: cmdline: /home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg MOE: Starting: rom/ned rom/l4lx-gfx.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx-gfx.cfg' io | Io service io | Find root Pointer io | Find root Pointer: f09e0 io | ACPI: RSDP 0xf09e0 00014 (v00 BOCHS ) io | ACPI: RSDT 0xffffbc1 00034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001) io | ACPI: FACP 0xffff1c0 00074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001) io | ACPI: DSDT 0xfffe040 01180 (v01 BOCHS BXPCDSDT 00000001 BXPC 00000001) io | ACPI: FACS 0xfffe000 00040 io | ACPI: SSDT 0xffff234 008DD (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001) io | ACPI: APIC 0xffffb11 00078 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001) io | ACPI: HPET 0xffffb89 00038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001) io | Parsing all Control Methods: io | Table [DSDT](id 0001) - 144 Objects with 18 Devices 52 Methods 8 Regions io | Parsing all Control Methods: io | Table [SSDT](id 0002) - 155 Objects with 32 Devices 42 Methods 1 Regions io | tbxfload-0274 [02] TbLoadNamespace : ACPI Tables successfully acquired io | evxfevnt-0175 [02] Enable : Transition to ACPI mode successful io | evgpeblk-0523 [04] EvCreateGpeBlock : GPE 00 to 0F [_GPE] 2 regs on int 0x9 io | Completing Region/Field/Buffer/Package initialization:..................................... io | Initialized 9/9 Regions 2/2 Fields 21/21 Buffers 5/5 Packages (308 nodes) io | Initializing Device/Processor/Thermal objects by executing _INI methods: io | Executed 0 _INI methods requiring 1 _STA executions (examined 53 objects) io | ACPICA-Version:20121018, System in ACPI MODE, 32bit timer io | evgpeblk-0615 [03] EvInitializeGpeBlock : Enabled 16 GPEs in this block io | IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=40201) io | IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=40201) io | rom/l4lx-x86.io:17.28-36: warning: could not find 'PNP0100' io | Ready. Waiting for request. mag | Hello from MAG fb-drv | Trying execution of ``set VBE mode'' using x86emu fb-drv | Found VESA BIOS version 3.0 fb-drv | OEM SeaBIOS VBE(C) 2011 fb-drv | VBE mode 0x117 successfully set. fb-drv | Framebuffer memory: phys: fc000000 - fc400000 fb-drv | virt: 400000 - 800000 fb-drv | Starting server loop mag | mapped frame buffer at 0x400000 mag | View::Info: mag | flags: 0 mag | size: 1024x768 pos: 0, 0 mag | bytes_per_line: 2048 mag | buffer_offset: 0 mag | RGBA(2): 5(11):6(5):5(0):0(0) mag | memory 400000-800000 mag | Plugin: Mag_client service started mag | Plugin: Frame-buffer service started mag | L4INPUT native mode activated mag | L4INPUT: !!! W A R N I N G !!! mag | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. mag | L4INPUT: !!! W A R N I N G !!! mag | serio: i8042 AUX port at 0x60,0x64 irq 12 mag | serio: i8042 KBD port at 0x60,0x64 irq 1 mag | input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1 mag | input: AT Translated Set 2 keyboard on isa0060/serio0 mag | connect "ImExPS/2 Generic Explorer Mouse", isa0060/serio1/input0 mag | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 l4linux | PH 0 (t: 1) offs=00001000 vaddr=00400000 vend=006dc000 l4linux | phys=00400000 ephys=006dc000 l4linux | f_sz=002dc000 memsz=002dc000 flgs=r-x l4linux | PH 1 (t: 1) offs=002dd000 vaddr=006dc000 vend=007d8000 l4linux | phys=006dc000 ephys=007d8000 l4linux | f_sz=00050f30 memsz=000fc000 flgs=rw- l4linux | PH 2 (t: 4) offs=0023cd64 vaddr=0063bd64 vend=0063bd88 l4linux | phys=0063bd64 ephys=0063bd88 l4linux | f_sz=00000024 memsz=00000024 flgs=--- l4linux | Starting binary at 0x400000, argc=6 argv=0xafff4f90 *argv=0xb1007ff4 argv0=rom/vmlinuz l4linux | External resolver is at 0xa8000730 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.16.0-l4 (lhj@ubuntu) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #1 Tue May 26 16:58:34 CST 2015 l4linux | Binary name: rom/vmlinuz l4linux | Linux kernel command line (5 args): mem=64M console=tty0 l4x_rd=rom/ramdisk-x86.rd root=1:0 ramdisk_size=4000 l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 00400000 - 007d8000 [3936 KiB]. l4linux | Areas: Text: 00400000 - 006dc000 [2928kB] (a bit longer) l4linux | Data: 006dc000 - 00706ac0 [170kB] l4linux | Initdata: 00709000 - 0072d000 [144kB] l4linux | BSS: 0072e000 - 007c2000 [592kB] l4linux | gs=43 fs=43 l4linux | Device scan: l4linux | Device: L4ICU l4linux | Device: PCI0 l4linux | Device: pci_l4x[0000] l4linux | PORT: 0000c040 - 0000c04f l4linux | PORT: 000001f0 - 000001f7 l4linux | PORT: 000003f6 - 000003f6 l4linux | IRQ: 0000000e - 0000000e l4linux | PORT: 00000170 - 00000177 l4linux | PORT: 00000376 - 00000376 l4linux | IRQ: 0000000f - 0000000f l4linux | Device: pci_l4x[0001] l4linux | IRQ: 0000000b - 0000000b l4linux | MEM: febc0000 - febdffff l4linux | PORT: 0000c000 - 0000c03f l4linux | Device scan done. l4linux | l4x_fiasco_gdt_entry_offset = 9 l4linux | rtc not found l4linux | WARNING: RTC server does not seem to be there! l4linux | l4lx_thread_create: Created thread 417 (cpu0) (u:b3000e00, v:b3000c00, sp:006ddfac) l4linux | main thread will be 417 l4linux | l4x_register_pointer_section: addr = 006dc000 size = 1032192 l4linux | section-with-init: Virt: 0x6dc000 to 0x7d7fff [1008 KiB] l4linux | section-with-init: Phys: 0x0090f000 to 0x00a0afff, [1008 KiB] l4linux | Main thread running, waiting... l4linux | WARNING: Unknown wrmsr: 0000008b at 0x411f0d l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 00400000 l4linux | Main memory: Virt: 0x800000 to 0x47fffff [65536 KiB] l4linux | Main memory: Phys: 0x03400000 to 0x073fffff, [65536 KiB] l4linux | l4x: vmalloc area: 04800000 - 0c800000 l4linux | Filling lower ptabs... l4linux | Done (1062 entries). l4linux | l4x_register_pointer_section: addr = 00400000 size = 2998272 l4linux | text: Virt: 0x400000 to 0x6dbfff [2928 KiB] l4linux | text: Phys: 0x00614000 to 0x008effff, [2928 KiB] l4linux | Loading: rom/ramdisk-x86.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 0c91b000 to 0cc1b000 [3072KiB] l4linux | rtc not found l4linux | l4lx_thread_create: Created thread 41f (timer0) (u:b3000a00, v:00000000, sp:0075bfa8) l4linux | WARNING: Unknown wrmsr: 0000008b at 0x411f0d l4linux | WARNING: Unknown rdmsr: 00000186 at 0x710579 l4linux | WARNING: Unknown rdmsr: 00000187 at 0x710579 l4linux | WARNING: Unknown wrmsr: 000000c1 at 0x71064a mag | Input: new pointer device (src='<Input_source userdata: 1D80C>' stream='userdata: 0x3abb4') mag | bus='i8042' vendor=0x2 product=0x6 version=0 mag | Input: new keyboard device (src='<Input_source userdata: 1D80C>' stream='userdata: 0x3b358') mag | bus='i8042' vendor=0x1 product=0x1 version=43841 And I printed my screen. See attached png-file. Thanks for any reply!

2 1

Running L4Linux + Fiasco on Freescale i.MX 6 Sabre SD
by Mahdi Aichouch 28 May '15

28 May '15

Hello, I tried to run L4Linux + Fiasco on a Freescale i.mx 6 Sabre SD board. The L4Linux is started but it stops at loading the ramdisk, as shown in the debug messages below. Does someone has an idea of what might be wrong. Thank you very much in advance. Best regards, Mahdi L4 Bootstrapper Build: #80 Wed May 27 18:22:31 CEST 2015, 4.8.3 20140320 (prerelease) Scanning up to 256 MB RAM, starting at offset 32MB Memory size is 256MB (10000000 - 1fffffff) RAM: 0000000010000000 - 000000001fffffff: 262144kB Total RAM: 256MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 10 modules behind 11100000 moving module 02 { 118aa000-118e363f } -> { 1199a000-119d363f } [235072] moving module 01 { 118a0000-118a938b } -> { 11990000-1199938b } [37772] moving module 00 { 11848000-1189fb17 } -> { 11938000-1198fb17 } [359192] moving module 09 { 11548000-11847fff } -> { 11638000-11937fff } [3145728] moving module 08 { 111d6000-11547497 } -> { 112c6000-11637497 } [3609752] moving module 07 { 111d5000-111d50bc } -> { 112c5000-112c50bc } [189] moving module 06 { 1107e000-111d446f } -> { 1116e000-112c446f } [1401968] moving module 05 { 1107d000-1107d17b } -> { 1116d000-1116d17b } [380] moving module 04 { 1102a000-1107cc1f } -> { 1111a000-1116cc1f } [338976] moving module 03 { 11010000-11029473 } -> { 11100000-11119473 } [103540] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x10002000 Regions of list 'regions' [ 10000000, 1000015f] { 160} Root mbi_rt [ 10001000, 10001aff] { b00} Kern fiasco [ 10002000, 10066fff] { 65000} Kern fiasco [ 10090000, 10096edf] { 6ee0} Sigma0 sigma0 [ 10098000, 1009e177] { 6178} Sigma0 sigma0 [ 10140000, 10171d77] { 31d78} Root moe [ 10178000, 101934ab] { 1b4ac} Root moe [ 11000000, 1100f58f] { f590} Boot bootstrap [ 11100000, 11937fff] { 838000} Root Module API Version: (87) experimental Sigma0 config ip:10090100 sp:00000000 Roottask config ip:10140260 sp:00000000 Starting kernel fiasco at 100012c8 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 L2: ID=410000c7 Type=9e340340 Aux=02070000 WMask=ffff S=0 L2: Type L2C-310 Size = 1024kB Ways=16 Waysize=64 GIC: Switching IRQ 58 to secure SERIAL ESC: allocated IRQ 58 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: rexported compiled with gcc 4.8.3 for i.MX6 [] Build: #14 Wed Apr 29 13:37:03 CEST 2015 GIC: Switching IRQ 29 to secure Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 10002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:10000000;10000fff] [0:10067000;1008ffff] [0:10097000;10097fff] [0:1009f000;1013ffff] [4:10140000;10171fff] [0:10172000;10177fff] [4:10178000;10193fff] [0:10194000;110fffff] [4:11100000;11937fff] [0:11938000;1effffff] IOMEM:---------------------- [0:0;fffffff] [0:20000000;ffffffff] MOE: Hello world MOE: found 236564 KByte free memory MOE: found RAM from 10000000 to 1f000000 MOE: allocated 240 KByte for the page array @0x1009f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [11100000-11119474] [C:503000] l4re BOOTFS: [1111a000-1116cc20] [C:504000] ned BOOTFS: [1116d000-1116d17c] [C:505000] l4lx.cfg BOOTFS: [1116e000-112c4470] [C:506000] io BOOTFS: [112c5000-112c50bd] [C:507000] arm-rv.io BOOTFS: [112c6000-11637498] [C:508000] vmlinuz.arm BOOTFS: [11638000-11938000] [C:509000] ramdisk-arm.rd MOE: cmdline: moe rom/l4lx.cfg MOE: Starting: rom/ned rom/l4lx.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx.cfg' l4linux | libio: Warning: Query of 'vbus' failed! l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=023defa8 l4linux | phys=02000000 ephys=023defa8 l4linux | f_sz=00359394 memsz=003defa8 flgs=rwx l4linux | PH 1 (t: 4) offs=0031afe0 vaddr=02312fe0 vend=02313004 l4linux | phys=02312fe0 ephys=02313004 l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x20002b0, argc=6 argv=0xafff4f8c *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa8000788 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.16.0-l4 (aichouch@aichouch-ThinkCentre-M90) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #1 Wed May 27 18:04:14 CEST 2015 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (5 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 02000000 - 02400000 [4096 KiB]. l4linux | Areas: Text: 02000000 - 02332000 [3272kB] (a bit longer) l4linux | Data: 02332000 - 023543a0 [136kB] l4linux | Initdata: 02314000 - 02331024 [116kB] l4linux | BSS: 02359394 - 023defa8 [535kB] l4linux | Device scan: l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:02333fa4) l4linux | main thread will be 413 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4059136 l4linux | section-with-init: Virt: 0x2000000 to 0x23defa7 [3963 KiB] l4linux | section-with-init: Phys: 0x1025a000 to 0x10638fa7, [3963 KiB] l4linux | Main thread running, waiting... l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 02000000 l4linux | Main memory: Virt: 0x2400000 to 0x63fffff [65536 KiB] l4linux | Main memory: Phys: 0x11a00000 to 0x159fffff, [65536 KiB] l4linux | l4x: vmalloc area: 06400000 - 0e400000 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4059136 l4linux | text: Virt: 0x2000000 to 0x23defa7 [3963 KiB] l4linux | text: Phys: 0x1025a000 to 0x10638fa7, [3963 KiB] l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] l4linux | 'swp(b)' instruction at 0224f728 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? ...

2 1

Utcb in syscall
by watermirror 27 May '15

27 May '15

hi ,in sys_ipc_wrapper, the code first get the current thread's syscall entry frame: .... Thread *curr=current_thread(); Syscall_frame *f = curr-regs(); ... according to the Syscall_frame's implemention, it can get the Utcb by Syscall_frame::utcb(). but the following code get the Utcb in another way: Utcb *utcb = curr->utcb().access(true); what's the difference between those two Utcb?

4 4

Re: Booting error in L4android for Exynos 5250.
by Youren Shen 27 May '15

27 May '15

> > > > I'm trying to booting L4Android in Exynos 5250 platform. I got some > > > questions. If anyone can give me any direction or document, It will be > > very > > > helpful. > > > > > > 1, How to edit this vbus and devs file to match my platform? > > > For example, if I want replace the MOUSE in vbus with TOUCHSCREEN, what > > > should I write to determine the driver of the touchscreen, and the > > register > > > address of the driver? > > > It seems the .hid can assign the driver? And the MMio can remap the > > address > > > of the IO for driver? > > > > A vbus defines the resources (IRQs and MMIO) for a whole client, i.e. > > it's not per driver but per client (e.g. L4Linux). For the touchscreen > > you need to give the MMIO regions and IRQs that the touchscreen driver > > is using. > > > > > 2, As for GUI driver, what the mag and fb-drv do ? Should I write one > > > > The fb-drv is the framebuffer driver, i.e. the driver that maps some > > memory in such a way to the framebuffer hardware that something appears > > on the screen. mag is a small window manager that makes multiple > > windows, that you can drag around, out of the single hardware > > framebuffer. > > > > > driver in L4RE or I can reuse the driver in Linux? > > > > Reusing the driver from L4Linux is possible but typically framebuffer > > drivers are reasonable small to be implemented standalone. > > For the driver reuse: I read the User Guide of rearview platform, it seems that the MMIO should set as the register Address in memory map. And the IRQs should be the interrupt number + 32. I know how to write LCD driver and framebuffer in native Linux System. But for L4Linux, I still have some question. I am not sure how to reuse the driver of Linux or rewrite the fb-drv. Here is the situation: The folder in arch/arm/mach-exynos has plenty code to initial the platform, so I added config L4_PLATFORM_EXYNOS in arch/l4/Kconfig and PLATFORMNAME-$(CONFIG_L4_PLATFORM_EXYNOS) = exynos in arch/l4/Makefile. However, when build the kernel, there is some error. It seems like the L4Linux startup invoke some variables defined in Realview or Generic platform like NR_IRQS_HW. Is this rectifiable? I found that there is l4fb.c as driver in driver/video, what's different with the module in l4/pkg? And last question, how to run the driver I want to use? Thank you very much! -- Best Regards. Youren Shen.

2 1

Re: Booting error in L4android for Exynos 5250.
by Youren Shen 27 May '15

27 May '15

Thank you very much for your reply. > > On Wed May 13, 2015 at 22:23:18 +0800, Youren Shen wrote: > > I'm trying to booting L4Android in Exynos 5250 platform. I got some > > questions. If anyone can give me any direction or document, It will be > very > > helpful. > > > > 1, How to edit this vbus and devs file to match my platform? > > For example, if I want replace the MOUSE in vbus with TOUCHSCREEN, what > > should I write to determine the driver of the touchscreen, and the > register > > address of the driver? > > It seems the .hid can assign the driver? And the MMio can remap the > address > > of the IO for driver? > > A vbus defines the resources (IRQs and MMIO) for a whole client, i.e. > it's not per driver but per client (e.g. L4Linux). For the touchscreen > you need to give the MMIO regions and IRQs that the touchscreen driver > is using. > > > 2, As for GUI driver, what the mag and fb-drv do ? Should I write one > > The fb-drv is the framebuffer driver, i.e. the driver that maps some > memory in such a way to the framebuffer hardware that something appears > on the screen. mag is a small window manager that makes multiple > windows, that you can drag around, out of the single hardware > framebuffer. > > > driver in L4RE or I can reuse the driver in Linux? > > Reusing the driver from L4Linux is possible but typically framebuffer > drivers are reasonable small to be implemented standalone. > > > *For this two question I just need some guide*, I can't find details > > explanation of the file or tutorial in Wiki page. > > > > Thank you very much! > > > > Also I got some new error when booting. The system mount failed. Would > you > > mind to take a look? > > > > RAMDISK: Loading 1024KiB [1 disk] into ram disk... done. > > > > EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities > > > > EXT4-fs (ram0): mounting ext2 file system using the ext4 subsystem > > > > EXT4-fs warning (device ram0): ext4_update_dynamic_rev:701: updating to > rev > > 1 bd > > EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) > > > > VFS: Mounted root (ext2 filesystem) on device 1:0. > > > > Freeing unused kernel memory: 164K (02356000 - 0237f000) > > > > init: cannot open '/initlogo.rle' > > > > EXT4-fs (ram0): re-mounted. Opts: (null) > > > > init: Unable to open persistent property directory /data/property errno: > 2 > > > > init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj > > inste. > > init: cannot find '/system/bin/servicemanager', disabling > 'servicemanager' > > init: cannot find '/system/bin/vold', disabling 'vold' > > Looks like the system partition could not be mounted. Where should it > be? > > I'm using the image and config files that L4Android.org supplied. I copied the two image file(root-arm-ginger.img and system-arm-ginger.img) to l4/build/bin/$arch/l4f So here is the module list: *entry l4android-arm* *roottask moe rom/l4_gingerbread-arm.cfg* *kernel fiasco -serial_esc* *module l4re* *module ned* *module io* *module mag* *module fb-drv* *module l4_gingerbread-arm.cfg* *module arm-rv-eb.devs* *module l4_android-arm.vbus* *module vmlinuz.android* *module root-arm-ginger.img* *module system-arm-ginger.img* And here is the parameter of loader:start in ned script. *"rom/" .. lxname .. " console=ttyLv0 androidboot.console=ttyLv0 mem=256M l4bdds.add=rom/system-arm-ginger.img,rw boot=local android.ril=ttyLv1 ip=dhcp l4x_rd=rom/root-arm-ginger.img rw root=1:0 ramdisk_size=1500 init=/init --debug l4fb.touchscreen=1* In the root-arm-ginger.img file, the init script should mount the /system: *mount cramfs /l4bdds0 /system **mount cramfs /l4bdds0 /system ro remount **mount tmpfs tmpfs /data size=32M* But it failed. I check the CRAMFS and it's enable in Linux kernel. Then I have no idea about what can cause this /system mount error. Thank you very much for your help! -- Best Regards. Youren Shen.

2 1

Kobject_h::invoke
by watermirror 27 May '15

27 May '15

hi, in what situation, the fiasco will call method Kobject_h::invoke?

2 1

Re: l4-hackers Digest, Vol 145, Issue 7
by Reinier Millo Sánchez 26 May '15

26 May '15

Hi Adam On 05/11/2015 06:00 AM, l4-hackers-request(a)os.inf.tu-dresden.de wrote: > On Tue May 05, 2015 at 01:28:46 -0400, Reinier Millo S?nchez wrote: >> > >> >Hi Adam >>>>> > >>> FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, >>>>> > >>> p: dbl/sngl >>>>> > >>> >>>>> > >>> KERNEL: Warning: No page-fault handler for 0xee202214, error >>>>> > >>> 0x94000848, pc f0039420 >>>>> > >>> >>>>> > >>>Somebody have tested Fiasco.OC+L4re on ODROID-X2 or another Exynos 4412 >>>>> > >>>platform? >>> > >On this platform this seems to be some pattern. However, last time I >>> > >tried it worked for me. So, hmm, could you try another compiler version >>> > >and see if it changes behavior? Maybe this gives us some hints. >> >I'm using a linaro toolchain >> >(gcc-linaro-arm-linux-gnueabihf-4.8-2014.03_x86_64). I have tried the >> >arm-none-eabi toolchain in Debian repository but fails compiling the >> >snapshot. >> >I have made some progress trying to run FiascoOC+L4re on Odroid-X2. There >> >are some changes that I have made: >> >I have modified the file "l4/mk/platforms/exynos4.conf" adapting Exynos4's >> >platform to Odroid-X2. In this case the RAM size differs (Odroid-X2 have >> >2Gb). In this file I have configured the UART for serial output (I'm using >> >UART 1). >> > >> > PLATFORM_RAM_BASE = 0x40000000 >> > - PLATFORM_RAM_SIZE_MB = 1024 >> > + PLATFORM_RAM_SIZE_MB = 2047 >> > + PLATFORM_UART_NR = 1 >> > >> >Booting the generated image I have detected that bootstrap's server is not >> >using UART 1 for output. I have modified the "init" function on >> >"l4/pkg/bootstrap/server/src/platform/exynos.cc" to use the configured UART >> >on the platform file modified above. >> > >> > unsigned long uart_base; >> > - unsigned uart_nr = 2; >> > + unsigned uart_nr = PLATFORM_UART_NR; >> > >> >I have tried to compile and test the image on the Odroid-X2, but fails the >> >execution, this is the serial output: >> > >> > L4 Bootstrapper >> > Build: #18 Sat May 2 15:56:00 CDT 2015, 4.8.3 20140303 (prerelease) >> > Scanning up to 2047 MB RAM, starting at offset 32MB >> > Memory size is 2047MB (40000000 - bfefffff) >> > Limiting 'RAM' region [ 40000000, bfefffff] { 7ff00000} to [ >> > 40000000, bcffffff] { 7d000000} due to 3024 MB address limit >> > RAM: 0000000040000000 - 00000000bcffffff: 2048000kB >> > Total RAM: 2000MB >> > Scanning fiasco >> > Scanning sigma0 >> > Scanning moe >> > Moving up to 5 modules behind 41100000 >> > moving module 02 { 410b4000-410e565f } -> { 411a5000-411d665f } >> > [202336] >> > moving module 01 { 410aa000-410b3377 } -> { 4119b000-411a4377 } >> > [37752] >> > moving module 00 { 41043000-410a9daf } -> { 41134000-4119adaf } >> > [421296] >> > moving module 04 { 41029000-410425b3 } -> { 4111a000-411335b3 } >> > [103860] >> > moving module 03 { 4100f000-41028493 } -> { 41100000-41119493 } >> > [103572] >> > Loading fiasco >> > Loading sigma0 >> > Loading moe >> > find kernel info page... >> > found kernel info page at 0x40002000 >> > Regions of list 'regions' >> > [ 40000000, 400000e3] { e4} Root mbi_rt >> > [ 40001000, 40001aff] { b00} Kern fiasco >> > [ 40002000, 40076fff] { 75000} Kern fiasco >> > [ 40090000, 4009681b] { 681c} Sigma0 sigma0 >> > [ 40098000, 4009e177] { 6178} Sigma0 sigma0 >> > [ 40140000, 4018b4ab] { 4b4ac} Root moe >> > [ 41000000, 4100e4ff] { e500} Boot bootstrap >> > [ 41100000, 41133fff] { 34000} Root Module >> > API Version: (87) experimental >> > Sigma0 config ip:40090100 sp:00000000 >> > Roottask config ip:4014020c sp:00000000 >> > Starting kernel fiasco at 400012c8 >> > Hello from Startup::stage2 >> > Per_cpu_data_alloc: (orig: 0xf0063a50-0xf00644d0) >> > 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 >> > >> > KERNEL: Warning: No page-fault handler for 0xee202214, error >> > 0x94000848, pc f0039420 >> > >> >I have been testing and changing the compiling configuration. Using the >> >below configuration to compile Fiasco.OC, the system boots and hangs at >> >"Calibrating timer loop...": >> > >> > Platform Timer -> Multi-core timer >> > Use ExtGic -> True >> > Execution Model -> TrustZone normal side >> > Secure Monitor Interface -> Mobicore >> > Enable multi processor support -> True >> > Maximal supported number of CPUs -> 4 > Interesting. What's the difference to the previos config? In the first configuration i was using: Platform Timer -> Multi-core timer Use ExtGic -> True Execution Model -> Standard mode Enable multi processor support -> False >> >This is the serial output when tested the image on Odroid-X2: >> > Calibrating timer loop... >> > >> >I think that the problem now is with the Exynos4's Timers, but i have been >> >reviewing the implementations and it seems fine. >> >Is there anything wrong on my configuration or somebody have any idea? > Does the counter of the timer count, i.e. multiple reads return > different values? We have checked and the system clock at Kip (Kip::k()->clock) is updating on every tick in the function "Timer::update_system_clock", but multiple reads of the clock in the function "Delay::measure" returns the same value. We have made another small changes to test the snapshot on the Odroid-X2 board. We have compiled Fiasco.OC using this configuration: Execution Model ->TrustZone Normal side Secure Monitor Interface ->none Enable multi processor support ->Disable We have commented the "Delay:init();" line in the Kernel_thread::bootstrap() in the "src/kernel/fiasco/src/kern/kernel_thread.cpp" file. When test the compiled image on the board, we have the following output with one "Hello World" and then stops in the sleep. We remain thinking that the problem is in the timers implementation. U-Boot 2010.12-svn (Dec 21 2012 - 19:44:04) for Exynox4412 CPU: S5PC220 [Samsung SOC on SMP Platform Base on ARM CortexA9] APLL = 1000MHz, MPLL = 880MHz DRAM: 2047 MiB PMIC VERSION : 0x00, CHIP REV : 2 TrustZone Enabled BSP BL1 version: 20121128 Checking Boot Mode ... SDMMC MMC Device 0: 7695 MB MMC Device 1 not found ModeKey Check... run normal_boot Net: No ethernet found. Partition1: Start Address(0xc00), Size(0x40400) reading hello.raw 741376 bytes read Boot with zImage Starting kernel ... L4 Bootstrapper Build: #32 Fri May 8 15:32:04 EDT 2015, 4.8.3 20140303 (prerelease) Scanning up to 1023 MB RAM, starting at offset 32MB Memory size is 1023MB (40000000 - 7fefffff) RAM: 0000000040000000 - 000000007fefffff: 1047552kB Total RAM: 1023MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 5 modules behind 41100000 moving module 02 { 41083000-410b465f } -> { 41174000-411a565f } [202336] moving module 01 { 41079000-41082377 } -> { 4116a000-41173377 } [37752] moving module 00 { 41043000-410782bb } -> { 41134000-411692bb } [217788] moving module 04 { 41029000-410425b3 } -> { 4111a000-411335b3 } [103860] moving module 03 { 4100f000-41028493 } -> { 41100000-41119493 } [103572] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x40002000 Regions of list 'regions' [ 40000000, 400000e3] { e4} Root mbi_rt [ 40001000, 40001aff] { b00} Kern fiasco [ 40002000, 4003efff] { 3d000} Kern fiasco [ 40090000, 4009681b] { 681c} Sigma0 sigma0 [ 40098000, 4009e177] { 6178} Sigma0 sigma0 [ 40140000, 4016ef97] { 2ef98} Root moe [ 40170000, 4018b4ab] { 1b4ac} Root moe [ 41000000, 4100e4ff] { e500} Boot bootstrap [ 41100000, 41133fff] { 34000} Root Module API Version: (87) experimental Sigma0 config ip:40090100 sp:00000000 Roottask config ip:4014020c sp:00000000 Starting kernel fiasco at 400012c8 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 85 for serial uart Not using serial hack in slow timer handler. \0x1b[1;32mWelcome to Fiasco.OC (arm)! \0x1b[0;32mL4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: unknown compiled with gcc 4.8.3 for Samsung Exynos [] Build: #109 Fri May 8 15:25:47 EDT 2015 \0x1b[0m Timer for CPU0 is at IRQ 28 Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 40002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:40000000;40000fff] [0:4003f000;4008ffff] [0:40097000;40097fff] [0:4009f000;4013ffff] [4:40140000;4016efff] [0:4016f000;4016ffff] [4:40170000;4018bfff] [0:4018c000;410fffff] [4:41100000;41133fff] [0:41134000;7eefffff] IOMEM:---------------------- [0:0;3fffffff] [0:7ff00000;ffffffff] MOE: Hello world MOE: found 1030352 KByte free memory MOE: found RAM from 40000000 to 7ef00000 MOE: allocated 1007 KByte for the page array @0x4018c000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [41100000-41119494] [C:503000] l4re BOOTFS: [4111a000-411335b4] [C:504000] hello MOE: cmdline: moe --init=rom/hello MOE: Starting: rom/hello MOE: loading 'rom/hello' Hello World! Somebody have any suggestion? Best regards -- Lic. Reinier Millo Sánchez Centro de Estudios de Informática Universidad Central "Marta Abreu" de Las Villas Carretera a Camajuaní Km 5 1/2 Santa Clara, Villa Clara, Cuba CP 54830 "antes de discutir ... respira; antes de hablar ... escucha; antes de escribir ... piensa; antes de herir ... siente; antes de rendirte ... intenta; antes de morir ... vive"

2 3

Does Fiasco support floating point?
by Yuxin Ren 19 May '15

19 May '15

Hi All, Does Fiasco support floating point processing? If it supports, where is code to initialize and save/store floating point registers? Thanks a lot. Yuxin

3 2

Fiasco.OC-UX and recent Linux kernels
by Paul Boddie 18 May '15

18 May '15

Hello, I have been experimenting a little with L4/Fiasco.OC and have been trying to gradually build up my skills by looking at Fiasco.OC-UX. However, there are a few things that aren't really very clear to me from looking at the documentation. Looking at the L4Re and Fiasco documentation, it appears that I first build L4Re normally... http://l4re.org/build.html ...and then I need to build Fiasco.OC... http://os.inf.tu-dresden.de/fiasco/build.html ...but indicating the "Linux Usermode Platform" in the "Platform" section of the "Target configuration" when doing "make config". The documentation mentions doing "make ux E=hello", but I found that a MODULE_SEARCH_PATH was required. Otherwise, the Makefile directs a script to look in directories of the L4Re build hierarchy that don't exist... http://os.inf.tu-dresden.de/fiasco/ux-using.html Having got this far, running "make ux" with the necessary options gave me the following error: openpty: No such file or directory Problems setting up timer interrupt! Aborted I did start to wonder whether there might be permission issues, whether the UX mode is no longer supported, or whether it isn't supported on Linux 3.x kernels. (I use User Mode Linux a lot and never have to do so as a privileged user, by the way.) The documentation seems to indicate that a 2.6 kernel is required... http://os.inf.tu-dresden.de/fiasco/ux-status.html ...which probably few people run on a desktop or laptop any more, but for the record I am using the 32-bit x86 architecture and not amd64/x86-64, and my distribution is Debian Wheezy. Am I trying something which I shouldn't expect to work? A perusal of the mailing list archives didn't really provide any obvious answers. Thanks for any help in advance, Paul

2 2

Booting error in L4android for Exynos 5250.
by Youren Shen 18 May '15

18 May '15

Hi, L4Hackers: I'm trying to booting L4Android in Exynos 5250 platform. I got some questions. If anyone can give me any direction or document, It will be very helpful. 1, How to edit this vbus and devs file to match my platform? For example, if I want replace the MOUSE in vbus with TOUCHSCREEN, what should I write to determine the driver of the touchscreen, and the register address of the driver? It seems the .hid can assign the driver? And the MMio can remap the address of the IO for driver? 2, As for GUI driver, what the mag and fb-drv do ? Should I write one driver in L4RE or I can reuse the driver in Linux? *For this two question I just need some guide*, I can't find details explanation of the file or tutorial in Wiki page. Thank you very much! Also I got some new error when booting. The system mount failed. Would you mind to take a look? ## Starting application at 0x41000000 ... L4 Bootstrapper Build: #4 Tue May 5 18:39:47 CST 2015, 4.6.4 Scanning up to 2047 MB RAM, starting at offset 256MB Memory size is 2047MB (40000000 - bfefffff) Limiting 'RAM' region [ 40000000, bfefffff] { 7ff00000} to [ 40000000, t RAM: 0000000040000000 - 00000000bcffffff: 2048000kB Total RAM: 2000MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 14 modules behind 41100000 moving module 02 { 4fbec000-4fc255ef } -> { 4fcdb000-4fd145ef } [234992] moving module 01 { 4fbe2000-4fbeb33b } -> { 4fcd1000-4fcda33b } [37692] moving module 00 { 4fb7e000-4fbe127f } -> { 4fc6d000-4fcd027f } [406144] moving module 13 { 41794000-4fb7df5b } -> { 41883000-4fc6cf5b } [238985052] moving module 12 { 41694000-41793fff } -> { 41783000-41882fff } [1048576] moving module 11 { 412ca000-41693487 } -> { 413b9000-41782487 } [3970184] moving module 10 { 412c9000-412c9109 } -> { 413b8000-413b8109 } [266] moving module 09 { 412c8000-412c84c0 } -> { 413b7000-413b74c0 } [1217] moving module 08 { 412c7000-412c765e } -> { 413b6000-413b665e } [1631] moving module 07 { 4129d000-412c65ef } -> { 4138c000-413b55ef } [169456] moving module 06 { 411ed000-4129cc0f } -> { 412dc000-4138bc0f } [719888] moving module 05 { 41086000-411ec44f } -> { 41175000-412db44f } [1467472] moving module 04 { 4102b000-41085bcf } -> { 4111a000-41174bcf } [371664] moving module 03 { 41011000-4102a427 } -> { 41100000-41119427 } [103464] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x40002000 Regions of list 'regions' [ 40000000, 40000203] { 204} Root mbi_rt [ 40001000, 40001c3f] { c40} Kern fiasco [ 40002000, 40072fff] { 71000} Kern fiasco [ 40090000, 40096f0b] { 6f0c} Sigma0 sigma0 [ 40098000, 4009e177] { 6178} Sigma0 sigma0 [ 40140000, 40174a53] { 34a54} Root moe [ 40178000, 4018ef03] { 16f04} Root moe [ 41000000, 410105f7] { 105f8} Boot bootstrap [ 41100000, 4fc6cfff] { eb6d000} Root Module API Version: (87) experimental Sigma0 config ip:40090100 sp:00000000 Roottask config ip:40140198 sp:00000000 Starting kernel fiasco at 40001360 Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf005ff90-0xf0060990) Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv4(4), Part: VFPv3(30), r: 0, v: f, i: 41, t: hard, p: dbl/sngl Watchdog initialized SERIAL ESC: allocated IRQ 85 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: unknown compiled with gcc 4.6.4 for Samsung Exynos [] Build: #1 Tue May 5 16:52:03 CST 2015 Per_cpu_data_alloc: (orig: 0xf005ff90-0xf0060990) Allocate 2560 bytes (3KB) for CPU[4] local storage (offset=118b070, 0xf11eb000-) Timer for CPU0 is at IRQ 152 Number of CPUs: 1 Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 40002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:40000000;40000fff] [0:40073000;4008ffff] [0:40097000;40097fff] [0:4009f000;4013ffff] [4:40140000;40174fff] [0:40175000;40177fff] [4:40178000;4018efff] [0:4018f000;410fffff] [4:41100000;4fc6cfff] [0:4fc6d000;bbffffff] IOMEM:---------------------- [0:0;3fffffff] [0:bd000000;ffffffff] MOE: Hello world MOE: found 1789720 KByte free memory MOE: found RAM from 40000000 to bc000000 MOE: allocated 1984 KByte for the page array @0x4018f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [41100000-41119428] [C:503000] l4re BOOTFS: [4111a000-41174bd0] [C:504000] ned BOOTFS: [41175000-412db450] [C:505000] io BOOTFS: [412dc000-4138bc10] [C:506000] mag BOOTFS: [4138c000-413b55f0] [C:507000] fb-drv BOOTFS: [413b6000-413b665f] [C:508000] l4_gingerbread-arm.cfg BOOTFS: [413b7000-413b74c1] [C:509000] arm-rv-eb.devs BOOTFS: [413b8000-413b810a] [C:50a000] l4_android-arm.vbus BOOTFS: [413b9000-41782488] [C:50b000] vmlinuz.android BOOTFS: [41783000-41883000] [C:50c000] root-arm-ginger.img BOOTFS: [41883000-4fc6cf5c] [C:50d000] system-arm-ginger.img MOE: cmdline: moe rom/l4_gingerbread-arm.cfg MOE: Starting: rom/ned rom/l4_gingerbread-arm.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4_gingerbread-arm.cfg' io | Io service io | Ready. Waiting for request. mag | Hello from MAG fb | Using LCD driver: ARM AMBA PrimeCell 11x fb | Unknown LCD: periphid = 00000000, cellid = 00000000 fb | Video memory is at virtual 0x5000 (size: 0x96000 Bytes) fb | Physical video memory is at 0x40654000 fb | Color mode: 10:5:0 5:5:5 fb | Detected a 'Unknown' device. fb | Configure 3.8 CLCD fb | Starting server loop mag | mapped frame buffer at 0x200000 mag | View::Info: mag | flags: 0 mag | size: 640x480 pos: 0, 0 mag | bytes_per_line: 1280 mag | buffer_offset: 0 mag | RGBA(2): 5(10):5(5):5(0):0(0) mag | memory 200000-296000 mag | Plugin: Mag_client service started mag | Plugin: Frame-buffer service started mag | L4INPUT native mode activated mag | L4INPUT: !!! W A R N I N G !!! mag | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. mag | L4INPUT: !!! W A R N I N G !!! android | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=0246e454 android | phys=02000000 ephys=0246e454 android | f_sz=003ab5bc memsz=0046e454 flgs=rwx android | PH 1 (t: 4) offs=0035ddb8 vaddr=02355db8 vend=02355ddc android | phys=02355db8 ephys=02355ddc android | f_sz=00000024 memsz=00000024 flgs=r-x android | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 android | phys=00000000 ephys=00000000 android | f_sz=00000000 memsz=00000000 flgs=rwx android | Starting binary at 0x2000358, argc=15 argv=0xafff4f6c *argv=0xb1007fed android | External resolver is at 0xa800070c android | ======> L4Linux starting... <======== android | Linux version 3.16.0-l4 (shenyouren@Dell-Shen) (gcc version 4.6.x-goo5 android | Binary name: rom/vmlinuz.android android | This is an AEABI build. android | Linux kernel command line (14 args): console=ttyLv0 androidboot.conso1 android | CPU mapping (l:p)[1]: 0:0 android | Image: 020000a0 - 02600000 [6143 KiB]. android | Areas: Text: 020000a0 - 02380000 [3583kB] (a bit longer) android | Data: 02380000 - 023a6fa0 [155kB] android | Initdata: 02356000 - 0237f900 [166kB] android | BSS: 023ab5bc - 0246e454 [779kB] android | Device scan: android | Device: L4ICU android | Device scan done. android | l4lx_thread_create: Created thread 416 (cpu0) (u:b3000e00, v:b3000c00) android | main thread will be 416 android | l4x_register_pointer_section: addr = 02000000 size = 4648960 android | section-with-init: Virt: 0x2000000 to 0x246e453 [4537 KiB] android | section-with-init: Phys: 0x407fa000 to 0x40c68453, [4537 KiB] android | Main thread running, waiting... android | L4x: Memory size: 256MB android | L4x: Setting superpages for main memory android | L4x: Adjusted memory start: 02000000 android | Main memory: Virt: 0x2600000 to 0x125fffff [262144 KiB] android | Main memory: Phys: 0x4fe00000 to 0x5fdfffff, [262144 KiB] android | l4x: vmalloc area: 12600000 - 1a600000 android | l4x_register_pointer_section: addr = 02000000 size = 4648960 android | text: Virt: 0x2000000 to 0x246e453 [4537 KiB] android | text: Phys: 0x407fa000 to 0x40c68453, [4537 KiB] android | Loading: rom/root-arm-ginger.img android | INITRD: Size of RAMdisk is 1024KiB android | RAMdisk from 00002000 to 00102000 [1024KiB] android | l4lx_thread_create: Created thread 41c (timer0) (u:b3000a00, v:000000) Booting Linux on physical CPU 0x0 Linux version 3.16.0-l4 (shenyouren@Dell-Shen) (gcc version 4.6.x-google 2012015 CPU: Fiasco [410fc0f4] revision 4 (ARMv7), cr=00000000 CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache Machine: L4 Ignoring unrecognised tag 0x00000000 Forcing write-allocate cache policy for SMP Forcing shared mappings for SMP Memory policy: Data cache writealloc INITRD: 00002000 - 00102000 PERCPU: Embedded 7 pages/cpu @123a0000 s6400 r8192 d14080 u32768 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 66484 Kernel command line: console=ttyLv0 androidboot.console=ttyLv0 mem=256M l4bdds.) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 259556K/268288K available (2687K kernel code, 155K rwdata, 728K rodata,) Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xffe00000 (2048 kB) vmalloc : 0x12600000 - 0x1a600000 ( 128 MB) lowmem : 0x00000000 - 0x12600000 ( 294 MB) modules : Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xffe00000 (2048 kB) vmalloc : 0x12600000 - 0x1a600000 ( 128 MB) lowmem : 0x00000000 - 0x12600000 ( 294 MB) moHierarchical RCU implementation. RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1. RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 NR_IRQS:220 l4timer: Using IRQ210 sched_clock: 64 bits at 1000kHz, resolution 1000ns, wraps every 2147483648000ns Console: colour dummy device 80x30 console [ttyLv0] enabled Calibrating delay loop... 1987.37 BogoMIPS (lpj=9936896) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Setting up static identity map for 0x2287610 - 0x2287610 Brought up 1 CPUs SMP: Total of 1 processors activated. CPU: All CPU(s) started in SVC mode. VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0 NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations Added static device 'L4ICU' with 0 resources. Failed to create "l4x" debugfs directory: 1 l4vbus: is running Switched to clocksource l4kipclk NET: Registered protocol family 2 TCP established hash table entries: 4096 (order: 2, 16384 bytes) TCP bind hash table entries: 4096 (order: 3, 32768 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP: reno registered UDP hash table entries: 256 (order: 1, 8192 bytes) UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (junk in compressed archive); looks like an initrd INITRD: Freeing memory. l4x: Checks passed. NetWinder Floating Point Emulator V0.97 (double precision) futex hash table entries: 256 (order: 2, 16384 bytes) msgmni has been set to 506 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) l4fb.0: looking for capability 'fb' as goos session l4fb l4fb.0: 640x480@16 2bypp, size: 614400 @ 200000 l4fb l4fb.0: 5:5:5 10:5:0 linelen=1280 visual=2 l4fb l4fb.0: l4fb L4 frame buffer device (refresh: 10jiffies) Console: switching to colour frame buffer device 80x30 L4 serial driver ttyLv0 at MMIO 0x1 (irq = 211, base_baud = 230400) is a L4 l4ser_shm: L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded *l4bdds: Disk 'rom/system-arm-ginger.img' size = 233384 KB (227 MB) flags=101 ad0* * l4bdds0: unknown partition table * *[sched_delayed] sched: RT throttling activated * *l4bdds: Disk 'rom/system-arm-ginger.img' size = 233384 KB (227 MB) flags=101 ad4* mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 Registering SWP/SWPB emulation handler RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 1024KiB [1 disk] into ram disk... done. EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities EXT4-fs (ram0): mounting ext2 file system using the ext4 subsystem EXT4-fs warning (device ram0): ext4_update_dynamic_rev:701: updating to rev 1 bd EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) VFS: Mounted root (ext2 filesystem) on device 1:0. Freeing unused kernel memory: 164K (02356000 - 0237f000) init: cannot open '/initlogo.rle' EXT4-fs (ram0): re-mounted. Opts: (null) init: Unable to open persistent property directory /data/property errno: 2 init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj inste. init: cannot find '/system/bin/servicemanager', disabling 'servicemanager' init: cannot find '/system/bin/vold', disabling 'vold' init: cannot find '/system/bin/netd', disabling 'netd' init: cannot find '/system/bin/debuggerd', disabling 'debuggerd' init: cannot find '/system/bin/rild', disabling 'ril-daemon' init: cannot find '/system/bin/app_process', disabling 'zygote' init: cannot find '/system/bin/mediaserver', disabling 'media' init: cannot find '/system/bin/dbus-daemon', disabling 'dbus' init: cannot find '/system/bin/installd', disabling 'installd' init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' init: cannot find '/system/bin/keystore', disabling 'keystore' init: cannot find '/system/bin/sh', disabling 'console' random: adbd urandom read with 6 bits of entropy available Thank you very much. -- Best Regards. Youren Shen.

2 1

Question about ext2 in Fiasco/L4re
by yang.wei9＠zte.com.cn 17 May '15

17 May '15

Hi, Does Fiasco/L4re can support for ext2 filesystem and flash drivers? If it hasn't, then how hard will to implement it or to port an existing implementation? Could provide some guides? -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

2 1

Question about RCU subsystem in Fiasco kernel.
by deng.chao1＠zte.com.cn 17 May '15

17 May '15

Hi, I find Fiasco has a implementation of RCU(Read-Copy Update)synchronization mechanism, but I did not find there was any usage of it in Fiasco kernel.. Is this implementation of RCU complete? Will there be any RCU's application in Fiasco kernel?

2 1

question about file mapping
by yang.wei9＠zte.com.cn 17 May '15

17 May '15

Hi, I create a file on tmpfs, and it read/write works fine. However, it cannot mmap, and returns EINVAL. I found the reason is that dataspace of the file is not valid. L4::Cap<L4Re::Dataspace> fds = fi->data_space() if (!fds.is_valid()) { return -EINVAL; } How to make it valid? Is there another method to do file mapping? Here is an example code snippet: ========================== const char* filename = "/tmp/testfile"; ret = mount("/", "tmp", "tmpfs", 0, 0); fd = open(filename, O_RDWR|O_CREAT); write 10K data into file addr = mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0); //return -1, and errno is EINVAL -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

2 1

anything wrong when call Thread::do_ipc?
by watermirror 17 May '15

17 May '15

hi. in the Thread_object::invoke, it call Thread::do_ipc like this: ct->do_ipc(f->tag(), partner, partner, have_rcv, sender, f->timeout(), f, rights); the second parameter's type is Thread*. but the Thread::do_ipc's implemention is like this: Thread::do_ipc(L4_msg_tag const &tag, bool have_send, Thread *partner, bool have_receive, Sender *sender, L4_timeout_pair t, Syscall_frame *regs, L4_fpage::Rights rights) {...} the second parameter's type is bool. is there anything wrong with the code, or i have make some mistakes?

2 1

the Thread::do_ipc's parameter
by watermirror 17 May '15

17 May '15

Hi, in the method Thread::do_ipc, there's a parameter named 'partner'.what is the 'partner' used for?

2 1

Fiasco & L4 boot performance
by Arttu Pulli 11 May '15

11 May '15

Hi, I'm working on optimizing the boot time of our Fiasco/L4Re based system. So far I've implemented some simple optimizations, like using fixed delay loop calibration value, disabling prints (is there some centralized way to disable all printing for the whole system?), and removing all unnecessary IO configurations which helped quite a bit. However, I'm pretty new to L4 and Fiasco, so I wanted to ask if you'd have some tips & tricks (no matter how arcane) on improving either the boot performance or reducing the resulting image size? My current boot time on an iMX6Q board from after U-Boot gives execution to L4 to my own L4 app is ~225 ms, and the resulting image size is 2.8 MB (1.2 MB LZO'ed). Do those numbers sound like there is anything to be gained anymore, or are those close to some maybe-known lower limits already? Regarding IO initialization, is there any way to perform some of the IO inits later on instead of when IO starts during boot time? My goal is to have my own L4 app running as fast as possible, and boot L4Linux after that. The problem is, the IO configs for the L4Linux take a lot of time, so I'd much rather invoke them at the latest possible moment. I've also removed all unnecessary modules from the modules.list configuration file, I take it that this means no unnecessary stuff is added to the image even though most everything is compiled at build time? Best regards, Arttu

2 1

Re: Testing Fiasco.OC+L4re on ODROID-X2(Exynos4412)
by Reinier Millo Sánchez 11 May '15

11 May '15

Hi Adam >> > FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, >> > p: dbl/sngl >> > >> > KERNEL: Warning: No page-fault handler for 0xee202214, error >> > 0x94000848, pc f0039420 >> > >> >Somebody have tested Fiasco.OC+L4re on ODROID-X2 or another Exynos 4412 >> >platform? > On this platform this seems to be some pattern. However, last time I > tried it worked for me. So, hmm, could you try another compiler version > and see if it changes behavior? Maybe this gives us some hints. I'm using a linaro toolchain (gcc-linaro-arm-linux-gnueabihf-4.8-2014.03_x86_64). I have tried the arm-none-eabi toolchain in Debian repository but fails compiling the snapshot. I have made some progress trying to run FiascoOC+L4re on Odroid-X2. There are some changes that I have made: I have modified the file "l4/mk/platforms/exynos4.conf" adapting Exynos4's platform to Odroid-X2. In this case the RAM size differs (Odroid-X2 have 2Gb). In this file I have configured the UART for serial output (I'm using UART 1). PLATFORM_RAM_BASE = 0x40000000 - PLATFORM_RAM_SIZE_MB = 1024 + PLATFORM_RAM_SIZE_MB = 2047 + PLATFORM_UART_NR = 1 Booting the generated image I have detected that bootstrap's server is not using UART 1 for output. I have modified the "init" function on "l4/pkg/bootstrap/server/src/platform/exynos.cc" to use the configured UART on the platform file modified above. unsigned long uart_base; - unsigned uart_nr = 2; + unsigned uart_nr = PLATFORM_UART_NR; I have tried to compile and test the image on the Odroid-X2, but fails the execution, this is the serial output: L4 Bootstrapper Build: #18 Sat May 2 15:56:00 CDT 2015, 4.8.3 20140303 (prerelease) Scanning up to 2047 MB RAM, starting at offset 32MB Memory size is 2047MB (40000000 - bfefffff) Limiting 'RAM' region [ 40000000, bfefffff] { 7ff00000} to [ 40000000, bcffffff] { 7d000000} due to 3024 MB address limit RAM: 0000000040000000 - 00000000bcffffff: 2048000kB Total RAM: 2000MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 5 modules behind 41100000 moving module 02 { 410b4000-410e565f } -> { 411a5000-411d665f } [202336] moving module 01 { 410aa000-410b3377 } -> { 4119b000-411a4377 } [37752] moving module 00 { 41043000-410a9daf } -> { 41134000-4119adaf } [421296] moving module 04 { 41029000-410425b3 } -> { 4111a000-411335b3 } [103860] moving module 03 { 4100f000-41028493 } -> { 41100000-41119493 } [103572] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x40002000 Regions of list 'regions' [ 40000000, 400000e3] { e4} Root mbi_rt [ 40001000, 40001aff] { b00} Kern fiasco [ 40002000, 40076fff] { 75000} Kern fiasco [ 40090000, 4009681b] { 681c} Sigma0 sigma0 [ 40098000, 4009e177] { 6178} Sigma0 sigma0 [ 40140000, 4018b4ab] { 4b4ac} Root moe [ 41000000, 4100e4ff] { e500} Boot bootstrap [ 41100000, 41133fff] { 34000} Root Module API Version: (87) experimental Sigma0 config ip:40090100 sp:00000000 Roottask config ip:4014020c sp:00000000 Starting kernel fiasco at 400012c8 Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf0063a50-0xf00644d0) 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 KERNEL: Warning: No page-fault handler for 0xee202214, error 0x94000848, pc f0039420 I have been testing and changing the compiling configuration. Using the below configuration to compile Fiasco.OC, the system boots and hangs at "Calibrating timer loop...": Platform Timer -> Multi-core timer Use ExtGic -> True Execution Model -> TrustZone normal side Secure Monitor Interface -> Mobicore Enable multi processor support -> True Maximal supported number of CPUs -> 4 This is the serial output when tested the image on Odroid-X2: L4 Bootstrapper Build: #56 Tue May 5 01:08:40 CDT 2015, 4.8.3 20140303 (prerelease) Scanning up to 2047 MB RAM, starting at offset 32MB Memory size is 2047MB (40000000 - bfefffff) Limiting 'RAM' region [ 40000000, bfefffff] { 7ff00000} to [ 40000000, bcffffff] { 7d000000} due to 3024 MB address limit RAM: 0000000040000000 - 00000000bcffffff: 2048000kB Total RAM: 2000MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 5 modules behind 41100000 moving module 02 { 41090000-410c165f } -> { 41181000-411b265f } [202336] moving module 01 { 41086000-4108f377 } -> { 41177000-41180377 } [37752] moving module 00 { 41043000-4108534f } -> { 41134000-4117634f } [271184] moving module 04 { 41029000-410425b3 } -> { 4111a000-411335b3 } [103860] moving module 03 { 4100f000-41028493 } -> { 41100000-41119493 } [103572] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x40002000 Regions of list 'regions' [ 40000000, 400000e3] { e4} Root mbi_rt [ 40001000, 40001aff] { b00} Kern fiasco [ 40002000, 4004efff] { 4d000} Kern fiasco [ 40090000, 4009681b] { 681c} Sigma0 sigma0 [ 40098000, 4009e177] { 6178} Sigma0 sigma0 [ 40140000, 4018b4ab] { 4b4ac} Root moe [ 41000000, 4100e4ff] { e500} Boot bootstrap [ 41100000, 41133fff] { 34000} Root Module API Version: (87) experimental Sigma0 config ip:40090100 sp:00000000 Roottask config ip:4014020c sp:00000000 Starting kernel fiasco at 400012c8 Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf0040110-0xf0040b18) 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 85 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: unknown compiled with gcc 4.8.3 for Samsung Exynos [] Build: #68 Tue May 5 01:08:28 CDT 2015 Per_cpu_data_alloc: (orig: 0xf0040110-0xf0040b18) KERNEL: Warning: Buddy::alloc: Size mismatch: a08 v 1000 Allocate 2568 bytes (3KB) for CPU[4] local storage (offset=13a4ef0, 0xf13e5000-0xf13e5a08) Timer for CPU0 is at IRQ 28 Number of CPUs: 4 Calibrating timer loop... Per_cpu_data_alloc: (orig: 0xf0040110-0xf0040b18) KERNEL: Warning: Buddy::alloc: Size mismatch: a08 v 1000 Allocate 2568 bytes (3KB) for CPU[1] local storage (offset=13a6ef0, 0xf13e7000-0xf13e7a08) FPU1: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl Per_cpu_data_alloc: (orig: 0xf0040110-0xf0040b18) Timer for CPU1 is at IRQ 28 KERNEL: Warning: Buddy::alloc: Size mismatch: a08 v 1000 CPU[1]: goes to idle loop Allocate 2568 bytes (3KB) for CPU[2] local storage (offset=13a9ef0, 0xf13ea000-0xf13eaa08) FPU2: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl Per_cpu_data_alloc: (orig: 0xf0040110-0xf0040b18) Timer for CPU2 is at IRQ 28 KERNEL: Warning: Buddy::alloc: Size mismatch: a08 v 1000 CPU[2]: goes to idle loop Allocate 2568 bytes (3KB) for CPU[3] local storage (offset=13acef0, 0xf13ed000-0xf13eda08) FPU3: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl Timer for CPU3 is at IRQ 28 CPU[3]: goes to idle loop I think that the problem now is with the Exynos4's Timers, but i have been reviewing the implementations and it seems fine. Is there anything wrong on my configuration or somebody have any idea? Best regards -- Lic. Reinier Millo Sánchez Centro de Estudios de Informática Universidad Central "Marta Abreu" de Las Villas Carretera a Camajuaní Km 5 1/2 Santa Clara, Villa Clara, Cuba CP 54830 "antes de discutir ... respira; antes de hablar ... escucha; antes de escribir ... piensa; antes de herir ... siente; antes de rendirte ... intenta; antes de morir ... vive"

2 1

Re: Using a second UART to control a serial device
by Pflaum, Clemens 10 May '15

10 May '15

Hi L4 Hackers, Since i sadly still cant get the uart to work i have some more questions. 1. I've noticed that the offsets of all the registers in the /drivers-frst/uart/src/uart_pxa.cc are are incorrect by a multiple of 4. So if IER is defined to be at 0x01 it is actually at 0x04, respectivly the LCR which is said to be at 0x03 is actually at 0x0C. After I changed these values to reflect the allwinner A20 manual, the kernel stopped loading properly. It gets stuck on bootup at "Starting kernel...". In fact it does continue although at a pace of one character every 5 to 6 minutes. So after 30mins i had "L4 Bootstra" in the next line. My assumption is that my UART0 from which i run the console on my linux pc actually uses the uart_pxa driver with the incorrect register offset and it works for it. By changing the registers I somehow break my UART0. If I'm correct then I should be able to find the routine which the kernel uses to initilize UART0, to help me understand how to get UART3 to work. Sadly I couldn't find anything alike. 2.So i went on by writing a new uart_16550bananapi.cc with changed registers. It did infact solve the kernel not starting issue. I can now access and write to all of the uart registers... apart from the Line Control Register(LCR). It starts off with 0x03 written to it although it has a default of 0x00(in the a20 manual) as soon as i write 0x00 to it my console starts throwing out seemingly random chars: This code in the uart startup() function: scratch = _regs->read<unsigned char>(LCR); printf("\ncurrent LCR: %#010x\n", scratch); printf("Setting LCR to 0\n"); printf("This gets overritten\n"); _regs->write<unsigned char>(LCR, 0); /* clear line control register */ printf("It worked\n"); gives me this outpot on console: Maestro | Maestro | current LCR: 0x00000003 Maestro | Setting LCR to 0 Maese|iw�k�{m{[e|{m{[e|pp`'br�l�z{mos�pppppn{m{[e��r|{m{[e p�ot[ lLzppppp{m{[e|pq`�rppppp{m{ێm[e|pqlNzppppv{m{[e|pq`�rppppp{m{ێm[e q The same thing happens if i write 0x80 to it to add the DLAB bit that i need to access the two Divisor Latch registers to initilize the Baudrate for the first time. The 0x03 in LCR means that i run my Uart in 8N1 mode setting which my UART0 console is running aswell. Setting it to 0 means to run 5N1. So I assume for some reason it might somehow change my UART0 settings if i write to UART3 LCR reg. But the same error occurs if i write 0x83 to it to leave 8N1 on and set the DLAB bit, so that cant be the case can it? Without setting Baudrate however i obviously cant hope for UART3 to work. Thanks for any answers in advance, Clemens

3 8

about Ram_quota
by watermirror 08 May '15

08 May '15

hi, what is Ram_quota used for?

2 1

Static_object::construct
by watermirror 08 May '15

08 May '15

hi, template< typename T > class Static_object { public: .... template< typename... A > T *construct(A&&... args) { return new (_i) T(cxx::forward<A>(args)...); } ... }; this template class is defined in fiasco/src/types.h, what does the method 'construct' mean? i have tried to move this class to eclipse cdt project, but it can not be compiled correctly. how does this class be compiled in fiasco?

2 1

Testing Fiasco.OC+L4re on ODROID-X2(Exynos4412)
by Reinier Millo Sánchez 04 May '15

04 May '15

Hi comunity I'm trying to test the hello application on the ODROID-X2(Exynos4412) board. I'm using the Fiasco.OC+L4re snapshot(l4re-snapshot-2014092821). I have configured and compiled Fiasco.OC with support to Samsung Exynos4412: export SYSTEM_TARGET=arm-linux-gnueabihf- make BUILDDIR=build-foc make menuconfig make -j16 After that, I have compiled the entire L4re for armv7a (SamsungExynos4) make B=build-l4re make O=build-l4re ARCH=arm SYSTEM_TARGET=arm-linux-gnueabihf- menuconfig make O=build-l4re ARCH=arm SYSTEM_TARGET=arm-linux-gnueabihf- -j16 To generate the raw image have modified the conf/Makeconf.boot to set the Fiasco.OC build path and executed: make O=build-l4re ARCH=arm SYSTEM_TARGET=arm-linux-gnueabihf- rawimage E=hello I have copied the generated image into the SD card and tried to boot from u-boot: fatload mmc 0:1 0x41000000 hello.raw bootm 0x41000000 The system starts but stops execution. This is the serial output: Partition1: Start Address(0xc00), Size(0x40400) reading hello.raw 942080 bytes read Boot with zImage Starting kernel ... Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf0063a50-0xf00644d0) 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 KERNEL: Warning: No page-fault handler for 0xee202214, error 0x94000848, pc f0039420 Somebody have tested Fiasco.OC+L4re on ODROID-X2 or another Exynos 4412 platform? Best regards -- Lic. Reinier Millo Sánchez Centro de Estudios de Informática Universidad Central "Marta Abreu" de Las Villas Carretera a Camajuaní Km 5 1/2 Santa Clara, Villa Clara, Cuba CP 54830 "antes de discutir ... respira; antes de hablar ... escucha; antes de escribir ... piensa; antes de herir ... siente; antes de rendirte ... intenta; antes de morir ... vive"

2 1

Experimenting the vm-tz example on the Freescale i.mx6 SDB
by Mahdi Aichouch 04 May '15

04 May '15

Hello, I am trying to experiment the "vm-tz" example on the Freescale i.mx6 SDB board. At first, my goal is to understand the example, thus I am interested in running a simple test kernel instead of a full linux kernel. Specifically, I am trying to reproduce the experimentation of the article related to the trustzone implementation on Fiasco.OC L4re, "ARM Trustzone as a Virtualization Technique in Embedded Systems". In particular, it is mentioned in the article at the "Implementation" paragraph that "Multiplexing two or more OS is supported by our design." I would like to investigate this point. I created a new entry to generate the vm-tz binary. I added the following entry to the "src/l4/conf/modules.list" file : entry tz_vm roottask moe --init=rom/vm-tz module l4re module vm-tz Is my configuration entry correct, is there any missing modules that are required by the example? I tested the binary on the board using tftp, and I obtained the following results: L4 Bootstrapper Build: #12 Tue Mar 17 12:10:02 CET 2015, 4.8.3 20140320 (prerelease) Scanning up to 1024 MB RAM, starting at offset 32MB Memory size is 1024MB (10000000 - 4fffffff) RAM: 0000000010000000 - 000000004fffffff: 1048576kB Total RAM: 1024MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 5 modules behind 11100000 moving module 02 { 110a5000-110de63f } -> { 11195000-111ce63f } [235072] moving module 01 { 1109b000-110a438b } -> { 1118b000-1119438b } [37772] moving module 00 { 11044000-1109a0c7 } -> { 11134000-1118a0c7 } [352456] moving module 04 { 1102a000-11043597 } -> { 1111a000-11133597 } [103832] moving module 03 { 11010000-11029473 } -> { 11100000-11119473 } [103540] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x10002000 Regions of list 'regions' [ 10000000, 100000e3] { e4} Root mbi_rt [ 10001000, 10001aff] { b00} Kern fiasco [ 10002000, 10062fff] { 61000} Kern fiasco [ 10090000, 10096edf] { 6ee0} Sigma0 sigma0 [ 10098000, 1009e177] { 6178} Sigma0 sigma0 [ 10140000, 10171d77] { 31d78} Root moe [ 10178000, 101934ab] { 1b4ac} Root moe [ 11000000, 1100f4ff] { f500} Boot bootstrap [ 11100000, 11133fff] { 34000} Root Module API Version: (87) experimental Sigma0 config ip:10090100 sp:00000000 Roottask config ip:10140260 sp:00000000 Starting kernel fiasco at 100012c8 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 L2: ID=410000c7 Type=9e340340 Aux=02070000 WMask=ffff S=0 L2: Type L2C-310 Size = 1024kB Ways=16 Waysize=64 SERIAL ESC: allocated IRQ 58 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: rexported compiled with gcc 4.8.3 for i.MX6 [] Build: #3 Wed Mar 11 16:43:41 CET 2015 Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 10002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:10000000;10000fff] [0:10063000;1008ffff] [0:10097000;10097fff] [0:1009f000;1013ffff] [4:10140000;10171fff] [0:10172000;10177fff] [4:10178000;10193fff] [0:10194000;110fffff] [4:11100000;11133fff] [0:11134000;4effffff] IOMEM:---------------------- [0:0;fffffff] [0:50000000;ffffffff] MOE: Hello world MOE: found 1031220 KByte free memory MOE: found RAM from 10000000 to 4f000000 MOE: allocated 1008 KByte for the page array @0x10194000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [11100000-11119474] [C:503000] l4re BOOTFS: [1111a000-11133598] [C:504000] vm-tz MOE: cmdline: moe --init=rom/vm-tz MOE: Starting: rom/vm-tz MOE: loading 'rom/vm-tz' Vmm started terminate called after throwing an instance of 'N2L413Runtime_errorE' MOE: task 270000679 exited with 127 The code stops at the beginning when it tries to create a VM : L4Re::chksys(env->factory()->create_vm(vm)); After reading through the code, I saw that the code example is expecting a linux-image and an initrd to be provided. Is it possible to tell me where these should be added in the build directory? In my test case, the linux-image will be replaced by a simple kernel image. Could someone help me to correct my test case. Many thanks in advance. Best regards, Mahdi

2 19

context::regs
by watermirror 03 May '15

03 May '15

hi,the implemention of Context::regs() is like this: return reinterpret_cast<Entry_frame*>(Cpu::stack_align(reinterpret_cast<Mword>(this + Size)) -1; how this algorithm came out?i think the memory of the object is allocated by c++ compiler, but why '(this + Size)' could get Entry_frame of a thread?

2 1