l4-hackers November 2012

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

21 participants
21 discussions

Full virtualization with Trustzone
by meng-qy 19 Nov '12

19 Nov '12

Hi,all: Now,we have transplanted fiaso to imx51 bbg board, when we use l4_vm_run to init NS world (according to example of vm-tz), we found the system stop in the step of "VM run". More specifically, we stop with the processing: "return l4_ipc(vm, u, L4_SYSF_CALL, *label, l4_msgtag(L4_PROTO_TASK, 3, 0, 0), label, L4_IPC_NEVER);" The log info can be described as following: [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-91133608] [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() looks OK. Ram_size = 0x4000000, // 128 MB Start_addr = Ram_base + 0x1000000, // +1MB The test.bin is bare uart test-app we test ok in imx51 board, we change the entry as 0x61009000, correspond with Start_addr. Maybe we make some mistakes, who can give some guidance and suggestions? Looking forward to 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. ---------------------------------------------------------------------------------------------------

1 0

Touchscreen
by Wajidali Whowe 15 Nov '12

15 Nov '12

Dear all, do you have any experience on configuring the touchscreen for L4? I have an x86 computer with a touchscreen and do not know where to start. Does anyone have a small tip for me to start? Best Regards

5 20

Fiasco.OC Kernel Semaphores r38->r40
by Daniel Waddington 14 Nov '12

14 Nov '12

Hi, I noticed that kernel semaphores seem to have vanished from Fiasco.OC r40 (when they were definitely there in r38). They seem to have been replaced with an ipc/sw irq solution - is this true? Can someone explain the design rationale behind this? If we want to back-port them into r40 is there anything we need to be aware of? Thanks, Daniel Waddington

2 1

how to run the vm-tz example?
by 朱振 14 Nov '12

14 Nov '12

Hi all, I try to run the vm-tz example on imx51,in the example it start a linux in NS world by vm function,my question are: 1. How can i get (or build) the linux image and ramdisk files that the example requires ? 2. I want to run a fiasco in NS world use the example code ,some body can tell me how to get it done? I'm looking forward to your reply!

1 0

Re: Trustzone Dual-OS
by meng-qy 14 Nov '12

14 Nov '12

Hi,l4-hackers: We read some history mails and fiasco src in detail. We found some tz-supports in fiasco, one part is ivt.s in fiasco kernal , the other is vmm in L4re. The vmm provide a entry to load non-secure os, the example demonstrates a full virtualization of tz-linux. However, we found tz-linux is just a concept. Does our understanding above have something wrong? How can we reach the final dual-os goal in the shortest possible time? We sincerely request your help! Best regards Steven Meng ----- Original Message ----- From: meng-qy To: l4-hackers(a)os.inf.tu-dresden.de Sent: Monday, November 12, 2012 4:28 PM Subject: Trustzone Dual-OS Hi,all： Now,we are trying to make dual-os solution based on fiasco, android and trustzone. Does it already have the stable dual-os soluton in l4-hacker community? If have, how can we get it? we can not find the trustzone-surpport in the latest release of source tree. Thanks and looking forward your response. Best Regards 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. ---------------------------------------------------------------------------------------------------

1 0

Trustzone Dual-OS
by meng-qy 12 Nov '12

12 Nov '12

Hi,all： Now,we are trying to make dual-os solution based on fiasco, android and trustzone. Does it already have the stable dual-os soluton in l4-hacker community? If have, how can we get it? we can not find the trustzone-surpport in the latest release of source tree. Thanks and looking forward your response. Best Regards 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. ---------------------------------------------------------------------------------------------------

1 0

bootstrapper error
by Ryan Brown 10 Nov '12

10 Nov '12

Hi, I just tried updating to fiasco/l4re from 2012081219, and now I'm getting bootstrapper errors. Previously bootstrap went like this: L4 Bootstrapper Build: #1 Wed Jun 27 14:54:16 PDT 2012, x86-32, 4.4.3 RAM: 0000000000000000 - 000000000009f3ff: 637kB RAM: 0000000000100000 - 0000000012bfcfff: 306164kB Total RAM: 299MB Moving 11 modules to 1100000 with offset f2fc2000 moving module 01 { e13e000, e1b4914 } (ELF) -> { 1100000 - 1176914 } moving module 02 { e1b5000, e1f5a05 } (ELF) -> { 1177000 - 11b7a05 } moving module 03 { e1f6000, e3b92fb } (ELF) -> { 11b8000 - 137b2fb } moving module 04 { e3ba000, e4a8004 } (ELF) -> { 137c000 - 146a004 } moving module 05 { e4a9000, e6a301e } (ELF) -> { 146b000 - 166501e } moving module 06 { 12a71000, 12a71237 } (-- v) -> { 5a33000 - 5a33237 } moving module 07 { e6a4000, ef0f8c7 } (ELF) -> { 1666000 - 1ed18c7 } moving module 08 { ef10000, eff8eba } (ELF) -> { 1ed2000 - 1fbaeba } moving module 09 { 12bcd000, 12bcd3b7 } (# vi) -> { 5b8f000 - 5b8f3b7 } moving module 10 { 12a72000, 12a72106 } (l4li) -> { 5a34000 - 5a34106 } moving module 11 { eff9000, f9280a6 } (ELF) -> { 1fbb000 - 28ea0a6 } => Images moved But now I get this: L4 Bootstrapper Build: #1 Tue Nov 6 15:26:40 PST 2012, x86-32, 4.6.x RAM: 0000000000000000 - 000000000009f3ff: 637kB RAM: 0000000000100000 - 0000000012bfcfff: 306164kB Total RAM: 299MB Moving modules behind 1100000 moving module 00 { e13e000-e163d3f } -> { 12b6c000-12b91d3f } [154944] moving module 01 { e164000-e1c0c6b } -> { 12b92000-12beec6b } [380012] moving module 02 { e1c1000-e41df1f } -> { 12bef000-12e4bf1f } [2477856] ERROR: module target [12bef000-12e4bf1f) overlaps [ 12bfd000, 12bfffff] { 3000} Arch BIOS can not move module Key press reboots... I've tried specifying different modaddrs, but it always starts moving modules to 12b6c000 and runs past the end of RAM. I tried increasing the ram to my virtual machine, but bootstrap just picks a higher address that doesn't work. What am I doing wrong? Also, I noticed now that io is 11mb. Is it normal for it to be this big?

2 1

bug report: compile about l4re
by Wangjintang 06 Nov '12

06 Nov '12

Environment: Linux linux-tilera 2.6.32.12-0.7-default #1 SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/Linux gcc version 4.3.4 [gcc-4_3-branch revision 152973] (SUSE Linux) packet: l4re-core-2012081219.tar.bz2 step: 1. Create build directory somedir$ cd src/kernel/fiasco somedir/src/kernel/fiasco$ make BUILDDIR=mybuild The make step will generate a build directory called mybuild. 1. Got the build directory somedir/src/kernel/fiasco$ cd mybuild 1. Configure kernel build somedir/src/kernel/fiasco/mybuild$ make config Will launch the configuration menu. This is the time to configure your kernel. The default config will build a uniprocessor IA32 kernel with debugging features enabled. If you're happy with this step you may skip it. 1. Build it somedir/src/kernel/fiasco/mybuild$ make -j4 In file included from /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/kern/kmem_alloc.cpp:3, from /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/boot/bootstrap.cc:18: /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/kern/auto_quota.h:13: error: invalid pure specifier (only `= 0' is allowed) before ';' token /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/kern/auto_quota.h:14: error: invalid pure specifier (only `= 0' is allowed) before ';' token In file included from /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist:22, from /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/kern/kmem_alloc.cpp:4, from /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/boot/bootstrap.cc:18: /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/bits/list_basics.h:50: error: invalid pure specifier (only `= 0' is allowed) before ';' token /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/bits/list_basics.h:51: error: invalid pure specifier (only `= 0' is allowed) before ';' token In file included from /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/kern/kmem_alloc.cpp:4, from /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/boot/bootstrap.cc:18: /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist:46: error: invalid pure specifier (only `= 0' is allowed) before ';' token /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist:47: error: invalid pure specifier (only `= 0' is allowed) before ';' token In file included from /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/boot/bootstrap.cc:18: /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/bits/list_basics.h: In instantiation of 'cxx::Bits::Basic_list<cxx::Bits::Basic_list_policy<Kmem_alloc_reaper, cxx::S_list_item> >': /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist:45: instantiated from 'cxx::S_list<Kmem_alloc_reaper, cxx::Bits::Basic_list_policy<Kmem_alloc_reaper, cxx::S_list_item> >' /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist:127: instantiated from 'cxx::S_list_bss<Kmem_alloc_reaper>' /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/kern/kmem_alloc.cpp:309: instantiated from here /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/bits/list_basics.h:50: error: initializer specified for non-virtual method 'cxx::Bits::Basic_list<POLICY>::Basic_list(const cxx::Bits::Basic_list<POLICY>&) [with POLICY = cxx::Bits::Basic_list_policy<Kmem_alloc_reaper, cxx::S_list_item>]' /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/bits/list_basics.h:51: error: initializer specified for non-virtual method 'void cxx::Bits::Basic_list<POLICY>::operator=(const cxx::Bits::Basic_list<POLICY>&) [with POLICY = cxx::Bits::Basic_list_policy<Kmem_alloc_reaper, cxx::S_list_item>]' /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist: In instantiation of 'cxx::S_list<Kmem_alloc_reaper, cxx::Bits::Basic_list_policy<Kmem_alloc_reaper, cxx::S_list_item> >': /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist:127: instantiated from 'cxx::S_list_bss<Kmem_alloc_reaper>' /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/kern/kmem_alloc.cpp:309: instantiated from here /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist:46: error: initializer specified for non-virtual method 'cxx::S_list<T, P>::S_list(const cxx::S_list<T, P>&) [with T = Kmem_alloc_reaper, POLICY = cxx::Bits::Basic_list_policy<Kmem_alloc_reaper, cxx::S_list_item>]' /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist:47: error: initializer specified for non-virtual method 'void cxx::S_list<T, P>::operator=(const cxx::S_list<T, P>&) [with T = Kmem_alloc_reaper, POLICY = cxx::Bits::Basic_list_policy<Kmem_alloc_reaper, cxx::S_list_item>]' ... Making __assert_fail.o

2 1

Compiling l4re on ubuntu 12.10
by Ali Nehzat 05 Nov '12

05 Nov '12

Hi, Could someone please let me know what the expected dev environment is and which tool chains I should in fact be using? I'm trying to compile L4Re for a pandaboard on a 32-bit stock standard Ubuntu 12.10 dev machine with gcc-arm-linux-gnueabihf installed on it, however during the "make O=<build-path> config" step, after going through the menu config I get a pile of "bash: arm-linux-gcc: command not found" error. Thanks in advance, Ali

2 1

1G memory for L4Linux on Panda
by Владимир Шилкин 01 Nov '12

01 Nov '12

Hello, When allow L4Linux using more than 512M of memory, user level apps execution can cause ‘Segmentation fault’ or glibc error. For example run 'find' command on fresh booted system. We use PandaBoard. To configure system use 1Gb RAM we set in src/l4/mk/platforms/pandaboard.conf PLATFORM_RAM_SIZE_MB = 1024 Best Regards, Vladimir

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