- l4-hackers - example.com Site

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