- l4-hackers - example.com Site

Re: Explanation of ARM TrustZone Support?
by Wesley Miaw 14 Jan '11

14 Jan '11

On Jan 13, 2011, at 3:00 AM, l4-hackers-request(a)os.inf.tu-dresden.de wrote: > Wesley Miaw(wesley@wesman.net)@2011.01.12 17:22:52 -0800: >> I was also thinking that L4Linux was run as the non-secure Linux via >> TrustZone but that was incorrect. L4Linux is for a paravirtualized >> security split while something like TZ-Linux is used for a full >> virtualized security split, with L4 as the "Hypervisor". Has TZ- >> Linux and >> its associated work been publicly released? > > No. Its just a prove of concept. However there exists a snapshot that > should build and run out of the box on a recent Realview/PBX board. > With the upcoming virtualization extensions for ARM this approach is > more > or less obsolete. I'd be interested in taking a look at this snapshot if you are willing to share it. I'm doing some investigation work into how to put together an execution environment like your proof of concept. Thanks, -- Wesley Miaw wesley(a)wesman.net

1 0

Explanation of ARM TrustZone Support?
by Wesley Miaw 13 Jan '11

13 Jan '11

Hi, I was wondering if someone could point me at documentation, or describe in a reply, how L4 Fiasco + L4Re makes use of the ARM TrustZone hardware? I see that support for TrustZone is listed listed as one of the features of Fiasco, but haven't been able to figure out exactly what that means. If built for an ARM chip with TrustZone support, does L4 automatically set up a TrustZone execution environment for each L4 server? Or do I need to tell it somewhere to put each server into its own environment? Are the hardware calls automatically made when switching between servers? How does use of TrustZone influence message passing between servers? I'm afraid all I've found in the source appears to be some code in the hardware porting layer that is a relative mystery to me. Thanks, -- Wesley Miaw wesley(a)wesman.net

3 4

Need for a copy of the original Assembly Code of L4
by 王彬彬 11 Jan '11

11 Jan '11

Who have the original assembly code of L4 could you please send me a copy? thanks very much!

2 1

Re: ARM L4Linux Kernel Panic
by Wesley Miaw 06 Jan '11

06 Jan '11

Hi Adam, I don't know what caused the problem, but I have figured out how to work around it. I was compiling with the "Sourcery G++ Lite 2010.09-50" build. Your README indicates "Sourcery G++ Lite 2009q3-67" is known to work. I downgraded to that version and now L4linux starts up without any errors. Thanks, -- Wesley Miaw wesley(a)wesman.net

2 1

Re: ARM L4Linux Kernel Panic
by Wesley Miaw 05 Jan '11

05 Jan '11

Hi Adam, > On Mon Jan 03, 2011 at 16:04:01 -0800, Wesley Miaw wrote: >> I am attempting to run the L4linux ARM build from the Fiasco + L4Re + L4linux snapshot l4re-snapshot-2010111519.tar.bz2 but L4linux is kernel panicking during startup. Here's my build information and a snippet of the >> error output. I'd appreciate any help trying to figure out what's going wrong and resolving the problem. >> GCC_PATH_PREFIX=/opt/sourcery-g++-lite/bin/arm-none-linux-gnueabi- L4ARCH=arm >> make setup >> -> selected ARM realview >> make >> cd obj/l4linux/arm-up >> make arm_defconfig >> make menuconfig >> -> set L4 build path obj/l4/arm-rv >> -> set cross compile prefix arm-none-linux-gnueabi- >> -> turned on ARM EABI + old EABI binaries options >> make >> cd obj/l4/arm-rv >> make image E="L4linux ARM" >> qemu-arm-l4 images/bootstrap.elf >> Got through to Ned: loading file: 'rom/l4lx.cfg' without any apparent issues. L4linux started, but got a bunch of bad page errors: >> BUG: Bad page state in process swapper pfn:0431c >> page:00488380 count:4752264 mapcount:0 mapping:00488390 index:0x488390 page flags: 0x488380(slab|owner_priv_1|arch_1|tail|buddy|mlocked) These went through, and then it looked like the kernel was proceeding, but >> eventually: > I think the "bad page state" messages are the cause for the following oops. I tried to reproduce that by following your steps but I failed, i.e. it always works for me. Could you give me some more info, like all of the Linux output so that I see gcc version used etc. Qemu is which version? I'll try attaching the startup output as a text file, so as to avoid a gigantic email body. Here's the Linux and QEMU info: Ubuntu 10.04 LTS Linux lgux-wmiaw2 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 16 19:48:22 UTC 2010 i686 GNU/Linux QEMU PC emulator version 0.12.3 (qemu-kvm-0.12.3), Copyright (c) 2003-2008 Fabrice Bellard I have the QEMU Ubuntu packages installed: qemu-kvm-extras 0.12.3+noroms-0ubuntu9.3 vgabios 0.6c-2ubuntu1 qemu-common 0.12.3+noroms-0ubuntu9.3 qemu-kvm 0.12.3+noroms-0ubuntu9.3 Here's the Sourcery G++ version info: $ arm-none-linux-gnueabi-gcc -v Using built-in specs. COLLECT_GCC=arm-none-linux-gnueabi-gcc COLLECT_LTO_WRAPPER=/opt/sourcery-g++-lite/bin/../libexec/gcc/arm-none-linux-gnueabi/4.5.1/lto-wrapper Target: arm-none-linux-gnueabi Configured with: /scratch/nathan/arm-lite/src/gcc-4.5-2010.09/configure --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --target=arm-none-linux-gnueabi --enable-threads --disable-libmudflap --disable-libssp --disable-libstdcxx-pch --enable-extra-sgxxlite-multilibs --with-arch=armv5te --with-gnu-as --with-gnu-ld --with-specs='%{save-temps: -fverbose-asm} %{funwind-tables|fno-unwind-tables|mabi=*|ffreestanding|nostdlib:;:-funwind-tables} -D__CS_SOURCERYGXX_MAJ__=2010 -D__CS_SOURCERYGXX_MIN__=9 -D__CS_SOURCERYGXX_REV__=50 %{O2:%{!fno-remove-local-statics: -fremove-local-statics}} %{O*:%{O|O0|O1|O2|Os:;:%{!fno-remove-local-statics: -fremove-local-statics}}}' --enable-languages=c,c++ --enable-shared --enable-lto --enable-symvers=gnu --enable-__cxa_atexit --with-pkgversion='Sourcery G++ Lite 2010.09-50' --with-bugurl=https://support.codesourcery.com/GNUToolchain/ --disable-nls --prefix=/opt/codesourcery --with-sysroot=/opt/codesourcery/arm-none-linux-gnueabi/libc --with-build-sysroot=/scratch/nathan/arm-lite/install/arm-none-linux-gnueabi/libc --with-gmp=/scratch/nathan/arm-lite/obj/host-libs-2010.09-50-arm-none-linux-gnueabi-i686-pc-linux-gnu/usr --with-mpfr=/scratch/nathan/arm-lite/obj/host-libs-2010.09-50-arm-none-linux-gnueabi-i686-pc-linux-gnu/usr --with-mpc=/scratch/nathan/arm-lite/obj/host-libs-2010.09-50-arm-none-linux-gnueabi-i686-pc-linux-gnu/usr --with-ppl=/scratch/nathan/arm-lite/obj/host-libs-2010.09-50-arm-none-linux-gnueabi-i686-pc-linux-gnu/usr --with-host-libstdcxx='-static-libgcc -Wl,-Bstatic,-lstdc++,-Bdynamic -lm' --with-cloog=/scratch/nathan/arm-lite/obj/host-libs-2010.09-50-arm-none-linux-gnueabi-i686-pc-linux-gnu/usr --with-libelf=/scratch/nathan/arm-lite/obj/host-libs-2010.09-50-arm-none-linux-gnueabi-i686-pc-linux-gnu/usr --disable-libgomp --enable-poison-system-directories --with-build-time-tools=/scratch/nathan/arm-lite/install/arm-none-linux-gnueabi/bin --with-build-time-tools=/scratch/nathan/arm-lite/install/arm-none-linux-gnueabi/bin Thread model: posix gcc version 4.5.1 (Sourcery G++ Lite 2010.09-50) And my local /usr/bin/gcc: $ gcc -v Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.3-4ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) -- Wesley Miaw wesley(a)wesman.net

1 0

ARM L4Linux Kernel Panic
by Wesley Miaw 04 Jan '11

04 Jan '11

Hi, I am attempting to run the L4linux ARM build from the Fiasco + L4Re + L4linux snapshot l4re-snapshot-2010111519.tar.bz2 but L4linux is kernel panicking during startup. Here's my build information and a snippet of the error output. I'd appreciate any help trying to figure out what's going wrong and resolving the problem. GCC_PATH_PREFIX=/opt/sourcery-g++-lite/bin/arm-none-linux-gnueabi- L4ARCH=arm make setup -> selected ARM realview make cd obj/l4linux/arm-up make arm_defconfig make menuconfig -> set L4 build path obj/l4/arm-rv -> set cross compile prefix arm-none-linux-gnueabi- -> turned on ARM EABI + old EABI binaries options make cd obj/l4/arm-rv make image E="L4linux ARM" qemu-arm-l4 images/bootstrap.elf Got through to Ned: loading file: 'rom/l4lx.cfg' without any apparent issues. L4linux started, but got a bunch of bad page errors: BUG: Bad page state in process swapper pfn:0431c page:00488380 count:4752264 mapcount:0 mapping:00488390 index:0x488390 page flags: 0x488380(slab|owner_priv_1|arch_1|tail|buddy|mlocked) These went through, and then it looked like the kernel was proceeding, but eventually: l4lx_irq_init: creating IRQ thread on cpu 0 irq_thread: Starting IRQ thread on CPU 0 Console: colour dummy device 80x30 console [ttyLv0] enabled Calibrating delay loop... 161.79 BogoMIPS (lpj=808960) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 l4linux | EXvcada: pfa=1 pc=12eda8 l4linux | l4x_setup_die_utcb 2863 Internal error: Boom!: 410017 [#1] last sysfs file: Modules linked in: CPU: 0 Tainted: G B (2.6.36-l4 #1) PC is at __wake_up_common+0x2c/0x98 LR is at __wake_up+0x40/0x50 pc : [<0012eda8>] lr : [<0012f1c0>] psr: 0000001f sp : 0035dea0 ip : ffffffff fp : 0035decc r10: 00000003 r9 : 0035def8 r8 : 00000000 r7 : 00488208 r6 : 00000001 r5 : 0035def8 r4 : 00000001 r3 : 00000000 r2 : 00000001 r1 : 00000003 r0 : ffffffff Flags: nzcv IRQs on FIQs on Mode SYS_32 ISA ARM Segment kernel Process swapper (pid: 0, stack limit = 0x0035c270) Stack: (0x0035dea0 to 0x0035e000) dea0: 000000d0 00000001 03c00dd0 00000001 0035def8 00000001 00000003 00488208 dec0: 00000000 00000000 0035def4 0012f1c0 0035def8 00000001 00387508 03c00dd0 dee0: 00368528 0035df08 00368528 002da0e8 00000000 0014d164 03c00edc 00000003 df00: 0035df08 001dbd2c 00000000 0e4e1c02 62656572 00400000 0420c400 001de490 df20: 0420e9e0 00368558 0032d1fc 00400000 00000000 00195454 0420e9e0 00000000 df40: 00000000 00388818 00000000 00000000 00000000 0010abec 00000000 00109da4 df60: 00387648 00001000 00003dcb 00109dc8 00000000 001097e4 00000000 00000000 df80: 00000000 003874f0 00003dcb 00109a98 00000000 0038769c 00000001 00109f18 dfa0: 00385d94 00000001 004884c0 00100628 001000d0 0037809c 0040f000 00114fec dfc0: 00000000 0037809c 0040f000 00102b10 346c0000 67752078 2d657461 00000030 dfe0: 00000000 00000000 00000000 00000000 0035dff4 0040f000 00000000 00000000 [<0012eda8>] (__wake_up_common+0x2c/0x98) from [<0012f1c0>] (__wake_up+0x40/0x50) [<0012f1c0>] (__wake_up+0x40/0x50) from [<0014d164>] (__wake_up_bit+0x28/0x30) [<0014d164>] (__wake_up_bit+0x28/0x30) from [<001dbd2c>] (sysfs_get_inode+0x10c/0x1a0) [<001dbd2c>] (sysfs_get_inode+0x10c/0x1a0) from [<001de490>] (sysfs_get_sb+0xd4/0x190) [<001de490>] (sysfs_get_sb+0xd4/0x190) from [<00195454>] (vfs_kern_mount+0x54/0x120) [<00195454>] (vfs_kern_mount+0x54/0x120) from [<0010abec>] (sysfs_init+0x60/0xbc) [<0010abec>] (sysfs_init+0x60/0xbc) from [<00109dc8>] (mnt_init+0x8c/0x1ac) [<00109dc8>] (mnt_init+0x8c/0x1ac) from [<00109a98>] (vfs_caches_init+0xe0/0x110) [<00109a98>] (vfs_caches_init+0xe0/0x110) from [<00100628>] (start_kernel+0x22c/0x294) [<00100628>] (start_kernel+0x22c/0x294) from [<00102b10>] (l4x_linux_startup+0x1d0/0x208) [<00102b10>] (l4x_linux_startup+0x1d0/0x208) from [<00000000>] (0x0) Code: e1570000 e50b2028 e1a08003 e59b9004 (e41c400c) ---[ end trace 1b75b31a2719ed1c ]--- Kernel panic - not syncing: Attempted to kill the idle task! [<00125b4c>] (unwind_backtrace+0x0/0xf0) from [<002d1130>] (panic+0x58/0x178) [<002d1130>] (panic+0x58/0x178) from [<00139b2c>] (do_exit+0x5c4/0x600) [<00139b2c>] (do_exit+0x5c4/0x600) from [<0011ee9c>] (die+0x2a8/0x384) [<0011ee9c>] (die+0x2a8/0x384) from [<00000000>] (0x0) panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye Thanks, -- Wesley Miaw wesley(a)wesman.net

2 1

Problems booting Pistachio
by Ashford Nichols 26 Dec '10

26 Dec '10

I recently built the microkernel and tried to boot it using "qemu" but it doesn't work. qemu just seems to not even seem to recognize the image as a bootable image. I followed the instructions given on the site and everything worked, right up to the point where it doesn't boot. I must say though that I did slightly tweak the steps given on the site to create the image file since the original ones didn't work for me. I am really new to qemu so I don't have the slightest clue as to why this isn't working. If anyone experienced this problem or at least know how to resolve this please help me. The step I followed in order to create the image follows: dd if=/dev/zero of=l4-image.img bs=512 count=8640mke2fs l4-image.imgmkdir /media/mount_pointmount -o loop l4-image.img /media/mount_pointmkdir /media/mount_point/bootmkdir /media/mount_point/boot/grubcp -aR grub_stages/* /media/mount_point/boot/grubcp -aR modules/* /media/mount_pointumount /media/mount_point

1 0

L4Re: Thread local storage
by Taru Karttunen 22 Dec '10

22 Dec '10

Hello The following program crashes: #include <stdio.h> #include <pthread.h> __thread int i; int main(void) { puts("Hello World!"); printf("address of i=%p\n", &i); printf("i=%d\n", i); return 0; } with: MOE: loading 'rom/hello2' Hello World! address of i=0xb30001fc L4Re: unhandled exception: pc=0x100013c How should TLS initialization be done? This is with L4_MULTITHREADED = y Dump of assembler code for function main: 0x01000100 <+0>: push %ebp 0x01000101 <+1>: mov %esp,%ebp 0x01000103 <+3>: and $0xfffffff0,%esp 0x01000106 <+6>: sub $0x10,%esp 0x01000109 <+9>: movl $0x1017b20,(%esp) 0x01000110 <+16>: call 0x100dab0 <puts> 0x01000115 <+21>: movl $0x1,(%esp) 0x0100011c <+28>: call 0x100f9a0 <sleep> 0x01000121 <+33>: mov %gs:0x0,%eax 0x01000127 <+39>: movl $0x1017b2d,(%esp) 0x0100012e <+46>: add $0xfffffffc,%eax 0x01000133 <+51>: mov %eax,0x4(%esp) 0x01000137 <+55>: call 0x100da80 <printf> 0x0100013c <+60>: mov %gs:0xfffffffc,%eax 0x01000142 <+66>: movl $0x1017b3e,(%esp) 0x01000149 <+73>: mov %eax,0x4(%esp) 0x0100014d <+77>: call 0x100da80 <printf> 0x01000152 <+82>: xor %eax,%eax 0x01000154 <+84>: leave 0x01000155 <+85>: ret So how to get this working? ps. I have a rudimentary port of gccgo on L4Re working, and am polishing it over the holidays. - Taru Karttunen

3 2

schedule system call
by Ashford Nichols 20 Dec '10

20 Dec '10

In version 2 of the interface under the schedule system call, it says that the call can be used be schedulers. However, in the next sentence it goes on to say that the calling thread must reside in the same address space as the scheduler. Also, it goes on to say that an error code will be set if the calling thread is not the scheduler. So is the "schedule" system call made by the scheduler or by a thread that simply resides in the same address space as the scheduler?

1 0

L4 pager
by Ashford Nichols 19 Dec '10

19 Dec '10

I am new to L4 microkernels and I am reading the reference manual on version 2 of the interface. From what I've read so far the manual suggests that there's more than one pager, but if this is so what is the purpose of more than one pager?

2 2