- l4-hackers - example.com Site

Re: Extending l4sys by reading/writing register values of a preempted thread
by Christian Ludwig 20 Mar '17

20 Mar '17

Hi, > I want to implement a new syscall for getting/setting stored register > values of a specific thread (identified by its cap). Why not use ex_regs() on the thread to trigger an exception. That way, the attached userland exception handler can introspect the thread's complete register set. It can also alter the registers, so that the thread continues to run with the modified register set. Is there anything more you need? > Before implementing the syscall, I need to better understand the > kernel-part of Fiasco.OC. Can you help me answer the following questions > and point me to the source code regarding each question: > > * Where (in the source code) are threads preempted and their register > state stored? A thread's userland registers are stored on every entry to the kernel. The class in Fiasco is called Entry_frame. The userland exception handler mentioned above modifies that Entry_frame. > * Where is the register state of a thread loaded to the CPU and the > thread started (e.g. after a preempt)? When the scheduler selects a thread, its userland state (Entry_frame) is restored on exit from kernel mode. > * How can I introspect the stored thread register of a thread in the > kernel debugger JDB? > ** My thoughts: Is it K<kobj_ptr> with kobj_ptr of the thread and the 3 > lines beginning with PC=...? > e.g. > " > PC=010579cc USP=200ffdb0 smlatbeq r9, r0, r2, r5 > [0] 00000003 000010c0 00218003 00000000 tsteq000r5, ip, rrx > [8] 200ffdb0 200ffe40 01086ef0 200ffe98 [c] 200ffef8 010579cc fffffff8 > 20000010 > " Yes, that PC line is the userland program counter. the USP is the userland stack pointer. All userland registers are located at the top of kernel stack for a particular thread. > I also have another, short, off-topic question: > * How can I introspect the capability space of a task inside the kernel > debugger? In short mode, press 's' for a list of all tasks. Select the task in question and the press 'o' to see the capability space for that task. Hope that helps, - Christian

3 2

Extending l4sys by reading/writing register values of a preempted thread
by Denis Huber 13 Mar '17

13 Mar '17

Dear L4 hackers community, I want to implement a new syscall for getting/setting stored register values of a specific thread (identified by its cap). Preliminary note: I'm using the ARM architecture. Before implementing the syscall, I need to better understand the kernel-part of Fiasco.OC. Can you help me answer the following questions and point me to the source code regarding each question: * Where (in the source code) are threads preempted and their register state stored? * Where is the register state of a thread loaded to the CPU and the thread started (e.g. after a preempt)? * Where is the register state stored of each thread? * How can I introspect the stored thread register of a thread in the kernel debugger JDB? ** My thoughts: Is it K<kobj_ptr> with kobj_ptr of the thread and the 3 lines beginning with PC=...? e.g. " PC=010579cc USP=200ffdb0 smlatbeq r9, r0, r2, r5 [0] 00000003 000010c0 00218003 00000000 tsteq000r5, ip, rrx [8] 200ffdb0 200ffe40 01086ef0 200ffe98 [c] 200ffef8 010579cc fffffff8 20000010 " I also have another, short, off-topic question: * How can I introspect the capability space of a task inside the kernel debugger? Kind regards, Denis

1 0

Run L4Re/Fiasco hello example under QEMU (ARM)
by Piotr Piwko 05 Mar '17

05 Mar '17

Hi, I would like to run hello example under qemu-system-arm, so I successfully built the images using gcc-linaro-6.3.1 toolchain with following configuration: L4Re: Target Architecture (ARM architecture) CPU variant (ARMv7A type CPU) Platform Selection (ARM Integrator) Fiasco: Architecture (ARM processor family) Platform (ARM Integrator Platform) CPU (ARM 926 Processor) Unfortunately, after booting boostrap_hello.elf image under qemu-system-arm (the latest 2.8.0 version) there is nothing printed out on the console: $ QEMU_OPTIONS="-machine integratorcp -m 256 -serial mon:stdio -nographic" make qemu E=hello MODULE_SEARCH_PATH=/path/to/fiasco/build/ Do you have any idea what I omitted or what is wrong in my setup? Thank you in advance for your help. -- Piotr Piwko http://www.embedded-engineering.pl/

2 1

read/write to virtual address
by Daniel Krefft 17 Feb '17

17 Feb '17

Hello, while working on a checkpoint/restore mechanism for fiasco.oc, we want to trace read and write (kernel) calls to (virtual) memory. 1) Where are these calls defined? We're just able to find ARM specific calls inside the kernel, which allow writing and reading to/from a virtual address 2) Are these calls (if existent) platform agnostic (user-space)? Is there any kind of interface? Best regards -- Daniel Krefft MSc. Wissenschaftlicher Mitarbeiter Technische Universitaet Muenchen Fakultaet fuer Informatik Lehrstuhl fuer Betriebssysteme Arcisstrasse 21 80333 Muenchen Tel. +49 89 289 18791 daniel.krefft(a)tum.de www.os.in.tum.de/personen/krefft

3 7

About l4linux debug method
by li94575 17 Jan '17

17 Jan '17

Hi all, I have faced a thorny problem, l4linux died occasionally after running into the command line, and there are no errors displayed, pressing the ESC key also cannot enter fiasco jdb-mode. I don't know what caused the problem, can someone provide some methods to help locating this problem? Thanks in advance!

2 7

Memory usage analysis and optimization
by Jesse-SC Chou (周書正) 20 Dec '16

20 Dec '16

Hi L4-hackers, I’m analyzing the memory usage of Fiasco/L4Re/L4Linux. On my platform, there are 128MB physical memory. L4 bootstrap can detect it correctly. ================================================== L4 Bootstrapper Build: #164 拻 12堎 9 11:39:51 CST 2016, 4.8.4 Scanning up to 128 MB RAM, starting at offset 32MB Memory size is 128MB (20000000 - 27ffffff) RAM: 0000000020000000 - 0000000027ffffff: 131072kB Total RAM: 128MB ================================================== The memory regions after boot up and sigma0 loaded: ================================================== Regions of list 'regions' [ 20000000, 200001c7] { 1c8} Root mbi_rt [ 20001000, 20001aff] { b00} Kern fiasco [ 20002000, 20092fff] { 91000} Kern fiasco [ 200c0000, 200c9f43] { 9f44} Sigma0 sigma0 [ 200d0000, 200d6177] { 6178} Sigma0 sigma0 [ 20140000, 20168c27] { 28c28} Root moe [ 20170000, 2017b58b] { b58c} Root moe [ 21000000, 2100e5e3] { e5e4} Boot bootstrap [ 21100000, 21a2dfff] { 92e000} Root Module SIGMA0: Hello! KIP @ 20002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:20000000;20000fff] [0:20093000;200bffff] [0:200ca000;200cffff] [0:200d7000;2013ffff] [4:20140000;20168fff] [0:20169000;2016ffff] [4:20170000;2017bfff] [0:2017c000;210fffff] [4:21100000;21a2dfff] [0:21a2e000;26ffffff] ================================================== The largest unused continuous memory region are at “0x21a2e000 ~ 0x26ffffff”, which is about 85MB. I would like to make continuous memory region larger and have the following ideas and questions: 1. The memory used by bootstrap may be freed after the system bring up. If moving “bootstrap” program to 0x26000000, the “Module” programs can append to “MOE” program. The “Module” will be started “0x207c0000” (aligned to page size 4KB). Thus, I can get larger continuous memory area that originally separated by “bootstrap” program. Is this idea correct ? [ 20170000, 2017b58b] { b58c} Root moe [ 21000000, 2100e5e3] { e5e4} Boot bootstrap [ 21100000, 21a2dfff] { 92e000} Root Module 2. There are a reserved region “0x27000000 ~ 0x27FFFFFF” not shown in boot log. When I traced into program, this region seems used by sigma0. What is this memory used for? I think 16MB is a very large chunk in current embedded system. Can we compute the amount this area really use and shrink to a smaller size? Any suggestion is very appreciated. Thanks. BRs, Jesse

2 2

About IO server settings for DMA in L4Linux
by Jesse-SC Chou (周書正) 12 Dec '16

12 Dec '16

Hi L4-hackers, I'm a newbie of L4 micro-kernel. The Fiasco/L4/L4Linux is really a good design for system architecture in the future. I'm trying to porting the L4 system to my target then evaluate. On my target, there is an DMA controller, which moves data to flash. Originally, Native-Linux uses dma_alloc_coherent() to allocate a DMA-dedicated memory. CPU copies data to that DMA-dedicated memory, then DMA controller moves data from DMA-dedicated memory to flash. In L4Linux, I guess there should be some settings of DMA in I/O server configuration files. I'm searching for an example of configuring DMA-related settings. I use the snapshot “l4re-snapshot-2016082114”. In my current configuration, "DEVICE1" is the DMA controller, "DEVICE2" is the flash, and "DMAMEM" is the DMA-dedicated memory. However, it generates some DMA-related error in boot messages. Such as: IO | no 'iommu' capability found use CPU-phys for DMA IO | warning: inconsistent fixed resource @ device: /System Bus/ error: failed to get physical address for 2000000. And so on. The first thing I want to do is to make the boot message correct and I have the following questions: 1. Is the "DMAMEM" device needed to be configured? If needed, how to specify this to be a DMA memory? 2. Will dma_alloc_coherent() use the "DMAMEM" or other memory? Can I use dma_alloc_coherent() as Native-Linux? 3. I've also found a flag "Property.flags = Io.Hw_device_DF_dma_supported;". I'm not sure its usage. I just add this flag to DEVICE1(DMA controller) and DEVICE2(flash), is it correct? 4. Is my l4linux-io.devs and l4linux-io.io correct or need other modification for DMA? 5. I’ve found “IO | DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6)” in the boot message. What the “DMADOM” means? Any suggestion is very appreciated. Thanks. BRs, Jesse Here is my configurations: ---------------------------------------- l4linux-io.cfg: local L4 = require("L4"); loader = L4.default_loader; local lxname = "vmlinuz"; vbus_l4linux = loader:new_channel(); loader:start( { caps = { sigma0 = L4.cast(L4.Proto.Factory, L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; l4linux = vbus_l4linux:svr(); }, log = {"IO", "magenta"}, }, "rom/io -vvv rom/l4linux-io.devs rom/l4linux-io.io"); -- Start Linux loader:start( { caps = { vbus = vbus_l4linux; }, l4re_dbg = L4.Dbg.Warn, log = L4.Env.log:m("rws"), }, "rom/vmlinuz mem=64M console=ttyLv0 l4x_dtb=rom/simple.dtb l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 ramdisk_size=3072"); ---------------------------------------- l4linux-io.devs: local Res = Io.Res local Hw = Io.Hw Io.hw_add_devices(function() DEVICE1 = Hw.Device(function() Property.hid = "device1"; compatible = {"arm,device1"}; Resource.regs = Res.mmio(0x14000000, 0x15ffffff); Property.flags = Io.Hw_device_DF_dma_supported; end); DEVICE2 = Hw.Device(function() Property.hid = "device2"; compatible = {"arm,device2"}; Resource.regs = Res.mmio(0x1F000000, 0x1F3fffff); Resource.irq = Res.irq(66); Property.flags = Io.Hw_device_DF_dma_supported; end); DMAMEM = Hw.Device(function() Property.hid = "dmamem"; compatible = {"arm,dmamem"}; Resource.mmio = Io.Mmio_data_space(0x10000, 0); end); end) ---------------------------------------- l4linux-io.io: local hw = Io.system_bus() Io.add_vbus("l4linux", Io.Vi.System_bus { DEVICE1 = wrap(hw:match("arm,device1")); DEVICE2 = wrap(hw:match("arm,device2")); DMAMEM = wrap(hw:match("arm,dmamem")); }) ---------------------------------------- boot messages: L4 Bootstrapper Build: #164 拻 12堎 9 11:39:51 CST 2016, 4.8.4 Scanning up to 128 MB RAM, starting at offset 32MB Memory size is 128MB (20000000 - 27ffffff) RAM: 0000000020000000 - 0000000027ffffff: 131072kB Total RAM: 128MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 13 modules behind 21100000 moving module 02 { 219d5000-21a064ab } -> { 21ac6000-21af74ab } [201900] moving module 01 { 219c3000-219d434b } -> { 21ab4000-21ac534b } [70476] moving module 00 { 2193d000-219c29db } -> { 21a2e000-21ab39db } [547292] moving module 12 { 21935000-2193cd5d } -> { 21a26000-21a2dd5d } [32094] moving module 11 { 21635000-21934fff } -> { 21726000-21a25fff } [3145728] moving module 10 { 2121b000-21634487 } -> { 2130c000-21725487 } [4297864] moving module 09 { 2121a000-2121a0fa } -> { 2130b000-2130b0fa } [251] moving module 08 { 21219000-2121939b } -> { 2130a000-2130a39b } [924] moving module 07 { 2109e000-212188db } -> { 2118f000-213098db } [1550556] moving module 06 { 21084000-2109d583 } -> { 21175000-2118e583 } [103812] moving module 05 { 2102a000-210836b7 } -> { 2111b000-211746b7 } [366264] moving module 04 { 21010000-21029473 } -> { 21101000-2111a473 } [103540] moving module 03 { 2100f000-2100f325 } -> { 21100000-21100325 } [806] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page (via ELF) at 20002000 Regions of list 'regions' [ 20000000, 200001c7] { 1c8} Root mbi_rt [ 20001000, 20001aff] { b00} Kern fiasco [ 20002000, 20092fff] { 91000} Kern fiasco [ 200c0000, 200c9f43] { 9f44} Sigma0 sigma0 [ 200d0000, 200d6177] { 6178} Sigma0 sigma0 [ 20140000, 20168c27] { 28c28} Root moe [ 20170000, 2017b58b] { b58c} Root moe [ 21000000, 2100e5e3] { e5e4} Boot bootstrap [ 21100000, 21a2dfff] { 92e000} Root Module found kernel options (via ELF) at 20003000 API Version: (87) experimental Sigma0 config ip:200c0100 sp:00000000 Roottask config ip:2014020c sp:00000000 Starting kernel fiasco at 200012b8 Realview System ID: Rev=0 HBI=000 Build=0 Arch=0 FPGA=00 Invalid System ID for this kernel config Expected (00000000 & cfffff00) == 0190f500 Stopping. Hello from Startup::stage2 Number of IRQs available at this GIC: 160 FPU: Initialize FPU0: Subarch: 2, Part: 30, Rev: 5, Var: 7, Impl: 41 ARM generic timer: freq=6000000 interval=6000 cnt=18158508199882336289 SERIAL ESC: allocated IRQ 98 for serial uart Not using serial hack in slow timer handler. Welcome to L4/Fiasco.OC! L4/Fiasco.OC microkernel on arm Rev: r72 compiled with gcc 4.8.4 for Realview [] Build: #16 Tue Nov 29 12:16:44 CST 2016 Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 20002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:20000000;20000fff] [0:20093000;200bffff] [0:200ca000;200cffff] [0:200d7000;2013ffff] [4:20140000;20168fff] [0:20169000;2016ffff] [4:20170000;2017bfff] [0:2017c000;210fffff] [4:21100000;21a2dfff] [0:21a2e000;26ffffff] IOMEM:---------------------- [0:0;1fffffff] [0:28000000;ffffffff] MOE: Hello world MOE: found 104420 KByte free memory MOE: found RAM from 20000000 to 27000000 MOE: allocated 112 KByte for the page array @0x20093000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:103000] BOOTFS: [21100000-21100326] [C:105000] l4linux-io.cfg BOOTFS: [21101000-2111a474] [C:107000] l4re BOOTFS: [2111b000-211746b8] [C:109000] ned BOOTFS: [21175000-2118e584] [C:10b000] hello BOOTFS: [2118f000-213098dc] [C:10d000] io BOOTFS: [2130a000-2130a39c] [C:10f000] l4linux-io.devs BOOTFS: [2130b000-2130b0fb] [C:111000] l4linux-io.io BOOTFS: [2130c000-21725488] [C:113000] vmlinuz BOOTFS: [21726000-21a26000] [C:115000] ramdisk-arm.rd BOOTFS: [21a26000-21a2dd5e] [C:117000] simple.dtb MOE: cmdline: moe rom/l4linux-io.cfg MOE: Starting: rom/ned rom/l4linux-io.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4linux-io.cfg' IO | Io service IO | Verboseness level: 4 IO | unused physical memory space: IO | [00000000000000-0000001fffffff] IO | [00000028000000-000000ffffffff] IO | no 'iommu' capability found use CPU-phys for DMA IO | Loading: config 'rom/l4linux-io.devs' IO | warning: inconsistent fixed resource @ device: /System Bus/ IO | : hid=device1 IO | DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6) IO | warning: inconsistent fixed resource @ device: /System Bus/ IO | : hid=device2 IO | DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6) IO | Loading: config 'rom/l4linux-io.io' IO | Real Hardware ----------------------------------- IO | System Bus: hid= IO | Resources: ==== start ==== IO | DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6) IO | Resources: ===== end ===== IO | DEVICE1: hid=device1 IO | Clients: ===== start ==== IO | DEVICE1: [N2Vi9Proxy_devE] IO | Clients: ===== end ==== IO | Resources: ==== start ==== IO | IOMEM [00000014000000-00000015ffffff 2000000] non-pref (32bit) (align=1ffffff flags=2) IO | DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6) IO | Resources: ===== end ===== IO | DEVICE2: hid=device2 IO | Clients: ===== start ==== IO | DEVICE2: [N2Vi9Proxy_devE] IO | Clients: ===== end ==== IO | Resources: ==== start ==== IO | IOMEM [0000001f000000-0000001f3fffff 400000] non-pref (32bit) (align=3fffff flags=2) IO | IRQ [00000000000042-00000000000042 1] none (32bit) (align=0 flags=1) IO | DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6) IO | Resources: ===== end ===== IO | DMAMEM: hid=dmamem IO | Clients: ===== start ==== IO | DMAMEM: [N2Vi9Proxy_devE] IO | Clients: ===== end ==== IO | Resources: ==== start ==== IO | IOMEM [00000020124000-00000020133fff 10000] non-pref (32bit) (align=ffff flags=2) IO | Resources: ===== end ===== IO | warning: could not register control interface at cap 'platform_ctl' IO | Ready. Waiting for request. PH 0 offs=00008000 flags=rwx PH-type=0x1 virt=02000000 evirt=0248c17c phys=02000000 ephys=0248c17c f_sz=004023d5 memsz=0048c17c PH 1 offs=003b7404 flags=r-x PH-type=0x4 virt=023af404 evirt=023af428 phys=023af404 ephys=023af428 f_sz=00000024 memsz=00000024 PH 2 offs=00000000 flags=rwx PH-type=0x6474e551 virt=00000000 evirt=00000000 phys=00000000 ephys=00000000 f_sz=00000000 memsz=00000000 Starting binary at 0x2000330, argc=7 argv=0xafff4f8c *argv=0xb1007ff4 argv0=rom/vmlinuz External resolver is at 0xa80007c4 ======> L4Linux starting... <======== Linux version 4.7.0-l4 (jesse@tplabpcu07640) (gcc version 4.8.4 (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1) ) #119 Thu Dec 8 18:05:42 CST 2016 Binary name: rom/vmlinuz This is an AEABI build. Linux kernel command line (6 args): mem=64M console=ttyLv0 l4x_dtb=rom/simple.dtb l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=3072 CPU mapping (l:p)[1]: 0:0 Image: 02000000 - 02600000 [6144 KiB]. Areas: Text: 02000000 - 023af428 [3773kB] RO-Data: 022c7000 - 02397000 [832kB] Data: 023d8000 - 023fda80 [150kB] Init: 023b0000 - 023d8000 [160kB] BSS: 024023d5 - 0248c17c [551kB] Device scan: Device: L4ICU Device: DMAMEM MEM: 20124000 - 20133fff Device: DEVICE1 MEM: 14000000 - 15ffffff DMAD: 00000000 - 00000000 Device: DEVICE2 MEM: 1f000000 - 1f3fffff IRQ: 00000042 - 00000042 DMAD: 00000000 - 00000000 Device scan done. l4lx_thread_create: Created thread 41d (cpu0) (u:b3000e00, v:b3000c00, sp:023d9fa4) main thread will be 41d L4x: section-with-init(-data): Virt: 0x2000000 to 0x248cfff [4660 KiB] section-with-init(-data): Phys: 0x2017c000 to 0x20608fff, [4660 KiB] L4x: section-with-init-text: Virt: 0x2000000 to 0x248cfff [4660 KiB] error: failed to get physical address for 2000000. L4x: Main thread running, waiting... L4x: Memory size: 64MB L4x: Setting superpages for main memory L4x: Adjusted memory start: 02000000 L4x: Main memory: Virt: 0x2600000 to 0x65fffff [65536 KiB] Main memory: Phys: 0x21c00000 to 0x25bfffff, [65536 KiB] l4x: vmalloc area: 06600000 - 0e600000 L4x: text: Virt: 0x2000000 to 0x248cfff [4660 KiB] error: failed to get physical address for 2000000. Loading: rom/ramdisk-arm.rd INITRD: Size of RAMdisk is 3072KiB RAMdisk from 00002000 to 00302000 [3072KiB] l4lx_thread_create: Created thread 422 (timer0) (u:b3000a00, v:00000000, sp:02423fa0) IO | new iomem region: p=1f000000 v=400000 s=400000 (bmb=0x34470) Booting Linux on physical CPU 0x0 Linux version 4.7.0-l4 (jesse@tplabpcu07640) (gcc version 4.8.4 (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1) ) #119 Thu Dec 8 18:05:42 CST 2016 DTB: virt=02600100 phys=21c00100 CPU: Fiasco [410fc075] revision 5 (ARMv7), cr=00400000 CPU: div instructions available: patching division code CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine model: L4Linux (DT) Memory policy: Data cache writealloc CPU: All CPU(s) started in SVC mode. INITRD: 00002000 - 00302000 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 17717 Kernel command line: mem=64M console=ttyLv0 l4x_dtb=rom/simple.dtb l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=3072 PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 64632K/71684K available (2941K kernel code, 150K rwdata, 832K rodata, 160K init, 551K bss, 7052K reserved, 0K cma-reserved) Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xfff00000 (3072 kB) vmalloc : 0x06600000 - 0x0e600000 ( 128 MB) lowmem : 0x00000000 - 0x06600000 ( 102 MB) modules : 0x01010000 - 0x02000000 ( 15 MB) .text : 0x02000000 - 0x023af428 (3774 kB) .init : 0x023b0000 - 0x023d8000 ( 160 kB) .data : 0x023d8000 - 0x023fda80 ( 151 kB) .bss : 0x024023d5 - 0x0248c17c ( 552 kB) NR_IRQS:282 clocksource: l4kipclk: mask: 0xffffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 3526361616960 ns l4timer: Using IRQ210 sched_clock: 64 bits at 1000kHz, resolution 1000ns, wraps every 2199023255500ns __l4x_ioremap: Mapping physaddr 1f000000 [0x400000 Bytes, 1f000000+400000] to 00400000+000000 clocksource_probe: no matching clocksources found Console: colour dummy device 80x30 console [ttyLv0] enabled Calibrating delay loop... 1594.16 BogoMIPS (lpj=7970816) 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 Setting up static identity map for 0x2000000 - 0x2000000 VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5 clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations Failed to create "l4x" debugfs directory: 1 clocksource: Switched to clocksource l4kipclk NET: Registered protocol family 2 TCP established hash table entries: 1024 (order: 0, 4096 bytes) TCP bind hash table entries: 1024 (order: 0, 4096 bytes) TCP: Hash tables configured (established 1024 bind 1024) UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 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: -1, 3072 bytes) workingset: timestamp_bits=29 max_order=14 bucket_order=0 squashfs: version 4.0 (2009/01/31) Phillip Lougher jffs2: version 2.2. ? 2001-2006 Red Hat, Inc. io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) L4 serial driver serial-ttyLv.0: ttyLv0 at MMIO 0x1 (irq = 211, base_baud = 230400) is a L4-vcon l4ser_shm: L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded l4bdds: No name given, not starting. mousedev: PS/2 mouse device common for all mice IO | new iomem region: p=14000000 v=2000000 s=2000000 (bmb=0x344f8) __l4x_ioremap: Mapping physaddr 14000000 [0x2000000 Bytes, 14000000+2000000] to 0e600000+000000 Creating 1 MTD partitions on "NOR_FLASH": 0x000000f00000-0x000001000000 : "DATA" NET: Registered protocol family 17 L4IRQ: set irq type of 211 to 1 RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 3072KiB [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 (ram0): mounted filesystem without journal. Opts: (null) VFS: Mounted root (ext2 filesystem) readonly on device 1:0. Freeing unused kernel memory: 160K (023b0000 - 023d8000) This architecture does not have kernel memory protection. Please press Enter to activate this console.

2 3

Fwd: Microkernels / Component-based OSes devroom - Call for Participation
by Norman Feske 18 Oct '16

18 Oct '16

Hello L4 hackers, I'd like to invite you to the microkernel developer room at the upcoming FOSDEM in Brussels. Please find the call for participation below. Cheers Norman FOSDEM 2017 - Microkernels / Component-based OSes devroom CALL FOR PARTICIPATION The developers of several free and open-source microkernel-based operating systems will meet at FOSDEM 2017 [1] in Brussels, Belgium and will share a developer room on Saturday of February 04, 2017 [2]. The devroom is currently looking for content in the form of talks and activities related to the area of microkernel-based operating systems. Possible topics include, but are not limited to: * Introduction of a specific OS or framework * Design of subsystems and the general architecture of an OS * Enabling support for hardware (architectures, device drivers) * Used languages and tools * Maintainance and testing * Security and robustness * Trends and challenges * Use cases, experiences, lessons learned and demos Please use the Pentabarf [3] system to submit your proposals and file it under the track “Microkernels and Component-based OS”. You do not need to create a new account if you already have one. When in doubt, please use the devroom mailing list [4]. If you do not want to give a talk yourself, you may still send suggestions for what else you would like to see, or do in the devroom. Please send your suggestions to the mailing list. The deadline for your proposal is on December the 4th. Make sure to include the following in your proposal: * Title of your talk (will be printed in the FOSDEM booklet) * Your full name (will be printed in the FOSDEM booklet) * A short abstract (one or two paragraphs) * Duration of your talk (please, at least 25 and no longer than 45 min) The official devroom schedule (along with the accepted talks) will be announced on December the 11th on the devroom's mailing list and the speakers will be notified via e-mail. The schedule will also be published on the FOSDEM website. About FOSDEM FOSDEM is a two-day event organised by volunteers to promote the widespread use of free and open source software. Taking place in the beautiful city of Brussels (Belgium), FOSDEM is widely recognised as the best such conference in Europe. FOSDEM covers a wide spectrum of free and open source software projects, and offers a platform for people to collaborate. To this end, FOSDEM has set up developer rooms (devrooms) with network/internet connectivity and projectors where teams can meet and showcase their projects. Devrooms are a place for teams to discuss, hack and publicly present latest directions, lightning talks, news and discussions. Besides developer rooms, FOSDEM also offers main tracks, lightning talks, certification exams and project stands. Every year, FOSDEM hosts more than 5000 developers at the ULB Solbosch campus. Participation and attendance is totally free, though the organisers gratefully accept donations and sponsorship. No registration necessary. About the devroom Since the first Microkernel devroom in 2012 this devroom has been part of each following FOSDEM. By now it has become a somewhat institutionalized tradition for the micro kernel community to meet there; to this date over a dozen projects have participated in one way or another. Each of the projects face similar challenges but come up with partially differend solutions. Therefore, the goal of the Microkernel devroom is to bring the various projects together, let them exchange ideas, cross-pollinate and socialize. Social events It also has become a habit that the microkernel projects dine together somewhere in downtown Brussels after the devroom closes. The year 2017 will not be any different, so there is going to be a microkernel family dinner on Saturday night. The exact location and time will be specified later. Consult the FOSDEM web and other projects for additional social events such as the famous FOSDEM-organized Friday Beer Event and the FOSDEM-arranged free sightseeing tours for spouses. Important dates recap * 04.12.2016: Deadline for submissions * 11.12.2016: Schedule published and speakers notified of acceptance * 04.02.2017: The devroom takes places Links [1] http://fosdem.org/ [2] https://fosdem.org/2017/practical/transportation/ [3] https://fosdem.org/submit [4] https://lists.fosdem.org/listinfo/microkernel-devroom See you all at FOSDEM!

1 0

fiasco.oc i.MX7d port
by Marc CHALAND 14 Oct '16

14 Oct '16

Hi, I'm trying to port fiasco.oc to i.MX7d. It works, but I cannot start second core. I set trampoline addr into corresponding GPR and enables CORE1. But nothing happens. I saw that trampoline assembler code enables SCU through external registers. But with cortex a7, SCU hasn't got external registers. So, I ifdefed it but CPU0 still doesn't startup. Can somebody help me ? Regards Marc

2 7

L4Linux stop at "Calibrating delay loop ..."
by li94575 09 Oct '16

09 Oct '16

Hi，l4hackers I compiled the l4re-snapshot-2014092821 with the default modules.list, and everything seems goes well. However, L4Linux would stop at "Calibrating delay loop ...", because the value of jiffies did not change. Timer thread has not generate soft interrupt? If I entered jdb via ESC at this time, and quit via "g", then l4linux can run again. It makes me confused so much. Any help or suggestion will be very welcome. The log is showing below: L4 Bootstrapper Build: #12 2016年 09月 19日星期一 18:58:15 CST, 4.8.3 20140320 (prerelease) Scanning up to 2048 MB RAM, starting at offset 32MB Memory size is 2048MB (00000000 - 7fffffff) RAM: 0000000000000000 - 000000007fffffff: 2097152kB Total RAM: 2048MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 10 modules behind 1100000 moving module 02 { 1968000-19a163f } -> { 1a58000-1a9163f } [235072] moving module 01 { 195e000-196738b } -> { 1a4e000-1a5738b } [37772] moving module 00 { 18f8000-195d9db } -> { 19e8000-1a4d9db } [416220] moving module 09 { 15f8000-18f7fff } -> { 16e8000-19e7fff } [3145728] moving module 08 { 11d6000-15f7497 } -> { 12c6000-16e7497 } [4330648] moving module 07 { 11d5000-11d50bc } -> { 12c5000-12c50bc } [189] moving module 06 { 107e000-11d446f } -> { 116e000-12c446f } [1401968] moving module 05 { 107d000-107d19b } -> { 116d000-116d19b } [412] moving module 04 { 102a000-107cc1f } -> { 111a000-116cc1f } [338976] moving module 03 { 1010000-1029473 } -> { 1100000-1119473 } [103540] 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, 72fff] { 71000} Kern fiasco [ 73000, 7315f] { 160} Root mbi_rt [ 90000, 96edf] { 6ee0} Sigma0 sigma0 [ 98000, 9e177] { 6178} Sigma0 sigma0 [ 140000, 171d8f] { 31d90} Root moe [ 178000, 1934ab] { 1b4ac} Root moe [ 1000000, 100f58b] { f58c} Boot bootstrap [ 1100000, 19e7fff] { 8e8000} Root Module API Version: (87) experimental Sigma0 config ip:00090100 sp:00000000 Roottask config ip:00140260 sp:00000000 Starting kernel fiasco at 000012e0 Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf0061720-0xf00620e8) Number of IRQs available at this GIC: 128 FPU0: Arch: Unkn(2), Part: VFPv3(30), r: 5, v: 7, i: 41, t: hard, p: dbl/sngl ARM generic timer: freq=1000000 interval=1000 cnt=-262144 SERIAL ESC: allocated IRQ 89 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: 8fd26ca-dirty compiled with gcc 4.8.3 for [] Build: #3 Mon Sep 19 18:55:38 CST 2016 Per_cpu_data_alloc: (orig: 0xf0061720-0xf00620e8) Allocate 2504 bytes (2KB) for CPU[4] local storage (offset=118a8e0, 0xf11ec000-0xf11ec9c8) cpu1: powered-up Per_cpu_data_alloc: (orig: 0xf0061720-0xf00620e8) cpu2: powered-up Allocate 2504 bytes (2KB) for CPU[1] local storage (offset=118c8e0, 0xf11ee000-0xf11ee9c8) cpu3: powered-up FPU1: Arch: Unkn(2), Part: VFPv3(30), r: 5, v: 7, i: 41, t: hard, p: dbl/sngl Calibrating timer loop... Per_cpu_data_alloc: (orig: 0xf0061720-0xf00620e8) done. Allocate 2504 bytes (2KB) for CPU[2] local storage (offset=118f8e0, 0xf11f1000-0xf11f19c8) Cache config: ON MDB: use page size: 30 FPU2: Arch: Unkn(2), Part: VFPv3(30), r: 5, v: 7, i: 41, t: hard, p: dbl/sngl ID_PFR[01]: 00001131 00011011Per_cpu_data_alloc: (orig: 0xf0061720-0xf00620e8) MDB: use page size: 21 Allocate 2504 bytes (2KB) for CPU[3] local storage (offset=11968e0, 0xf11f8000-0xf11f89c8) ID_[DA]FR0: 02010555 00000000 Cache config: ON MDB: use page size: 12 FPU3: Arch: Unkn(2), Part: VFPv3(30), r: 5, v: 7, i: 41, t: hard, p: dbl/sngl ID_PFR[01]: 00001131 00011011SID_MMFR[04]: 10101105 40000000 01240000 02102211 Cache config: ON ID_[DA]FR0: 02010555 00000000 ID_PFR[01]: 00001131 00011011ID_MMFR[04]: 10101105 40000000 01240000 02102211 ICPU[2]: goes to idle loop ID_[DA]FR0: 02010555 00000000 GID_MMFR[04]: 10101105 40000000 01240000 02102211 CPU[1]: goes to idle loop CPU[3]: goes to idle loop MA0: Hello! KIP @ 2000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:0;fff] [4:73000;73fff] [0:74000;8ffff] [0:97000;97fff] [0:9f000;13ffff] [4:140000;171fff] [0:172000;177fff] [4:178000;193fff] [0:194000;10fffff] [4:1100000;19e7fff] [0:19e8000;3effffff] [0:40000000;7fffffff] IOMEM:---------------------- [0:80000000;ffffffff] MOE: Hello world MOE: found 2070816 KByte free memory MOE: found RAM from 73000 to 80000000 MOE: allocated 2047 KByte for the page array @0x194000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [1100000-1119474] [C:503000] l4re BOOTFS: [111a000-116cc20] [C:504000] ned BOOTFS: [116d000-116d19c] [C:505000] l4lx.cfg BOOTFS: [116e000-12c4470] [C:506000] io BOOTFS: [12c5000-12c50bd] [C:507000] arm-rv.io BOOTFS: [12c6000-16e7498] [C:508000] vmlinuz.arm BOOTFS: [16e8000-19e8000] [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=024c8dd4 l4linux | phys= 02000000 ephys=024c8dd4 l4linux | f_sz= 00404594 memsz=004c8dd4 flgs=rwx l4linux | PH 1 (t: 4) offs=003b44e0 vaddr=023ac4e0 vend=023ac504 l4linux | phys= 023ac4e0 ephys=023ac504 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 0x2000360, argc=8 argv=0xafff4f84 *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa8000788 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.16.0-l4 (li94575@li94575-Lenovo) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #3 SMP Mon Sep 19 18:57:16 CST 2016 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (7 args): mem=64M l4x_cpus=4 l4x_cpus_map=0,1,2,3 console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 l4linux | CPU mapping (l:p)[4]: 0:0, 1:1, 2:2, 3:3 l4linux | Image: 020000a0 - 02600000 [6143 KiB]. l4linux | Areas: Text: 020000a0 - 023d6000 [3927kB] (a bit longer) l4linux | Data: 023d6000 - 023ff520 [165kB] l4linux | Initdata: 023ad000 - 023d57c0 [161kB] l4linux | BSS: 02404594 - 024c8dd4 [786kB] l4linux | Device scan: l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:023d7fa4) l4linux | main thread will be 413 l4linux | l4x_register_pointer_section: addr = 02000000 size = 5017600 l4linux | section-with-init: Virt: 0x2000000 to 0x24c8dd3 [4899 KiB] l4linux | section-with-init: Phys: 0x0042b000 to 0x008f3dd3, [4899 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: 0x2600000 to 0x65fffff [65536 KiB] l4linux | Main memory: Phys: 0x01a00000 to 0x059fffff, [65536 KiB] l4linux | l4x: vmalloc area: 06600000 - 0e600000 l4linux | l4x_register_pointer_section: addr = 02000000 size = 5017600 l4linux | text: Virt: 0x2000000 to 0x24c8dd3 [4899 KiB] l4linux | text: Phys: 0x0042b000 to 0x008f3dd3, [4899 KiB] l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] l4linux | l4lx_thread_create: Created thread 419 (timer0) (u:b3000a00, v:00000000, sp:0245dfa0) Booting Linux on physical CPU 0x0 Linux version 3.16.0-l4 (li94575@li94575-Lenovo) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #3 SMP Mon Sep 19 18:57:16 CST 2016 CPU: Fiasco [410fc075] revision 5 (ARMv7), cr=00000000 CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing 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 - 00302000 PERCPU: Embedded 5 pages/cpu @06509000 s6080 r0 d14400 u32768 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 17716 Kernel command line: mem=64M l4x_cpus=4 l4x_cpus_map=0,1,2,3 console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 64728K/71680K available (3157K kernel code, 165K rwdata, 604K rodata, 161K init, 786K bss, 6952K reserved) Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xffe00000 (2048 kB) vmalloc : 0x06600000 - 0x0e600000 ( 128 MB) lowmem : 0x00000000 - 0x06600000 ( 102 MB) .text : Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xffe00000 (2048 kB) vmalloc : 0x06600000 - 0x0e600000 ( 128 MB) loHierarchical RCU implementation. 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...

3 7