- l4-hackers - example.com Site

Fix IO-APIC/IRQ-Routing Bug (affects GSIs 24, 48, 72, ...)
by Christian Ehrhardt 08 Jul '11

08 Jul '11

Hi, there seems to by an off-by-one error in Io_apic::find_apic() that kills IRQ-routing for GSIs that are a multiple of 24. Please consider the patch below (tested on real hardware with 3 IO-APICS). regards Christian diff --git a/src/kernel/fiasco/src/kern/io_apic.cpp b/src/kernel/fiasco/src/kern/io_apic.cpp index 88ffe68..897a1a0 100644 --- a/src/kernel/fiasco/src/kern/io_apic.cpp +++ b/src/kernel/fiasco/src/kern/io_apic.cpp @@ -331,7 +331,7 @@ Io_apic::find_apic(unsigned irqnum) { for (unsigned i = Max_ioapics; i > 0; --i) { - if (_apics[i-1]._apic && _apics[i-1]._offset < irqnum) + if (_apics[i-1]._apic && _apics[i-1]._offset <= irqnum) return i - 1; } return 0;

1 0

Newbie question: L4Linux as a patch
by Pablo Chacin 06 Jul '11

06 Jul '11

Hi all I'm doing a review of options for virtualization in Linux. From the documentation, it seems that L4Linux is a complete port of the Linux Kernel. I'm wondering if there is a patch (or series of patches) that could be used to modify an standard Linux kernel and make it compatible with the L4 virtualization? The question comes from my scenario: I need to deploy a customized linux kernel and want to do so over L4. This kernel is build from the standard kernel applying some patches. I would like to do the same with L4Linux, so the resulting kernel has my patches plus L4. Is this feasible? has been tested? thanks in advance and please consider I'm new to L4Linux. Regards -- ======================================================================== 0 0 0 Pablo Chacin | Dept. d'Arquitectura de Computadors 0 0 0 e-mail: pchacin(a)ac.upc.edu | UPC-Campus Nord. Modul D6-212 0 0 0 phone: +34 +93 405 4059 | Jordi Girona, 1-3 U P C fax: +34 +93 401 7055 | 08034 Barcelona - SPAIN www: http://personals.ac.upc.es/pchacin ========================================================================

2 3

Fiasco.OC Kernel symbolic debugger
by Daniel Waddington 06 Jul '11

06 Jul '11

Hello, Adam, are you likely to get the source-level symbolic debugging working in jdb in the near future? Using objdump is a bit drastic! ;-) Thanks Daniel

2 1

L4 for amd64
by Daniel Müller 05 Jul '11

05 Jul '11

Hi, I have some problems with running L4 for amd64 (i586 is just fine). I am trying to run (qemu-14.1.) the hello world binary and get: --------- L4 Bootstrapper Build: #1 Mi 29. Jun 17:41:45 CEST 2011, x86-64, 4.4.5 RAM: 0000000000000000 - 000000000009f3ff: 637kB RAM: 0000000000100000 - 0000000007ffcfff: 130036kB Total RAM: 127MB Moving 7 modules to 2000000 with offset fa8000 moving module 07 { 1679000-1739a52 } -> { 2621000-26e1a52 } moving module 06 { 1678000-1678039 } -> { 2620000-2620039 } moving module 05 { 1566000-167779e } -> { 250e000-261f79e } moving module 04 { 132d000-1565b9e } -> { 22d5000-250db9e } moving module 03 { 110c000-132cb58 } -> { 20b4000-22d4b58 } moving module 02 { 10be000-110b397 } -> { 2066000-20b3397 } moving module 01 { 1058000-10bdb00 } -> { 2000000-2065b00 } Scanning /fiasco -serial_esc -comspeed 115200 -comport 1 -nokdb This is an invalid binary, fix it (wrong ELF architecture). Key press reboots... Rebooting. --------- This is done with a clean checkout URL: http://svn.tudos.org/repos/oc/tudos/trunk Repository Root: http://svn.tudos.org/repos/oc/tudos Repository UUID: d050ee49-bd90-4346-b210-929a50b99cfc Revision: 33 configured for K8-type CPU. /usr/bin/file tells me: build/obj/bin/amd64_K8/l4f/sigma0: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped build/obj/bin/amd64_K8/l4f/moe: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped build/obj/bin/amd64_K8/l4f/ned: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped build/obj/bin/amd64_K8/l4f/l4re: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped build/obj/bin/amd64_K8/l4f/loader: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped build/obj/bin/amd64_K8/l4f/hello: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped build/obj/bin/amd64_K8/bootstrap: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, not stripped ./../kernel/fiasco/build/fiasco: symbolic link to `main' So why is bootstrap not built as 64 bit binary? Daniel

2 3

libc environment for l4linux
by Vasily Sartakov 04 Jul '11

04 Jul '11

Hello Does l4re snapshot has a libc environment for build a applications for l4linux? what toolchains did you use for build busybox? -- Sartakov A. Vasily

2 1

Fiasco.OC
by Daniel Waddington 03 Jul '11

03 Jul '11

Hi, I want to use 32bit x86 Fiasco.OC with lots of SMP CPUs (48+). Can you tell me where the current 32 (for 32bit) and 64 (for 64bit) limitations exist in the code - and suggest whether this could be changed? Thanks Daniel Waddington

2 1

the booting error of l4linux
by cheng guanghui 01 Jul '11

01 Jul '11

Hello: I downloaded the latest l4re-snapshot-2011062216. All the compilation is ok. The hello demo could boot successfully. But when i try to boot L4Linux with this command : make qemu E=L4Linux-mag-x86 O=/home/cheng/TUDOS/Src/l4re-snapshot-2011062216/obj/l4/x86 There are some errors as following: Allocate cpu_mem @ 0xfc54c000 Local APIC[00]: version=11 max_lvt=5 APIC ESR value before/after enabling: 00000000/00000000 Using the PIT (i8254) on IRQ 2 for scheduling Absolute KIP Syscalls using: Sysenter CPU[0:0]: GenuineIntel (6:3:3:0)[00000633] Model: Pentium II (Klamath) at 2395 MHz 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. SIGMA0: Hello! KIP @ 400000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:1000;9efff] [0:10b000;13ffff] [4:140000;18bfff] [0:18c000;2dcfff] [4:2dd000;2ddfff] [0:2de000;3fffff] [0:465000;136cfff] [4:136d000;166ffff] [0:1670000;1614bfff] IOMEM:---------------------- [0:0;fff] [0:9f000;fffff] [0:17ffd000;febfffff] [0:fec01000;fedfffff] [0:fee01000;ffffffff] IO PORTS-------------------------- [0:0;fffffff] MOE: Hello world MOE: found 357544 KByte free memory MOE: found RAM from 1000 to 1614c000 MOE: allocated 353 KByte for the page array @0x1000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [136d000-1470e6d] [C:503000] l4re BOOTFS: [1471000-166e572] [C:504000] ned BOOTFS: [166f000-166f578] [C:505000] l4lx-gfx.cfg MOE: cmdline: /home/cheng/TUDOS/Src/l4re-snapshot-2011062216/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 | L4Re: FATAL: Exception No such object found: 'rom/io' io | Exception: No such object found: rom/io: backtrace ... fb-drv | L4Re: FATAL: Exception No such object found: 'rom/fb-drv' fb-drv | Exception: No such object found: rom/fb-drv: backtrace ... mag | L4Re: FATAL: Exception No such object found: 'rom/mag' mag | Exception: No such object found: rom/mag: backtrace ... Ned[lua]: Hm, cpapbility 430000 does not support the meta protocol: -2004 Ned: ERROR: rom/l4lx-gfx.cfg:54: attempt to call method 'create' (a nil value) Do i miss something else? Thanks a lot. Warm regards. Cheng Guanghui

2 6

pthread_exit in L4re
by Chen Tian 30 Jun '11

30 Jun '11

Hello, I want a thread to exit after it finishes its job. The function pthread_exit seems not working. I still can see all threads I created through kernel debugger. Any idea? Best, Chen

2 1

Nokia N900 and Fiasco.OC/l4re
by Valery V. Sedletski 29 Jun '11

29 Jun '11

Hi all Is there a possibility to use Fiasco.OC and L4Re with L4Linux on Nokia N900 internet tablet/phone? Which ARM platform it is compatible with, if so? -- It is based on ARM Cortex A8 600 MHz processor, 256 Mb RAM and 784 Mb swap, Maemo (Debian GNU/Linux based) platform (see http://www.gsmarena.com/nokia_n900-2917.php, for example). Or, if not so, is it possible to use it with Genode or OKL4? WBR, valery

3 6

bbclone fbdrv lcd problem
by Vasily Sartakov 23 Jun '11

23 Jun '11

Hello. I try to start ex_fb_spectrum example on beagleboard clone with 7" 480x800 LCD and have error in fbdrv//lcd-omap3.c: when a i call any l4vbus_i2c* and l4vbus_gpio function i have return -38 --- ENOSYS error whats may be wrong? my configs: -------------------------------------- arm-rv-lcd-io: gui => new System_bus() { # KBD => wrap(hw-root.KBD); # MOUSE => wrap(hw-root.MOUSE); } fbdrv => new System_bus() { sys => wrap(hw-root.sys); lcd => wrap(hw-root.lcd); i2c1 => wrap(hw-root.i2c1); gpio => wrap(hw-root.gpio); } ------------------------------------- arm-rv-lcd-cfg require("L4"); local l = L4.default_loader; local io_buses = { gui = l:new_channel(); fbdrv = l:new_channel(); }; l:start({ caps = { gui = io_buses.gui:svr(), fbdrv = io_buses.fbdrv:svr(), icu = L4.Env.icu, sigma0 = L4.cast(L4.Proto.Factory, L4.Env.sigma0):create(L4.Proto.Sigma0), }, log = { "IO", "y" }, l4re_dbg = L4.Dbg.Warn, }, "rom/io rom/arm-omap3-full.devs rom/arm-rv-lcd.io"); local fbdrv_fb = l:new_channel(); l:startv({ caps = { vbus = io_buses.fbdrv, fb = fbdrv_fb:svr(), }, log = { "fbdrv", "r" }, l4re_dbg = L4.Dbg.Warn, }, "rom/fb-drv", "-c", "init"); local mag_caps = { mag = l:new_channel(), svc = l:new_channel(), }; l:start({ caps = { vbus = io_buses.gui, fb = fbdrv_fb, mag = mag_caps.mag:svr(), svc = mag_caps.svc:svr(), }, log = { "mag", "g" }, l4re_dbg = L4.Dbg.Warn, -- scheduler = L4.Env.user_factory:create(L4.Proto.Scheduler, 0xa0, 0x80), }, "rom/mag"); e = l:start({ caps = { fb = mag_caps.svc:create(L4.Proto.Goos, "g=480x480"), }, log = { "spectrum", "b" }, l4re_dbg = L4.Dbg.Warn, -- scheduler = L4.Env.user_factory:create(L4.Proto.Scheduler, 0x18, 0x8), }, "rom/ex_fb_spectrum"); print("ex_fb_spectrum exited with: " .. e:wait()); ------------------------------------ arm-omap3-full.devs: hw-root { sys => new Device() { .hid = "System Control"; new-res Mmio(0x48002000 .. 0x48002fff); new-res Mmio(0x48004000 .. 0x48004fff); } prcm => new Device() { .hid = "OMAP PRCM qq"; new-res Mmio(0x48000000 .. 0x48000fff); new-res Mmio(0x48001000 .. 0x48001fff); new-res Mmio(0x48002000 .. 0x48002fff); new-res Mmio(0x48003000 .. 0x48003fff); new-res Mmio(0x48004000 .. 0x48004fff); new-res Mmio(0x48005000 .. 0x48005fff); } gpio => new Device() { .hid = "gpio"; new-res Mmio(0x48004000 .. 0x48004fff); new-res Mmio(0x48310000 .. 0x48310fff); new-res Mmio(0x49050000 .. 0x49050fff); new-res Mmio(0x49052000 .. 0x49052fff); new-res Mmio(0x49054000 .. 0x49054fff); new-res Mmio(0x49056000 .. 0x49056fff); new-res Mmio(0x49058000 .. 0x49058fff); } lcd => new Device() { .hid = "OMAP_LCD"; new-res Mmio(0x48050000 .. 0x48050fff); } i2c1 => new Device() { .hid = "i2c"; new-res Mmio(0x48070000 .. 0x48070fff); } } -- Sartakov A. Vasily

2 4