- l4-hackers - example.com Site

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

how to get Task
by 朱振 01 Nov '12

01 Nov '12

hi, I want to know the memory size that each Task uses,Is there any API can help me to get this ? Thanks

2 1

Page Fault on real hardware
by Wajidali Whowe 31 Oct '12

31 Oct '12

Dear all, I have been trying to run L4linux on a real hardware (x86 PC). Everything seems fine once I try the image with the qemu, however the following error appears on the real hardware: .. .. .. vmlinuz . | main thread will be 413 vmlinuz . | l4x_register_pointer_section: addr = 005e6000 size 929792 vmlinuz . | section-with-init: virt: 0x5e6000 to 0x6c8fff [908KiB] vmlinuz . | section-with-init: virt: .... .. .. .. vmlinuz . | Loading: rom/ramdiskfs.tar.gz vmlinuz . | INITRD: Size of RAMdisk is 32768KiB vmlinuz . | RAMdisk from 188800000 to 1a800000 [32768KiB] vmlinuz . | Page fault (non-resolved): pfa=0 pc=473569 Die message: Trap: 14 vmlinuz . | panic: going to sleep forever, bye Would you please have an idea or a suggestion for this problem? Best Regards

3 7

get memory size each task uses
by 朱振 30 Oct '12

30 Oct '12

hi, I want to know the memory size that each Task uses,Is there any API that can help me to get this ? Thanks

1 0

Re: FOSDEM 2013 - Microkernels / Component-based OSes devroom
by Stefan Kalkowski 30 Oct '12

30 Oct '12

Hi all, apologies for the high cross-posting traffic. I left out the information on how to subscribe to the devroom's mailing list previously: https://lists.fosdem.org/listinfo/microkernel-devroom Please, limit the discussion regarding the devroom's organization, respectively your proposals to the above list instead of replying to all organizations in this mail-header. Thank you in advance Stefan On 29.10.2012 13:01, Stefan Kalkowski wrote: > FOSDEM 2013 - Microkernels / Component-based OSes devroom > *CALL FOR PARTICIPATION* > http://fosdem.org/2013 > > The developers of several free and open-source component- and/or > microkernel-based operating systems will meet at FOSDEM 2013 in > Brussels, Belgium and will share a developer room. > > The devroom is currently looking for content in the form of talks > related to the area of component- and/or microkernel-based operating > systems. Possible topics include, but are not limited to: > > * OS introduction to developers of other OS > * Subsystems and architecture > * Hardware and device drivers > * Tools and languages > * Release engineering and testing > * Experience and learning from mistakes > * Technical challenges > * Community and life with an OS-project > * Academia and education > > Please send your talk proposal(s) no later than by 2012-12-15 to: > > microkernel-devroom at lists.fosdem.org > > 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 > * duration of your talk (please, no longer than 45 minutes) > > The final devroom schedule (along with accepted talks) will be announced > on the above mailing list on 2012-12-22. Moreover, the speakers will be > notified via e-mail. The schedule will be also published on the FOSDEM > web and in the FOSDEM booklet after 2013-01-10. > > 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 above mailing list. > > The devroom is scheduled for Saturday of February 2. The seating > capacity of the room is 74 seats. Any changes will be announced in the > above mailing list. > -- Stefan Kalkowski Genode Labs http://www.genode-labs.com/ · http://genode.org/

1 0

FOSDEM 2013 - Microkernels / Component-based OSes devroom
by Stefan Kalkowski 29 Oct '12

29 Oct '12

FOSDEM 2013 - Microkernels / Component-based OSes devroom *CALL FOR PARTICIPATION* http://fosdem.org/2013 The developers of several free and open-source component- and/or microkernel-based operating systems will meet at FOSDEM 2013 in Brussels, Belgium and will share a developer room. The devroom is currently looking for content in the form of talks related to the area of component- and/or microkernel-based operating systems. Possible topics include, but are not limited to: * OS introduction to developers of other OS * Subsystems and architecture * Hardware and device drivers * Tools and languages * Release engineering and testing * Experience and learning from mistakes * Technical challenges * Community and life with an OS-project * Academia and education Please send your talk proposal(s) no later than by 2012-12-15 to: microkernel-devroom at lists.fosdem.org 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 * duration of your talk (please, no longer than 45 minutes) The final devroom schedule (along with accepted talks) will be announced on the above mailing list on 2012-12-22. Moreover, the speakers will be notified via e-mail. The schedule will be also published on the FOSDEM web and in the FOSDEM booklet after 2013-01-10. 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 above mailing list. The devroom is scheduled for Saturday of February 2. The seating capacity of the room is 74 seats. Any changes will be announced in the above mailing list.

1 0

In l4vcpu_irq_restore function don't use l4vcpu_irq_disable(vcpu)
by Ildar Ismagilov 17 Oct '12

17 Oct '12

In function l4vcpu_irq_restore on l4/pkg/libvcpu/include/vcpu.h file: L4_CV L4_INLINE void l4vcpu_irq_restore(l4_vcpu_state_t *vcpu, l4vcpu_irq_state_t s, l4_utcb_t *utcb, l4vcpu_event_hndl_t do_event_work_cb, l4vcpu_setup_ipc_t setup_ipc) L4_NOTHROW { if (s & L4_VCPU_F_IRQ) l4vcpu_irq_enable(vcpu, utcb, do_event_work_cb, setup_ipc); } why don't call l4vcpu_irq_disable(vcpu) if "s" variable don't include L4_VCPU_F_IRQ flag? possible should be so: L4_CV L4_INLINE void l4vcpu_irq_restore(l4_vcpu_state_t *vcpu, l4vcpu_irq_state_t s, l4_utcb_t *utcb, l4vcpu_event_hndl_t do_event_work_cb, l4vcpu_setup_ipc_t setup_ipc) L4_NOTHROW { if (s & L4_VCPU_F_IRQ) l4vcpu_irq_enable(vcpu, utcb, do_event_work_cb, setup_ipc); else l4vcpu_irq_disable(vcpu); } -- Best regards Ildar

3 2

Build of ipcmon under Ubuntu 12.04
by Dustin Oprea 11 Oct '12

11 Oct '12

I'm currently stuck on building due to the ipcmon subproject and a "__sprintf_chk" error under Ubuntu 12.04: /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `.L741': (.text+0x4088): undefined reference to `__sprintf_chk' /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `.L747': (.text+0x45c3): undefined reference to `__sprintf_chk' /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `.L747': (.text+0x473b): undefined reference to `__sprintf_chk' /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `.L747': (.text+0x4833): undefined reference to `__sprintf_chk' /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `d_print_mod_list': (.text+0x62e9): undefined reference to `__sprintf_chk' make[3]: *** [ipcmon] Error 1 make[3]: Leaving directory `/home/dustin/tudos.build/l4/pkg/ipcmon/server/src/OBJ-x86_586-l4v2' make[2]: *** [/home/dustin/tudos.build/l4/pkg/ipcmon/server/src/OBJ-x86_586-l4v2] Error 2 make[2]: Leaving directory `/home/dustin/tudos/l4/pkg/ipcmon/server/src' make[1]: *** [src] Error 2 make[1]: Leaving directory `/home/dustin/tudos/l4/pkg/ipcmon/server' make: *** [server] Error 2 I tried disabling the substitution. According to the GCC documentation, any one of three separate options will do it: -fstack-protector Emit extra code to check for buffer overflows, such as stack smashing attacks. This is done by adding a guard variable to functions with vulnerable objects. This includes functions that call alloca, and functions with buffers larger than 8 bytes. The guards are initialized when a function is entered and then checked when the function exits. If a guard check fails, an error message is printed and the program exits. NOTE: In Ubuntu 6.10 and later versions this option is enabled by default for C, C++, ObjC, ObjC++, if none of -fno-stack-protector, -nostdlib, nor -ffreestanding are found. So, I added all three of the options (at the bottom) to binary.inc: CXXFLAGS+= $(BID_CFLAGS_GSTAB) $(BID_CFLAGS_OMIT_FP) CXXFLAGS+= $(CXXFLAGS_$(OSYSTEM)) CXXFLAGS+= $(CXXFLAGS_$(@:.o=.cc)) $(CXXFLAGS_$(@:.o=.cc)_$(OSYSTEM)) CXXFLAGS+= $(CXXFLAGS_$(@:.o=.cpp)) $(CXXFLAGS_$(@:.o=.cpp)_$(OSYSTEM)) CXXFLAGS+= $(OPTS) $(filter-out -Wmissing-declarations -Wstrict-prototypes -Wmissing-prototypes,$(WARNINGS)) CXXFLAGS+= -fno-common -fno-stack-protector -nostdlib -ffreestanding I also added the same options on to the back of CFLAGS, just to be thorough. This is the output. As you can see, they make it into the command-line (there's some duplication due to our redundant adds), but I'm still getting the same error: ... Compiling ipcmon-server.o LD_PRELOAD=/home/dustin/tudos.build/l4/tool/gendep/libgendep.so GENDEP_TARGET=ipcmon-server.o GENDEP_BINARY=cc1 gcc -m32 -c -DLOG_TAG=\"ipcmon\" -DUSE_UCLIBC=y -DRAM_BASE=0x0 -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -DCONFIG_L4_CALL_SYSCALLS -DCONFIG_L4_ABS_SYSCALLS -I/home/dustin/tudos.build/l4/pkg/ipcmon/idl/OBJ-x86-l4v2 -I/home/dustin/tudos.build/l4/include/x86/l4v2 -I/home/dustin/tudos.build/l4/include/l4v2 -I/home/dustin/tudos.build/l4/include/x86 -I/home/dustin/tudos.build/l4/include -I/home/dustin/tudos/l4/../dice/include -I/home/drops/include/x86/l4v2 -I/home/drops/include/l4v2 -I/home/drops/include/x86 -I/home/drops/include -nostdinc -I/home/dustin/tudos.build/l4/include/x86/uclibc -I/home/dustin/tudos.build/l4/include/uclibc -I/home/dustin/tudos.build/l4/include/uclibc++ -I/home/drops/include/x86/uclibc -I/home/drops/include/uclibc -I/home/drops/include/uclibc++ -I/usr/lib/gcc/i686-linux-gnu/4.6/include -I/usr/lib/gcc/i686-linux-gnu/4.6/include-fixed -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -fno-common -fno-stack-protector -nostdlib -ffreestanding -fno-stack-protector -g /home/dustin/tudos.build/l4/pkg/ipcmon/idl/OBJ-x86-l4v2/ipcmon-server.c -o ipcmon-server.o ==> Linking ipcmon LD_PRELOAD=/home/dustin/tudos.build/l4/tool/gendep/libgendep.so GENDEP_TARGET=ipcmon GENDEP_BINARY=ld GENDEP_BINARY_ALT1=ld ld -m elf_i386 -o ipcmon /home/dustin/tudos.build/l4/lib/x86_586/crt0.o components.o capdescriptor.o capmanager.o blacklist.o whitelist.o ipcmon-server.o -Ttext=0x1000000 --hash-style=sysv -L/home/dustin/tudos.build/l4/lib/x86_586/l4v2 -L/home/dustin/tudos.build/l4/lib/x86_586 -L/home/dustin/tudos.build/l4/lib -L/home/drops/lib/x86_586/l4v2 -L/home/drops/lib/x86_586 -L/home/drops/lib -T/home/dustin/tudos.build/l4/lib/x86_586/main_stat.ld -lparsecmdline -static -lgeneric_ts -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -lsemaphore -llogserver_capsule -lnames -ll4util_root -ll4util -lsigma0 -lroot -ll4env -ll4env_err -ll4rm -ldm_generic -ldm_mem -lthread -lslab -ll4sys -luc_c++ -lc++start.o /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a -lmain -lcxx_base -nostdlib -luc_c -luclibc_support -u mmap_anon -lc_be_simple_mem -lc_be_mmap -lc_be_mmap_util -lc_be_l4env_start_stop -lc_be_minimal_log_io -luc_be_simple_sleep -ll4env -llogserver_capsule -ll4rm -ldm_generic -ldm_mem -lthread -lgeneric_ts -luc_c /usr/lib/gcc/i686-linux-gnu/4.6/libgcc_eh.a /usr/lib/gcc/i686-linux-gnu/4.6/libgcc.a -luc_c -ll4sys -ll4util -luc_be_minimal_io -Ttext=0x1000000 --warn-common -gc-sections /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `.L741': (.text+0x4088): undefined reference to `__sprintf_chk' /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `.L747': (.text+0x45c3): undefined reference to `__sprintf_chk' /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `.L747': (.text+0x473b): undefined reference to `__sprintf_chk' /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `.L747': (.text+0x4833): undefined reference to `__sprintf_chk' /usr/lib/gcc/i686-linux-gnu/4.6/libsupc++.a(cp-demangle.o): In function `d_print_mod_list': (.text+0x62e9): undefined reference to `__sprintf_chk' make[3]: *** [ipcmon] Error 1 make[3]: Leaving directory `/home/dustin/tudos.build/l4/pkg/ipcmon/server/src/OBJ-x86_586-l4v2' make[2]: *** [/home/dustin/tudos.build/l4/pkg/ipcmon/server/src/OBJ-x86_586-l4v2] Error 2 make[2]: Leaving directory `/home/dustin/tudos/l4/pkg/ipcmon/server/src' make[1]: *** [src] Error 2 make[1]: Leaving directory `/home/dustin/tudos/l4/pkg/ipcmon/server' make: *** [server] Error 2 Then, I built a test program, which builds perfectly: #include <stdio.h> void main() { char message[100]; __sprintf_chk(message, 0, 100, "Test."); printf("Out: %s\n", message); } The output: $ gcc -o sprintfchk_test sprintfchk_test.c $ ./sprintfchk_test Out: Test. I then thought "maybe it's the GCC version", since your list of dependencies indicates GCC 3 (my version is 4.6.3). So, I tried 3.0.4, 3.1.0, and 3.4.6, but none of them would build due to hard build errors (clearly, I'm missing some required flags). I'd appreciate some help with this error. Obviously, I'd prefer Ubuntu, but what distributions would you suggest for building? Dustin

3 2

Re: Build of ipcmon under Ubuntu 12.04
by Dustin Oprea 11 Oct '12

11 Oct '12

Bjoern: I've already run through the process at the L4RE link, and got the "hello" example booting in a VirtualBox instance. However, I want a full-environment.. I want a command-prompt. I'd also like to build the DOpE GUI (just to be complete). All I see there is useful only for module development and kernel development, but no instructions on how to get a full system running. Where do I go for help on that? These ambiguities are one of the reasons it has taken me so long to sit down and work on DROPS. There are many paths that seem similar to an outsider. Perhaps the group can take that old website down, for the further clarity to the outsiders and the peace-of-mind of the insiders? Dustin On Thu, Oct 11, 2012 at 11:05 AM, Björn Döbel <doebel(a)os.inf.tu-dresden.de>wrote: > Am Thu, 11 Oct 2012 10:33:51 -0400 > schrieb Dustin Oprea <myselfasunder(a)gmail.com>: > > > Thank you, Björn. > > > > I followed the directions and checked-out repomgr, which, in turn, > > downloaded what I have. The instructions are on this page: > > > > http://os.inf.tu-dresden.de/drops/download.html > > This page has been last modified 5 years ago! ;) Please use the links > below: > > > > http://os.inf.tu-dresden.de/fiasco > > > http://os.inf.tu-dresden.de/l4re > > > Bjoern > > -- > Dipl.-Inf. Bjoern Doebel Mail: doebel(a)tudos.org > TU Dresden, OS Chair Phone: +49 351 463 38 799 > Noethnitzer Str. 46 Fax: +49 351 463 38 284 > 01187 Dresden, Germany WWW: http://www.tudos.org/~doebel > -- > "Futbol no es en simple juego. Es una arma de la revolucion!" >

2 1

About ARM11 support
by james 10 Oct '12

10 Oct '12

Hi hackers, Afaik, fiasco does not support ARM11 architecture. I wonder whether it is in progress. James --------------------------------------------------------------------------------------------------- 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: Fiasco.oc & trustzone
by Nikolay Golikov 24 Sep '12

24 Sep '12

2012/9/20 Nikolay Golikov <decaprox(a)gmail.com>: > 2012/9/20 Adam Lackorzynski <adam(a)os.inf.tu-dresden.de>: >> On Thu Sep 20, 2012 at 15:25:54 +0400, Nikolay Golikov wrote: >>> 2012/9/20 Adam Lackorzynski <adam(a)os.inf.tu-dresden.de>: >>> > On Wed Sep 19, 2012 at 17:41:01 +0400, Nikolay Golikov wrote: >>> >> Now I have another problem: I map aipstz-1 registers with >>> >> l4io_request_iomem(base, AISPTZ_SIZE, L4IO_MEM_NONCACHED, &_vbase); >>> >> (base = 0x53F00000, AISPTZ_SIZE = 0x4000) >>> >> It return 0. >>> >> >>> >> But when I try to write to mapped registers my program stopping: >>> >> *((volatile l4_umword_t *)(_vbase + reg)) = val >>> >> (reg = 0x0, val = 0x77777777) >>> > >>> > Could you check whether it page-faults permanently? (Enable page-fault >>> > logging in jdb: P*, let it go, then check trace-buffer via shift-T.) >>> > Also try using l4_mem_write as it could be that writing from userspace >>> > does not work. >>> >>> Yes, It's page-faults permanently. In tracebuffer I see: >>> >>> pf: 0044 pfa=00003000 ip=01000294 (Wp) spc=0xf12e4690 79598 >>> pf: 0044 pfa=00003000 ip=01000294 (Wp) spc=0xf12e4690 79597 >>> pf: 0044 pfa=00003000 ip=01000294 (Wp) spc=0xf12e4690 79596 >>> >>> why it happening? >> >> Device may only be written/read from secure privileged mode, this is one >> of them (I think). Please try writing/reading via l4_mem_write and >> l4_mem_read. >> >> >> >> Adam >> -- >> Adam adam(a)os.inf.tu-dresden.de >> Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > I tried use l4_mem_write for write 0x77777777, it looks ok. But, when > I tried l4_mem_read for read from same register it returns 0x0. > But similar code injected to bootstrap startup function works fine. I tried use l4_mem_write for write 0x77777777, it looks ok. But, when I tried l4_mem_read for read from same register it returns 0x0. But similar code injected to bootstrap startup function works fine.

2 1

problem booting L4Linux
by Death Jester 24 Sep '12

24 Sep '12

Hello Everybody, does anybody know what the following message means: ------------------------------------------------------------- Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2012 TU Dresden Rev: r40 compiled with gcc 4.4.5 for Marvell Kirkwood [] Build: #1 Thu Sep 20 09:59:27 UTC 2012 Calibrating timer loop... done. SIGMA0: Hello! KIP @ 2000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:0;fff] [0:59000;8ffff] [0:97000;97fff] [0:9f000;13ffff] [4:140000;174fff] [0:175000;177fff] [4:178000;18efff] [0:18f000;100efff] [4:100f000;100ffff] [0:1010000;10fffff] [4:1100000;1528fff] [0:1529000;effffff] IOMEM:---------------------- [0:10000000;ffffffff] MOE: Hello world MOE: found 240780 KByte free memory MOE: found RAM from 59000 to f000000 MOE: allocated 239 KByte for the page array @0x9f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [14b4000-14cd448] [C:503000] l4re BOOTFS: [14ce000-1528bc8] [C:504000] ned BOOTFS: [1100000-1100189] [C:505000] l4lx.cfg BOOTFS: [1101000-11eb1ac] [C:506000] io BOOTFS: [11ec000-11ec0bd] [C:507000] arm-rv.io BOOTFS: [11ed000-14ae474] [C:508000] vmlinuz.arm BOOTFS: [14af000-14b3a86] [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' Ned: ERROR: cannot read rom/l4lx.cfg: Invalid argument ------------------------------------------------------------------ My 'l4lx.cfg' file is the default file from the l4/conf/examples folder. I haven't changed anything. And my 'modules.list' looks like this: -------------------------- modaddr 0x01100000 entry L4Linux_ARM kernel fiasco -serial_esc roottask moe rom/l4lx.cfg module l4re module ned module l4lx.cfg module io module arm-rv.io module vmlinuz.arm module ramdisk-arm.rd --------------------------- I'm using the latest L4re, Fiasco and L4Linux checked out from the SVN today and I'm running a Kirkwood based device. Any help is appreciated! Cheers, Jester

2 1

Fiasco.oc & trustzone
by Nikolay Golikov 20 Sep '12

20 Sep '12

Hello. I trying to use trustzone on i.mx53 with fiasco.oc Vm. I want run fiasco.oc in secure world, and run another fiasco.oc in normal world. But I can't find any example about use Vm kernel objects in fiasco.oc. May be someone did something like this?

2 7

Board-specific devices in L4Linux
by Dmitry Shubin 20 Sep '12

20 Sep '12

Hi. I would like to bring up the issue that has been highlighted in [1] and [2] quite some time ago. Has any progress been made since then? Adam, even if you ended up not making those changes, don't you mind sharing your thoughts/ideas on the matter? [1] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/004831.html [2] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/005074.html

2 1

omap4.dev config file for PandaBoard
by sebastian.eckl＠mytum.de 19 Sep '12

19 Sep '12

Hi, I own a PandaBoard with OMAP 4430 processor and have unavailingly tried to build L4Android for it. As basis I take the latest l4re_snapshot 2012081219. L4Re and Fiasco kernel itself are running, the provided Hello World example shows no problems. I already realized that I'll need a correct .dev config file specific to my platform, when creating the .uimage file for U-Boot. Unfortunately, an omap4.dev or panda.dev configuration file does not exist at the moment. So, I'd like to ask, if someone already adapted a .dev file to the PandaBoard and can provide me with some information or even may share his configuration with me or the public. Thank you very much in advance for your help. Sebastian

1 0

a question about L4_MAP_ITEM_GRANT
by Chen Tian 13 Sep '12

13 Sep '12

Hello, I have a simple question. If a parent maps a page into a child's space with this flag, can the parent regain this page and remove this mapping later? I did a simple test. It seems that with this flag in l4_task_map, the child owns the mapped page permanently. What I'd like to do is when a child finishes its job and returns such a granted page to its parent, the parent can reuse this page for some other child. Thanks.

2 1

Startup help for L4Linux
by Andrej S 12 Sep '12

12 Sep '12

Hi Adam, I have build some packages on my self on-top of bare fiasco, but however I didn't get l4linux to run. I got snapshot, I configure it, like readmy says me, with 'make setup' with all default settings and paths. Then I build it with 'make'. What should be my next steps to run l4linux? 2012/7/2 Adam Lackorzynski <adam(a)os.inf.tu-dresden.de>: > > On Sun Jul 01, 2012 at 08:57:41 -0500, Andrej S wrote: >> thanks for answer. >> I explored sources given with snapshot little bit and now I'm able to >> compile and run fiasco-ux. >> >> But not all is perfect: >> 1. I copied fiasco-ux with irq0, moe, ned and sigma0 together, but >> if I try to run hello-example it quits with >> FATAL exception in MOE: >> Exception: No such object found: rom/l4re: backtrace ... > > Go to the l4-obj directory where L4Re was built to and issue: > make ux E=hello > > You'll probably need to setup the path to the Fiasco UX build in > l4/conf/Makeconf.boot > >> 2. I have no idea, which package and why should I give to fiasco-ux to >> run l4linux. > > make ux E=L4Linux-mag-x86 > > or similar. The key here is the l4/conf/modules.list file which contains > which files are taken for which boot entry etc. > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

2 1

Mapping physical mem region
by Nikolay Golikov 12 Sep '12

12 Sep '12

Hi, l4-hackers! How I can map some physical memory region to task address space? I tried to use l4sigma0_map_mem, but it return me "No fpage received" error. I tried different region szes from 256M to 4K. PS I try to do it on i.mx53 TZ-VMM | Hello from tz-vmm! TZ-VMM | Nonsecure Ram mapping failed (No fpage received)! TZ-VMM | Addr: 0x80000000 Size: 0x1000 (4K) SIGMA0: Memory usage: a total of 4096 byte are in the memory pool allocated 10 of 203 objects this are 200 of 4060 byte SIGMA0: Dump of all resource maps RAM:------------------------ [4:70000000;70000fff] [4:70061000;7008ffff] [4:70097000;70097fff] [4:7009f000;8effffff] IOMEM:---------------------- [0:0;53efffff] [10:53f00000;53f03fff] [0:53f04000;63f9bfff] [10:63f9c000;63f9ffff] [0:63fa0000;6fffffff] [0:90000000;ffffffff]

2 1