- l4-hackers - example.com Site

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 (周書正) 13 Dec '16

13 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

Is L4Linux can use its existed Linux driver to access hardware device?
by Zhe Zhao 14 Sep '16

14 Sep '16

Hi, After read the basic ideas of L4Linux I have some questions related to it. Is L4Linux run as a paravirtualization VM on L4Re? Then the traditional Linux Process just still compiled against Linux system and put them together with L4Linux disk image? so it means L4Re works like qemu and Linuxl? or L4Re works as a micro kernel operating system, and L4Linux run as a process on it, all devices handled to L4Linux to reuse the drivers of L4Linux? and the previous Linux process compiled with Linux, but run direct on L4Re as L4 processes which communicate with L4Linux through IPC? it is quite confused after read a little of the codes, in L4Linux, seems there is some injection of L4 task stuffs inside thread_struct of Linux, but also have some vCPU related stuffs, can you help me about what is the real behavior of L4Linux? I'm sorry to ask this basic questions, but after some digging I feel quite confused about how it works. Thanks Br Alex

2 7

Partitioned Scheduling
by Edinger, Stefan 09 Sep '16

09 Sep '16

Hi, is it possible to have partitioned scheduling in the way that one can use different schedulers for different cpu-cores? And if yes, can I do the mapping from scheduler to core on runtime or is it done at compile time? Thanks, Stefan

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

Genode + Fiasco.OC: How to access multiple run queues?
by Guru Siddesh 08 Aug '16

08 Aug '16

Hello L4-hackers , I'm writing a Genode component which should access and modify the Run queues of the scheduler. Based on what I have read and looked there will be one scheduler for each processor. How to access the different scheduler objects and Run queues from Genode side? I have looked through the code and able to print the run queue from the ready_queue_fp.cpp. But how do you access 2 run queues when number of processors is more than one? And what is the easy way to manipulate these from Genode component.? PS: I have read Genode book and have a basic idea of Genode architecture. Best regards, Guru

2 1

memory map/unmap performance
by Yuxin Ren 02 Aug '16

02 Aug '16

Hi all, I am curious memory mapping/unmapping performance. Are there any applications that stress the memory mapping and unmapping utility? Thanks a lot! Yuxin

2 1

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

where can I download the previous version of L4linux?
by li94575 07 Jul '16

07 Jul '16

Hi, I want to use L4linux3.5 and L4linux3.10, but L4linux SVN repository and l4re-snapshot both are the latest release. Can anyone tell me where to download it? Thank you!

2 3

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

04 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

1 0

building fiasco on alpine linux
by Michael Schnupp 27 Jun '16

27 Jun '16

Hi, I tried to build fiasco on alpine linux. This will fail with the following line: auto/jdb_ktrace.cc:1:0: error: code model kernel does not support PIC mode Their gcc enables PIC per default for security reasons. Since fiasco seems to need PIC disabled I have to tell the build system either to add -fno-PIC explictly, or to -D__KERNEL__ in any way. (I already tried DEFINES += -D__KERNEL__ or CFLAGS := -fno-PIC in Makeconf without success.) What is the correct way to add such an option to the fiasco build system? Would it hurt to add -D__KERNEL__ per default on future releases? (After all it *is* a kernel.) BTW, the above file looks very much like a jdb file. Is it correct that this file is compiled even when I configured fiasco to not include jdb? BR, Michael

2 6

Cross-compiling L4Re for MIPS32
by Paul Boddie 22 Jun '16

22 Jun '16

Hello, I finally got round to looking at L4/Fiasco.OC again, and having previously looked at the MIPS32 port that was made available on GitHub... https://github.com/MIPS/fiasco-l4re ...I have been attempting to cross-compile Fiasco and L4Re using the l4re.org sources. Getting Fiasco to cross-compile was mostly a matter of repeating the same procedure as last time: cd src/kernel/fiasco make BUILDDIR=mybuild cd mybuild/ make config make However, I needed to edit src/kernel/fiasco/src/Makeconf.mips32 to change the compiler settings. I'm using the toolchains in Debian unstable: CROSS_COMPILE ?= mipsel-linux-gnu- Previously, I used a Makeconf.local file to set the following: SYSTEM_TARGET=mipsel-linux-gnu- SHARED_FLAGS=-mips32r2 -EL -msoft-float -mno-abicalls -fno-pic Maybe the previous work used some different mechanisms to those used by the more general source distribution, but this trick didn't seem to influence the build successfully this time around. However, the build did complete successfully with the toolchain set appropriately. Meanwhile, I had more problems with the L4Re part. I had expected to be able to do the following: cd src/l4 make B=mybuild make O=mybuild config make O=mybuild E=mips-fbspectrum (The target was something that I had managed to build previously after some messing around with packages and configuration files. I'd managed to build the fbspectrum example for Fiasco.OC-UX, as the list archives will attest.) However, I also had to change the compiler settings (as done above) in src/l4/mk/arch/Makeconf.mips, instead of using src/l4/Makeconf.local (as done previously). Again, maybe the way of doing things was different in the previous incarnation of this port. I also needed to edit src/l4/tool/gendep/syscall.c to add a definition before unistd.h gets included: #define __ARCH_WANT_SYSCALL_NO_AT I can't remember if I or anyone else has mentioned this before now, but without it, things like __NR_open are not defined. Unfortunately, I haven't yet reached a satisfactory conclusion in this latter exercise. Looking back at my previous messages, it seems that a bit more work might be needed to configure and build a suitable target, and so I was wondering if anyone had done this (and written it up) for any of the MIPS boards, perhaps the CI20. Indeed, I wonder if things like the framebuffer are even supported for the CI20 or other MIPS boards. Paul

2 10

L4Linux Compilation trouble with missing packages in L4
by Martin Gruber 13 Jun '16

13 Jun '16

Dear L4 community, i started diving into L4 stuff recently and it looks really interesting. Currently I am trying to get L4Linux working on top of Fiasco.OC. After configuring the L4 Kernel, I am getting following error message at build: ---------------------------------------------------------------------------- make O=../build/ make[1]: Entering directory '/home/gruber/l4re/l4linux/build' Package shmc was not found in the pkg-config search path. Perhaps you should add the directory containing `shmc.pc' to the PKG_CONFIG_PATH environment variable No package 'shmc' found Package rtc was not found in the pkg-config search path. Perhaps you should add the directory containing `rtc.pc' to the PKG_CONFIG_PATH environment variable No package 'rtc' found Getting required compilation flags failed. L4OBJ: /home/gruber/l4re/src/l4/l4build L4_REQUIRED_MODS: libc_be_minimal_log_io libc_minimal libc_minimal_l4re libsupc++_minimal log l4re_c-util libio libvcpu shmc rtc arch/l4/Makefile:391: *** Aborting.. Stop. make[1]: Leaving directory '/home/gruber/l4re/l4linux/build' Makefile:146: recipe for target 'sub-make' failed make: *** [sub-make] Error 2 ---------------------------------------------------------------------------- After checking the mailing list archive i found this question: http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007635.html http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007635.html I checked the l4/builddir/pc for missing libs and did not find them. Compilation of L4 worked fine, L4 also works with the small HelloWorld sample in QEMU. I checked the L4 config but was not able to find appropriate options. Does anyone have an tip for me what I am doing wrong? Thank you very much for your help! Kind Regards, Martin

2 1

Re: l4-hackers Digest, Vol 157, Issue 10
by Иван Филиппов 28 May '16

28 May '16

adam - maasdam ;-) 2016-05-28 13:00 GMT+03:00, l4-hackers-request(a)os.inf.tu-dresden.de <l4-hackers-request(a)os.inf.tu-dresden.de>: > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. L4Re Release (Adam Lackorzynski) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 27 May 2016 13:13:04 +0200 > From: Adam Lackorzynski <adam(a)l4re.org> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: L4Re Release > Message-ID: <20160527111304.GB12441(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > Hi, > > I'm happy to announce a new L4Re release. > > https://l4re.org/ > > This release adds support for the Imagination Technologies' > MIPS architecture, including support for MIPS' > virtualization architecture VZ to run virtual machines such > as Linux. L4Re is currently available for MIPS32, > MIPS64 is about to follow. The MIPS port is supported by > Imagination Technologies. > > > Further noteworthy changes of this release include: > - L4Linux has been updated to L4Linux-4.6 > - Conversion of debugging interface to capability-based > interface. Programs need to have the 'jdb' capability to > use JDB functionality. > - The virtual machines monitor, now called uvmm, supports > the MIPS and ARM architectures. > - A virtio-based peer-to-peer network component is available > in virtio-net. > - Documentation improvements > - Library updates > - Added ARM platforms: > - NXP Layerscape LS1021A > - i.MX28 > - MIPS platforms: > - Malta > - Sead3 > - Ci20 > - Baikal-T > - Bug fixes and small feature enhancements in the kernel and user-level > components: > - Added atomic IRQ re-attach call > - The vCPU data structures have been revised > > > Adam > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > > ------------------------------ > > End of l4-hackers Digest, Vol 157, Issue 10 > ******************************************* > -- Иван Филиппов

1 0

L4Re Release
by Adam Lackorzynski 27 May '16

27 May '16

Hi, I'm happy to announce a new L4Re release. https://l4re.org/ This release adds support for the Imagination Technologies' MIPS architecture, including support for MIPS' virtualization architecture VZ to run virtual machines such as Linux. L4Re is currently available for MIPS32, MIPS64 is about to follow. The MIPS port is supported by Imagination Technologies. Further noteworthy changes of this release include: - L4Linux has been updated to L4Linux-4.6 - Conversion of debugging interface to capability-based interface. Programs need to have the 'jdb' capability to use JDB functionality. - The virtual machines monitor, now called uvmm, supports the MIPS and ARM architectures. - A virtio-based peer-to-peer network component is available in virtio-net. - Documentation improvements - Library updates - Added ARM platforms: - NXP Layerscape LS1021A - i.MX28 - MIPS platforms: - Malta - Sead3 - Ci20 - Baikal-T - Bug fixes and small feature enhancements in the kernel and user-level components: - Added atomic IRQ re-attach call - The vCPU data structures have been revised Adam

1 0

Flexpage: shared Mem
by ba_f 23 May '16

23 May '16

Hello, writing a L4Linux Driver I'm expiring the C-Interface and low level(?) flexpages. So far, I can push a Dataspace Capability via flexpage, and the receiving server is able to read its content. But, whatever the server writes in that mem-region doesn't appear on the clients side. /* client.c */ l4_fpage_t fpage = l4_obj_fpage( dataspace, 0, L4_CAP_FPAGE_RW ); l4_utcb_mr()->mr[0] = size; l4_utcb_br()->br[0] = fpage.raw; /* server.c */ l4_utcb_br()->br[0] = dataspace | L4_RCV_ITEM_SINGLE_CAP; l4_ipc_wait(l4_utcb(), 0, L4_IPC_NEVER); // allocate, and attach Dataspace ... // read & write Dataspace ... l4_utcb_mr()->mr[0] = returnValue; l4_ipc_reply_and_wait(l4_utcb(), l4_msgtag(0, 1, 0, 0), 0, L4_IPC_NEVER); As I am creating the fpage with L4_CAP_FPAGE_RW my guess was I can write to that mem-region and the client can read my changes. Anyway, maybe I need some more understandings about capabilities & flexpages. (Are there any precise slides or papers about this topic?) So, the client creates a dataspace capability and allocates some memory. But, what happens when the flexpage is pushed to the server? The capability is copied and both pointing to the same allocated memory, or is the Cap and(!) the memory it is pointing to copied to server? Thanks, ba_f

2 5

Question about Fiasco.OC support for SPARC
by deng.chao1＠zte.com.cn 12 May '16

12 May '16

Hi everyone： I want to run Fiasco.OS on SPARC-leon3 platform. It seems that Fiasco.OS already has an unimplemented support for SPARC-leon3 according to the latest snapshot fiasco-2015123115 of Fiasco. Does Fiasco.OS support SPARC now? If it does, how can I get the source? If it doesn't, what are the unimplemented parts according to snapshot fiasco-2015123115? And another question, is there any good machine emulator for SPARC-leon3？ I have tried latest version of QEMU, but It doesn't work well on SPARC-leon3. Thanks Dengchao

2 3