l4-hackers November 2012

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

21 participants
21 discussions

App on L4Re
by OSDepend 30 Nov '12

30 Nov '12

Hi, all! I'm newbie on L4 microkernel, and have been confused by some questions of the L4 constructions! Are there any avaliable Applications or Projects directly on the L4Re but not depending On L4Linux? Like gcc or other app? If existed, can we can directly bulild some application or tools after boot L4 microkernel? Every feedbacks or documention links are appreciated! :> Best, Chen 2012-11-23 zhengc

7 14

Qusestion about building L4Re
by FU_LONG 30 Nov '12

30 Nov '12

3 2

Start Linux inside a Vancouver VM using a virtual disk.
by Mehdi AICHOUCH 27 Nov '12

27 Nov '12

Hello, I was trying to run Linux inside a Vancouver virtual machine and using a virtual disk. But, I got an error when Linux kernel try to mount the root file system. I tested the Linux kernel and the virtual disk image using Qemu and it worked well. I was also able to start the same Linux kernel on Vancouver but by providing an initrd ramfs file. Please see below the trace of the linux boot: (5) # [ 23.652175] VFS: Cannot open root device "(null)" or unknown-block(0,0) (5) # [ 23.652175] Please append a correct "root=" boot option; here are the availa (5) # | ble partitions: (5) # [ 23.652175] Kernel panic - not syncing: VFS: Unable to mount root fs on unkn (5) # | own-block(0,0) (5) # [ 23.652175] Pid: 1, comm: swapper/0 Tainted: G W 3.2.16-rt27 #3 (5) # [ 23.652175] Call Trace: (5) # [ 23.652175] [<c05f5299>] panic+0x66/0x173 (5) # [ 23.652175] [<c0849ca1>] mount_block_root+0x1d3/0x26c (5) # [ 23.652175] [<c02311bc>] ? sys_mknod+0x2c/0x30 (5) # [ 23.656100] [<c0849d93>] mount_root+0x59/0x5f (5) # [ 23.656100] [<c0849ee7>] prepare_namespace+0x14e/0x192 (5) # [ 23.656100] [<c0221665>] ? sys_access+0x25/0x30 (5) # [ 23.656100] [<c0849344>] kernel_init+0x13f/0x14e (5) # [ 23.656100] [<c0849205>] ? parse_early_options+0x25/0x25 (5) # [ 23.656100] [<c05fe6c2>] kernel_thread_helper+0x6/0x10 and this is the script I used to run Vancouver and Linux : #!/usr/bin/env novaboot # -*-sh-*- HYPERVISOR_PARAMS=serial WVDESC=Kernel compile inside VM (on virtual disk, EPT + VPID) WVTEST_TIMEOUT=1200 QEMU_FLAGS=-cpu phenom -m 2048M bin/apps/sigma0.nul tracebuffer_verbose S0_DEFAULT hostserial hostvga hostkeyb:0,0x60,1,12 script_start:1,1 \ service_config vdisk_empty:736870912 service_disk bin/apps/vancouver.nul bin/boot/munich imgs/bzImage imgs/mdisk.img vancuver.nulconfig <<EOF sigma0::mem:512 sigma0::dma name::/s0/log name::/s0/timer name::/s0/fs/rom name::/s0/admission name::/s0/disk disk::0 || rom://bin/apps/vancouver.nul PC_PS2 ahci:0xe0800000,14,0x30 drive:0,0,0 || rom://bin/boot/munich || rom://imgs/bzImage clocksource=tsc console=ttyS0 || rom://imgs/mdisk.img EOF Could someone tell me how to correct this error. Or give me some hints to another solution to build a disk image. I need a disk image in order to add some executable that I already compiled on my host machine and to run these executable on the Linux guest OS once it will start on Vancouver VM. Thank you very much in advance for your help. Mehdi

2 2

Our experience with Fiasco.OC + Genode on the Pandaboard
by Norman Feske 26 Nov '12

26 Nov '12

Dear L4 hackers, for those of you who enjoy reading experience reports, we have put together an article that describes our work with enabling the Genode OS Framework on the Pandaboard using the Fiasco.OC kernel: http://genode.org/documentation/articles/pandaboard With the new developed driver support for SD-card, USB, networking, and HDMI in place, we have become able to run a wide variety of Genode system scenarios including the GNU userland, Qt4, GDB, and L4Linux on this nice platform. In addition to creating and porting device drivers, we conducted extensive performance optimizations in order to reach an I/O performance that is roughly on par with native Linux. The article describes those steps in detail. Best regards Norman -- Dr.-Ing. Norman Feske Genode Labs http://www.genode-labs.com · http://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

2 2

Question about L4Linux
by OSDepend 26 Nov '12

26 Nov '12

Hi, I want to know why we build L4Linux here on L4? Is there any benefit comparing to pure Linux? Best, Chen 2012-11-23 郑晨

3 3

Full Virtualization with Trustzone
by meng-qy 25 Nov '12

25 Nov '12

Hi, Adam: Thank you for your reply! > Memory on imx51 is starting at 0x90000000. At 0x60000000 there are > pheripherals, i.e. there's no usable memory where something can be copied > to (or executed). I think we make a wrong understanding about " l4sigma0_map_iomem() " . >If you want to execute something it needs to be in the > region 0x90000000-0xafffffff. A simple trick is to reduce the memory for > secure side (e.g. via imx51.conf) and use the rest for NS. Now, we use 0x90000000-0x9fffffff to run secure side, and revise the vm configuration as following: Ram_base = 0xa1000000, Ram_size = 0x4000000, // 128 MB Start_addr = Ram_base + 0x100000, // +1MB The l4_vm_state is set as: state->pc = Start_addr; state->cpsr = 0x13; //svc state->r[0] = 0; state->r[1] = 0x84D; imx51 //arch num The NS bare app's entry is set as 0xa1100000, but we still stop at "VM run", we use some tracing methods and find the system stop at: // set pending events ldmia r0!, {r1} and r1, r1, #0x1c0 mcr p15, 0, r1, c12, c1, 1 // ivt.S line:954, looks like some ISR pending control. BTW, should we write a virtual-interrupt layer to map the NS call with Secure side? I think maybe NS bare app can not visit the pheripherals address directly. Steven Meng --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. ---------------------------------------------------------------------------------------------------

2 1

Re: l4-hackers Digest, Vol 115, Issue 18
by Death Jester 23 Nov '12

23 Nov '12

> Hi, > > On Wed Nov 21, 2012 at 18:45:25 +0100, Death Jester wrote: >> I have a problem with the latest version of L4Re. It just can't build it >> for ARM. I get the folllowing error message while building: >> ... Compiling cfg_scan.o >> ... Compiling cfg_parser.tab.o >> ==> Linking io >> main.o: In function `run': >> /home/jester/Repositories/test/src/l4re/l4/pkg/io/server/src/main.cc:385: undefined >> >> There seems to be an issue with the function luaopen_Io but I don't know >> what to do to fix this. Can anybody help me? >> I have already tried different toolchains. The Linaro toolchain 2012.10 >> and also different versions from Code Sourcery (2010.09 and 2012.09). > There could be some unfortunate thing in the Makefile. Is > lua_glue.swg.cc maybe empty? If yes, restore it and try again. > > > Adam Hi Adam, thank you for your answer, that fixed the problem for me. I just removed the file and did a "svn update src/l4re/l4/pkg/io/server/src/lua_glue.swg.cc" to pull it again from the server. Afterwards I was able to build L4re again. Cheers, Jester

1 0

Problem with "luaopen_Io"
by Death Jester 21 Nov '12

21 Nov '12

Hello Everybody, I have a problem with the latest version of L4Re. It just can't build it for ARM. I get the folllowing error message while building: ... Compiling cfg_scanner.o ... Compiling cfg_scan.o ... Compiling cfg_parser.tab.o ==> Linking io main.o: In function `run': /home/jester/Repositories/test/src/l4re/l4/pkg/io/server/src/main.cc:385: undefined reference to `luaopen_Io' make[5]: *** [io] Error 1 make[5]: Leaving directory `/home/jester/Repositories/test/build/l4re/pkg/io/server/src/OBJ-arm_armv7a-l4f' make[4]: *** [/home/jester/Repositories/test/build/l4re/pkg/io/server/src/OBJ-arm_armv7a-l4f] Error 2 make[4]: Leaving directory `/home/jester/Repositories/test/src/l4re/l4/pkg/io/server/src' make[3]: *** [src] Error 2 make[3]: Leaving directory `/home/jester/Repositories/test/src/l4re/l4/pkg/io/server' make[2]: *** [server] Error 2 make[2]: Leaving directory `/home/jester/Repositories/test/src/l4re/l4/pkg/io' make[1]: *** [io] Error 2 make[1]: Leaving directory `/home/jester/Repositories/test/src/l4re/l4/pkg' make: *** [pkg] Error 2 Creating build directory "/home/jester/Repositories/test/build/fiasco"... Already exists, aborting. make: *** [builddir] Error 1 make -C /home/jester/Repositories/test/src/l4re/kernel/fiasco/src/../tool/kconfig O=/home/jester/Repositories/test/build/fiasco Kconfig=Kconfig KCONFIG_AUTOHEADER=globalconfig.h KCONFIG_TRISTATE=config/tristate.conf KCONFIG_CONFIG=globalconfig.out KCONFIG_AUTOCONFIG=config/auto.conf KERNELVERSION=SVN MENUCONFIG_COLOR=blackbg INCLUDE_PPC32= INCLUDE_SPARC= fiasco_srcdir=/home/jester/Repositories/test/src/l4re/kernel/fiasco/src/.. menuconfig silentoldconfig make[1]: Entering directory `/home/jester/Repositories/test/src/l4re/kernel/fiasco/tool/kconfig' scripts/kconfig/mconf Kconfig *** End of the configuration. *** Execute 'make' to start the build or try 'make help'. make[2]: *** [menuconfig] Interrupt make[1]: *** [sub-make] Interrupt make: *** [config] Interrupt There seems to be an issue with the function luaopen_Io but I don't know what to do to fix this. Can anybody help me? I have already tried different toolchains. The Linaro toolchain 2012.10 and also different versions from Code Sourcery (2010.09 and 2012.09). Thanks in advance. Cheers, Jester

2 1

l4linux kernel as input server
by Wajidali Whowe 21 Nov '12

21 Nov '12

Hi all, I was testing l4linux server as input server and was planning to run it without io package. For this purpose I wanted to rebuild the l4linux kernel with input server option and "without use pci virtual bus" option. My purpose was to see whether the kernel could reach the real IO ports and the result was off-course as expected a kernel panic... My question is how the io package is allowed to reach the IO ports but not the l4linux kernel? Please kindly see the kernel output and the corresponding lua script below: The lua script: require("L4"); local lxname = "vmlinuz.android"; local l = L4.default_loader; local hid = l:new_channel(); local linux_caps = { log = L4.Env.log:m("rws"); -- vbus = io_caps.linux_bus, --rtc = rtc_caps.rtc, ev = hid:svr(), rom = L4.Env.rom, }; l:start( { caps = linux_caps, }, "rom/vmlinuz.android mem=256M l4-input-srv.enable=1 console=ttyLv0 ramdisk=rom/openwrt-x86-alix2-rootfs.tar.gz root=1:0 ramdisk_size=32768 l4x_rd=rom/openwrt-x86-alix2-rootfs.tar.gz init=/etc/preinit"); Kernel output: NET: Registered protocol family 16 vmlinuz.| Invalid IO-Port access at pc = 007718f1 port=0xcfb vmlinuz.| Die message: Trap: 14 Trap: 14: 0000 [#1] Modules linked in: Pid: 1, comm: swapper Not tainted 3.6.0-l4-svn27 #3 EIP: 0000:[<007718f1>] EFLAGS: 00000246 CPU: 0 EIP is at pci_direct_probe+0x53/0x1d8 EAX: 00417001 EBX: 00000003 ECX: 00110000 EDX: 00000cfb ESI: 00000001 EDI: 0077174c EBP: 10437f78 ESP: 10437f5c DS: 0000 ES: 0000 FS: 0023 GS: 0000 SS: 0023 Process swapper (pid: 1, ti=10436000 task=10435bc0 task.ti=10436000) Stack: 10437f64 00000000 0070ff6b 00000000 00441a4c 00000003 00000000 10437f88 00771756 10454ed8 00000003 10437fc0 0040005a 10437fb0 00030003 007362d4 006e8588 00000000 10bffd86 10bffd81 10bffd92 00000001 00000003 00000049 Call Trace: [<00441a4c>] ? suspend_set_ops+0x3c/0x50 [<00771756>] pci_arch_init+0xa/0x50 [<0040005a>] do_one_initcall+0x2a/0x170 [<0075e698>] kernel_init+0xd1/0x166 [<0075e119>] ? do_early_param+0x74/0x74 [<0075e5c7>] ? start_kernel+0x298/0x298 [<00407dd4>] kernel_thread_start+0x24/0x30 Code: 00 00 00 00 c7 04 24 6b ff 70 00 e8 3a 39 cb ff 85 c0 0f 84 8b 00 00 00 e8 3d 1e c9 ff 89 c6 e8 c6 21 c9 ff ba fb 0c 00 00 b0 01 <ee> b2 f8 ed 89 45 f4 b8 00 00 00 80 ef ed 31 db 3d 00 00 00 80 EIP: [<007718f1>] pci_direct_probe+0x53/0x1d8 SS:ESP 0023:10437f5c ---[ end trace 4eaa2a86a8e2da22 ]--- Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b panic: going to sleep forever, bye vmlinuz.| panic: going to sleep forever, bye Best regards,

2 1

Full Virtulization for Trustzone
by meng-qy 21 Nov '12

21 Nov '12

Hi, all: Now,we have transplanted fiasco to imx 51 bbg board. When we use l4_vm_run to init a NS world(refer to the example of vm-tz), the system stop in the step of "VM run". More specially, we stop with the function of "tz_switch_to_ns" according to debug info. Following is our log info: RAM:------------------------ [0:90000000;90000fff] [0:90061000;9008ffff] [0:90097000;90097fff] [0:9009f000;9013ffff] [4:90140000;90172fff] [0:90173000;90177fff] [4:90178000;9018efff] [0:9018f000;9100ffff] [4:91010000;91010fff] [0:91011000;910fffff] [4:91100000;91134fff] [0:91135000;aeffffff] IOMEM:---------------------- [0:0;8fffffff] [0:b0000000;ffffffff] MOE: Hello world MOE: found 506952 KByte free memory MOE: found RAM from 90000000 to af000000 MOE: allocated 496 KByte for the page array @0x9009f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [91100000-91119428] [C:503000] l4re BOOTFS: [9111a000-91133544] [C:504000] vm-tz BOOTFS: [91134000-911341e4] [C:505000] test.bin MOE: cmdline: moe --init=rom/vm-tz MOE: Starting: rom/vm-tz MOE: loading 'rom/vm-tz' Vmm started Vm run Our configuration is: Ram_base = 0x60009000, // The reserved address in imx51, l4sigma0_map_iomem() seems ok. Ram_size = 0x4000000, // 128 MB Start_addr = Ram_base + 0x1000000, // +1MB test.bin is bare uart test-app which tested ok in imx51 bbg, we set entry "0x60009000" corresponds with Start_addr. Maybe we make some mistakes or some wrong understanding, can someone give some guidance and suggestion? Thanks a lot! Looking forward your reply. Steven Meng --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. ---------------------------------------------------------------------------------------------------

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers November 2012