l4-hackers July 2016

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

7 participants
12 discussions

Porting Fiasco + L4Re to Raspberry Pi 2
by Antoine DEBUT 26 Nov '17

26 Nov '17

Hello l4-hackers, I am currently working on porting the Fiasco.OC micro kernel onto the Raspberry pi 2. Therefore, I am struggling with memory mapping, and I encounter the following error when launching the default 'hello' entry: L4 Bootstrapper Build: #2 Tue Feb 23 11:57:19 CET 2016, 4.8.3 20140303 (prerelease) Scanning up to 1024 MB RAM, starting at offset 32MB Memory size is 1024MB (00000000 - 3fffffff) RAM: 0000000000000000 - 000000003fffffff: 1048576kB Total RAM: 1024MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 5 modules behind 1100000 moving module 02 { 10db000-110c4d7 } -> { 11cc000-11fd4d7 } [201944] moving module 01 { 10c9000-10da373 } -> { 11ba000-11cb373 } [70516] moving module 00 { 1043000-10c889f } -> { 1134000-11b989f } [546976] moving module 04 { 1029000-10425af } -> { 111a000-11335af } [103856] moving module 03 { 100f000-102849b } -> { 1100000-111949b } [103580] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list 'regions' [ 1000, 1aff] { b00} Kern fiasco [ 2000, 92fff] { 91000} Kern fiasco [ 93000, 930eb] { ec} Root mbi_rt [ c0000, c9c33] { 9c34} Sigma0 sigma0 [ d0000, d6177] { 6178} Sigma0 sigma0 [ 140000, 16905b] { 2905c} Root moe [ 170000, 17b58b] { b58c} Root moe [ 1000000, 100e4ff] { e500} Boot bootstrap [ 1100000, 1133fff] { 34000} Root Module API Version: (87) experimental Sigma0 config ip:000c0100 sp:00000000 Roottask config ip:00140250 sp:00000000 Starting kernel fiasco at 000012b8 Non-HYP kernel detected but running in HYP mode, switching back. Hello from Startup::stage2 Assertion failed at /home/adebut/Documents/snapshotTest/l4re-snapshot-2015123115/src/kernel/fiasco/src/kern/buddy_alloc.cpp:101: (unsigned long)block >= _base Press any key to reboot. I am currently working on the latest snapshot (2015123115), with U-Boot as a bootloader, and testing on a real board (Raspberry Pi 2 model B V1.1). The entry built is the standard 'hello', and I use the ramdisk-arm.rd given in the snapshot. I did add a custom Bsp for the board, mainly based on the first Raspberry Pi except for the Base Address, that is 0x3F000000 instead of the first Pi's 0x20000000. I highly think that it is an address configuration problem, because it first happened when I did expand the RAM size to 1024MB. With further investigation, I found out that it was the kernel memory allocation that causes this error, and suspect an incorrect MMU mapping. This suspicion comes from the fact that the assertion takes the address _base (0xf0400000) and the currently allocated block (0xee100000). I did not modify any parameter in the kern/arm/mem_layout-arm.cpp file on the Fiasco directory, which provides the default ARM addressing. Maybe that's where my error comes from ? How can I correctly configure my memory mapping, besides what I already configure in the Bsp (given in attachment) ? Also, it is the first time that I am assigned for porting a system, do you have some hints, like important steps to follow ? I am pretty sure it is a newbie error, but I cannot figure it out for now :( Thanks in advance for your time, -- Antoine Debut EPITA 2016 - GISTRE

3 7

Graphical desktop, l4con, mag
by teclis High Elf 02 Jun '17

02 Jun '17

Guten Tag, I've got the Hello app runing with fiasco and l4re in qemu, how do I get the graphical UI and console running that I see on the screen shots page? Do I need to use l4con and mag? I don't see an entry with l4con in modules.list. danke * <http://german.about.com/library/media/Audio/gutentag.wav>*

6 15

Benchmarks in l4
by Maxim Baryshnikov 01 Jun '17

01 Jun '17

Hello everybody, Does the L4re contain some kind of simple performance benchmarks which are already prepared to use? I've tried to launch some demos from the ferret package but not succeed... Thank you in advance for any suggestions. Sincerely, Maxim Baryshnikov.

4 11

libfs/ FUSE on L4Re
by Stark, Josef 31 May '17

31 May '17

Hello, yesterday I came across a very interesting paper titled "Porting FUSE to L4Re", accessible here: http://os.inf.tu-dresden.de/papers_ps/pester-beleg.pdf For porting FUSE, the author uses a library called "libfs" which provides filesystem request forwarding and processing, if I understood correctly. It reads as if libfs is already included in L4Re. However, I couldn't find neither FUSE nor libfs in the current L4Re snapshot. Are they by any chance publicly available somewhere else, or are both not to be published? Cheers, Josef

4 7

l4_thread_ex_regs and suspending thread
by Valery V. Sedletski 16 Aug '16

16 Aug '16

hi, l4-hackers. I am now using l4v2 API with L4/Fiasco. I know that on L4 v.2 API, the thread is created if set eip/esp/pager/preempter to real values. And it seems that likewise, thread can be suspended if setting these values to invalid ones. But as I tried it, setting the running thread eip/esp to -1 causes double page fault in that thread. Setting them to 0 does not change these values (though, in headers' comments, documented value is ~0). Setting pager/preempter to L4_INVALID_ID also causes double page fault. This is strange, as docs/comments state the converse. So, is it possible anyhow to suspend/resume the running thread from another thread? I know, that the thread can be suspended if entering unconditional l4_ipc_wait(), but this is from the inside that thread. How could it be done from an outside thread? Thanks in advance, valery

4 12

USDHC driver for i.MX6
by AIT HMID Moha 29 Jul '16

29 Jul '16

Hi L4 hackers, Is a L4Linux/Fiasco driver for Freescale i.MX6 processor USDHC module available ? If not any input/clue to port an existing implementation ? Best regards, MAH

2 1

l4linux panic on iMX6SX
by AIT HMID Moha 29 Jul '16

29 Jul '16

Hi L4 hackers, I am using l4re-snapshot-2014092821 and running L4Linux/L4 on Freescale iMX6SX SABRE SDB card. Here attached my Fiasco, L4, L4Linux and moe starting configurations and the resulted displayed traces. I got a l4linux 'kernel panic'. Any idea about the issue ? Best regards, MAH

2 1

Question: The future of Fiasco & L4Re
by Ratko Rudič 18 Jul '16

18 Jul '16

Hi hackers! I've been looking at microkernels for some time and am writing a high overview paper about them for our faculty. Adam wrote[1] that all discussions happen mostly in-house so finding info about Fiasco's future is probably hard. So, if any of you hackers have a minute to spare, I'd be glad to hear what you intend to implement in future L4 releases. It doesn't need to have dates - maybe just pointers what you'd like to see in a year or so. Thank you, Ratko Rudic [1] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007538.html

2 1

l4re programming language support
by Michael Schnupp 12 Jul '16

12 Jul '16

Hi, I am aware that pretty much the whole l4re system is written in C++ and that the C(++) binding is the main way to write new tasks. However I also noticed some packages which look like there is also support for languages like fortran, python, and ocaml. Is there any documentation/example on how to use these to write a new task in those languages? (Is there generally any documentation on how to use the existing packages?) I would really love to write own tasks in rust. Is there any chance to build a l4re binary using rust, too? (Is there generally any documentation on how a binary must look like in order to be able to run on l4re?) Rust supports specifying custom linking options and has good support for cross compiling. Especially it also allows linking against musl to build static binaries. All this make me feel it should be possible to target l4re, too, but I really don't understand the l4re build system well enough. Do you see any chance in doing so? Some references: https://doc.rust-lang.org/book/advanced-linking.html https://github.com/japaric/rust-cross Michael

2 1

l4re-snapshot-2016060908 lunch "L4Linux-mag-x86" problem
by 张鑫 07 Jul '16

07 Jul '16

Hi, Everyone, I'm a newer in L4Linux,I get the lastest snapshort and follow the README which builds it successfully, When I execute make qemu in /my_dir/obj/l4/x86 ,it comes up Entry selection , I tested all but "L4Linux-mag-x86" is'nt work successfully. I prebuild the snapshot in Ubuntu 14.04.4 LTS, the following is the ubuntu output message: L4 Bootstrapper Build: #1 Fri Jul 1 02:18:27 PDT 2016, x86-32, 4.8.4 RAM: 0000000000000000 - 000000000009fbff: 639kB RAM: 0000000000100000 - 000000000fffdfff: 261112kB Total RAM: 255MB Scanning /home/zhangxin/Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco -serial_esc Scanning /home/zhangxin/Desktop/l4re-snapshot-2016060908 /obj/l4/x86/bin/x86_586/l4f/sigma0 Scanning /home/zhangxin/Desktop/l4re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg need 1424 bytes to copy MBI reserved 1424 bytes at 0x2000 Moving up to 13 modules behind 1100000 moving module 12 { 3013400-33133ff } -> { 3e32000-4131fff } [3145728] moving module 11 { 2b28400-3012aa4 } -> { 3947000-3e316a4 } [5154469] moving module 10 { 2b27400-2b2765e } -> { 3946000-394625e } [607] moving module 09 { 2b26400-2b26737 } -> { 3945000-3945337 } [824] moving module 08 { 24e6400-2b25ab7 } -> { 3305000-39446b7 } [6551224] moving module 07 { 2209400-24e5ebb } -> { 3028000-3304abb } [3001020] moving module 06 { e86400-2208973 } -> { 1ca5000-3027573 } [20456820] moving module 05 { e85400-e8591b } -> { 1ca4000-1ca451b } [1308] moving module 04 { b24400-e846a5 } -> { 1943000-1ca32a5 } [3539622] moving module 03 { 968400-b23b8f } -> { 1787000-194278f } [1816464] moving module 02 { 41e400-967f0a } -> { 123d000-1786b0a } [5544715] moving module 01 { 378400-41dcbf } -> { 1197000-123c8bf } [678080] moving module 00 { 2e1400-378257 } -> { 1100000-1196e57 } [618072] Loading /Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco Loading re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/sigma0 Loading /l4re-snapshot-2016060908/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 /Desktop/l4re-snapshot- 2016060908/obj/fiasco/ia32/fiasco [ 2000, 258f] { 590} Root mbi_rt [ 9fc00, 9ffff] { 400} Arch BIOS [ f0000, fffff] { 10000} Arch BIOS [ 100000, 10f193] { f194} Sigma0 re-snapshot-2016060908 /obj/l4/x86/bin/x86_586/l4f/sigma0 [ 140000, 17c367] { 3c368} Root /l4re-snapshot-2016060908 /obj/l4/x86/bin/x86_586/l4f/moe [ 2d0400, 2df43f] { f040} Boot bootstrap [ 300000, 38ffff] { 90000} Kern /Desktop/l4re-snapshot- 2016060908/obj/fiasco/ia32/fiasco [ 400000, 49bfff] { 9c000} Kern /Desktop/l4re-snapshot- 2016060908/obj/fiasco/ia32/fiasco [ 1787000, 4131fff] { 29ab000} Root Module [ fffe000, fffffff] { 2000} Arch BIOS [ fffc0000, ffffffff] { 40000} Arch BIOS API Version: (87) experimental Sigma0 config ip:001001d4 sp:00000000 Roottask config ip:001401f6 sp:00000000 Starting kernel /Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco at 003007c0 Welcome to L4/Fiasco.OC! L4/Fiasco.OC microkernel on ia32 Rev: unknown compiled with gcc 4.8.4 for Intel Pentium [] Build: #1 Fri Jul 1 02:13:30 PDT 2016 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: RSDP[0xf0990] r00 OEM:BOCHS. 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 f8 (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 3397MHz 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: 28672 bytes (7 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:110000;13ffff] [4:140000;17cfff] [0:17d000;3fffff] [0:495000;1786fff] [4:1787000;4131fff] [0:4132000;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 197224 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:103000] BOOTFS: [1787000-1942790] [C:105000] l4re BOOTFS: [1943000-1ca32a6] [C:107000] ned BOOTFS: [1ca4000-1ca451c] [C:109000] l4lx-gfx.cfg BOOTFS: [1ca5000-3027574] [C:10b000] io BOOTFS: [3028000-3304abc] [C:10d000] fb-drv BOOTFS: [3305000-39446b8] [C:10f000] mag BOOTFS: [3945000-3945338] [C:111000] x86-legacy.devs BOOTFS: [3946000-394625f] [C:113000] l4lx-x86.io BOOTFS: [3947000-3e316a5] [C:115000] vmlinuz BOOTFS: [3e32000-4132000] [C:117000] ramdisk-x86.rd MOE: cmdline: /home/zhangxin/Desktop/l4re-snapshot-2016060908/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: f0990 io | ACPI: RSDP 0x00000000000F0990 000014 (v00 BOCHS ) io | ACPI: RSDT 0x000000000FFFFBC1 000034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001) io | ACPI: FACP 0x000000000FFFF1C0 000074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001) io | ACPI: DSDT 0x000000000FFFE040 001180 (v01 BOCHS BXPCDSDT 00000001 BXPC 00000001) io | ACPI: FACS 0x000000000FFFE000 000040 io | ACPI: SSDT 0x000000000FFFF234 0008DD (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001) io | ACPI: APIC 0x000000000FFFFB11 000078 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001) io | ACPI: HPET 0x000000000FFFFB89 000038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001) io | io | Initializing Namespace objects: io | Table [DSDT: BXPCDSDT] (id 01) - 144 Objects with 18 Devices, 8 Regions, 52 Methods (6/46/5 Serial/Non/Cvt) io | Table [SSDT: BXPCSSDT] (id 02) - 155 Objects with 32 Devices, 1 Regions, 42 Methods (0/42/0 Serial/Non/Cvt) io | ACPI: 2 ACPI AML tables successfully acquired and loaded io | io | Completing Region/Field/Buffer/Package initialization: io | Initialized 9/9 Regions 2/2 Fields 21/21 Buffers 5/5 Packages (308 nodes) io | evxfevnt-0182 Enable : Transition to ACPI mode successful io | Initializing General Purpose Events (GPEs): io | Initialized GPE 00 to 0F [_GPE] 2 regs on interrupt 0x9 (SCI) io | Initializing Device/Processor/Thermal objects and executing _INI/_STA methods: io | Executed 0 _INI methods requiring 1 _STA executions (examined 53 objects) io | ACPICA-Version:20160318, System in ACPI MODE, 32bit timer io | ACPI Error: Could not enable PowerButton event (20160318/evxfevnt-304) io | ACPI Warning: Could not enable fixed event - PowerButton (2) (20160318/evxface-821) io | ACPI: could not register power-button handler: AE_NO_HARDWARE_RESPONSE io | ACPI: Enabled 16 GPEs in block 00 to 0F io | IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=40201) io | IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=40201) 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: 200000 - 600000 fb-drv | Starting server loop mag | mapped frame buffer at 0x400000 mag | View::Info: mag | flags: 0 mag | size: 1024x768 mag | pos: 0x0 mag | bytes_per_line: 2048 mag | buffer_offset: 0 mag | RGBA(2):5(11):6(5):5(0):0(0) mag | memory 0x400000 - 0x800000 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 PH 0 offs=00001000 flags=r-x PH-type=0x1 virt=00100000 evirt=00473000 phys=00100000 ephys=00473000 f_sz=00373000 memsz=00373000 PH 1 offs=00374000 flags=rw- PH-type=0x1 virt=00473000 evirt=00573000 phys=00473000 ephys=00573000 f_sz=00052afe memsz=00100000 PH 2 offs=002b708c flags=--- PH-type=0x4 virt=003b608c evirt=003b60b0 phys=003b608c ephys=003b60b0 f_sz=00000024 memsz=00000024 Starting binary at 0x100000, argc=6 argv=0xafff4f90 *argv=0xb1007ff4 argv0=rom/vmlinuz External resolver is at 0xa80008c0 ======> L4Linux starting... <======== Linux version 4.6.0-l4 (zhangxin@ubuntu) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #1 Fri Jul 1 02:34:46 PDT 2016 Binary name: rom/vmlinuz Linux kernel command line (5 args): mem=64M console=tty0 l4x_rd=rom/ramdisk-x86.rd root=1:0 ramdisk_size=4000 CPU mapping (l:p)[1]: 0:0 Image: 00100000 - 00573000 [4556 KiB]. Areas: Text: 00100000 - 003b5a5b [2774kB] RO-Data: 003b7000 - 00473000 [752kB] Data: 00473000 - 0049a500 [157kB] Init: 0049c000 - 004c6000 [168kB] BSS: 004c6000 - 0055d000 [604kB] gs=43 fs=43 Device scan: Device: L4ICU Device: PCI0 Device: pci_l4x[1] IRQ: 0000000b - 0000000b MEM: febc0000 - febdffff PORT: 0000c000 - 0000c03f DMAD: 00000000 - 00000000 Device: pci_l4x[2] PORT: 0000c040 - 0000c04f DMAD: 00000000 - 00000000 PORT: 000001f0 - 000001f7 PORT: 000003f6 - 000003f6 IRQ: 0000000e - 0000000e PORT: 00000170 - 00000177 PORT: 00000376 - 00000376 IRQ: 0000000f - 0000000f Device scan done. l4x_fiasco_gdt_entry_offset = 9 l4lx_thread_create: Created thread 41e (cpu0) (u:b3000e00, v:b3000c00, sp:00475fac) main thread will be 41e section-with-init(-data): Virt: 0x473000 to 0x572fff [1024 KiB] section-with-init(-data): Phys: 0x00298000 to 0x00397fff, [1024 KiB] section-with-init-text: Virt: 0x473000 to 0x572fff [1024 KiB] *error: failed to get physical address for 473000.* Main thread running, waiting... L4x: Memory size: 64MB L4x: Setting superpages for main memory L4x: Adjusted memory start: 00000000 Main memory: Virt: 0x800000 to 0x47fffff [65536 KiB] Main memory: Phys: 0x04400000 to 0x083fffff, [65536 KiB] l4x: vmalloc area: 04800000 - 0c800000 Filling lower ptabs... Done (254 entries). text: Virt: 0x100000 to 0x472fff [3532 KiB] text: Phys: 0x00495000 to 0x00807fff, [3532 KiB] Loading: rom/ramdisk-x86.rd INITRD: Size of RAMdisk is 3072KiB RAMdisk from 0ca1b000 to 0cd1b000 [3072KiB] l4lx_thread_create: Created thread 425 (timer0) (u:b3000a00, v:00000000, sp:004f5fa8) WARNING: Unknown rdmsr: 00000186 at 0x4a4737 WARNING: Unknown rdmsr: 00000187 at 0x4a4737 WARNING: Unknown rdmsr: 000000c2 at 0x4a47f0 WARNING: Unknown wrmsr: 000000c2 at 0x4a480e WARNING: Unknown rdmsr: 000000c2 at 0x4a4814 the qemu out stop here: I find the error,But I have no idea about, can anybody help me ? Thanks in advanced! Best Reagrds！ ryan.zhang

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 July 2016