- l4-hackers - OS Site

Re: Graphical desktop, l4con, mag
by Leslie Zhai 04 Jun '17

04 Jun '17

Hi Jean, Thanks for your help! 在 2017年06月03日 04:56, Jean Wolter 写道: > Hello Leslie, > > On 02/06/17 11:33, Jean Wolter wrote: >> I replaced my "ned" binary with yours and the system boots up fine. >> >> Now I wonder how I could reproduce your problem. It looks like I >> >> * either need all binaries or >> * need to build them the same way you are building them. I used a >> fresh checkout from the svn repositories and use gcc version >> 4.9.2 (Debian 4.9.2-10) to build the components. >> > > Since I neither have your binaries nor know how you build them I follow the http://os.inf.tu-dresden.de/fiasco/build.html and http://l4re.org/build.html and my environment is Fedora 24, gcc 6.3.1, qemu 2.6.2 and clang-5.0svn. hello example is able to work :) > I thought about how you could diagnose the problem further. To > demonstrate how to do this I intentionally added a null pointer > dereference to ned and would like to discuss how I would diagnose this. > > --- ned/server/src/main.cc (revision 72) > +++ ned/server/src/main.cc (working copy) > @@ -35,6 +35,8 @@ > Dbg::set_level(Dbg::Warn); > info.printf("Hello from Ned\n"); > > + *(int *)0 = 0; > + > boot_info.printf("cmdline: "); > for (int i = 0; i < argc; ++i) > boot_info.cprintf("%s ", argv[i]); > > 1. Add -serial_esc -wait to kernel options in conf/modules.list > > --- modules.list (revision 72) > +++ modules.list (working copy) > @@ -80,6 +80,7 @@ > module libuc_c.so > > entry framebuffer-example-x86 > +kernel fiasco -serial_esc -wait > roottask moe rom/x86-fb.cfg > module x86-fb.cfg > module l4re > > If you boot this the kernel will enter the kernel debugger before > doing anything else. Enter the following commands: > > * P+ /* show every pagefault before forwarding it to the pager */ > * Prx0<space>100<space> /* restrict pagefault logging to pagefaults > between [0-100] */. > * g /* go */ > > The kernel should stop when the access to 0x18 happens, then you can > enter the kernel debugger using 'i' and can check who is responsible > and maybe get a correct instruction pointer. If I do this here it > looks like follows (I added -serial stdio to the qemu options): > > qemu-system-x86_64 -kernel > /home/jw5/build/tmp/l4re/bin/amd64_K8/bootstrap -append "bootstrap > -modaddr 0x01100000" -serial stdio -initrd > "/home/jw5/build/tmp/fiasco//fiasco -serial_esc > -wait,/home/jw5/build/tmp/l4re/bin/amd64_K8/l4f/sigma0 > ,/home/jw5/build/tmp/l4re/bin/amd64_K8/l4f/moe > rom/x86-fb.cfg,/home/jw5/src/l4resvn/src/l4/conf/examples//x86-fb.cfg > ,/home/jw5/build/tmp/l4re/bin/amd64_K8/l4f/l4re > ,/home/jw5/build/tmp/l4re/bin/amd64_K8/l4f/ned > ,/home/jw5/build/tmp/l4re/bin/amd64_K8/l4f/io > ,/home/jw5/src/l4resvn/src/l4/pkg/io/io/config//x86-legacy.devs > ,/home/jw5/src/l4resvn/src/l4/conf/examples//x86-fb.io > ,/home/jw5/build/tmp/l4re/bin/amd64_K8/l4f/fb-drv > ,/home/jw5/build/tmp/l4re/bin/amd64_K8/l4f/mag > ,/home/jw5/build/tmp/l4re/bin/amd64_K8/l4f/ex_fb_spectrum_cc " > ... > Freeing init code/data: 49152 bytes (12 pages) > > Calibrating timer loop... done. > > --------------------------------------------------------------------- > CPU 0 [fffffffff003df99]: Wait > jdb: P+ when I input p+ then pressed Enter, but jdb did not print out "PF logging enabled" to me https://pbs.twimg.com/media/DBcu1DUUwAAkiDl.png > PF logging enabled > jdb: Pr restrict to addr in [0-100] /* pressed > Prx0<space>100<space> */ > PF logging enabled, restricted to 0000000000000000 <= pfa <= > 0000000000000100 > jdb: g /* g does no show up in output */ but input g then pressed Enter will continue to go https://pbs.twimg.com/media/DBc0XlWUAAAmgSN.png sorry I am not familiar with jdb, but have some experience with gdb. > ... > MOE: cmdline: /home/jw5/build/tmp/l4re/bin/amd64_K8/l4f/moe rom/x86-fb.cfg > MOE: Starting: rom/ned rom/x86-fb.cfg > MOE: loading 'rom/ned' > pf: 0022 pfa=0000000000000000 ip=00000000010038a2 (w-) > spc=0xffffffff807c3dd8 > /* press i */ > --------------------------------------------------------------------- > CPU 0 [fffffffff0062116]: LOG > jdb: > > Now you can use the kernel debugger to inspect the current state of > the system. Here I simply use addr2line to find the error: so I failed to debug the on purpose null ptr dereference issue *(int *)0 = 0; in your patch via jdb. > addr2line -p -i -e bin/amd64_K8/l4f/ned -a 10038a2 > 0x00000000010038a2: > /home/jw5/src/l4resvn/src/l4/pkg/l4re-core/ned/server/src/main.cc:38 > (inlined by) > /home/jw5/src/l4resvn/src/l4/pkg/l4re-core/ned/server/src/main.cc:77 > > > Line 38 is the line with the null pointer dereference. > > I hope this helps, > Jean > > > -- Regards, Leslie Zhai - a LLVM hacker https://reviews.llvm.org/p/xiangzhai/

1 0

Re: Graphical desktop, l4con, mag
by Leslie Zhai 02 Jun '17

02 Jun '17

在 2017年06月02日 15:34, Jean Wolter 写道: > > Hello Leslie, > > On 02/06/17 05:52, Leslie Zhai wrote: >> Thanks for your reply! but I met the same story for L4Linux >> https://pbs.twimg.com/media/DBSQtoNUIAEE2HY.png > It looks like the very same error, an unhandled read page-fault at > address 0x18 triggered by an instruction at 0x102d72a. > >> > Maybe you could use addr2line/objdump >> > to figure out, what happens at address 0x102d72a in ned. >> >> cd /home/zhaixiang/project/l4re/l4/build >> addr2line -p -e bin/amd64_K8/l4f/ned 0x102d72a >> >> but there is no output easy to read for humans, I am not familiar >> with addr2line, please give me some advice, thanks a lot! > If I try it with an instruction pointer somewhere in the main function > it looks like follows: > > ~/build/tmp/l4re/bin/amd64_K8/l4f$ addr2line -p -i -e ned -a 10038b3 > 0x00000000010038b3: > /home/.../src/l4resvn/src/l4/pkg/l4re-core/ned/server/src/main.cc:39 > (inlined by) > /home/.../src/l4resvn/src/l4/pkg/l4re-core/ned/server/src/main.cc:75 > > >> objdump -D bin/amd64_K8/l4f/ned > ned.S >> > If you use -lSd you should see line number information in the > disassembled output, e.g: > > /home/.../src/l4resvn/src/l4/pkg/l4re-core/ned/server/src/main.cc:39 > for (int i = 0; i < argc; ++i) > 10038b3: 85 db test %ebx,%ebx > > >> 102d72a: 66 0f 12 05 9e 7b 02 movlpd 0x27b9e(%rip),%xmm0 # >> 10552d0 <_ZL7HOOKKEY+0x 8> >> is it enough to figure out what happened? if not, I will upload the >> disassemble to my Google drive. > This looks strange. There is nothing looking like an access to 0x18. > Could send me your ned binary? https://drive.google.com/open?id=0ByE8c-y74l_uVlB6cnJBdWV1VzA > > regards, > Jean > -- Regards, Leslie Zhai - a LLVM hacker https://reviews.llvm.org/p/xiangzhai/

1 0

xorriso : FAILURE : Not a known command
by Leslie Zhai 02 Jun '17

02 Jun '17

Hi L4 hackers, When I Running hello.iso http://os.inf.tu-dresden.de/fiasco/build.html via *make grub2iso E=hello MODULE_SEARCH_PATH=/path/to/fiasco-build-dir *it failed to generate ISO, xorriso thrown such error: xorriso : FAILURE : Not a known command: '-f' xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE' Failed to create ISO at tool/lib/L4/Grub.pm line 123. Makefile:598: recipe for target 'grub2iso' failed so I simply changed the option: Index: tool/lib/L4/Grub.pm =================================================================== --- tool/lib/L4/Grub.pm (revision 72) +++ tool/lib/L4/Grub.pm (working copy) @@ -116,7 +116,7 @@ close A; }; my $cmd = "$mkr --output=\"$isofilename\" $dir ". - join(' ', @morefiles)." --$opt -f"; + join(' ', @morefiles)." --$opt -follow default"; system("$cmd"); die "Failed to create ISO" if $?; # grub-mkrescue does not propagate internal tool errors please review my patch, thanks a lot! -- Regards, Leslie Zhai - a LLVM hacker https://reviews.llvm.org/p/xiangzhai/

4 10

Graphical desktop, l4con, mag
by teclis High Elf 02 Jun '17

02 Jun '17

Guten Tag, I've got the Hello app runing with fiasco and l4re in qemu, how do I get the graphical UI and console running that I see on the screen shots page? Do I need to use l4con and mag? I don't see an entry with l4con in modules.list. danke * <http://german.about.com/library/media/Audio/gutentag.wav>*

6 15

L4Linux CONFIG_MTRR must not be enabled
by 翟翔 02 Jun '17

02 Jun '17

Hi L4 hackers, When I am building L4Linux https://l4linux.org/build.shtml make O=build menuconfig changed the L4 tree build directory, then Exit for saving to .config make O=build it thrown ERROR: CONFIG_XXX must not be enabled, then I edited build/.config to comment the CONFIG_XXX is not set, then make O=build again, but it always thrown such error: make[1]: Entering directory '/home/zhaixiang/project/l4linux/build' =============================================== For quick build instructions, please visit: http://wiki.tudos.org/Quickstart http://l4linux.org/build.shtml =============================================== ERROR: CONFIG_MTRR must not be enabled. ERROR: CONFIG_DMI must not be enabled. ERROR: CONFIG_X86_SMAP must not be enabled. arch/l4/Makefile:578: recipe for target 'check_linux_config' failed make[1]: *** [check_linux_config] Error 1 make[1]: Leaving directory '/home/zhaixiang/project/l4linux/build' Makefile:150: recipe for target 'sub-make' failed make: *** [sub-make] Error 2 even I commented CONFIG_MTRR, CONFIG_DMI and CONFIG_X86_SMAP is not set, but rebuilt it again, the CONFIG_MTRR=y, are they requires by other modules? infinite dependence issue? so I simply changed the arch/l4/Makefile Index: arch/l4/Makefile =================================================================== --- arch/l4/Makefile (revision 54) +++ arch/l4/Makefile (working copy) @@ -557,9 +557,9 @@ DIS_OPTS-arm-32 := PERF_EVENTS ARM_PATCH_PHYS_VIRT HIGHMEM \ DEBUG_RODATA DEBUG_ALIGN_RODATA DIS_OPTS := HIGHMEM4G HIGHMEM64G PCI_GOANY PCI_GOBIOS \ - X86_MCE X86_MCE MTRR PARAVIRT KEXEC MCA SOFTWARE_SUSPEND APM \ - CPU_FREQ VM86 X86_DS X86_PTRACE_BTS HT_IRQ DMI \ - TRANSPARENT_HUGEPAGE COMPACTION X86_PAE ACPI X86_SMAP \ + X86_MCE X86_MCE PARAVIRT KEXEC MCA SOFTWARE_SUSPEND APM \ + CPU_FREQ VM86 X86_DS X86_PTRACE_BTS HT_IRQ \ + TRANSPARENT_HUGEPAGE COMPACTION X86_PAE ACPI \ M486 M586 M586TSC M586MMX PNP \ X86_16BIT MICROCODE \ $(DIS_OPTS-$(BASEARCH)-$(BITS)) it is monkey patch, please give me some advice, thanks a lot! -- Regards, Leslie Zhai - a LLVM hacker https://reviews.llvm.org/p/xiangzhai/

3 2

Benchmarks in l4
by Maxim Baryshnikov 01 Jun '17

01 Jun '17

Hello everybody, Does the L4re contain some kind of simple performance benchmarks which are already prepared to use? I've tried to launch some demos from the ferret package but not succeed... Thank you in advance for any suggestions. Sincerely, Maxim Baryshnikov.

4 11

Re: libfs/ FUSE on L4Re
by Leslie Zhai 01 Jun '17

01 Jun '17

diff --git a/libfs/lib/libc_backend/l4fs.cc b/libfs/lib/libc_backend/l4fs.cc index 7a229ff..31ad120 100644 --- a/libfs/lib/libc_backend/l4fs.cc +++ b/libfs/lib/libc_backend/l4fs.cc @@ -219,10 +219,10 @@ int L4fs_dir::get_entry(const char *name, int flags, mode_t mode, //printf("mode=%x,flags=%x\n", mode, flags); if (S_ISDIR(mode)) { //printf("open '%s' as directory\n", name); - *file = new L4fs_dir(_svr, fh); + *file = cxx::ref_ptr(new L4fs_dir(_svr, fh)); } else { //printf("open '%s' as file\n", name); - *file = new L4fs_file(_svr, fh); + *file = cxx::ref_ptr(new L4fs_file(_svr, fh)); } return (*file) ? 0 : -ENOMEM; @@ -325,7 +325,7 @@ int L4fs_file_system::mount(char const *source, unsigned long mountflags, if (fh < 0) return fh; - *dir = new L4fs_dir(svr, fh); + *dir = cxx::ref_ptr(new L4fs_dir(svr, fh)); if (!dir) return -ENOMEM; 在 2017年06月01日 15:36, Xiang Zhai 写道: > Hi Florian, > > > /home/zhaixiang/project/l4re/l4/pkg/libfs/lib/libc_backend/l4fs.cc: In > member function ‘virtual int L4fs::L4fs_dir::get_entry(const char*, > int, mode_t, cxx::Ref_ptr<L4Re::Vfs::File>*)’: > /home/zhaixiang/project/l4re/l4/pkg/libfs/lib/libc_backend/l4fs.cc:222:38: > error: no match for ‘operator=’ (operand types are > ‘cxx::Ref_ptr<L4Re::Vfs::File>’ and ‘L4fs::L4fs_dir*’) > *file = new L4fs_dir(_svr, fh); > ^ > In file included from > /home/zhaixiang/project/l4re/l4/build/include/l4/l4re_vfs/vfs.h:41:0, > from > /home/zhaixiang/project/l4re/l4/build/include/l4/l4re_vfs/backend:22, > from > /home/zhaixiang/project/l4re/l4/pkg/libfs/lib/libc_backend/l4fs.cc:15: > /home/zhaixiang/project/l4re/l4/build/include/l4/cxx/ref_ptr:186:8: > note: candidate: template<class OT> void cxx::Ref_ptr<T, > CNT>::operator=(const cxx::Ref_ptr<OT>&) [with OT = OT; T = > L4Re::Vfs::File; CNT = cxx::Default_ref_counter] > void operator = (Ref_ptr<OT> const &o) throw() > ^~~~~~~~ > /home/zhaixiang/project/l4re/l4/build/include/l4/cxx/ref_ptr:186:8: > note: template argument deduction/substitution failed: > /home/zhaixiang/project/l4re/l4/pkg/libfs/lib/libc_backend/l4fs.cc:222:38: > note: mismatched types ‘const cxx::Ref_ptr<T>’ and ‘L4fs::L4fs_dir*’ > *file = new L4fs_dir(_svr, fh); > ^ > In file included from > /home/zhaixiang/project/l4re/l4/build/include/l4/l4re_vfs/vfs.h:41:0, > from > /home/zhaixiang/project/l4re/l4/build/include/l4/l4re_vfs/backend:22, > from > /home/zhaixiang/project/l4re/l4/pkg/libfs/lib/libc_backend/l4fs.cc:15: > /home/zhaixiang/project/l4re/l4/build/include/l4/cxx/ref_ptr:193:8: > note: candidate: void cxx::Ref_ptr<T, CNT>::operator=(const > cxx::Ref_ptr<T>&) [with T = L4Re::Vfs::File; CNT = > cxx::Default_ref_counter] > void operator = (Ref_ptr<T> const &o) throw() > ^~~~~~~~ > /home/zhaixiang/project/l4re/l4/build/include/l4/cxx/ref_ptr:193:8: > note: no known conversion for argument 1 from ‘L4fs::L4fs_dir*’ to > ‘const cxx::Ref_ptr<L4Re::Vfs::File>&’ > /home/zhaixiang/project/l4re/l4/build/include/l4/cxx/ref_ptr:203:8: > note: candidate: void cxx::Ref_ptr<T, CNT>::operator=(cxx::Ref_ptr<T, > CNT>::Null_type) [with T = L4Re::Vfs::File; CNT = > cxx::Default_ref_counter; cxx::Ref_ptr<T, CNT>::Null_type = > std::nullptr_t] > void operator = (Null_type) throw() > ^~~~~~~~ > /home/zhaixiang/project/l4re/l4/build/include/l4/cxx/ref_ptr:203:8: > note: no known conversion for argument 1 from ‘L4fs::L4fs_dir*’ to > ‘cxx::Ref_ptr<L4Re::Vfs::File>::Null_type {aka std::nullptr_t}’ > /home/zhaixiang/project/l4re/l4/build/include/l4/cxx/ref_ptr:218:8: > note: candidate: template<class OT> void cxx::Ref_ptr<T, > CNT>::operator=(cxx::Ref_ptr<OT>&&) [with OT = OT; T = > L4Re::Vfs::File; CNT = cxx::Default_ref_counter] > void operator = (Ref_ptr<OT> &&o) throw() > ^~~~~~~~ > /home/zhaixiang/project/l4re/l4/build/include/l4/cxx/ref_ptr:218:8: > note: template argument deduction/substitution failed: > /home/zhaixiang/project/l4re/l4/pkg/libfs/lib/libc_backend/l4fs.cc:222:38: > note: mismatched types ‘cxx::Ref_ptr<T>’ and ‘L4fs::L4fs_dir*’ > *file = new L4fs_dir(_svr, fh); > ^ > In file included from > /home/zhaixiang/project/l4re/l4/build/include/l4/l4re_vfs/vfs.h:41:0, > from > /home/zhaixiang/project/l4re/l4/build/include/l4/l4re_vfs/backend:22, > from > /home/zhaixiang/project/l4re/l4/pkg/libfs/lib/libc_backend/l4fs.cc:15: > /home/zhaixiang/project/l4re/l4/build/include/l4/cxx/ref_ptr:224:8: > note: candidate: void cxx::Ref_ptr<T, > CNT>::operator=(cxx::Ref_ptr<T>&&) [with T = L4Re::Vfs::File; CNT = > cxx::Default_ref_counter] > void operator = (Ref_ptr<T> &&o) throw() > ^~~~~~~~ > /home/zhaixiang/project/l4re/l4/build/include/l4/cxx/ref_ptr:224:8: > note: no known conversion for argument 1 from ‘L4fs::L4fs_dir*’ to > ‘cxx::Ref_ptr<L4Re::Vfs::File>&&’ > > > So I simply added cxx::ref_ptr() for reference counting pointer with > automatic cleanup: > > > diff --git a/libfs/lib/libc_backend/l4fs.cc > b/libfs/lib/libc_backend/l4fs.cc > index 7a229ff..31ad120 100644 > --- a/libfs/lib/libc_backend/l4fs.cc > +++ b/libfs/lib/libc_backend/l4fs.cc > @@ -219,10 +219,10 @@ int L4fs_dir::get_entry(const char *name, int > flags, mode_t mode, > //printf("mode=%x,flags=%x\n", mode, flags); > if (S_ISDIR(mode)) { > //printf("open '%s' as directory\n", name); > - *file = new L4fs_dir(_svr, fh); > + *file = cxx::ref_ptr(new L4fs_dir(_svr, fh)); > } else { > //printf("open '%s' as file\n", name); > - *file = new L4fs_file(_svr, fh); > + *file = cxx::ref_ptr(new L4fs_file(_svr, fh)); > } > > return (*file) ? 0 : -ENOMEM; > @@ -325,7 +325,7 @@ int L4fs_file_system::mount(char const *source, > unsigned long mountflags, > if (fh < 0) > return fh; > > - *dir = new L4fs_dir(svr, fh); > + *dir = cxx::ref_ptr(new L4fs_dir(svr, fh)); > if (!dir) > return -ENOMEM; > > > please review my patch, thanks a lot! > -- Regards, Leslie Zhai - a LLVM hacker https://reviews.llvm.org/p/xiangzhai/

1 0

libfs/ FUSE on L4Re
by Stark, Josef 31 May '17

31 May '17

Hello, yesterday I came across a very interesting paper titled "Porting FUSE to L4Re", accessible here: http://os.inf.tu-dresden.de/papers_ps/pester-beleg.pdf For porting FUSE, the author uses a library called "libfs" which provides filesystem request forwarding and processing, if I understood correctly. It reads as if libfs is already included in L4Re. However, I couldn't find neither FUSE nor libfs in the current L4Re snapshot. Are they by any chance publicly available somewhere else, or are both not to be published? Cheers, Josef

4 7

Microkernel + Alumni Meetup
by Bjoern Doebel 30 May '17

30 May '17

Hi all, it has been a while since we last met for a beer. Water went down the Elbe river, companies were closed, companies were started, research papers got accepted, technical advancements were made. Let's catch up on all of that! To find a suitable time, please visit https://dudle.inf.tu-dresden.de/ukm-01-2017/ Bjoern

2 3

clang-5.0 is not supported. Please use one of the following versions
by Leslie Zhai 29 May '17

29 May '17

Hi L4 hackers, I am using clang (svn trunk 303321) to build fiasco, it thrown such error: kernel/fiasco/src/Makeconf:264: *** clang-5.0 is not supported. Please use one of the following versions: 3.5 3.6 3.7 3.8 so I simply add other versions for clang, please review my patch, thanks a lot! Index: kernel/fiasco/src/Makeconf =================================================================== --- kernel/fiasco/src/Makeconf (revision 72) +++ kernel/fiasco/src/Makeconf (working copy) @@ -245,7 +245,7 @@ CC_WHITELIST-gcc := 4.5 4.6 4.7 4.8 4.9 5 6 -CC_WHITELIST-clang := 3.5 3.6 3.7 3.8 +CC_WHITELIST-clang := 3.5 3.6 3.7 3.8 3.9 4.0 5.0 CC_WHITELIST := $(CC_WHITELIST-$(CC_TYPE)) CC_BLACKLIST-arm-gcc := 4.8.0 4.8.1 4.8.2 -- Regards, Leslie Zhai https://reviews.llvm.org/p/xiangzhai/

2 1

Share exist memory over IPC with L4Re
by Alexander Fratzer 16 May '17

16 May '17

Dear L4-Hackers, I have a very simple problem but I can't find the solution in the L4Re-Doc and examples so far. I wrote a very simple Unix-Like Shell with a Filesystem-Server and a Loader-Server and I implemented some Posix-Call as an abstraction for the communication with the Filesystem-Server (virtual). Now I have a problem of double copies for a read-Operation. I want a complete abstraction from the L4Re mechanisms and the underlying Client-Server architecture for the usage of this interface. The (bad) mechanism is as follow: Function (client side): ssize_t read(int fd, void *buf, size_t count) Algorithm: 1. Allocate Dataspace with size of count. 2. Send Cap of Dataspace to the Filesystem-Server. 3. Copy content of Dataspace to buf. 4. Cleanups. Function (server side): long VFSSrv::op_file_read(VFS::Rights, TaskRegistry::TaskId task, TaskRegistry::FileDescriptor fd, size_t size, L4::Ipc::Snd_fpage& flexp, size_t& rsize) Algorithm: 1. Get Dataspace-Cap from Ipc-fpage. 2. Reserve area with Region-Manager. 3. Attach Dataspace to the area. 4. Copy content of the file to the attached area. 5. Cleanups. This was my first working solution without focus on runtime but the creation of a new task from an ELF-File of 1.4 MB size takes 20 seconds on Cortex A8. This suxx so I have to optimize. Therefor I need a way to share the content of my file (virtual, heap allocated memory) without copying to the client but i don't find a way to share exist memory over IPC. I think I'm using the Dataspace-mechanism in a wrong way but maybe a Dataspace isn't the right choice in my case. A simple solution would be a new Filesystem which is based on Dataspaces but I don't want to do this. Have anybody a better idea? Thanks for help. Best regards Alex.

2 1

Fiasco.OC: null-pointer dereference?
by Stefan Kalkowski 09 May '17

09 May '17

Dear L4-Hackers, recently, I started to upgrade the Fiasco.OC kernel version that is used by the Genode OS framework to the lastly released version (r72). I took the opportunity to upgrade, because the upcoming Genode release uses a fresh compiler toolchain that refused to build the very old Fiasco.OC kernel version that was used until now (r56). Everything went quite smoothly, and I'm glad to see how the kernel develops further. Thanks to all developers at this point! Unfortunately, I stumbled across an issue when it comes to thread destruction. In our system all threads are constructed and destructed by the roottask that is called 'core'. In some cases, not always but quite often, the Ram_quota pointer of the thread object is zero during the call of the Thread_oject's delete operator, which leads to a page-fault within the kernel-code. A simple check[1] before dereferencing the pointer solves the problem, but I wonder whether we will leak quota or memory then, or in general cover some more serious problem. Obviously, we have different usage patterns of syscalls, e.g.: the order of destructing IPC-gates, threads, IRQs, and tasks. Moreover, we still have some very few patches[2] so that the kernel meets our requirements. But none of them explains the thread's Ram_quota pointer getting zero. The page-fault triggers across all x86 and arm platforms that we use. Any hint would be very much appreciated, all the best! Stefan [1] https://github.com/skalk/foc/commit/2b01c9d16fd8e29e6af18fe750be2c8a312b4762 [2] https://github.com/skalk/foc/commits/r72 -- Stefan Kalkowski Genode Labs https://github.com/skalk · http://genode.org/

2 3

Trying to build L4 on NixOS
by Mateusz Czaplinski 09 Apr '17

09 Apr '17

I'm trying to build L4 on NixOS in a VM (long term goal: try to learn how to replace NixOS's kernel with L4Linux, then maybe Genode). I'm getting an error like below: undefined reference to `__stack_chk_fail' during linking of bootstrap.elf - in a GCC's error-barf just after: [bootstrap] ==> Linking bootstrap.elf I've put up the precise Nix expression/script I'm using to build it on github - at: https://github.com/akavel/l4.nix/blob/0108dfcf8d84780e1ba884c41ece0d2dbf4dd… but what it generally boils down to is a sequence of commands like this: $ wget http://os.inf.tu-dresden.de/download/snapshots/l4re-core-2016082114.tar.xz $ tar xf l4re-core-2016082114.tar.xz $ cd l4re-core-2016082114 $ mkdir out $ cp src/l4/mk/defconfig/config.amd64 out/l4/.kconfig $ make -C src/l4 O=out/l4 olddefconfig $ make -C out/l4 I've tried various additional changes, based on some snippets found here and there on teh Internets, like: - adding V=0 to the last make (no idea what it does yet, just some cargo culting) - adding NIX_CFLAGS_COMPILE = "-fno-stack-protector"; to the Nix expression/script (also not really sure where it applies in the stack); but none of the above helped. Any idea what I could try doing to push it further? Thanks, /Mateusz.

2 7

Questions about Fiasco.OC scheduler and L4Linux
by Marc CHALAND 02 Apr '17

02 Apr '17

Hi, I'm doing a study to port old software on top of Fiasco.OC. This soft uses routines which blocks thread scheduling between EnterRegion and LeaveRegion call. Is there any equivalent on TUDOS ? Did somebody already get this challenge ? I would like to know if L4Linux uses Fiasco.OC scheduler or a user land one ? For our i.MX7d board, Freescale provides Linux drivers on 4.1. I don't know yet how many drivers we will need. Do you think it is better to port drivers from 4.1 to L4Linux 4.3 or later or get a L4Linux 4.1. I have no idea about the complexity on doing this. Regards Marc

4 13

L4linux __raw_writesl/readl undefined
by Manolis Ragkousis 01 Apr '17

01 Apr '17

Hello everyone, I am trying to enable sd card support on my zedboard running l4linux and I get this error: ERROR: "__raw_writesl" [drivers/mmc/host/mmci.ko] undefined! ERROR: "__raw_readsl" [drivers/mmc/host/mmci.ko] undefined! make[2]: *** [../scripts/Makefile.modpost:91: __modpost] Error 1 make[1]: *** [/home/manolis/repos/l4linux/Makefile:1173: modules] Error 2 make[1]: *** Waiting for unfinished jobs.... LD ldrImage GZIP vmlinuz LOCINST vmlinuz make[1]: Leaving directory '/home/manolis/repos/l4linux/build' make: *** [Makefile:150: sub-make] Error 2 In order to enable sd card support I understand that I need to enable MMC/SD/SDIO card support in the kernel + ARM AMBA Multimedia Card Interface support. I have followed the instructions from previous emails in this list [1][2]. What am I missing? Is there a config option which enables raw writes/reads on top of L4? Thank you for you time and help, Manolis [1] https://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/006296.html [2] https://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/006417.html

2 2

Can't find device node in /dev/ directory!
by li94575 21 Mar '17

21 Mar '17

Hi, I added some drivers in l4linux, of course, I assigned the corresponding peripheral resources (iomem, irq) to these drivers. From the driver's output log, it seems that they all work well, but when entering the command line, I could not find any relevant device node in /dev/ directory. To my confusion, I can see these devices info in /sys/ directory. The command line args is showing below: mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd ramdisk_size=4000 Any idea?

5 6

Re: Extending l4sys by reading/writing register values of a preempted thread
by Christian Ludwig 21 Mar '17

21 Mar '17

Hi, > I want to implement a new syscall for getting/setting stored register > values of a specific thread (identified by its cap). Why not use ex_regs() on the thread to trigger an exception. That way, the attached userland exception handler can introspect the thread's complete register set. It can also alter the registers, so that the thread continues to run with the modified register set. Is there anything more you need? > Before implementing the syscall, I need to better understand the > kernel-part of Fiasco.OC. Can you help me answer the following questions > and point me to the source code regarding each question: > > * Where (in the source code) are threads preempted and their register > state stored? A thread's userland registers are stored on every entry to the kernel. The class in Fiasco is called Entry_frame. The userland exception handler mentioned above modifies that Entry_frame. > * Where is the register state of a thread loaded to the CPU and the > thread started (e.g. after a preempt)? When the scheduler selects a thread, its userland state (Entry_frame) is restored on exit from kernel mode. > * How can I introspect the stored thread register of a thread in the > kernel debugger JDB? > ** My thoughts: Is it K<kobj_ptr> with kobj_ptr of the thread and the 3 > lines beginning with PC=...? > e.g. > " > PC=010579cc USP=200ffdb0 smlatbeq r9, r0, r2, r5 > [0] 00000003 000010c0 00218003 00000000 tsteq000r5, ip, rrx > [8] 200ffdb0 200ffe40 01086ef0 200ffe98 [c] 200ffef8 010579cc fffffff8 > 20000010 > " Yes, that PC line is the userland program counter. the USP is the userland stack pointer. All userland registers are located at the top of kernel stack for a particular thread. > I also have another, short, off-topic question: > * How can I introspect the capability space of a task inside the kernel > debugger? In short mode, press 's' for a list of all tasks. Select the task in question and the press 'o' to see the capability space for that task. Hope that helps, - Christian

3 2

Extending l4sys by reading/writing register values of a preempted thread
by Denis Huber 13 Mar '17

13 Mar '17

Dear L4 hackers community, I want to implement a new syscall for getting/setting stored register values of a specific thread (identified by its cap). Preliminary note: I'm using the ARM architecture. Before implementing the syscall, I need to better understand the kernel-part of Fiasco.OC. Can you help me answer the following questions and point me to the source code regarding each question: * Where (in the source code) are threads preempted and their register state stored? * Where is the register state of a thread loaded to the CPU and the thread started (e.g. after a preempt)? * Where is the register state stored of each thread? * How can I introspect the stored thread register of a thread in the kernel debugger JDB? ** My thoughts: Is it K<kobj_ptr> with kobj_ptr of the thread and the 3 lines beginning with PC=...? e.g. " PC=010579cc USP=200ffdb0 smlatbeq r9, r0, r2, r5 [0] 00000003 000010c0 00218003 00000000 tsteq000r5, ip, rrx [8] 200ffdb0 200ffe40 01086ef0 200ffe98 [c] 200ffef8 010579cc fffffff8 20000010 " I also have another, short, off-topic question: * How can I introspect the capability space of a task inside the kernel debugger? Kind regards, Denis

1 0

Run L4Re/Fiasco hello example under QEMU (ARM)
by Piotr Piwko 05 Mar '17

05 Mar '17

Hi, I would like to run hello example under qemu-system-arm, so I successfully built the images using gcc-linaro-6.3.1 toolchain with following configuration: L4Re: Target Architecture (ARM architecture) CPU variant (ARMv7A type CPU) Platform Selection (ARM Integrator) Fiasco: Architecture (ARM processor family) Platform (ARM Integrator Platform) CPU (ARM 926 Processor) Unfortunately, after booting boostrap_hello.elf image under qemu-system-arm (the latest 2.8.0 version) there is nothing printed out on the console: $ QEMU_OPTIONS="-machine integratorcp -m 256 -serial mon:stdio -nographic" make qemu E=hello MODULE_SEARCH_PATH=/path/to/fiasco/build/ Do you have any idea what I omitted or what is wrong in my setup? Thank you in advance for your help. -- Piotr Piwko http://www.embedded-engineering.pl/

2 1

read/write to virtual address
by Daniel Krefft 17 Feb '17

17 Feb '17

Hello, while working on a checkpoint/restore mechanism for fiasco.oc, we want to trace read and write (kernel) calls to (virtual) memory. 1) Where are these calls defined? We're just able to find ARM specific calls inside the kernel, which allow writing and reading to/from a virtual address 2) Are these calls (if existent) platform agnostic (user-space)? Is there any kind of interface? Best regards -- Daniel Krefft MSc. Wissenschaftlicher Mitarbeiter Technische Universitaet Muenchen Fakultaet fuer Informatik Lehrstuhl fuer Betriebssysteme Arcisstrasse 21 80333 Muenchen Tel. +49 89 289 18791 daniel.krefft(a)tum.de www.os.in.tum.de/personen/krefft

3 7

About l4linux debug method
by li94575 17 Jan '17

17 Jan '17

Hi all, I have faced a thorny problem, l4linux died occasionally after running into the command line, and there are no errors displayed, pressing the ESC key also cannot enter fiasco jdb-mode. I don't know what caused the problem, can someone provide some methods to help locating this problem? Thanks in advance!

2 7

Memory usage analysis and optimization
by Jesse-SC Chou (周書正) 20 Dec '16

20 Dec '16

Hi L4-hackers, I’m analyzing the memory usage of Fiasco/L4Re/L4Linux. On my platform, there are 128MB physical memory. L4 bootstrap can detect it correctly. ================================================== L4 Bootstrapper Build: #164 拻 12堎 9 11:39:51 CST 2016, 4.8.4 Scanning up to 128 MB RAM, starting at offset 32MB Memory size is 128MB (20000000 - 27ffffff) RAM: 0000000020000000 - 0000000027ffffff: 131072kB Total RAM: 128MB ================================================== The memory regions after boot up and sigma0 loaded: ================================================== Regions of list 'regions' [ 20000000, 200001c7] { 1c8} Root mbi_rt [ 20001000, 20001aff] { b00} Kern fiasco [ 20002000, 20092fff] { 91000} Kern fiasco [ 200c0000, 200c9f43] { 9f44} Sigma0 sigma0 [ 200d0000, 200d6177] { 6178} Sigma0 sigma0 [ 20140000, 20168c27] { 28c28} Root moe [ 20170000, 2017b58b] { b58c} Root moe [ 21000000, 2100e5e3] { e5e4} Boot bootstrap [ 21100000, 21a2dfff] { 92e000} Root Module SIGMA0: Hello! KIP @ 20002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:20000000;20000fff] [0:20093000;200bffff] [0:200ca000;200cffff] [0:200d7000;2013ffff] [4:20140000;20168fff] [0:20169000;2016ffff] [4:20170000;2017bfff] [0:2017c000;210fffff] [4:21100000;21a2dfff] [0:21a2e000;26ffffff] ================================================== The largest unused continuous memory region are at “0x21a2e000 ~ 0x26ffffff”, which is about 85MB. I would like to make continuous memory region larger and have the following ideas and questions: 1. The memory used by bootstrap may be freed after the system bring up. If moving “bootstrap” program to 0x26000000, the “Module” programs can append to “MOE” program. The “Module” will be started “0x207c0000” (aligned to page size 4KB). Thus, I can get larger continuous memory area that originally separated by “bootstrap” program. Is this idea correct ? [ 20170000, 2017b58b] { b58c} Root moe [ 21000000, 2100e5e3] { e5e4} Boot bootstrap [ 21100000, 21a2dfff] { 92e000} Root Module 2. There are a reserved region “0x27000000 ~ 0x27FFFFFF” not shown in boot log. When I traced into program, this region seems used by sigma0. What is this memory used for? I think 16MB is a very large chunk in current embedded system. Can we compute the amount this area really use and shrink to a smaller size? Any suggestion is very appreciated. Thanks. BRs, Jesse

2 2

About IO server settings for DMA in L4Linux
by Jesse-SC Chou (周書正) 13 Dec '16

13 Dec '16

Hi L4-hackers, I'm a newbie of L4 micro-kernel. The Fiasco/L4/L4Linux is really a good design for system architecture in the future. I'm trying to porting the L4 system to my target then evaluate. On my target, there is an DMA controller, which moves data to flash. Originally, Native-Linux uses dma_alloc_coherent() to allocate a DMA-dedicated memory. CPU copies data to that DMA-dedicated memory, then DMA controller moves data from DMA-dedicated memory to flash. In L4Linux, I guess there should be some settings of DMA in I/O server configuration files. I'm searching for an example of configuring DMA-related settings. I use the snapshot “l4re-snapshot-2016082114”. In my current configuration, "DEVICE1" is the DMA controller, "DEVICE2" is the flash, and "DMAMEM" is the DMA-dedicated memory. However, it generates some DMA-related error in boot messages. Such as: IO | no 'iommu' capability found use CPU-phys for DMA IO | warning: inconsistent fixed resource @ device: /System Bus/ error: failed to get physical address for 2000000. And so on. The first thing I want to do is to make the boot message correct and I have the following questions: 1. Is the "DMAMEM" device needed to be configured? If needed, how to specify this to be a DMA memory? 2. Will dma_alloc_coherent() use the "DMAMEM" or other memory? Can I use dma_alloc_coherent() as Native-Linux? 3. I've also found a flag "Property.flags = Io.Hw_device_DF_dma_supported;". I'm not sure its usage. I just add this flag to DEVICE1(DMA controller) and DEVICE2(flash), is it correct? 4. Is my l4linux-io.devs and l4linux-io.io correct or need other modification for DMA? 5. I’ve found “IO | DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6)” in the boot message. What the “DMADOM” means? Any suggestion is very appreciated. Thanks. BRs, Jesse Here is my configurations: ---------------------------------------- l4linux-io.cfg: local L4 = require("L4"); loader = L4.default_loader; local lxname = "vmlinuz"; vbus_l4linux = loader:new_channel(); loader:start( { caps = { sigma0 = L4.cast(L4.Proto.Factory, L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; l4linux = vbus_l4linux:svr(); }, log = {"IO", "magenta"}, }, "rom/io -vvv rom/l4linux-io.devs rom/l4linux-io.io"); -- Start Linux loader:start( { caps = { vbus = vbus_l4linux; }, l4re_dbg = L4.Dbg.Warn, log = L4.Env.log:m("rws"), }, "rom/vmlinuz mem=64M console=ttyLv0 l4x_dtb=rom/simple.dtb l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 ramdisk_size=3072"); ---------------------------------------- l4linux-io.devs: local Res = Io.Res local Hw = Io.Hw Io.hw_add_devices(function() DEVICE1 = Hw.Device(function() Property.hid = "device1"; compatible = {"arm,device1"}; Resource.regs = Res.mmio(0x14000000, 0x15ffffff); Property.flags = Io.Hw_device_DF_dma_supported; end); DEVICE2 = Hw.Device(function() Property.hid = "device2"; compatible = {"arm,device2"}; Resource.regs = Res.mmio(0x1F000000, 0x1F3fffff); Resource.irq = Res.irq(66); Property.flags = Io.Hw_device_DF_dma_supported; end); DMAMEM = Hw.Device(function() Property.hid = "dmamem"; compatible = {"arm,dmamem"}; Resource.mmio = Io.Mmio_data_space(0x10000, 0); end); end) ---------------------------------------- l4linux-io.io: local hw = Io.system_bus() Io.add_vbus("l4linux", Io.Vi.System_bus { DEVICE1 = wrap(hw:match("arm,device1")); DEVICE2 = wrap(hw:match("arm,device2")); DMAMEM = wrap(hw:match("arm,dmamem")); }) ---------------------------------------- boot messages: L4 Bootstrapper Build: #164 拻 12堎 9 11:39:51 CST 2016, 4.8.4 Scanning up to 128 MB RAM, starting at offset 32MB Memory size is 128MB (20000000 - 27ffffff) RAM: 0000000020000000 - 0000000027ffffff: 131072kB Total RAM: 128MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 13 modules behind 21100000 moving module 02 { 219d5000-21a064ab } -> { 21ac6000-21af74ab } [201900] moving module 01 { 219c3000-219d434b } -> { 21ab4000-21ac534b } [70476] moving module 00 { 2193d000-219c29db } -> { 21a2e000-21ab39db } [547292] moving module 12 { 21935000-2193cd5d } -> { 21a26000-21a2dd5d } [32094] moving module 11 { 21635000-21934fff } -> { 21726000-21a25fff } [3145728] moving module 10 { 2121b000-21634487 } -> { 2130c000-21725487 } [4297864] moving module 09 { 2121a000-2121a0fa } -> { 2130b000-2130b0fa } [251] moving module 08 { 21219000-2121939b } -> { 2130a000-2130a39b } [924] moving module 07 { 2109e000-212188db } -> { 2118f000-213098db } [1550556] moving module 06 { 21084000-2109d583 } -> { 21175000-2118e583 } [103812] moving module 05 { 2102a000-210836b7 } -> { 2111b000-211746b7 } [366264] moving module 04 { 21010000-21029473 } -> { 21101000-2111a473 } [103540] moving module 03 { 2100f000-2100f325 } -> { 21100000-21100325 } [806] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page (via ELF) at 20002000 Regions of list 'regions' [ 20000000, 200001c7] { 1c8} Root mbi_rt [ 20001000, 20001aff] { b00} Kern fiasco [ 20002000, 20092fff] { 91000} Kern fiasco [ 200c0000, 200c9f43] { 9f44} Sigma0 sigma0 [ 200d0000, 200d6177] { 6178} Sigma0 sigma0 [ 20140000, 20168c27] { 28c28} Root moe [ 20170000, 2017b58b] { b58c} Root moe [ 21000000, 2100e5e3] { e5e4} Boot bootstrap [ 21100000, 21a2dfff] { 92e000} Root Module found kernel options (via ELF) at 20003000 API Version: (87) experimental Sigma0 config ip:200c0100 sp:00000000 Roottask config ip:2014020c sp:00000000 Starting kernel fiasco at 200012b8 Realview System ID: Rev=0 HBI=000 Build=0 Arch=0 FPGA=00 Invalid System ID for this kernel config Expected (00000000 & cfffff00) == 0190f500 Stopping. Hello from Startup::stage2 Number of IRQs available at this GIC: 160 FPU: Initialize FPU0: Subarch: 2, Part: 30, Rev: 5, Var: 7, Impl: 41 ARM generic timer: freq=6000000 interval=6000 cnt=18158508199882336289 SERIAL ESC: allocated IRQ 98 for serial uart Not using serial hack in slow timer handler. Welcome to L4/Fiasco.OC! L4/Fiasco.OC microkernel on arm Rev: r72 compiled with gcc 4.8.4 for Realview [] Build: #16 Tue Nov 29 12:16:44 CST 2016 Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 20002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:20000000;20000fff] [0:20093000;200bffff] [0:200ca000;200cffff] [0:200d7000;2013ffff] [4:20140000;20168fff] [0:20169000;2016ffff] [4:20170000;2017bfff] [0:2017c000;210fffff] [4:21100000;21a2dfff] [0:21a2e000;26ffffff] IOMEM:---------------------- [0:0;1fffffff] [0:28000000;ffffffff] MOE: Hello world MOE: found 104420 KByte free memory MOE: found RAM from 20000000 to 27000000 MOE: allocated 112 KByte for the page array @0x20093000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:103000] BOOTFS: [21100000-21100326] [C:105000] l4linux-io.cfg BOOTFS: [21101000-2111a474] [C:107000] l4re BOOTFS: [2111b000-211746b8] [C:109000] ned BOOTFS: [21175000-2118e584] [C:10b000] hello BOOTFS: [2118f000-213098dc] [C:10d000] io BOOTFS: [2130a000-2130a39c] [C:10f000] l4linux-io.devs BOOTFS: [2130b000-2130b0fb] [C:111000] l4linux-io.io BOOTFS: [2130c000-21725488] [C:113000] vmlinuz BOOTFS: [21726000-21a26000] [C:115000] ramdisk-arm.rd BOOTFS: [21a26000-21a2dd5e] [C:117000] simple.dtb MOE: cmdline: moe rom/l4linux-io.cfg MOE: Starting: rom/ned rom/l4linux-io.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4linux-io.cfg' IO | Io service IO | Verboseness level: 4 IO | unused physical memory space: IO | [00000000000000-0000001fffffff] IO | [00000028000000-000000ffffffff] IO | no 'iommu' capability found use CPU-phys for DMA IO | Loading: config 'rom/l4linux-io.devs' IO | warning: inconsistent fixed resource @ device: /System Bus/ IO | : hid=device1 IO | DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6) IO | warning: inconsistent fixed resource @ device: /System Bus/ IO | : hid=device2 IO | DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6) IO | Loading: config 'rom/l4linux-io.io' IO | Real Hardware ----------------------------------- IO | System Bus: hid= IO | Resources: ==== start ==== IO | DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6) IO | Resources: ===== end ===== IO | DEVICE1: hid=device1 IO | Clients: ===== start ==== IO | DEVICE1: [N2Vi9Proxy_devE] IO | Clients: ===== end ==== IO | Resources: ==== start ==== IO | IOMEM [00000014000000-00000015ffffff 2000000] non-pref (32bit) (align=1ffffff flags=2) IO | DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6) IO | Resources: ===== end ===== IO | DEVICE2: hid=device2 IO | Clients: ===== start ==== IO | DEVICE2: [N2Vi9Proxy_devE] IO | Clients: ===== end ==== IO | Resources: ==== start ==== IO | IOMEM [0000001f000000-0000001f3fffff 400000] non-pref (32bit) (align=3fffff flags=2) IO | IRQ [00000000000042-00000000000042 1] none (32bit) (align=0 flags=1) IO | DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6) IO | Resources: ===== end ===== IO | DMAMEM: hid=dmamem IO | Clients: ===== start ==== IO | DMAMEM: [N2Vi9Proxy_devE] IO | Clients: ===== end ==== IO | Resources: ==== start ==== IO | IOMEM [00000020124000-00000020133fff 10000] non-pref (32bit) (align=ffff flags=2) IO | Resources: ===== end ===== IO | warning: could not register control interface at cap 'platform_ctl' IO | Ready. Waiting for request. PH 0 offs=00008000 flags=rwx PH-type=0x1 virt=02000000 evirt=0248c17c phys=02000000 ephys=0248c17c f_sz=004023d5 memsz=0048c17c PH 1 offs=003b7404 flags=r-x PH-type=0x4 virt=023af404 evirt=023af428 phys=023af404 ephys=023af428 f_sz=00000024 memsz=00000024 PH 2 offs=00000000 flags=rwx PH-type=0x6474e551 virt=00000000 evirt=00000000 phys=00000000 ephys=00000000 f_sz=00000000 memsz=00000000 Starting binary at 0x2000330, argc=7 argv=0xafff4f8c *argv=0xb1007ff4 argv0=rom/vmlinuz External resolver is at 0xa80007c4 ======> L4Linux starting... <======== Linux version 4.7.0-l4 (jesse@tplabpcu07640) (gcc version 4.8.4 (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1) ) #119 Thu Dec 8 18:05:42 CST 2016 Binary name: rom/vmlinuz This is an AEABI build. Linux kernel command line (6 args): mem=64M console=ttyLv0 l4x_dtb=rom/simple.dtb l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=3072 CPU mapping (l:p)[1]: 0:0 Image: 02000000 - 02600000 [6144 KiB]. Areas: Text: 02000000 - 023af428 [3773kB] RO-Data: 022c7000 - 02397000 [832kB] Data: 023d8000 - 023fda80 [150kB] Init: 023b0000 - 023d8000 [160kB] BSS: 024023d5 - 0248c17c [551kB] Device scan: Device: L4ICU Device: DMAMEM MEM: 20124000 - 20133fff Device: DEVICE1 MEM: 14000000 - 15ffffff DMAD: 00000000 - 00000000 Device: DEVICE2 MEM: 1f000000 - 1f3fffff IRQ: 00000042 - 00000042 DMAD: 00000000 - 00000000 Device scan done. l4lx_thread_create: Created thread 41d (cpu0) (u:b3000e00, v:b3000c00, sp:023d9fa4) main thread will be 41d L4x: section-with-init(-data): Virt: 0x2000000 to 0x248cfff [4660 KiB] section-with-init(-data): Phys: 0x2017c000 to 0x20608fff, [4660 KiB] L4x: section-with-init-text: Virt: 0x2000000 to 0x248cfff [4660 KiB] error: failed to get physical address for 2000000. L4x: Main thread running, waiting... L4x: Memory size: 64MB L4x: Setting superpages for main memory L4x: Adjusted memory start: 02000000 L4x: Main memory: Virt: 0x2600000 to 0x65fffff [65536 KiB] Main memory: Phys: 0x21c00000 to 0x25bfffff, [65536 KiB] l4x: vmalloc area: 06600000 - 0e600000 L4x: text: Virt: 0x2000000 to 0x248cfff [4660 KiB] error: failed to get physical address for 2000000. Loading: rom/ramdisk-arm.rd INITRD: Size of RAMdisk is 3072KiB RAMdisk from 00002000 to 00302000 [3072KiB] l4lx_thread_create: Created thread 422 (timer0) (u:b3000a00, v:00000000, sp:02423fa0) IO | new iomem region: p=1f000000 v=400000 s=400000 (bmb=0x34470) Booting Linux on physical CPU 0x0 Linux version 4.7.0-l4 (jesse@tplabpcu07640) (gcc version 4.8.4 (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1) ) #119 Thu Dec 8 18:05:42 CST 2016 DTB: virt=02600100 phys=21c00100 CPU: Fiasco [410fc075] revision 5 (ARMv7), cr=00400000 CPU: div instructions available: patching division code CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine model: L4Linux (DT) Memory policy: Data cache writealloc CPU: All CPU(s) started in SVC mode. INITRD: 00002000 - 00302000 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 17717 Kernel command line: mem=64M console=ttyLv0 l4x_dtb=rom/simple.dtb l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=3072 PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 64632K/71684K available (2941K kernel code, 150K rwdata, 832K rodata, 160K init, 551K bss, 7052K reserved, 0K cma-reserved) Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xfff00000 (3072 kB) vmalloc : 0x06600000 - 0x0e600000 ( 128 MB) lowmem : 0x00000000 - 0x06600000 ( 102 MB) modules : 0x01010000 - 0x02000000 ( 15 MB) .text : 0x02000000 - 0x023af428 (3774 kB) .init : 0x023b0000 - 0x023d8000 ( 160 kB) .data : 0x023d8000 - 0x023fda80 ( 151 kB) .bss : 0x024023d5 - 0x0248c17c ( 552 kB) NR_IRQS:282 clocksource: l4kipclk: mask: 0xffffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 3526361616960 ns l4timer: Using IRQ210 sched_clock: 64 bits at 1000kHz, resolution 1000ns, wraps every 2199023255500ns __l4x_ioremap: Mapping physaddr 1f000000 [0x400000 Bytes, 1f000000+400000] to 00400000+000000 clocksource_probe: no matching clocksources found Console: colour dummy device 80x30 console [ttyLv0] enabled Calibrating delay loop... 1594.16 BogoMIPS (lpj=7970816) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok Setting up static identity map for 0x2000000 - 0x2000000 VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5 clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations Failed to create "l4x" debugfs directory: 1 clocksource: Switched to clocksource l4kipclk NET: Registered protocol family 2 TCP established hash table entries: 1024 (order: 0, 4096 bytes) TCP bind hash table entries: 1024 (order: 0, 4096 bytes) TCP: Hash tables configured (established 1024 bind 1024) UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (junk in compressed archive); looks like an initrd INITRD: Freeing memory. l4x: Checks passed. NetWinder Floating Point Emulator V0.97 (double precision) futex hash table entries: 256 (order: -1, 3072 bytes) workingset: timestamp_bits=29 max_order=14 bucket_order=0 squashfs: version 4.0 (2009/01/31) Phillip Lougher jffs2: version 2.2. ? 2001-2006 Red Hat, Inc. io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) L4 serial driver serial-ttyLv.0: ttyLv0 at MMIO 0x1 (irq = 211, base_baud = 230400) is a L4-vcon l4ser_shm: L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded l4bdds: No name given, not starting. mousedev: PS/2 mouse device common for all mice IO | new iomem region: p=14000000 v=2000000 s=2000000 (bmb=0x344f8) __l4x_ioremap: Mapping physaddr 14000000 [0x2000000 Bytes, 14000000+2000000] to 0e600000+000000 Creating 1 MTD partitions on "NOR_FLASH": 0x000000f00000-0x000001000000 : "DATA" NET: Registered protocol family 17 L4IRQ: set irq type of 211 to 1 RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 3072KiB [1 disk] into ram disk... done. EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities EXT4-fs (ram0): mounting ext2 file system using the ext4 subsystem EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) VFS: Mounted root (ext2 filesystem) readonly on device 1:0. Freeing unused kernel memory: 160K (023b0000 - 023d8000) This architecture does not have kernel memory protection. Please press Enter to activate this console.

2 3

Fwd: Microkernels / Component-based OSes devroom - Call for Participation
by Norman Feske 18 Oct '16

18 Oct '16

Hello L4 hackers, I'd like to invite you to the microkernel developer room at the upcoming FOSDEM in Brussels. Please find the call for participation below. Cheers Norman FOSDEM 2017 - Microkernels / Component-based OSes devroom CALL FOR PARTICIPATION The developers of several free and open-source microkernel-based operating systems will meet at FOSDEM 2017 [1] in Brussels, Belgium and will share a developer room on Saturday of February 04, 2017 [2]. The devroom is currently looking for content in the form of talks and activities related to the area of microkernel-based operating systems. Possible topics include, but are not limited to: * Introduction of a specific OS or framework * Design of subsystems and the general architecture of an OS * Enabling support for hardware (architectures, device drivers) * Used languages and tools * Maintainance and testing * Security and robustness * Trends and challenges * Use cases, experiences, lessons learned and demos Please use the Pentabarf [3] system to submit your proposals and file it under the track “Microkernels and Component-based OS”. You do not need to create a new account if you already have one. When in doubt, please use the devroom mailing list [4]. 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 mailing list. The deadline for your proposal is on December the 4th. 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 (one or two paragraphs) * Duration of your talk (please, at least 25 and no longer than 45 min) The official devroom schedule (along with the accepted talks) will be announced on December the 11th on the devroom's mailing list and the speakers will be notified via e-mail. The schedule will also be published on the FOSDEM website. About FOSDEM FOSDEM is a two-day event organised by volunteers to promote the widespread use of free and open source software. Taking place in the beautiful city of Brussels (Belgium), FOSDEM is widely recognised as the best such conference in Europe. FOSDEM covers a wide spectrum of free and open source software projects, and offers a platform for people to collaborate. To this end, FOSDEM has set up developer rooms (devrooms) with network/internet connectivity and projectors where teams can meet and showcase their projects. Devrooms are a place for teams to discuss, hack and publicly present latest directions, lightning talks, news and discussions. Besides developer rooms, FOSDEM also offers main tracks, lightning talks, certification exams and project stands. Every year, FOSDEM hosts more than 5000 developers at the ULB Solbosch campus. Participation and attendance is totally free, though the organisers gratefully accept donations and sponsorship. No registration necessary. About the devroom Since the first Microkernel devroom in 2012 this devroom has been part of each following FOSDEM. By now it has become a somewhat institutionalized tradition for the micro kernel community to meet there; to this date over a dozen projects have participated in one way or another. Each of the projects face similar challenges but come up with partially differend solutions. Therefore, the goal of the Microkernel devroom is to bring the various projects together, let them exchange ideas, cross-pollinate and socialize. Social events It also has become a habit that the microkernel projects dine together somewhere in downtown Brussels after the devroom closes. The year 2017 will not be any different, so there is going to be a microkernel family dinner on Saturday night. The exact location and time will be specified later. Consult the FOSDEM web and other projects for additional social events such as the famous FOSDEM-organized Friday Beer Event and the FOSDEM-arranged free sightseeing tours for spouses. Important dates recap * 04.12.2016: Deadline for submissions * 11.12.2016: Schedule published and speakers notified of acceptance * 04.02.2017: The devroom takes places Links [1] http://fosdem.org/ [2] https://fosdem.org/2017/practical/transportation/ [3] https://fosdem.org/submit [4] https://lists.fosdem.org/listinfo/microkernel-devroom See you all at FOSDEM!

1 0

fiasco.oc i.MX7d port
by Marc CHALAND 14 Oct '16

14 Oct '16

Hi, I'm trying to port fiasco.oc to i.MX7d. It works, but I cannot start second core. I set trampoline addr into corresponding GPR and enables CORE1. But nothing happens. I saw that trampoline assembler code enables SCU through external registers. But with cortex a7, SCU hasn't got external registers. So, I ifdefed it but CPU0 still doesn't startup. Can somebody help me ? Regards Marc

2 7

L4Linux stop at "Calibrating delay loop ..."
by li94575 09 Oct '16

09 Oct '16

Hi，l4hackers I compiled the l4re-snapshot-2014092821 with the default modules.list, and everything seems goes well. However, L4Linux would stop at "Calibrating delay loop ...", because the value of jiffies did not change. Timer thread has not generate soft interrupt? If I entered jdb via ESC at this time, and quit via "g", then l4linux can run again. It makes me confused so much. Any help or suggestion will be very welcome. The log is showing below: L4 Bootstrapper Build: #12 2016年 09月 19日星期一 18:58:15 CST, 4.8.3 20140320 (prerelease) Scanning up to 2048 MB RAM, starting at offset 32MB Memory size is 2048MB (00000000 - 7fffffff) RAM: 0000000000000000 - 000000007fffffff: 2097152kB Total RAM: 2048MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 10 modules behind 1100000 moving module 02 { 1968000-19a163f } -> { 1a58000-1a9163f } [235072] moving module 01 { 195e000-196738b } -> { 1a4e000-1a5738b } [37772] moving module 00 { 18f8000-195d9db } -> { 19e8000-1a4d9db } [416220] moving module 09 { 15f8000-18f7fff } -> { 16e8000-19e7fff } [3145728] moving module 08 { 11d6000-15f7497 } -> { 12c6000-16e7497 } [4330648] moving module 07 { 11d5000-11d50bc } -> { 12c5000-12c50bc } [189] moving module 06 { 107e000-11d446f } -> { 116e000-12c446f } [1401968] moving module 05 { 107d000-107d19b } -> { 116d000-116d19b } [412] moving module 04 { 102a000-107cc1f } -> { 111a000-116cc1f } [338976] moving module 03 { 1010000-1029473 } -> { 1100000-1119473 } [103540] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list 'regions' [ 1000, 1aff] { b00} Kern fiasco [ 2000, 72fff] { 71000} Kern fiasco [ 73000, 7315f] { 160} Root mbi_rt [ 90000, 96edf] { 6ee0} Sigma0 sigma0 [ 98000, 9e177] { 6178} Sigma0 sigma0 [ 140000, 171d8f] { 31d90} Root moe [ 178000, 1934ab] { 1b4ac} Root moe [ 1000000, 100f58b] { f58c} Boot bootstrap [ 1100000, 19e7fff] { 8e8000} Root Module API Version: (87) experimental Sigma0 config ip:00090100 sp:00000000 Roottask config ip:00140260 sp:00000000 Starting kernel fiasco at 000012e0 Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf0061720-0xf00620e8) Number of IRQs available at this GIC: 128 FPU0: Arch: Unkn(2), Part: VFPv3(30), r: 5, v: 7, i: 41, t: hard, p: dbl/sngl ARM generic timer: freq=1000000 interval=1000 cnt=-262144 SERIAL ESC: allocated IRQ 89 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: 8fd26ca-dirty compiled with gcc 4.8.3 for [] Build: #3 Mon Sep 19 18:55:38 CST 2016 Per_cpu_data_alloc: (orig: 0xf0061720-0xf00620e8) Allocate 2504 bytes (2KB) for CPU[4] local storage (offset=118a8e0, 0xf11ec000-0xf11ec9c8) cpu1: powered-up Per_cpu_data_alloc: (orig: 0xf0061720-0xf00620e8) cpu2: powered-up Allocate 2504 bytes (2KB) for CPU[1] local storage (offset=118c8e0, 0xf11ee000-0xf11ee9c8) cpu3: powered-up FPU1: Arch: Unkn(2), Part: VFPv3(30), r: 5, v: 7, i: 41, t: hard, p: dbl/sngl Calibrating timer loop... Per_cpu_data_alloc: (orig: 0xf0061720-0xf00620e8) done. Allocate 2504 bytes (2KB) for CPU[2] local storage (offset=118f8e0, 0xf11f1000-0xf11f19c8) Cache config: ON MDB: use page size: 30 FPU2: Arch: Unkn(2), Part: VFPv3(30), r: 5, v: 7, i: 41, t: hard, p: dbl/sngl ID_PFR[01]: 00001131 00011011Per_cpu_data_alloc: (orig: 0xf0061720-0xf00620e8) MDB: use page size: 21 Allocate 2504 bytes (2KB) for CPU[3] local storage (offset=11968e0, 0xf11f8000-0xf11f89c8) ID_[DA]FR0: 02010555 00000000 Cache config: ON MDB: use page size: 12 FPU3: Arch: Unkn(2), Part: VFPv3(30), r: 5, v: 7, i: 41, t: hard, p: dbl/sngl ID_PFR[01]: 00001131 00011011SID_MMFR[04]: 10101105 40000000 01240000 02102211 Cache config: ON ID_[DA]FR0: 02010555 00000000 ID_PFR[01]: 00001131 00011011ID_MMFR[04]: 10101105 40000000 01240000 02102211 ICPU[2]: goes to idle loop ID_[DA]FR0: 02010555 00000000 GID_MMFR[04]: 10101105 40000000 01240000 02102211 CPU[1]: goes to idle loop CPU[3]: goes to idle loop MA0: Hello! KIP @ 2000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:0;fff] [4:73000;73fff] [0:74000;8ffff] [0:97000;97fff] [0:9f000;13ffff] [4:140000;171fff] [0:172000;177fff] [4:178000;193fff] [0:194000;10fffff] [4:1100000;19e7fff] [0:19e8000;3effffff] [0:40000000;7fffffff] IOMEM:---------------------- [0:80000000;ffffffff] MOE: Hello world MOE: found 2070816 KByte free memory MOE: found RAM from 73000 to 80000000 MOE: allocated 2047 KByte for the page array @0x194000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [1100000-1119474] [C:503000] l4re BOOTFS: [111a000-116cc20] [C:504000] ned BOOTFS: [116d000-116d19c] [C:505000] l4lx.cfg BOOTFS: [116e000-12c4470] [C:506000] io BOOTFS: [12c5000-12c50bd] [C:507000] arm-rv.io BOOTFS: [12c6000-16e7498] [C:508000] vmlinuz.arm BOOTFS: [16e8000-19e8000] [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' l4linux | libio: Warning: Query of 'vbus' failed! l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=024c8dd4 l4linux | phys= 02000000 ephys=024c8dd4 l4linux | f_sz= 00404594 memsz=004c8dd4 flgs=rwx l4linux | PH 1 (t: 4) offs=003b44e0 vaddr=023ac4e0 vend=023ac504 l4linux | phys= 023ac4e0 ephys=023ac504 l4linux | f_sz= 00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys= 00000000 ephys=00000000 l4linux | f_sz= 00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x2000360, argc=8 argv=0xafff4f84 *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa8000788 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.16.0-l4 (li94575@li94575-Lenovo) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #3 SMP Mon Sep 19 18:57:16 CST 2016 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (7 args): mem=64M l4x_cpus=4 l4x_cpus_map=0,1,2,3 console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 l4linux | CPU mapping (l:p)[4]: 0:0, 1:1, 2:2, 3:3 l4linux | Image: 020000a0 - 02600000 [6143 KiB]. l4linux | Areas: Text: 020000a0 - 023d6000 [3927kB] (a bit longer) l4linux | Data: 023d6000 - 023ff520 [165kB] l4linux | Initdata: 023ad000 - 023d57c0 [161kB] l4linux | BSS: 02404594 - 024c8dd4 [786kB] l4linux | Device scan: l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:023d7fa4) l4linux | main thread will be 413 l4linux | l4x_register_pointer_section: addr = 02000000 size = 5017600 l4linux | section-with-init: Virt: 0x2000000 to 0x24c8dd3 [4899 KiB] l4linux | section-with-init: Phys: 0x0042b000 to 0x008f3dd3, [4899 KiB] l4linux | Main thread running, waiting... l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 02000000 l4linux | Main memory: Virt: 0x2600000 to 0x65fffff [65536 KiB] l4linux | Main memory: Phys: 0x01a00000 to 0x059fffff, [65536 KiB] l4linux | l4x: vmalloc area: 06600000 - 0e600000 l4linux | l4x_register_pointer_section: addr = 02000000 size = 5017600 l4linux | text: Virt: 0x2000000 to 0x24c8dd3 [4899 KiB] l4linux | text: Phys: 0x0042b000 to 0x008f3dd3, [4899 KiB] l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] l4linux | l4lx_thread_create: Created thread 419 (timer0) (u:b3000a00, v:00000000, sp:0245dfa0) Booting Linux on physical CPU 0x0 Linux version 3.16.0-l4 (li94575@li94575-Lenovo) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #3 SMP Mon Sep 19 18:57:16 CST 2016 CPU: Fiasco [410fc075] revision 5 (ARMv7), cr=00000000 CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: L4 Ignoring unrecognised tag 0x00000000 Forcing write-allocate cache policy for SMP Forcing shared mappings for SMP Memory policy: Data cache writealloc INITRD: 00002000 - 00302000 PERCPU: Embedded 5 pages/cpu @06509000 s6080 r0 d14400 u32768 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 17716 Kernel command line: mem=64M l4x_cpus=4 l4x_cpus_map=0,1,2,3 console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 64728K/71680K available (3157K kernel code, 165K rwdata, 604K rodata, 161K init, 786K bss, 6952K reserved) Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xffe00000 (2048 kB) vmalloc : 0x06600000 - 0x0e600000 ( 128 MB) lowmem : 0x00000000 - 0x06600000 ( 102 MB) .text : Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xffe00000 (2048 kB) vmalloc : 0x06600000 - 0x0e600000 ( 128 MB) loHierarchical RCU implementation. NR_IRQS:220 l4timer: Using IRQ210 sched_clock: 64 bits at 1000kHz, resolution 1000ns, wraps every 2147483648000ns Console: colour dummy device 80x30 console [ttyLv0] enabled Calibrating delay loop...

3 7

Is L4Linux can use its existed Linux driver to access hardware device?
by Zhe Zhao 14 Sep '16

14 Sep '16

Hi, After read the basic ideas of L4Linux I have some questions related to it. Is L4Linux run as a paravirtualization VM on L4Re? Then the traditional Linux Process just still compiled against Linux system and put them together with L4Linux disk image? so it means L4Re works like qemu and Linuxl? or L4Re works as a micro kernel operating system, and L4Linux run as a process on it, all devices handled to L4Linux to reuse the drivers of L4Linux? and the previous Linux process compiled with Linux, but run direct on L4Re as L4 processes which communicate with L4Linux through IPC? it is quite confused after read a little of the codes, in L4Linux, seems there is some injection of L4 task stuffs inside thread_struct of Linux, but also have some vCPU related stuffs, can you help me about what is the real behavior of L4Linux? I'm sorry to ask this basic questions, but after some digging I feel quite confused about how it works. Thanks Br Alex

2 7

Partitioned Scheduling
by Edinger, Stefan 09 Sep '16

09 Sep '16

Hi, is it possible to have partitioned scheduling in the way that one can use different schedulers for different cpu-cores? And if yes, can I do the mapping from scheduler to core on runtime or is it done at compile time? Thanks, Stefan

4 7

l4_thread_ex_regs and suspending thread
by Valery V. Sedletski 16 Aug '16

16 Aug '16

hi, l4-hackers. I am now using l4v2 API with L4/Fiasco. I know that on L4 v.2 API, the thread is created if set eip/esp/pager/preempter to real values. And it seems that likewise, thread can be suspended if setting these values to invalid ones. But as I tried it, setting the running thread eip/esp to -1 causes double page fault in that thread. Setting them to 0 does not change these values (though, in headers' comments, documented value is ~0). Setting pager/preempter to L4_INVALID_ID also causes double page fault. This is strange, as docs/comments state the converse. So, is it possible anyhow to suspend/resume the running thread from another thread? I know, that the thread can be suspended if entering unconditional l4_ipc_wait(), but this is from the inside that thread. How could it be done from an outside thread? Thanks in advance, valery

4 12

Genode + Fiasco.OC: How to access multiple run queues?
by Guru Siddesh 08 Aug '16

08 Aug '16

Hello L4-hackers , I'm writing a Genode component which should access and modify the Run queues of the scheduler. Based on what I have read and looked there will be one scheduler for each processor. How to access the different scheduler objects and Run queues from Genode side? I have looked through the code and able to print the run queue from the ready_queue_fp.cpp. But how do you access 2 run queues when number of processors is more than one? And what is the easy way to manipulate these from Genode component.? PS: I have read Genode book and have a basic idea of Genode architecture. Best regards, Guru

2 1

memory map/unmap performance
by Yuxin Ren 02 Aug '16

02 Aug '16

Hi all, I am curious memory mapping/unmapping performance. Are there any applications that stress the memory mapping and unmapping utility? Thanks a lot! Yuxin

2 1

USDHC driver for i.MX6
by AIT HMID Moha 29 Jul '16

29 Jul '16

Hi L4 hackers, Is a L4Linux/Fiasco driver for Freescale i.MX6 processor USDHC module available ? If not any input/clue to port an existing implementation ? Best regards, MAH

2 1

l4linux panic on iMX6SX
by AIT HMID Moha 29 Jul '16

29 Jul '16

Hi L4 hackers, I am using l4re-snapshot-2014092821 and running L4Linux/L4 on Freescale iMX6SX SABRE SDB card. Here attached my Fiasco, L4, L4Linux and moe starting configurations and the resulted displayed traces. I got a l4linux 'kernel panic'. Any idea about the issue ? Best regards, MAH

2 1

Question: The future of Fiasco & L4Re
by Ratko Rudič 18 Jul '16

18 Jul '16

Hi hackers! I've been looking at microkernels for some time and am writing a high overview paper about them for our faculty. Adam wrote[1] that all discussions happen mostly in-house so finding info about Fiasco's future is probably hard. So, if any of you hackers have a minute to spare, I'd be glad to hear what you intend to implement in future L4 releases. It doesn't need to have dates - maybe just pointers what you'd like to see in a year or so. Thank you, Ratko Rudic [1] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007538.html

2 1

l4re programming language support
by Michael Schnupp 12 Jul '16

12 Jul '16

Hi, I am aware that pretty much the whole l4re system is written in C++ and that the C(++) binding is the main way to write new tasks. However I also noticed some packages which look like there is also support for languages like fortran, python, and ocaml. Is there any documentation/example on how to use these to write a new task in those languages? (Is there generally any documentation on how to use the existing packages?) I would really love to write own tasks in rust. Is there any chance to build a l4re binary using rust, too? (Is there generally any documentation on how a binary must look like in order to be able to run on l4re?) Rust supports specifying custom linking options and has good support for cross compiling. Especially it also allows linking against musl to build static binaries. All this make me feel it should be possible to target l4re, too, but I really don't understand the l4re build system well enough. Do you see any chance in doing so? Some references: https://doc.rust-lang.org/book/advanced-linking.html https://github.com/japaric/rust-cross Michael

2 1

l4re-snapshot-2016060908 lunch "L4Linux-mag-x86" problem
by 张鑫 07 Jul '16

07 Jul '16

Hi, Everyone, I'm a newer in L4Linux,I get the lastest snapshort and follow the README which builds it successfully, When I execute make qemu in /my_dir/obj/l4/x86 ,it comes up Entry selection , I tested all but "L4Linux-mag-x86" is'nt work successfully. I prebuild the snapshot in Ubuntu 14.04.4 LTS, the following is the ubuntu output message: L4 Bootstrapper Build: #1 Fri Jul 1 02:18:27 PDT 2016, x86-32, 4.8.4 RAM: 0000000000000000 - 000000000009fbff: 639kB RAM: 0000000000100000 - 000000000fffdfff: 261112kB Total RAM: 255MB Scanning /home/zhangxin/Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco -serial_esc Scanning /home/zhangxin/Desktop/l4re-snapshot-2016060908 /obj/l4/x86/bin/x86_586/l4f/sigma0 Scanning /home/zhangxin/Desktop/l4re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg need 1424 bytes to copy MBI reserved 1424 bytes at 0x2000 Moving up to 13 modules behind 1100000 moving module 12 { 3013400-33133ff } -> { 3e32000-4131fff } [3145728] moving module 11 { 2b28400-3012aa4 } -> { 3947000-3e316a4 } [5154469] moving module 10 { 2b27400-2b2765e } -> { 3946000-394625e } [607] moving module 09 { 2b26400-2b26737 } -> { 3945000-3945337 } [824] moving module 08 { 24e6400-2b25ab7 } -> { 3305000-39446b7 } [6551224] moving module 07 { 2209400-24e5ebb } -> { 3028000-3304abb } [3001020] moving module 06 { e86400-2208973 } -> { 1ca5000-3027573 } [20456820] moving module 05 { e85400-e8591b } -> { 1ca4000-1ca451b } [1308] moving module 04 { b24400-e846a5 } -> { 1943000-1ca32a5 } [3539622] moving module 03 { 968400-b23b8f } -> { 1787000-194278f } [1816464] moving module 02 { 41e400-967f0a } -> { 123d000-1786b0a } [5544715] moving module 01 { 378400-41dcbf } -> { 1197000-123c8bf } [678080] moving module 00 { 2e1400-378257 } -> { 1100000-1196e57 } [618072] Loading /Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco Loading re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/sigma0 Loading /l4re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/moe find kernel info page... found kernel info page at 0x400000 Regions of list 'regions' [ 0, fff] { 1000} Arch BIOS [ 1000, 1fff] { 1000} Kern /Desktop/l4re-snapshot- 2016060908/obj/fiasco/ia32/fiasco [ 2000, 258f] { 590} Root mbi_rt [ 9fc00, 9ffff] { 400} Arch BIOS [ f0000, fffff] { 10000} Arch BIOS [ 100000, 10f193] { f194} Sigma0 re-snapshot-2016060908 /obj/l4/x86/bin/x86_586/l4f/sigma0 [ 140000, 17c367] { 3c368} Root /l4re-snapshot-2016060908 /obj/l4/x86/bin/x86_586/l4f/moe [ 2d0400, 2df43f] { f040} Boot bootstrap [ 300000, 38ffff] { 90000} Kern /Desktop/l4re-snapshot- 2016060908/obj/fiasco/ia32/fiasco [ 400000, 49bfff] { 9c000} Kern /Desktop/l4re-snapshot- 2016060908/obj/fiasco/ia32/fiasco [ 1787000, 4131fff] { 29ab000} Root Module [ fffe000, fffffff] { 2000} Arch BIOS [ fffc0000, ffffffff] { 40000} Arch BIOS API Version: (87) experimental Sigma0 config ip:001001d4 sp:00000000 Roottask config ip:001401f6 sp:00000000 Starting kernel /Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco at 003007c0 Welcome to L4/Fiasco.OC! L4/Fiasco.OC microkernel on ia32 Rev: unknown compiled with gcc 4.8.4 for Intel Pentium [] Build: #1 Fri Jul 1 02:13:30 PDT 2016 Performance-critical config option(s) detected: CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off Superpages: yes Kmem:: cpu page at fffd000 (4096Bytes) ACPI: RSDP[0xf0990] r00 OEM:BOCHS. Allocate cpu_mem @ 0xfdbf9400 FPU0: SSE Local APIC[00]: version=11 max_lvt=5 APIC ESR value before/after enabling: 00000000/00000000 Using the Local APIC timer on vector f8 (Periodic Mode) for scheduling ACPI: FACS phys=fffe000 virt=0x203fe000 ACPI: HW sig=0 SERIAL ESC: allocated IRQ 4 for serial uart Absolute KIP Syscalls using: Sysenter Enable MSI support: chained IRQ mgr @ 0xfdbf9150 SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. CPU[0]: GenuineIntel (6:6:3:0)[00000663] Model: QEMU Virtual CPU version 2.0.0 at 3397MHz 32 KB L1 I Cache (8-way associative, 64 bytes per line) 32 KB L1 D Cache (8-way associative, 64 bytes per line) 2048 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 28672 bytes (7 pages) Calibrating timer loop... done. MDB: use page size: 22 MDB: use page size: 12 SIGMA0: Hello! KIP @ 400000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:2000;2fff] [0:3000;9efff] [0:110000;13ffff] [4:140000;17cfff] [0:17d000;3fffff] [0:495000;1786fff] [4:1787000;4131fff] [0:4132000;eb8afff] IOMEM:---------------------- [0:0;fff] [0:9f000;fffff] [0:fffe000;febfffff] [0:fec01000;fedfffff] [0:fee01000;ffffffff] IO PORTS-------------------------- [0:0;fffffff] MOE: Hello world MOE: found 197224 KByte free memory MOE: found RAM from 2000 to eb8b000 MOE: allocated 235 KByte for the page array @0x3000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:103000] BOOTFS: [1787000-1942790] [C:105000] l4re BOOTFS: [1943000-1ca32a6] [C:107000] ned BOOTFS: [1ca4000-1ca451c] [C:109000] l4lx-gfx.cfg BOOTFS: [1ca5000-3027574] [C:10b000] io BOOTFS: [3028000-3304abc] [C:10d000] fb-drv BOOTFS: [3305000-39446b8] [C:10f000] mag BOOTFS: [3945000-3945338] [C:111000] x86-legacy.devs BOOTFS: [3946000-394625f] [C:113000] l4lx-x86.io BOOTFS: [3947000-3e316a5] [C:115000] vmlinuz BOOTFS: [3e32000-4132000] [C:117000] ramdisk-x86.rd MOE: cmdline: /home/zhangxin/Desktop/l4re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg MOE: Starting: rom/ned rom/l4lx-gfx.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx-gfx.cfg' io | Io service io | Find root Pointer io | Find root Pointer: f0990 io | ACPI: RSDP 0x00000000000F0990 000014 (v00 BOCHS ) io | ACPI: RSDT 0x000000000FFFFBC1 000034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001) io | ACPI: FACP 0x000000000FFFF1C0 000074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001) io | ACPI: DSDT 0x000000000FFFE040 001180 (v01 BOCHS BXPCDSDT 00000001 BXPC 00000001) io | ACPI: FACS 0x000000000FFFE000 000040 io | ACPI: SSDT 0x000000000FFFF234 0008DD (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001) io | ACPI: APIC 0x000000000FFFFB11 000078 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001) io | ACPI: HPET 0x000000000FFFFB89 000038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001) io | io | Initializing Namespace objects: io | Table [DSDT: BXPCDSDT] (id 01) - 144 Objects with 18 Devices, 8 Regions, 52 Methods (6/46/5 Serial/Non/Cvt) io | Table [SSDT: BXPCSSDT] (id 02) - 155 Objects with 32 Devices, 1 Regions, 42 Methods (0/42/0 Serial/Non/Cvt) io | ACPI: 2 ACPI AML tables successfully acquired and loaded io | io | Completing Region/Field/Buffer/Package initialization: io | Initialized 9/9 Regions 2/2 Fields 21/21 Buffers 5/5 Packages (308 nodes) io | evxfevnt-0182 Enable : Transition to ACPI mode successful io | Initializing General Purpose Events (GPEs): io | Initialized GPE 00 to 0F [_GPE] 2 regs on interrupt 0x9 (SCI) io | Initializing Device/Processor/Thermal objects and executing _INI/_STA methods: io | Executed 0 _INI methods requiring 1 _STA executions (examined 53 objects) io | ACPICA-Version:20160318, System in ACPI MODE, 32bit timer io | ACPI Error: Could not enable PowerButton event (20160318/evxfevnt-304) io | ACPI Warning: Could not enable fixed event - PowerButton (2) (20160318/evxface-821) io | ACPI: could not register power-button handler: AE_NO_HARDWARE_RESPONSE io | ACPI: Enabled 16 GPEs in block 00 to 0F io | IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=40201) io | IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=40201) io | Ready. Waiting for request. mag | Hello from MAG fb-drv | Trying execution of ``set VBE mode'' using x86emu fb-drv | Found VESA BIOS version 3.0 fb-drv | OEM SeaBIOS VBE(C) 2011 fb-drv | VBE mode 0x117 successfully set. fb-drv | Framebuffer memory: phys: fc000000 - fc400000 fb-drv | virt: 200000 - 600000 fb-drv | Starting server loop mag | mapped frame buffer at 0x400000 mag | View::Info: mag | flags: 0 mag | size: 1024x768 mag | pos: 0x0 mag | bytes_per_line: 2048 mag | buffer_offset: 0 mag | RGBA(2):5(11):6(5):5(0):0(0) mag | memory 0x400000 - 0x800000 mag | Plugin: Mag_client service started mag | Plugin: Frame-buffer service started mag | L4INPUT native mode activated mag | L4INPUT: !!! W A R N I N G !!! mag | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. mag | L4INPUT: !!! W A R N I N G !!! mag | serio: i8042 AUX port at 0x60,0x64 irq 12 mag | serio: i8042 KBD port at 0x60,0x64 irq 1 mag | input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1 mag | input: AT Translated Set 2 keyboard on isa0060/serio0 mag | connect "ImExPS/2 Generic Explorer Mouse", isa0060/serio1/input0 mag | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 PH 0 offs=00001000 flags=r-x PH-type=0x1 virt=00100000 evirt=00473000 phys=00100000 ephys=00473000 f_sz=00373000 memsz=00373000 PH 1 offs=00374000 flags=rw- PH-type=0x1 virt=00473000 evirt=00573000 phys=00473000 ephys=00573000 f_sz=00052afe memsz=00100000 PH 2 offs=002b708c flags=--- PH-type=0x4 virt=003b608c evirt=003b60b0 phys=003b608c ephys=003b60b0 f_sz=00000024 memsz=00000024 Starting binary at 0x100000, argc=6 argv=0xafff4f90 *argv=0xb1007ff4 argv0=rom/vmlinuz External resolver is at 0xa80008c0 ======> L4Linux starting... <======== Linux version 4.6.0-l4 (zhangxin@ubuntu) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #1 Fri Jul 1 02:34:46 PDT 2016 Binary name: rom/vmlinuz Linux kernel command line (5 args): mem=64M console=tty0 l4x_rd=rom/ramdisk-x86.rd root=1:0 ramdisk_size=4000 CPU mapping (l:p)[1]: 0:0 Image: 00100000 - 00573000 [4556 KiB]. Areas: Text: 00100000 - 003b5a5b [2774kB] RO-Data: 003b7000 - 00473000 [752kB] Data: 00473000 - 0049a500 [157kB] Init: 0049c000 - 004c6000 [168kB] BSS: 004c6000 - 0055d000 [604kB] gs=43 fs=43 Device scan: Device: L4ICU Device: PCI0 Device: pci_l4x[1] IRQ: 0000000b - 0000000b MEM: febc0000 - febdffff PORT: 0000c000 - 0000c03f DMAD: 00000000 - 00000000 Device: pci_l4x[2] PORT: 0000c040 - 0000c04f DMAD: 00000000 - 00000000 PORT: 000001f0 - 000001f7 PORT: 000003f6 - 000003f6 IRQ: 0000000e - 0000000e PORT: 00000170 - 00000177 PORT: 00000376 - 00000376 IRQ: 0000000f - 0000000f Device scan done. l4x_fiasco_gdt_entry_offset = 9 l4lx_thread_create: Created thread 41e (cpu0) (u:b3000e00, v:b3000c00, sp:00475fac) main thread will be 41e section-with-init(-data): Virt: 0x473000 to 0x572fff [1024 KiB] section-with-init(-data): Phys: 0x00298000 to 0x00397fff, [1024 KiB] section-with-init-text: Virt: 0x473000 to 0x572fff [1024 KiB] *error: failed to get physical address for 473000.* Main thread running, waiting... L4x: Memory size: 64MB L4x: Setting superpages for main memory L4x: Adjusted memory start: 00000000 Main memory: Virt: 0x800000 to 0x47fffff [65536 KiB] Main memory: Phys: 0x04400000 to 0x083fffff, [65536 KiB] l4x: vmalloc area: 04800000 - 0c800000 Filling lower ptabs... Done (254 entries). text: Virt: 0x100000 to 0x472fff [3532 KiB] text: Phys: 0x00495000 to 0x00807fff, [3532 KiB] Loading: rom/ramdisk-x86.rd INITRD: Size of RAMdisk is 3072KiB RAMdisk from 0ca1b000 to 0cd1b000 [3072KiB] l4lx_thread_create: Created thread 425 (timer0) (u:b3000a00, v:00000000, sp:004f5fa8) WARNING: Unknown rdmsr: 00000186 at 0x4a4737 WARNING: Unknown rdmsr: 00000187 at 0x4a4737 WARNING: Unknown rdmsr: 000000c2 at 0x4a47f0 WARNING: Unknown wrmsr: 000000c2 at 0x4a480e WARNING: Unknown rdmsr: 000000c2 at 0x4a4814 the qemu out stop here: I find the error,But I have no idea about, can anybody help me ? Thanks in advanced! Best Reagrds！ ryan.zhang

2 1

where can I download the previous version of L4linux?
by li94575 07 Jul '16

07 Jul '16

Hi, I want to use L4linux3.5 and L4linux3.10, but L4linux SVN repository and l4re-snapshot both are the latest release. Can anyone tell me where to download it? Thank you!

2 3

l4re-snapshot-2016060908 lunch "L4Linux-mag-x86" problem
by 张鑫 04 Jul '16

04 Jul '16

Hi, Everyone, I'm a newer in L4Linux,I get the lastest snapshort and follow the README which builds it successfully, When I execute make qemu in /my_dir/obj/l4/x86 ,it comes up Entry selection , I tested all but "L4Linux-mag-x86" is'nt work successfully. I prebuild the snapshot in Ubuntu 14.04.4 LTS, the following is the ubuntu output message: L4 Bootstrapper Build: #1 Fri Jul 1 02:18:27 PDT 2016, x86-32, 4.8.4 RAM: 0000000000000000 - 000000000009fbff: 639kB RAM: 0000000000100000 - 000000000fffdfff: 261112kB Total RAM: 255MB Scanning /home/zhangxin/Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco -serial_esc Scanning /home/zhangxin/Desktop/l4re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/sigma0 Scanning /home/zhangxin/Desktop/l4re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg need 1424 bytes to copy MBI reserved 1424 bytes at 0x2000 Moving up to 13 modules behind 1100000 moving module 12 { 3013400-33133ff } -> { 3e32000-4131fff } [3145728] moving module 11 { 2b28400-3012aa4 } -> { 3947000-3e316a4 } [5154469] moving module 10 { 2b27400-2b2765e } -> { 3946000-394625e } [607] moving module 09 { 2b26400-2b26737 } -> { 3945000-3945337 } [824] moving module 08 { 24e6400-2b25ab7 } -> { 3305000-39446b7 } [6551224] moving module 07 { 2209400-24e5ebb } -> { 3028000-3304abb } [3001020] moving module 06 { e86400-2208973 } -> { 1ca5000-3027573 } [20456820] moving module 05 { e85400-e8591b } -> { 1ca4000-1ca451b } [1308] moving module 04 { b24400-e846a5 } -> { 1943000-1ca32a5 } [3539622] moving module 03 { 968400-b23b8f } -> { 1787000-194278f } [1816464] moving module 02 { 41e400-967f0a } -> { 123d000-1786b0a } [5544715] moving module 01 { 378400-41dcbf } -> { 1197000-123c8bf } [678080] moving module 00 { 2e1400-378257 } -> { 1100000-1196e57 } [618072] Loading /Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco Loading re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/sigma0 Loading /l4re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/moe find kernel info page... found kernel info page at 0x400000 Regions of list 'regions' [ 0, fff] { 1000} Arch BIOS [ 1000, 1fff] { 1000} Kern /Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco [ 2000, 258f] { 590} Root mbi_rt [ 9fc00, 9ffff] { 400} Arch BIOS [ f0000, fffff] { 10000} Arch BIOS [ 100000, 10f193] { f194} Sigma0 re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/sigma0 [ 140000, 17c367] { 3c368} Root /l4re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/moe [ 2d0400, 2df43f] { f040} Boot bootstrap [ 300000, 38ffff] { 90000} Kern /Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco [ 400000, 49bfff] { 9c000} Kern /Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco [ 1787000, 4131fff] { 29ab000} Root Module [ fffe000, fffffff] { 2000} Arch BIOS [ fffc0000, ffffffff] { 40000} Arch BIOS API Version: (87) experimental Sigma0 config ip:001001d4 sp:00000000 Roottask config ip:001401f6 sp:00000000 Starting kernel /Desktop/l4re-snapshot-2016060908/obj/fiasco/ia32/fiasco at 003007c0 Welcome to L4/Fiasco.OC! L4/Fiasco.OC microkernel on ia32 Rev: unknown compiled with gcc 4.8.4 for Intel Pentium [] Build: #1 Fri Jul 1 02:13:30 PDT 2016 Performance-critical config option(s) detected: CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off Superpages: yes Kmem:: cpu page at fffd000 (4096Bytes) ACPI: RSDP[0xf0990] r00 OEM:BOCHS. Allocate cpu_mem @ 0xfdbf9400 FPU0: SSE Local APIC[00]: version=11 max_lvt=5 APIC ESR value before/after enabling: 00000000/00000000 Using the Local APIC timer on vector f8 (Periodic Mode) for scheduling ACPI: FACS phys=fffe000 virt=0x203fe000 ACPI: HW sig=0 SERIAL ESC: allocated IRQ 4 for serial uart Absolute KIP Syscalls using: Sysenter Enable MSI support: chained IRQ mgr @ 0xfdbf9150 SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. CPU[0]: GenuineIntel (6:6:3:0)[00000663] Model: QEMU Virtual CPU version 2.0.0 at 3397MHz 32 KB L1 I Cache (8-way associative, 64 bytes per line) 32 KB L1 D Cache (8-way associative, 64 bytes per line) 2048 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 28672 bytes (7 pages) Calibrating timer loop... done. MDB: use page size: 22 MDB: use page size: 12 SIGMA0: Hello! KIP @ 400000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:2000;2fff] [0:3000;9efff] [0:110000;13ffff] [4:140000;17cfff] [0:17d000;3fffff] [0:495000;1786fff] [4:1787000;4131fff] [0:4132000;eb8afff] IOMEM:---------------------- [0:0;fff] [0:9f000;fffff] [0:fffe000;febfffff] [0:fec01000;fedfffff] [0:fee01000;ffffffff] IO PORTS-------------------------- [0:0;fffffff] MOE: Hello world MOE: found 197224 KByte free memory MOE: found RAM from 2000 to eb8b000 MOE: allocated 235 KByte for the page array @0x3000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:103000] BOOTFS: [1787000-1942790] [C:105000] l4re BOOTFS: [1943000-1ca32a6] [C:107000] ned BOOTFS: [1ca4000-1ca451c] [C:109000] l4lx-gfx.cfg BOOTFS: [1ca5000-3027574] [C:10b000] io BOOTFS: [3028000-3304abc] [C:10d000] fb-drv BOOTFS: [3305000-39446b8] [C:10f000] mag BOOTFS: [3945000-3945338] [C:111000] x86-legacy.devs BOOTFS: [3946000-394625f] [C:113000] l4lx-x86.io BOOTFS: [3947000-3e316a5] [C:115000] vmlinuz BOOTFS: [3e32000-4132000] [C:117000] ramdisk-x86.rd MOE: cmdline: /home/zhangxin/Desktop/l4re-snapshot-2016060908/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg MOE: Starting: rom/ned rom/l4lx-gfx.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx-gfx.cfg' io | Io service io | Find root Pointer io | Find root Pointer: f0990 io | ACPI: RSDP 0x00000000000F0990 000014 (v00 BOCHS ) io | ACPI: RSDT 0x000000000FFFFBC1 000034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001) io | ACPI: FACP 0x000000000FFFF1C0 000074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001) io | ACPI: DSDT 0x000000000FFFE040 001180 (v01 BOCHS BXPCDSDT 00000001 BXPC 00000001) io | ACPI: FACS 0x000000000FFFE000 000040 io | ACPI: SSDT 0x000000000FFFF234 0008DD (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001) io | ACPI: APIC 0x000000000FFFFB11 000078 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001) io | ACPI: HPET 0x000000000FFFFB89 000038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001) io | io | Initializing Namespace objects: io | Table [DSDT: BXPCDSDT] (id 01) - 144 Objects with 18 Devices, 8 Regions, 52 Methods (6/46/5 Serial/Non/Cvt) io | Table [SSDT: BXPCSSDT] (id 02) - 155 Objects with 32 Devices, 1 Regions, 42 Methods (0/42/0 Serial/Non/Cvt) io | ACPI: 2 ACPI AML tables successfully acquired and loaded io | io | Completing Region/Field/Buffer/Package initialization: io | Initialized 9/9 Regions 2/2 Fields 21/21 Buffers 5/5 Packages (308 nodes) io | evxfevnt-0182 Enable : Transition to ACPI mode successful io | Initializing General Purpose Events (GPEs): io | Initialized GPE 00 to 0F [_GPE] 2 regs on interrupt 0x9 (SCI) io | Initializing Device/Processor/Thermal objects and executing _INI/_STA methods: io | Executed 0 _INI methods requiring 1 _STA executions (examined 53 objects) io | ACPICA-Version:20160318, System in ACPI MODE, 32bit timer io | ACPI Error: Could not enable PowerButton event (20160318/evxfevnt-304) io | ACPI Warning: Could not enable fixed event - PowerButton (2) (20160318/evxface-821) io | ACPI: could not register power-button handler: AE_NO_HARDWARE_RESPONSE io | ACPI: Enabled 16 GPEs in block 00 to 0F io | IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=40201) io | IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=40201) io | Ready. Waiting for request. mag | Hello from MAG fb-drv | Trying execution of ``set VBE mode'' using x86emu fb-drv | Found VESA BIOS version 3.0 fb-drv | OEM SeaBIOS VBE(C) 2011 fb-drv | VBE mode 0x117 successfully set. fb-drv | Framebuffer memory: phys: fc000000 - fc400000 fb-drv | virt: 200000 - 600000 fb-drv | Starting server loop mag | mapped frame buffer at 0x400000 mag | View::Info: mag | flags: 0 mag | size: 1024x768 mag | pos: 0x0 mag | bytes_per_line: 2048 mag | buffer_offset: 0 mag | RGBA(2):5(11):6(5):5(0):0(0) mag | memory 0x400000 - 0x800000 mag | Plugin: Mag_client service started mag | Plugin: Frame-buffer service started mag | L4INPUT native mode activated mag | L4INPUT: !!! W A R N I N G !!! mag | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. mag | L4INPUT: !!! W A R N I N G !!! mag | serio: i8042 AUX port at 0x60,0x64 irq 12 mag | serio: i8042 KBD port at 0x60,0x64 irq 1 mag | input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1 mag | input: AT Translated Set 2 keyboard on isa0060/serio0 mag | connect "ImExPS/2 Generic Explorer Mouse", isa0060/serio1/input0 mag | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 PH 0 offs=00001000 flags=r-x PH-type=0x1 virt=00100000 evirt=00473000 phys=00100000 ephys=00473000 f_sz=00373000 memsz=00373000 PH 1 offs=00374000 flags=rw- PH-type=0x1 virt=00473000 evirt=00573000 phys=00473000 ephys=00573000 f_sz=00052afe memsz=00100000 PH 2 offs=002b708c flags=--- PH-type=0x4 virt=003b608c evirt=003b60b0 phys=003b608c ephys=003b60b0 f_sz=00000024 memsz=00000024 Starting binary at 0x100000, argc=6 argv=0xafff4f90 *argv=0xb1007ff4 argv0=rom/vmlinuz External resolver is at 0xa80008c0 ======> L4Linux starting... <======== Linux version 4.6.0-l4 (zhangxin@ubuntu) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #1 Fri Jul 1 02:34:46 PDT 2016 Binary name: rom/vmlinuz Linux kernel command line (5 args): mem=64M console=tty0 l4x_rd=rom/ramdisk-x86.rd root=1:0 ramdisk_size=4000 CPU mapping (l:p)[1]: 0:0 Image: 00100000 - 00573000 [4556 KiB]. Areas: Text: 00100000 - 003b5a5b [2774kB] RO-Data: 003b7000 - 00473000 [752kB] Data: 00473000 - 0049a500 [157kB] Init: 0049c000 - 004c6000 [168kB] BSS: 004c6000 - 0055d000 [604kB] gs=43 fs=43 Device scan: Device: L4ICU Device: PCI0 Device: pci_l4x[1] IRQ: 0000000b - 0000000b MEM: febc0000 - febdffff PORT: 0000c000 - 0000c03f DMAD: 00000000 - 00000000 Device: pci_l4x[2] PORT: 0000c040 - 0000c04f DMAD: 00000000 - 00000000 PORT: 000001f0 - 000001f7 PORT: 000003f6 - 000003f6 IRQ: 0000000e - 0000000e PORT: 00000170 - 00000177 PORT: 00000376 - 00000376 IRQ: 0000000f - 0000000f Device scan done. l4x_fiasco_gdt_entry_offset = 9 l4lx_thread_create: Created thread 41e (cpu0) (u:b3000e00, v:b3000c00, sp:00475fac) main thread will be 41e section-with-init(-data): Virt: 0x473000 to 0x572fff [1024 KiB] section-with-init(-data): Phys: 0x00298000 to 0x00397fff, [1024 KiB] section-with-init-text: Virt: 0x473000 to 0x572fff [1024 KiB] *error: failed to get physical address for 473000.* Main thread running, waiting... L4x: Memory size: 64MB L4x: Setting superpages for main memory L4x: Adjusted memory start: 00000000 Main memory: Virt: 0x800000 to 0x47fffff [65536 KiB] Main memory: Phys: 0x04400000 to 0x083fffff, [65536 KiB] l4x: vmalloc area: 04800000 - 0c800000 Filling lower ptabs... Done (254 entries). text: Virt: 0x100000 to 0x472fff [3532 KiB] text: Phys: 0x00495000 to 0x00807fff, [3532 KiB] Loading: rom/ramdisk-x86.rd INITRD: Size of RAMdisk is 3072KiB RAMdisk from 0ca1b000 to 0cd1b000 [3072KiB] l4lx_thread_create: Created thread 425 (timer0) (u:b3000a00, v:00000000, sp:004f5fa8) WARNING: Unknown rdmsr: 00000186 at 0x4a4737 WARNING: Unknown rdmsr: 00000187 at 0x4a4737 WARNING: Unknown rdmsr: 000000c2 at 0x4a47f0 WARNING: Unknown wrmsr: 000000c2 at 0x4a480e WARNING: Unknown rdmsr: 000000c2 at 0x4a4814 the qemu out stop here: I find the error,But I have no idea about, can anybody help me ? Thanks in advanced! Best Reagrds！ ryan.zhang

1 0

building fiasco on alpine linux
by Michael Schnupp 27 Jun '16

27 Jun '16

Hi, I tried to build fiasco on alpine linux. This will fail with the following line: auto/jdb_ktrace.cc:1:0: error: code model kernel does not support PIC mode Their gcc enables PIC per default for security reasons. Since fiasco seems to need PIC disabled I have to tell the build system either to add -fno-PIC explictly, or to -D__KERNEL__ in any way. (I already tried DEFINES += -D__KERNEL__ or CFLAGS := -fno-PIC in Makeconf without success.) What is the correct way to add such an option to the fiasco build system? Would it hurt to add -D__KERNEL__ per default on future releases? (After all it *is* a kernel.) BTW, the above file looks very much like a jdb file. Is it correct that this file is compiled even when I configured fiasco to not include jdb? BR, Michael

2 6

Cross-compiling L4Re for MIPS32
by Paul Boddie 22 Jun '16

22 Jun '16

Hello, I finally got round to looking at L4/Fiasco.OC again, and having previously looked at the MIPS32 port that was made available on GitHub... https://github.com/MIPS/fiasco-l4re ...I have been attempting to cross-compile Fiasco and L4Re using the l4re.org sources. Getting Fiasco to cross-compile was mostly a matter of repeating the same procedure as last time: cd src/kernel/fiasco make BUILDDIR=mybuild cd mybuild/ make config make However, I needed to edit src/kernel/fiasco/src/Makeconf.mips32 to change the compiler settings. I'm using the toolchains in Debian unstable: CROSS_COMPILE ?= mipsel-linux-gnu- Previously, I used a Makeconf.local file to set the following: SYSTEM_TARGET=mipsel-linux-gnu- SHARED_FLAGS=-mips32r2 -EL -msoft-float -mno-abicalls -fno-pic Maybe the previous work used some different mechanisms to those used by the more general source distribution, but this trick didn't seem to influence the build successfully this time around. However, the build did complete successfully with the toolchain set appropriately. Meanwhile, I had more problems with the L4Re part. I had expected to be able to do the following: cd src/l4 make B=mybuild make O=mybuild config make O=mybuild E=mips-fbspectrum (The target was something that I had managed to build previously after some messing around with packages and configuration files. I'd managed to build the fbspectrum example for Fiasco.OC-UX, as the list archives will attest.) However, I also had to change the compiler settings (as done above) in src/l4/mk/arch/Makeconf.mips, instead of using src/l4/Makeconf.local (as done previously). Again, maybe the way of doing things was different in the previous incarnation of this port. I also needed to edit src/l4/tool/gendep/syscall.c to add a definition before unistd.h gets included: #define __ARCH_WANT_SYSCALL_NO_AT I can't remember if I or anyone else has mentioned this before now, but without it, things like __NR_open are not defined. Unfortunately, I haven't yet reached a satisfactory conclusion in this latter exercise. Looking back at my previous messages, it seems that a bit more work might be needed to configure and build a suitable target, and so I was wondering if anyone had done this (and written it up) for any of the MIPS boards, perhaps the CI20. Indeed, I wonder if things like the framebuffer are even supported for the CI20 or other MIPS boards. Paul

2 10

L4Linux Compilation trouble with missing packages in L4
by Martin Gruber 13 Jun '16

13 Jun '16

Dear L4 community, i started diving into L4 stuff recently and it looks really interesting. Currently I am trying to get L4Linux working on top of Fiasco.OC. After configuring the L4 Kernel, I am getting following error message at build: ---------------------------------------------------------------------------- make O=../build/ make[1]: Entering directory '/home/gruber/l4re/l4linux/build' Package shmc was not found in the pkg-config search path. Perhaps you should add the directory containing `shmc.pc' to the PKG_CONFIG_PATH environment variable No package 'shmc' found Package rtc was not found in the pkg-config search path. Perhaps you should add the directory containing `rtc.pc' to the PKG_CONFIG_PATH environment variable No package 'rtc' found Getting required compilation flags failed. L4OBJ: /home/gruber/l4re/src/l4/l4build L4_REQUIRED_MODS: libc_be_minimal_log_io libc_minimal libc_minimal_l4re libsupc++_minimal log l4re_c-util libio libvcpu shmc rtc arch/l4/Makefile:391: *** Aborting.. Stop. make[1]: Leaving directory '/home/gruber/l4re/l4linux/build' Makefile:146: recipe for target 'sub-make' failed make: *** [sub-make] Error 2 ---------------------------------------------------------------------------- After checking the mailing list archive i found this question: http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007635.html http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007635.html I checked the l4/builddir/pc for missing libs and did not find them. Compilation of L4 worked fine, L4 also works with the small HelloWorld sample in QEMU. I checked the L4 config but was not able to find appropriate options. Does anyone have an tip for me what I am doing wrong? Thank you very much for your help! Kind Regards, Martin

2 1

Re: l4-hackers Digest, Vol 157, Issue 10
by Иван Филиппов 28 May '16

28 May '16

adam - maasdam ;-) 2016-05-28 13:00 GMT+03:00, l4-hackers-request(a)os.inf.tu-dresden.de <l4-hackers-request(a)os.inf.tu-dresden.de>: > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. L4Re Release (Adam Lackorzynski) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 27 May 2016 13:13:04 +0200 > From: Adam Lackorzynski <adam(a)l4re.org> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: L4Re Release > Message-ID: <20160527111304.GB12441(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > Hi, > > I'm happy to announce a new L4Re release. > > https://l4re.org/ > > This release adds support for the Imagination Technologies' > MIPS architecture, including support for MIPS' > virtualization architecture VZ to run virtual machines such > as Linux. L4Re is currently available for MIPS32, > MIPS64 is about to follow. The MIPS port is supported by > Imagination Technologies. > > > Further noteworthy changes of this release include: > - L4Linux has been updated to L4Linux-4.6 > - Conversion of debugging interface to capability-based > interface. Programs need to have the 'jdb' capability to > use JDB functionality. > - The virtual machines monitor, now called uvmm, supports > the MIPS and ARM architectures. > - A virtio-based peer-to-peer network component is available > in virtio-net. > - Documentation improvements > - Library updates > - Added ARM platforms: > - NXP Layerscape LS1021A > - i.MX28 > - MIPS platforms: > - Malta > - Sead3 > - Ci20 > - Baikal-T > - Bug fixes and small feature enhancements in the kernel and user-level > components: > - Added atomic IRQ re-attach call > - The vCPU data structures have been revised > > > Adam > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > > ------------------------------ > > End of l4-hackers Digest, Vol 157, Issue 10 > ******************************************* > -- Иван Филиппов

1 0

L4Re Release
by Adam Lackorzynski 27 May '16

27 May '16

Hi, I'm happy to announce a new L4Re release. https://l4re.org/ This release adds support for the Imagination Technologies' MIPS architecture, including support for MIPS' virtualization architecture VZ to run virtual machines such as Linux. L4Re is currently available for MIPS32, MIPS64 is about to follow. The MIPS port is supported by Imagination Technologies. Further noteworthy changes of this release include: - L4Linux has been updated to L4Linux-4.6 - Conversion of debugging interface to capability-based interface. Programs need to have the 'jdb' capability to use JDB functionality. - The virtual machines monitor, now called uvmm, supports the MIPS and ARM architectures. - A virtio-based peer-to-peer network component is available in virtio-net. - Documentation improvements - Library updates - Added ARM platforms: - NXP Layerscape LS1021A - i.MX28 - MIPS platforms: - Malta - Sead3 - Ci20 - Baikal-T - Bug fixes and small feature enhancements in the kernel and user-level components: - Added atomic IRQ re-attach call - The vCPU data structures have been revised Adam

1 0

Flexpage: shared Mem
by ba_f 23 May '16

23 May '16

Hello, writing a L4Linux Driver I'm expiring the C-Interface and low level(?) flexpages. So far, I can push a Dataspace Capability via flexpage, and the receiving server is able to read its content. But, whatever the server writes in that mem-region doesn't appear on the clients side. /* client.c */ l4_fpage_t fpage = l4_obj_fpage( dataspace, 0, L4_CAP_FPAGE_RW ); l4_utcb_mr()->mr[0] = size; l4_utcb_br()->br[0] = fpage.raw; /* server.c */ l4_utcb_br()->br[0] = dataspace | L4_RCV_ITEM_SINGLE_CAP; l4_ipc_wait(l4_utcb(), 0, L4_IPC_NEVER); // allocate, and attach Dataspace ... // read & write Dataspace ... l4_utcb_mr()->mr[0] = returnValue; l4_ipc_reply_and_wait(l4_utcb(), l4_msgtag(0, 1, 0, 0), 0, L4_IPC_NEVER); As I am creating the fpage with L4_CAP_FPAGE_RW my guess was I can write to that mem-region and the client can read my changes. Anyway, maybe I need some more understandings about capabilities & flexpages. (Are there any precise slides or papers about this topic?) So, the client creates a dataspace capability and allocates some memory. But, what happens when the flexpage is pushed to the server? The capability is copied and both pointing to the same allocated memory, or is the Cap and(!) the memory it is pointing to copied to server? Thanks, ba_f

2 5

Question about Fiasco.OC support for SPARC
by deng.chao1＠zte.com.cn 12 May '16

12 May '16

Hi everyone： I want to run Fiasco.OS on SPARC-leon3 platform. It seems that Fiasco.OS already has an unimplemented support for SPARC-leon3 according to the latest snapshot fiasco-2015123115 of Fiasco. Does Fiasco.OS support SPARC now? If it does, how can I get the source? If it doesn't, what are the unimplemented parts according to snapshot fiasco-2015123115? And another question, is there any good machine emulator for SPARC-leon3？ I have tried latest version of QEMU, but It doesn't work well on SPARC-leon3. Thanks Dengchao

2 3

Task Priority Setting
by Nourhan Mohamed 02 May '16

02 May '16

Dear L4Hackers, I have been trying to run 2 simple L4 tasks and give one of them highest scheduling priority and the other one the least. I have tried using the priority attribute in the start script as well as: scheduler = L4.Env.user_factory:create(L4.Proto.Scheduler, 0x18, 0x8) with different ranges for each of them but I don't notice any change in their runtimes. Am I missing something here? Thanks in advance, Nourhan

3 4

Question about ARM LPAE
by li94575 07 Apr '16

07 Apr '16

hello, I want to use the ARM LPAE in Fiasco.OC, may I need to modify the start code of l4re? The board supports two DDR3 channels, and each channel supports two chip-selects. I need to use the memory device on CS0 populated for each channel. One memory rang is from 0x00000000 to 0x3fffffff, the anther is from 0x100000000 to 0x13fffffff. How can sigma0 see both of them? thank you!

2 8

Bootstrap in real mode on x86_64: Possible?
by Maxim Baryshnikov 05 Apr '16

05 Apr '16

Hello everyone, I am trying to find some ways to port/launch Fiasco.OS into "The Jailhouse hypervisor <https://github.com/siemens/jailhouse.git>" environment using x86_64 architecture. This hypervisor does not provide any bootloader at all. It simply loads raw binary on the specified address and launches it in real mode from this address. In 'l4/pkg/bootstrap/server/src/README' I found two options described. I think it might be suitable for me. 3) bootstrap can boot from real-mode, esp. with pxelinux, i.e. it can be booted via PXE. For that it also needs include all images. This should also work with syslinux (e.g. from CDs/DVDs). (Note, grub can also read is9660 filesystems.) 4) bootstrap starts from protected mode but isn't started by a multiboot compliant loader. Also needs to include all modules. So, I started my tries from the 3th option. Following the bootstrap code, I find out that there is some piece of code for real mode bootstrapping and the defining of "REALMODE_LOADING" directive switches it on. I have tried to compile it with REALMODE_LOADING = 1 (and also with IMAGE_MODE = 1, and RML = 1), which I added in 'bootstrap/server/src/Makeconf.local' folder. Also, I commented the row with error command in Makefile.rules: |ifneq ($(REALMODE_LOADING)$(RML),00) REALMODE_LOADING := 1 #$(error Info: Default reloc needs to be 0x00100000) # And if you have done so you probably need to relink sigma0 and/or moe endif||| I admit that I did not actually understand the purpose of this block here.. I would really appreciate if someone explains it to me. Unfortunately, when I continue to make it without command mentioned above I've faced with the following compilation error: | [bootstrap] ... Compiling platform/x86_pc.o|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc: In member function ‘const char* {anonymous}::Platform_x86_1::cmdline() const’:|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc:73:26: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]|| || return (char const *)p;|| || ^|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc: In member function ‘virtual Boot_modules::Module {anonymous}::Platform_x86_multiboot::module(unsigned int, bool) const’:|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc:176:64: error: ‘mbi’ was not declared in this scope|| || l4util_mb_mod_t *mb_mod = (l4util_mb_mod_t*)(unsigned long)mbi->mods_addr;|| ||^|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc: In member function ‘virtual unsigned int {anonymous}::Platform_x86_multiboot::num_modules() const’:|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc:184:41: error: ‘mbi’ was not declared in this scope|| || unsigned num_modules() const { return mbi->mods_count; }|| || ^|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc: In member function ‘virtual void {anonymous}::Platform_x86_multiboot::reserve()’:|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc:190:43: error: ‘mbi’ was not declared in this scope|| || regions->add(Region::n((unsigned long)mbi,|| || ^|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc: In member function ‘virtual void {anonymous}::Platform_x86_multiboot::move_module(unsigned int, void*, bool)’:|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc:232:61: error: ‘mbi’ was not declared in this scope|| || l4util_mb_mod_t *mod = (l4util_mb_mod_t*)(unsigned long)mbi->mods_addr + index;|| ||^|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc: In member function ‘virtual l4util_mb_info_t* {anonymous}::Platform_x86_multiboot::construct_mbi(long unsigned int)’:|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc:249:9: error: ‘mbi’ was not declared in this scope|| || if (mbi->flags & L4UTIL_MB_CMDLINE)|| || ^|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc:253:9: error: ‘mbi’ was not declared in this scope|| || if (mbi->flags & L4UTIL_MB_VIDEO_INFO)|| || ^|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc:263:45: error: ‘mbi’ was not declared in this scope|| || total_size += sizeof(l4util_mb_mod_t) * mbi->mods_count;|| || ^|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc:345:3: warning: control reaches end of non-void function [-Wreturn-type]|| || }|| || ^|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc: In member function ‘virtual unsigned int {anonymous}::Platform_x86_multiboot::num_modules() const’:|| ||/home/coon848/projekt-git-clones/l4re-snap/src/l4/pkg/bootstrap/server/src/platform/x86_pc.cc:184:58: warning: control reaches end of non-void function [-Wreturn-type]|| || unsigned num_modules() const { return mbi->mods_count; }|| ||^|| ||/||home/coon848/projekt-git-clones/l4re-snap/src/l4/mk/binary.inc:825: recipe for target 'platform/x86_pc.o' failed| It says that problem is in 'platform/x86_pc.cc'. So, my question is, does the real mode option switch on like that or I did something wrong? How should it be done? And if it is possible to bootstrap without multiboot complaint loader in protected mode, how should it be compiled? Thank you in advance. Sincerely, Maxim Baryshnikov.

2 1

Microkernel Meetup
by Bjoern Doebel 03 Apr '16

03 Apr '16

Hi all, it is time for another meeting of current and former microkernel enthusiasts in Dresden. I prepared a Dudle to find a suitable time: http://dudle.inf.tu-dresden.de/mks-0316/ and will let you know about a location once we settled on a date. Looking forward to your replies! Bjoern

1 2

Can the latest L4Linux support for the ARM big.LITTLE architecture ?
by li94575 21 Mar '16

21 Mar '16

hi all, As we know, Linux has begun to support ARM big.LITTLE architecture from the 3.10 edition. Have this feature also been achieved in L4linux ? thank you!

2 1

Booting L4Linux on Raspberry Pi 2
by Antoine DEBUT 21 Mar '16

21 Mar '16

Hello l4-hackers, Since I was able to correctly set up my l4re for the Raspberry Pi 2 thanks to Adam, I did a bunch of tests on the board with custom programs and following the examples on the l4/pkg/examples directory. Therefore, I am now struggling with the ultimate test: booting and using L4Linux. I am trying to boot a vanilla L4Linux, using the entry 'L4Linux-basic' given in the default modules.list. Upon booting, L4Linux delivers this error : [...] l4linux | List of all partitions: l4linux | 0100 4000 ram0 (driver?) l4linux | 0101 4000 ram1 (driver?) l4linux | 0102 4000 ram2 (driver?) l4linux | 0103 4000 ram3 (driver?) l4linux | 0104 4000 ram4 (driver?) l4linux | 0105 4000 ram5 (driver?) l4linux | 0106 4000 ram6 (driver?) l4linux | 0107 4000 ram7 (driver?) l4linux | 0108 4000 ram8 (driver?) l4linux | 0109 4000 ram9 (driver?) l4linux | 010a 4000 ram10 (driver?) l4linux | 010b 4000 ram11 (driver?) l4linux | 010c 4000 ram12 (driver?) l4linux | 010d 4000 ram13 (driver?) l4linux | 010e 4000 ram14 (driver?) l4linux | 010f 4000 ram15 (driver?) l4linux | No filesystem could mount root, tried: ext3 ext2 ext4 cramfs l4linux | Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) l4linux | CPU: 0 PID: 1 Comm: swapper Not tainted 4.3.0-l4 #2 l4linux | Hardware name: L4 l4linux | [<0200cb88>] (unwind_backtrace) from [<0200583c>] (show_stack+0x10/0x14) l4linux | [<0200583c>] (show_stack) from [<020627a4>] (panic+0x7c/0x1cc) l4linux | [<020627a4>] (panic) from [<02354df0>] (mount_block_root+0x25c/0x29c) l4linux | [<02354df0>] (mount_block_root) from [<023550f4>] (prepare_namespace+0x160/0x1b4) l4linux | [<023550f4>] (prepare_namespace) from [<02354a40>] (kernel_init_freeable+0x178/0x1c0) l4linux | [<02354a40>] (kernel_init_freeable) from [<0227409c>] (kernel_init+0x8/0xec) l4linux | [<0227409c>] (kernel_init) from [<02007e34>] (ret_from_fork+0x14/0x20) l4linux | [<02007e34>] (ret_from_fork) from [<00000000>] ( (null)) l4linux | ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) l4linux | ------------[ cut here ]------------ l4linux | WARNING: CPU: 0 PID: 1 at /home/adebut/Documents/L4Hyperviseur-LBNV/l4re-snapshot-2015123115/src/l4linux/arch/l4/kernel/main.c:2148 l4x_blink+0x10/0x50() l4linux | Modules linked in: l4linux | CPU: 0 PID: 1 Comm: swapper Not tainted 4.3.0-l4 #2 l4linux | Hardware name: L4 l4linux | [<0200cb88>] (unwind_backtrace) from [<0200583c>] (show_stack+0x10/0x14) l4linux | [<0200583c>] (show_stack) from [<0201dee4>] (warn_slowpath_common+0x78/0xb0) l4linux | [<0201dee4>] (warn_slowpath_common) from [<0201dfb8>] (warn_slowpath_null+0x1c/0x24) l4linux | [<0201dfb8>] (warn_slowpath_null) from [<02001af0>] (l4x_blink+0x10/0x50) l4linux | [<02001af0>] (l4x_blink) from [<0206289c>] (panic+0x174/0x1cc) l4linux | [<0206289c>] (panic) from [<02354df0>] (mount_block_root+0x25c/0x29c) l4linux | [<02354df0>] (mount_block_root) from [<023550f4>] (prepare_namespace+0x160/0x1b4) l4linux | [<023550f4>] (prepare_namespace) from [<02354a40>] (kernel_init_freeable+0x178/0x1c0) l4linux | [<02354a40>] (kernel_init_freeable) from [<0227409c>] (kernel_init+0x8/0xec) l4linux | [<0227409c>] (kernel_init) from [<02007e34>] (ret_from_fork+0x14/0x20) l4linux | [<02007e34>] (ret_from_fork) from [<00000000>] ( (null)) l4linux | ---[ end trace 5ed140c2c802ee32 ]--- l4linux | panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye I cannot find any related mail on this mailing list, and therefore must ask you for some help. Could this be a partition misconfiguration ? Or is it related to the '(driver?)' warning on the partition list ? I have attached my globalconfig.out for Fiasco and the l4lx.cfg file that I am using, built l4linux for Arm architecture and ARMv7, and is using the l4re-snapshot-2015123115 with its ramdisk associated and U-boot. Thanks in advance for your help, -- Antoine Debut EPITA 2016 - GISTRE

2 5

Problems running example isr
by Nourhan Mohamed 21 Mar '16

21 Mar '16

Dear L4Hackers, I have a problem running the example "isr" in the pkg/examples/sys/isr folder in l4 source. It prints "isr | Press keys now, Shift-Q to exit" then It fails to detect any interrupts and just keeps waiting. My configuration is as follows, emulated using Qemu on vexpress-a15 machine: modules.list: entry isr kernel fiasco -jdb_cmd=JS -serial_esc roottask moe rom/ex_isr.cfg module ex_isr.cfg module isr module ned module l4re module keyboard.io module arm-ve.devs module io module cons arm-ve.devs: -- vim:set ft=lua: local Res = Io.Res local Hw = Io.Hw Io.hw_add_devices(function() KBD = Hw.Device(function() Property.hid = "AMBA KMI Kbd"; compatible = {"arm,pl050","arm,primecell"}; Resource.irq = Res.irq(44); Resource.regs = Res.mmio(0x1c060000, 0x1c060010); end); end) keyboard.io: local hw = Io.system_bus(); Io.add_vbus("keyboard", Io.Vi.System_bus { amba = wrap(hw:match("arm,pl050")); }) ex_isr.cfg: local L4 = require("L4"); local loader = L4.default_loader; vbus_key = loader:new_channel(); local cons = loader:new_channel(); loader:start( { caps = { cons = cons:svr() }, log = L4.Env.log, }, "rom/cons -k -a" ); L4.default_loader.log_fab = cons; loader:start( { caps = { sigma0 = L4.cast(L4.Proto.Factory,L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; keyboard = vbus_key:svr(); }, l4re_dbg = L4.Dbg.Boot, log = {"IO", "magenta"}, }, "rom/io -vvv rom/arm-ve.devs rom/keyboard.io"); loader:start({ caps = { icu = L4.Env.icu; vbus = vbus_key }, log = {"isr", "cyan", "key=1"}, }, "rom/isr"); where "rom/isr" refers to the example file "isr/main.c" provided. Thank you so much Nourhan

2 3

Fwd: 'Illegal Instruction' on L4Linux
by Alexander Tarasikov 18 Mar '16

18 Mar '16

Forwarding here just in case someone stumbles on this thread. Forgot to reply-all :( ---------- Forwarded message ---------- From: Alexander Tarasikov <alexander.tarasikov(a)gmail.com> Date: Mon, Feb 1, 2016 at 10:28 PM Subject: Re: 'Illegal Instruction' on L4Linux To: ba_f <ba_f(a)rbg.informatik.tu-darmstadt.de> On Mon, Feb 1, 2016 at 8:53 PM, ba_f <ba_f(a)rbg.informatik.tu-darmstadt.de> wrote: > Hello, > > > i have an issue with apps running on L4Linux. > > /usr/bin # ./helloWorld > Illegal instruction > > Actually, on the current l4re-snapshot-2015123115 my apps run without > problem. > But, on l4re-snapshot-2014022818 or l4re-snapshot-2014092821 the same app > don't works. > All apps say 'Illegal instruction'. > > I've built for Zynq. > > > Any idea what's wrong? You have not provided enough information. For example, how you compile Fiasco, L4Re and L4Linux. My experience with L4Re tells me you probably forgot to enable VFP/NEON in configuration options - check the menuconfig for Fiasco, L4Re and L4Linux. Most likely what happened is that the newer toolchain is by default using the "hardfloat" ABI and the compiler generates VFP/NEON instructions. If that fails, I suggest that you try debugging it yourself Therefore, there are several places you should look at: 1) First, you could try running the app under gdb. It will then print the stack trace and point to the offending instruction. 2) You could also install a SIGILL handler in your app and see what's the actual instruction causing the fault. I have an example code here - https://gist.github.com/astarasikov/9369538#file-arm-sigill-example-L71. It's actually a complicated example that patches the code at runtime. What you need to look at is at the following lines in "my_sh": # ucontext_t *uc = (ucontext_t*)data; # struct sigcontext *ctx = &(((ucontext_t*)uc)->uc_mcontext); # ctx->arm_pc; //this is the address of the instruction. You can printf it (as an unsigned integer) and decode the instruction. 3) If that fails, you could patch the invalid opcode handler in kernel to print the instruction. You should grep "arch/arm" and "arch/l4" for "SIGILL". Then, you can add the code to the trap handler. Alternatively, if you build kernel with CONFIG_DEBUG and CONFIG_DEBUG_USER, you will be able to see the stack trace and the hex dump of the instruction in the "dmesg" (or on the serial port console). > > (My project is stable on the old snapshots, that's why i try to avoid > migrating to current snapshot.) > > > > thanks, > ba_f > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers -- Regards, Alexander -- Regards, Alexander

2 3

L4linux IPC communication with L4re application
by Ahmed Makkawi 15 Mar '16

15 Mar '16

Hi all, I think the solution to the communication of an application on l4linux with an application on l4re would be to implement an ipc stream in the character device module in the l4linux kernel to communicate with the IPC stream on l4re application. the Problem now is l4linux modules are in C and the l4re application is in C++, is this a good idea to start searching in it or its a dead end and maybe someone would have a better idea to work on ? Ahmed Makkawi

4 3

FYI: microkernel.info community site
by Jakub Jermář 14 Mar '16

14 Mar '16

Hello, just FYI, I have set up a simple web page[1] to promote the wider microkernel community and its goals. So far, the page comes with a brief description of the microkernel concept and an incomplete list of microkernel projects with links to each project's web. The description is made out of the first two sentences I found in the "What is XYZ" section or elsewhere on the web of the respective project. I also took the freedom to use the respective project's logo (or what I believed was the project's logo) for promoting it. I hope you will find this small web a good idea. It was inspired by a similar (though a little bit more informative) site set up by the unikernel community [2]. The sources of the [1] web are hosted on Github [3], so feel free to submit issues or PR to make the site better. Please send me a PM if there are any issues pertaining your project's cartouche that cannot be dealt with using Github. Thanks, Jakub [1] http://microkernel.info [2] http://unikernel.org/projects/ [3] https://github.com/jermar/microkernel.info

5 5

Running the Bro IDS on an ARMv7 board.
by Mahdi Aichouch 03 Mar '16

03 Mar '16

Hello, I tried to run the Bro IDS on top of L4Linux and L4 Fiasco, on a Freescale i.MX6 ARM cortex A9. Starting the Bro program produces an unrecoverable error and make the L4 Fiasco enter an endless loop as shown below : Does anyone was able to run the Bro IDS on top of L4Linux on a ARMv7 board. Does someone has idea of how to track down the problem. Thank you very much in advance. Best regards, Mahdi /home # ./bro warning in /home/scripts/base/init-bare.bro, line 1: problem initializing NB-DNS: connect(0.0.0.0): Invalid argument KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr()) KERNEL: Warning: No page-fault handler for 0xffffffdc, error 0x9400084f, pc 0200ac80 /home/aichouch/dev/secure-hyp/l4re-snapshot-2014092821/src/kernel/fiasco/src/kern/arm/thread-arm.cpp:56: ASSERTION FAILED (r->check_valid_user_psr())

3 5

Re: Question about "TheGuide to access HW on L4Linux"
by Taeung Song 01 Mar '16

01 Mar '16

Hi, Manolis I renamed the file but I didn't know that a download link of it was broken.. :) So, Share "L4/Fiasco/L4Linux : Porting and Device driver guide on ARM (imx6q cortex-a9)" ,again. :-) http://developerpostit.blogspot.kr/2014/08/device-driver-guide-on-l4linux.h… The guide PDF can be downloaded on this page. Thanks, Taeung On 03/01/2016 11:55 PM, Manolis Ragkousis wrote: > Hello there, > > I found an old mail from 2014 in the l4-hackers mailing list which you > gave a link to a file named "The_Guide_to_access_HW_on_L4Linux_v1.0.pdf" > but unfortunately it is not available anymore. > > Is it still possible to get a copy of that file? L4/Fiasco is part of my > bachelor thesis and that pdf file will be really helpfull. > > Thank you for your time, > Manolis >

2 2

L4Linux with IPC
by Ahmed Makkawi 25 Feb '16

25 Feb '16

Hi All, Im trying to make a simple communication between an application running on L4linux and application running on L4re, so far I managed to make a server client application running on L4re to communicate using IPC, but I dont know how to make the L4Linux take the msg from the IPC channel and pass it to the character device I have running on L4Linux and vice versa. BR, Ahmed Makkawi

2 2

Compiling GPIO drivers for L4Linux
by Nourhan Mohamed 23 Feb '16

23 Feb '16

Dear all, Unlike the normal Linux (version 4.3.0) kernel configuration, when compiling the L4Linux (same version) kernel I couldn't find an option to enable GPIO or choose a driver for the architecture I am building upon (Since I am compiling for ARM, Versatile Express Cortex-A15 board over qemu). Is there an option to enable gpio for l4linux? I even tried modifying something in the gpio driver src in l4linux and when I re-compiled, it never detected any changes. BR, Nourhan

2 1

GPIO access on L4Linux
by Nourhan Mohamed 08 Feb '16

08 Feb '16

Hi all, Does anyone has a rough idea of the steps that should be carried to make L4Linux see GPIO pins? I mean when I navigate to /sys/class I have no gpio folder. So since I am new to this can anyone tell me what steps should be carried out? Thanks in advance, Nourhan

1 0

Running L4linux as a server
by Ahmed Makkawi 05 Feb '16

05 Feb '16

Hi all, in the L4Linux menuconfig, there is an option saying : [ ] make linux be a server Could someone explain to me what this feature does exactly ? BR, Ahmed Makkawi

2 1

L4Linux LKM
by Nourhan Mohamed 04 Feb '16

04 Feb '16

Dear all, I wanted to create a simple character device on L4Linux. I managed to cross-compile the module and run it on L4Linux on Versatile Express Realview Cortex-A15 ARM machine using the following command: make -C ~/l4re/obj/l4linux/arm-mp/ M=$PWD CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- L4ARCH=arm CONFIG_TCG_TPM=m modules V=1 When I try to insert the module using the insmod command I get the following printed out from the module: chardev: registered correctly with major number 254 chardev: device class registered correctly chardev: device class created correctly With no failures in initializing the device printed at all. Also lsmod displays the device in the module list with status live. However, the device doesn't appear in the /dev/ directory and hence I can not access it using the file operations. Any ideas where is the device located or how can it be accessed on L4Linux?

2 5

Building kernel modules for L4Linux
by Nourhan Mohamed 02 Feb '16

02 Feb '16

Hi everyone, I wanted to build a simple character device module for L4Linux on ARM device. However, I don't know who should I compile it for the L4Linux version (version 4.3.0). Can you please help me with what files should I download to cross compile the module and what should be included in the Makefile? My machine is a 64-bit machine running Ubuntu with Linux kernel version 4.3.3. Thanks in advance. Sincerely, Nourhan

2 2

'Illegal Instruction' on L4Linux
by ba_f 01 Feb '16

01 Feb '16

Hello, i have an issue with apps running on L4Linux. /usr/bin # ./helloWorld Illegal instruction Actually, on the current l4re-snapshot-2015123115 my apps run without problem. But, on l4re-snapshot-2014022818 or l4re-snapshot-2014092821 the same app don't works. All apps say 'Illegal instruction'. I've built for Zynq. Any idea what's wrong? (My project is stable on the old snapshots, that's why i try to avoid migrating to current snapshot.) thanks, ba_f

1 0

Device drivers and board support files
by Paul Boddie 27 Jan '16

27 Jan '16

Hello again, Emboldened by my recent modest success, and taking a look at the previously- mentioned MIP32 port of Fiasco.OC and L4Re [*], which doesn't really seem to have any community involved with it, I wondered whether there might be some general documentation about adding board support files to Fiasco.OC as well as writing drivers for L4Re. [*] https://github.com/MIPS/fiasco-l4re I've browsed around the L4Re site and have even looked at the TU Dresden teaching resources, but there appears to be a lot of slideshows and not so much in the way of concise guidance on such topics. Are there any documents out there that cover writing the actual code involved? With regard to board support, I get the feeling that I could possibly get away with something rather similar to other MIPS-based boards, and if I'm launching Fiasco.OC from U-Boot, I might not even need to do the basic board setup tasks (which include things like setting up the DRAM on the SoC concerned). However, I suspect that I would have to look into things like interrupt controllers for the various timers that I suppose must be needed by the kernel. As for driver support, I noticed a previous message that gives an outline of what should be done: http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007475.html Here, to be more specific, I imagine that the following things would be affected: 1. src/l4/pkg/io/config/<board>.devs would need populating with Device definitions employing those Mmio declarations 2. src/l4/pkg/io/config/vbus-config.vbus might need changing, perhaps to allow devices to match some bus identifier or other, although I don't completely follow this (I'm guessing that my driver should obtain a device reference via the vbus mechanism) 3. looking at the src/l4/pkg/drivers/lcd/src/lcd-omap3.c driver, which probably references devices in src/l4/pkg/io/io/config/plat- beagleboard/hw_devices.io, I see that the driver actually obtains a reference to the "dss" device using l4io_lookup_device, whereas the GPIO and I2C devices are obtained using l4vbus_get_device_by_hid, but I'm guessing that there is a distinction between specific and generic devices here 4. in src/l4/pkg/drivers/.../<device>.c the l4io_request_iomem call would employ the same physical addresses as those mentioned in (1) to access the device memory regions I did start looking at the existing LCD drivers, this being something that I've managed to get to work with bare-metal code on the board concerned, and I noticed that drivers/lcd seems to mention "arm" a lot, but would I be right in assuming that none of that code is actually ARM-specific? Thanks once again for any help you can offer! Paul

2 1

Setting up network in L4Linux
by Nourhan Mohamed 26 Jan '16

26 Jan '16

I have been trying to configure *L4Linux *to connect to the internet through *L4Re/Fiasco.OC*. I am using *qemu *on a *Versatile Express* Machine with *Cortex-A15* cpu. Below is my current configuration: *L4re-snapsot:* l4re-snapshot-2015123115 *obj/l4/arm-ca/conf/Makeconf.boot:* MODULE_SEARCH_PATH=/home/nour/l4re/obj/fiasco/arm-mp-rv-a9-vexpress:/home/nour/l4re/obj/l4linux/arm-mp:/home/nour/l4re/files:/home/nour/l4re/files/cfg:/home/nour/l4re/src/l4/conf:/home/nour/l4re/src/l4/conf/examples QEMU_OPTIONS += -M vexpress-a15 -cpu cortex-a15 -smp 4 QEMU_OPTIONS += -m 256 -serial stdio QEMU_OPTIONS += -net nic,model=lan9118 -net user PLATFORM_TYPE := rv_vexpress *l4re/files/cfg/arm-rv.devs:* -- vim:set ft=lua: local Res = Io.Res local Hw = Io.Hw Io.hw_add_devices(function() NIC = Hw.Device(function() Property.hid = "smc91x"; compatible = {"smsc,lan9118"}; Resource.regs = Res.mmio(0x10030000, 0x10030fff); Resource.irq = Res.irq(60); end); virtio_mmio3 = Hw.Device(function() compatible = {"virtio,mmio"}; Resource.mem = Res.mmio(0x10013600, 0x100137ff); Resource.irq = Res.irq(75); end); CTRL = Hw.Device(function() Property.hid = "System Control"; Resource.regs = Res.mmio(0x10000000, 0x10000fff); end); clcd = Hw.Device(function() Property.hid = "AMBA PL110"; compatible = {"arm,pl111","arm,primecell"}; Resource.regs = Res.mmio(0x10020000, 0x10020fff); end); kmi0 = Hw.Device(function() compatible = {"arm,pl050","arm,primecell"}; Resource.regs = Res.mmio(0x10006000, 0x10006fff); Resource.irq = Res.irq(44); end); kmi1 = Hw.Device(function() compatible = {"arm,pl050","arm,primecell"}; Resource.regs = Res.mmio(0x10007000, 0x10007fff); Resource.irq = Res.irq(45); end); end) *src/l4/conf/examples/l4lx-vbus.io <http://l4lx-vbus.io>:* local hw = Io.system_bus(); Io.add_vbus("l4linux", Io.Vi.System_bus { NIC = wrap(hw:match("smsc,lan9118")); }) src/l4/conf/examples/l4lx-net.cfg: -- vim:set ft=lua: local L4 = require("L4"); local lxname = "vmlinuz"; loader = L4.default_loader; vbus_l4linux = loader:new_channel(); local shmns = loader:create_namespace({shm = "ipctest"}); local cons = L4.default_loader:new_channel(); L4.default_loader:start( { caps = { cons = cons:svr() }, log = L4.Env.log, }, "rom/cons -k -a" ); L4.default_loader.log_fab = cons; loader:start( { caps = { sigma0 = L4.cast(L4.Proto.Factory,L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; l4linux = vbus_l4linux:svr(); }, log = {"IO", "magenta"}, }, "rom/io -vvv rom/arm-ve.devs rom/l4lx-vbus.io"); loader:start( { caps = { shmns = shmns:mode("rw"), vbus = vbus_l4linux; }, l4re_dbg = L4.Dbg.Warn, log = {"l4linux", "cyan", "key=1"}, }, "rom/" .. lxname .. " mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 rw ramdisk_size=4000 l4shmnet.add=shmns,macpart=1"); *src/l4/conf/modules.list:* entry L4Linux-net roottask moe rom/l4lx-net.cfg module l4lx-net.cfg module l4re module ned module io module cons module l4lx-vbus.io module arm-ve.devs module vmlinuz module[perl] "ramdisk-$ENV{ARCH}.rd" *Run:* L4 Bootstrapper Build: #4 Mi 20. Jan 18:13:56 CET 2016, 4.7.3 Scanning up to 256 MB RAM, starting at offset 32MB Memory size is 256MB (80000000 - 8fffffff) RAM: 0000000080000000 - 000000008fffffff: 262144kB Total RAM: 256MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 13 modules behind 81100000 moving module 02 { 81a7c000-81aad49f } -> { 81b6c000-81b9d49f } [201888] moving module 01 { 81a6a000-81a7b33b } -> { 81b5a000-81b6b33b } [70460] moving module 00 { 819d8000-81a69ebb } -> { 81ac8000-81b59ebb } [597692] moving module 12 { 816d8000-819d7fff } -> { 817c8000-81ac7fff } [3145728] moving module 11 { 81256000-816d747b } -> { 81346000-817c747b } [4723836] moving module 10 { 81255000-81255446 } -> { 81345000-81345446 } [1095] moving module 09 { 81254000-8125415d } -> { 81344000-8134415d } [350] moving module 08 { 81222000-81253823 } -> { 81312000-81343823 } [202788] moving module 07 { 811f8000-81221623 } -> { 812e8000-81311623 } [169508] moving module 06 { 81085000-811f761b } -> { 81175000-812e761b } [1517084] moving module 05 { 8102b000-81084693 } -> { 8111b000-81174693 } [366228] moving module 04 { 81011000-8102a463 } -> { 81101000-8111a463 } [103524] moving module 03 { 81010000-810103cb } -> { 81100000-811003cb } [972] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x80002000 Regions of list 'regions' [ 80000000, 800001bf] { 1c0} Root mbi_rt [ 80001000, 80001b7f] { b80} Kern fiasco [ 80002000, 8009ffff] { 9e000} Kern fiasco [ 800c0000, 800c9f6b] { 9f6c} Sigma0 sigma0 [ 800d0000, 800d6177] { 6178} Sigma0 sigma0 [ 80140000, 80169457] { 29458} Root moe [ 80170000, 80176ff3] { 6ff4} Root moe [ 81000000, 8100f5df] { f5e0} Boot bootstrap [ 81100000, 81ac7fff] { 9c8000} Root Module API Version: (87) experimental Sigma0 config ip:800c0100 sp:00000000 Roottask config ip:80140260 sp:00000000 Starting kernel fiasco at 80001374 Realview System ID: Rev=1 HBI=190 Build=f Arch=5 FPGA=00 Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf008f010-0xf008f5d8) Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv4(4), Part: VFPv3(30), r: 0, v: f, i: 41, t: hard, p: dbl/sngl ARM generic timer: freq=62500000 interval=62500 cnt=10064946 SERIAL ESC: allocated IRQ 37 for serial uart Not using serial hack in slow timer handler. Welcome to L4/Fiasco.OC! L4/Fiasco.OC microkernel on arm Rev: unknown compiled with gcc 4.7.3 [] Build: #1 Wed Jan 20 17:27:17 CET 2016 Per_cpu_data_alloc: (orig: 0xf008f010-0xf008f5d8) Allocate 1480 bytes (1KB) for CPU[9] local storage (offset=13557f0, 0xf13e4800-0xf13e4dc8) Number of CPUs: 1 Per_cpu_data_alloc: (orig: 0xf008f010-0xf008f5d8) Allocate 1480 bytes (1KB) for CPU[1] local storage (offset=115b7f0, 0xf11ea800-0xf11eadc8) FPU1: Arch: VFPv4(4), Part: VFPv3(30), r: 0, v: f, i: 41, t: hard, p: dbl/sngl Per_cpu_data_alloc: (orig: 0xf008f010-0xf008f5d8) Allocate 1480 bytes (1KB) for CPU[2] local storage (offset=115eff0, 0xf11ee000-0xf11ee5c8) FPU2: Arch: VFPv4(4), Part: VFPv3(30), r: 0, v: f, i: 41, t: hard, p: dbl/sngl Cache config: ON ID_PFR[01]: 00001131 00011011 ID_[DA]FR0: 02010555 00000000 ID_MMFR[04]: 10201105 20000000 01240000 02102211 CPU[2]: goes to idle loop Per_cpu_data_alloc: (orig: 0xf008f010-0xf008f5d8) Allocate 1480 bytes (1KB) for CPU[3] local storage (offset=1161ff0, 0xf11f1000-0xf11f15c8) FPU3: Arch: VFPv4(4), Part: VFPv3(30), r: 0, v: f, i: 41, t: hard, p: dbl/sngl Calibrating timer loop... Cache config: ON ID_PFR[01]: 00001131 00011011 ID_[DA]FR0: 02010555 00000000 ID_MMFR[04]: 10201105 20000000 01240000 02102211 CPU[1]: goes to idle loop Cache config: ON ID_PFR[01]: 00001131 00011011 ID_[DA]FR0: 02010555 00000000 ID_MMFR[04]: 10201105 20000000 01240000 02102211 CPU[3]: goes to idle loop done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 80002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:80000000;80000fff] [0:800a0000;800bffff] [0:800ca000;800cffff] [0:800d7000;8013ffff] [4:80140000;80169fff] [0:8016a000;8016ffff] [4:80170000;80176fff] [0:80177000;810fffff] [4:81100000;81ac7fff] [0:81ac8000;8effffff] IOMEM:---------------------- [0:0;7fffffff] [0:90000000;ffffffff] MOE: Hello world MOE: found 234840 KByte free memory MOE: found RAM from 80000000 to 8f000000 MOE: allocated 240 KByte for the page array @0x800d7000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:103000] BOOTFS: [81100000-811003cc] [C:105000] l4lx-net.cfg BOOTFS: [81101000-8111a464] [C:107000] l4re BOOTFS: [8111b000-81174694] [C:109000] ned BOOTFS: [81175000-812e761c] [C:10b000] io BOOTFS: [812e8000-81311624] [C:10d000] fb-drv BOOTFS: [81312000-81343824] [C:10f000] cons BOOTFS: [81344000-8134415e] [C:111000] l4lx-vbus.io BOOTFS: [81345000-81345447] [C:113000] arm-ve.devs BOOTFS: [81346000-817c747c] [C:115000] vmlinuz BOOTFS: [817c8000-81ac8000] [C:117000] ramdisk-arm.rd MOE: cmdline: moe rom/l4lx-net.cfg MOE: Starting: rom/ned rom/l4lx-net.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx-net.cfg' Console Server cons> Created vcon channel: IO [41f000] cons> Created vcon channel: l4linux [420000] cons> IO | Io service IO | Verboseness level: 4 IO | unused physical memory space: IO | [00000000000000-0000007fffffff] IO | [00000090000000-000000ffffffff] IO | no 'iommu' capability found use CPU-phys for DMA IO | Loading: config 'rom/arm-ve.devs' IO | Loading: config 'rom/l4lx-vbus.io' IO | Real Hardware ----------------------------------- IO | System Bus: hid= IO | Resources: ==== start ==== IO | DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6) IO | Resources: ===== end ===== IO | virtio_mmio3: hid= IO | Resources: ==== start ==== IO | IRQ [0000000000004b-0000000000004b 1] none (32bit) (align=0 flags=1) IO | IOMEM [00000010013600-000000100137ff 200] non-pref (32bit) (align=1ff flags=2) IO | Resources: ===== end ===== IO | clcd: hid=AMBA PL110 IO | Resources: ==== start ==== IO | IOMEM [00000010020000-00000010020fff 1000] non-pref (32bit) (align=fff flags=2) IO | Resources: ===== end ===== IO | kmi0: hid= IO | Resources: ==== start ==== IO | IRQ [0000000000002c-0000000000002c 1] none (32bit) (align=0 flags=1) IO | IOMEM [00000010006000-00000010006fff 1000] non-pref (32bit) (align=fff flags=2) IO | Resources: ===== end ===== IO | kmi1: hid= IO | Resources: ==== start ==== IO | IRQ [0000000000002d-0000000000002d 1] none (32bit) (align=0 flags=1) IO | IOMEM [00000010007000-00000010007fff 1000] non-pref (32bit) (align=fff flags=2) IO | Resources: ===== end ===== IO | NIC: hid=smc91x IO | Clients: ===== start ==== IO | NIC: [N2Vi9Proxy_devE] IO | Clients: ===== end ==== IO | Resources: ==== start ==== IO | IRQ [0000000000003c-0000000000003c 1] none (32bit) (align=0 flags=1) IO | IOMEM [00000010030000-00000010030fff 1000] non-pref (32bit) (align=fff flags=2) IO | Resources: ===== end ===== IO | CTRL: hid=System Control IO | Resources: ==== start ==== IO | IOMEM [00000010000000-00000010000fff 1000] non-pref (32bit) (align=fff flags=2) IO | Resources: ===== end ===== IO | warning: could not register control interface at cap 'platform_ctl' IO | Ready. Waiting for request. l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=0252b724 l4linux | phys=02000000 ephys=0252b724 l4linux | f_sz=004655df memsz=0052b724 flgs=rwx l4linux | PH 1 (t: 4) offs=004077b0 vaddr=023ff7b0 vend=023ff7d4 l4linux | phys=023ff7b0 ephys=023ff7d4 l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x2001338, argc=8 argv=0xafff4f84 *argv=0xb1007ff4 argv0=rom/vmlinuz l4linux | External resolver is at 0xa800079c l4linux | ======> L4Linux starting... <======== l4linux | Linux version 4.3.0-l4 (nour@nour-vb) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-12ubuntu1) ) #1 SMP Wed Jan 20 17:53:39 CET 2016 l4linux | Binary name: rom/vmlinuz l4linux | This is an AEABI build. l4linux | Linux kernel command line (7 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 rw ramdisk_size=4000 l4shmnet.add=shmns,macpart=1 l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 020000a0 - 02600000 [6143 KiB]. l4linux | Areas: Text: 020000a0 - 023ff7d4 [4093kB] l4linux | RO-Data: 0233f000 - 023e2000 [652kB] l4linux | Data: 02438000 - 02460fe0 [163kB] l4linux | Init: 02400000 - 02438000 [224kB] l4linux | BSS: 024655df - 0252b724 [792kB] l4linux | Device scan: l4linux | Device: L4ICU l4linux | Device: NIC l4linux | IRQ: 0000003c - 0000003c l4linux | MEM: 10030000 - 10030fff l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 41d (cpu0) (u:b3000e00, v:b3000c00, sp:02439fa4) l4linux | main thread will be 41d l4linux | section-with-init(-data): Virt: 0x2000000 to 0x252b723 [5293 KiB] l4linux | section-with-init(-data): Phys: 0x801a9000 to 0x806d4723, [5293 KiB] l4linux | section-with-init-text: Virt: 0x2000000 to 0x252b723 [5293 KiB] l4linux | section-with-init-text: Phys: 0x801a9000 to 0x806d4723, [5293 KiB] l4linux | Main thread running, waiting... l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 02000000 l4linux | Main memory: Virt: 0x2600000 to 0x65fffff [65536 KiB] l4linux | Main memory: Phys: 0x81c00000 to 0x85bfffff, [65536 KiB] l4linux | l4x: vmalloc area: 06600000 - 0e600000 l4linux | text: Virt: 0x2000000 to 0x252b723 [5293 KiB] l4linux | text: Phys: 0x801a9000 to 0x806d4723, [5293 KiB] l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] l4linux | l4lx_thread_create: Created thread 423 (timer0) (u:b3000a00, v:00000000, sp:024bffa0) l4linux | Booting Linux on physical CPU 0x0 l4linux | Linux version 4.3.0-l4 (nour@nour-vb) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-12ubuntu1) ) #1 SMP Wed Jan 20 17:53:39 CET 2016 l4linux | CPU: Fiasco [412fc0f1] revision 1 (ARMv7), cr=00400000 l4linux | CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache l4linux | Machine: L4 l4linux | Ignoring unrecognised tag 0x00000000 l4linux | Memory policy: Data cache writealloc l4linux | INITRD: 00002000 - 00302000 l4linux | PERCPU: Embedded 9 pages/cpu @0651f000 s12864 r0 d24000 u36864 l4linux | Built 1 zonelists in Zone order, mobility grouping on. Total pages: 17716 l4linux | Kernel command line: mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 rw ramdisk_size=4000 l4shmnet.add=shmns,macpart=1 l4linux | PID hash table entries: 512 (order: -1, 2048 bytes) l4linux | Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) l4linux | Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) l4linux | Memory: 64764K/71680K available (3441K kernel code, 163K rwdata, 652K rodata, 224K init, 792K bss, 6916K reserved, 0K cma-reserved) l4linux | Virtual kernel memory layout: l4linux | vector : 0xbffff000 - 0xc0000000 ( 4 kB) l4linux | fixmap : 0xffc00000 - 0xfff00000 (3072 kB) l4linux | vmalloc : 0x06600000 - 0x0e600000 ( 128 MB) l4linux | lowmem : 0x00000000 - 0x06600000 ( 102 MB) l4linux | .text : Virtual kernel memory layout: l4linux | vector : 0xbffff000 - 0xc0000000 ( 4 kB) l4linux | fixmap : 0xffc00000 - 0xfff00000 (3072 kB) l4linux | vmalloc : 0x06600000 - 0x0e600000 ( 128 MB) l4linux | loHierarchical RCU implementation. l4linux | Build-time adjustment of leaf fanout to 32. l4linux | RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1. l4linux | RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=1 l4linux | NR_IRQS:282 l4linux | clocksource: l4kipclk: mask: 0xffffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 3526361616960 ns l4linux | l4timer: Using IRQ210 l4linux | sched_clock: 64 bits at 1000kHz, resolution 1000ns, wraps every 2199023255500ns l4linux | Console: colour dummy device 80x30 l4linux | console [ttyLv0] enabled l4linux | Calibrating delay loop... 410.41 BogoMIPS (lpj=2052096) l4linux | pid_max: default: 32768 minimum: 301 l4linux | Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) l4linux | Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) l4linux | CPU: Testing write buffer coherency: ok l4linux | CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 l4linux | Setting up static identity map for 0x20000a0 - 0x20000a0 l4linux | Brought up 1 CPUs l4linux | SMP: Total of 1 processors activated (410.41 BogoMIPS). l4linux | CPU: All CPU(s) started in SVC mode. l4linux | VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0 l4linux | clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns l4linux | NET: Registered protocol family 16 l4linux | DMA: preallocated 256 KiB pool for atomic coherent allocations l4linux | Added static device 'L4ICU' with 0 resources. l4linux | Added static device 'NIC' with 2 resources. l4linux | l4vbus: is running l4linux | L4IRQ: set irq type of 212 to 1 l4linux | l4vbus-root :l4vbus-root:0: added vbus root driver l4linux | clocksource: Switched to clocksource l4kipclk l4linux | NET: Registered protocol family 2 l4linux | TCP established hash table entries: 1024 (order: 0, 4096 bytes) l4linux | TCP bind hash table entries: 1024 (order: 1, 8192 bytes) l4linux | TCP: Hash tables configured (established 1024 bind 1024) l4linux | UDP hash table entries: 256 (order: 1, 8192 bytes) l4linux | UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) l4linux | NET: Registered protocol family 1 l4linux | RPC: Registered named UNIX socket transport module. l4linux | RPC: Registered udp transport module. l4linux | RPC: Registered tcp transport module. l4linux | RPC: Registered tcp NFSv4.1 backchannel transport module. l4linux | Trying to unpack rootfs image as initramfs... l4linux | rootfs image is not initramfs (junk in compressed archive); looks like an initrd l4linux | INITRD: Freeing memory. l4linux | Hi from the sample module l4linux | sample module: Also a warm welcome to the console l4linux | l4x: Checks passed. l4linux | NetWinder Floating Point Emulator V0.97 (double precision) l4linux | futex hash table entries: 256 (order: 2, 16384 bytes) l4linux | NFS: Registering the id_resolver key type l4linux | Key type id_resolver registered l4linux | Key type id_legacy registered l4linux | jitterentropy: Initialization failed with host not compliant with requirements: 2 l4linux | io scheduler noop registered l4linux | io scheduler deadline registered l4linux | io scheduler cfq registered (default) l4linux | l4fb.0: looking for capability 'fb' as goos session l4linux | l4fb.0: init failed err=-2 l4linux | could not allocate fb device: fb l4linux | L4 serial driver l4linux | serial-ttyLv.0: ttyLv0 at MMIO 0x1 (irq = 211, base_baud = 230400) is a L4-vcon l4linux | l4ser_shm: L4 shared mem serial driver l4linux | l4cdds: No name given, not starting. l4linux | brd: module loaded l4linux | l4bdds: No name given, not starting. l4linux | PPP generic driver version 2.4.2 l4linux | NET: Registered protocol family 24 l4linux | shmns: Requesting, Shmsize 1024 Kbytes l4linux | mousedev: PS/2 mouse device common for all mice l4linux | NET: Registered protocol family 17 l4linux | Key type dns_resolver registered l4linux | Registering SWP/SWPB emulation handler l4linux | L4IRQ: set irq type of 211 to 1 l4linux | RAMDISK: ext2 filesystem found at block 0 l4linux | RAMDISK: Loading 3072KiB [1 disk] into ram disk... done. l4linux | EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities l4linux | EXT4-fs (ram0): mounting ext2 file system using the ext4 subsystem l4linux | EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) l4linux | VFS: Mounted root (ext2 filesystem) on device 1:0. l4linux | Freeing unused kernel memory: 224K (02400000 - 02438000) l4linux | l4linux | Please press Enter to activate this console. However once I enter the console, ifconfig command displays no up interfaces. /proc/net/dev file indicates eth0 and lo available and I can run "*ifconfig eth0 up*" successfully. I configure a static IP using ip command but can't get any connection to my host machine. Also, adding *ip=dhcp* to the l4lx-net.cfg file in the start configuration of L4Linux fails with: l4linux | Waiting up to 110 more seconds for network. ... l4linux | Sending DHCP requests ...... timed out! l4linux | IP-Config: Retrying forever (NFS root)... I hope you can help me with that. Thanks in advance: Best Regards, Nourhan

2 5

Fiasco-OC.UX, ux_con and the framebuffer examples
by Paul Boddie 22 Jan '16

22 Jan '16

Another year, another look at Fiasco-OC! ;-) I've been looking again at Fiasco-OC.UX and trying to make sense of the documentation. In particular, I'd like to be able to get the framebuffer examples working with the UX graphical console, but it isn't clear to me what I need to do. One thing I discovered straight away was that I needed to provide the -F option as part of the UX_OPTIONS variable when running UX via make. For example: cd src/l4 make O=mybuild ux E=hello MODULE_SEARCH_PATH=../kernel/fiasco/mybuild \ UX_OPTIONS='-G 800x600@24 -F ../kernel/fiasco/mybuild/ux_con' I suspect that to run a framebuffer example, such as the one in src/l4/conf/examples/x86-fb.list, I need to specify E=x86-fb-example and specify the list file using MODULES_LIST: make O=mybuild ux E=x86-fb-example \ MODULES_LIST=conf/examples/x86-fb.list \ MODULE_SEARCH_PATH=../kernel/fiasco/mybuild \ UX_OPTIONS='-G 800x600@24 -F ../kernel/fiasco/mybuild/ux_con' But this naive attempt gives me the following: Could not find 'x86-fb.cfg' with path '../kernel/fiasco/mybuild:/home/paulb/L4/src/l4/mybuild/bin/x86_prescott:... I imagine that I need to more effectively specify paths to various things and to check that they even make sense in the context of the UX environment. Should I even be using this x86-related stuff? Copying the different x86-fb files into one of my existing MODULE_SEARCH_PATH directories did seem to resolve the above immediate error, however, but I then appear to need to build various drivers. This seems to require chasing dependencies as they are reported as missing by the build system, and that makes me wonder whether I've overlooked a command that recursively checks out all dependencies for a given component. Anyway, running the above command with all dependencies compiled and with x86- fb (and x86-legacy.devs) files in the path gives an error like this... Ned: loading file: 'rom/x86-fb.cfg' IO | Io service IO | Find root Pointer IO | ACPI Error: Could not map memory at 0x000E0000 for length 131072 (20121018/tbxfroot-286) IO | Find root Pointer: 0 IO | Ready. Waiting for request. mag | Hello from MAG fbdrv | Trying execution of ``set VBE mode'' using x86emu fbdrv | L4Re[rm]: unhandled read page fault at 0xfd0 pc=0x1007d49 fbdrv | L4Re: unhandled exception: pc=0x1007d49 (pfa=fd4) fbdrv | L4Re: Global::l4re_aux->ldr_flags=0 ...which probably suggests that I really should be using something other than this x86-related stuff. Does anyone have any suggestions, or am I doing something that no-one thought sensible? (As mentioned last year on this list, I'm running everything under Debian on x86, and UX does work with the "hello" example.) Thanks in advance, Paul P.S. I've also found that various links on l4re.org to things like the "getting started" details are broken. For example: http://l4re.org/build.html -> http://l4re.org/doc/l4re_getting_started.html

2 6

How can I get L4linux 3.10 code?
by liu.xiaodong2＠zte.com.cn 19 Jan '16

19 Jan '16

Hi, I want to use L4linux 3.10. I see that L4linux 3.10 is available now from https://l4linux.org/, but I can't find any other download-website except L4linux 4.3. Is there some place I can get the older version(3.10) of the L4linux? thanks a lot! -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

2 1

Hiring engineers for seL4 work
by Gernot Heiser 12 Jan '16

12 Jan '16

Do you want to be paid for contributing to the seL4 microkernel and its ecosystem, and getting your code used in critical systems on a large scale? As part of a kick-ass team, while living in Sydney, one of the world’s most liveable cities? The seL4 team at DATA61 (formerly NICTA) is hiring OS engineers, see https://ssrg.nicta.com.au/jobs/OS-engineers2015 We’re also hiring: - proof engineers: https://ssrg.nicta.com.au/jobs/proof-engineers2015 - researchers/postdocs: https://ssrg.nicta.com.au/jobs/OS-researchers2015 Gernot

6 25

Question about memory management in L4 Fiasco O.C + L4re
by Mahdi Aichouch 04 Jan '16

04 Jan '16

Hello, I have some questions concerning memory management in Fiasco O.C + L4re. I would like to test two L4Linux instances, and for each L4Linux instance I want to reserve one static fixed physical memory partition. For instance, one 128MB for the first L4Linux and one 128MB for the second. Knowing that Fiasco O.C. uses "on demand paging" to allocate pages for user tasks, is it possible that each partition of L4Linux could be allocated a static physical memory region composed of contiguous physical frames. For instance, one memory region starting from 128MB to 256MB for the first L4Linux, and second memory region from 256MB to 512MB for the second L4Linux. Each memory region is allocated exclusively to one L4Linux instance. I would like to know if it is possible to load all the code + data of a L4Linux instance into its reserved memory partition, so no page fault will be encountered during runtime. Is it possible to tell me if these above operations could be realized in Fiasco O.C and L4re? If the answer is yes, is it possible to tell me what are the objects that should be used or adapted in order to implement these? What are the issues that I should pay attention to? Many thanks in advance for your answer. Best regards, Mahdi

2 37

L4Re Update
by Adam Lackorzynski 04 Jan '16

04 Jan '16

Hi, After a longer break I'm pleased to announce an update of the L4Re system software. https://l4re.org Besides bug fixes and enhancements, noteworthy changes and additions of this update include: All: - LLVM/Clang: Fiasco.OC is supported with Clang now, for the userland we're nearly there - Updates for recent GCC versions - CROSS_COMPILE is the preferred way to set the compiler prefix now - URLs have been consolidated to be under the l4re.org domain but old ones will remain to work for a foreseeable future. L4Re: - Package reorganization: Core packages have been moved to a more hierarchical structure, e.g. l4re-core and io - New RPC framework using C++ that generates client and server side code from a single definition, code and examples have been adapted accordingly - Software updates, e.g. libstdc++, lua, libpng, libjpeg, lwip - New L4Re::Dma_space interface to support DMA and IOMMUs - io gained support for IOMMUs and MSI remapping - Virtio library to support the development of virtio host applications - Documentation improvements: https://l4re.org/doc/ Fiasco.OC: - IOMMU support, including MSI remapping (currently VT-d) - Clang support L4Linux: - Added x86-64 variant - Updated to version Linux 4.3 - MSI / MSI-X support Happy new year, Adam

4 3

Performance of L4
by Patrick Staeblein 28 Dec '15

28 Dec '15

Hello Dear L4 Hackers, I am still writing on my bachelors-thesis on the performance of L4/Fiasco and wanted to ask you if you can give me some hints and ideas. My goal was to find out how the time-costs are divided between ipc, memory access and scheduling and resulting out of this what properties programs should have that makes them execute as fast as possible. For measuring the ipc-time i used the ipc_example.c-file in the ./src/l4/pkg/examples/sys directory and added rdtsc (Read Time Stamp Counter)-instructions before and after making the ipc-call and then calculating the difference between the two values. This was executed in a loop and the resulting values were divided into ten equal-sized range-classes depicting them as a histogram.The results showed the ipc-time to be pretty stable with almost all values falling into one class (Sorry for my shitty Englisch anyway). Does anyone have an idea what kind of measurement one could do for a measurement of the scheduling? I found the function l4_scheduler_idle_time (...), but I don't have an idea for using it in a concrete program or experiment setup. I also thought about repeatedly measuring the time it takes for one context-switch, but I don't know in which place exactly I would have to insert the rdtsc-instructions. Does anyone know which exact C-file would have to be modified for that? I am thankful for any answer, regards, the Steppenwolf

2 1

Serial console not working
by Lluís Vilanova 22 Dec '15

22 Dec '15

Hi there! I'm trying to find out why my setup is not booting on a real machine (some Dell PowerEdge R210 node; ned says it cannot find rom/l4re), but I'm unable to redirect output to the serial console. I'm able to use the serial console for both grub and linux, so it's not a hardware issue. An excerpt of my grub2 configuration: serial --unit=1 --speed=115200 --word=8 --parity=no --stop=1 terminal_input serial terminal_output serial # ... # for the linux entry linux /vmlinuz-3.16.0-4-amd64 root=UUID=7573ed62-a910-4b97-a577-dde47a16f87a ro console=ttyS1,115200n8 quiet Now, here's the entry I'm using for L4, which never gets me any output on the serial console: menuentry 'Test' { set root=(hd0,1) multiboot /l4/bootstrap -serial module /l4/fiasco -serial_esc -comspeed 115200 -comport 1 module /l4/sigma0 module /l4/moe rom/test.cfg module /l4/l4re module /l4/ned module /l4/test.cfg module /l4/bin/test } Thanks, Lluis

2 3

Problem with Hello app on Zedboard
by Manolis Ragkousis 14 Dec '15

14 Dec '15

Hello everyone, I am trying to make the Hello app run on the zedboard but it gets stuck at "Scanning up to 512 MB RAM, starting at offset 32MB". I have configured both fiasco and l4re with the correct configuration (I have attached my config files) and cross compiled them from a x86_64 linux machine with "Linaro GCC 4.9-2014.09 4.9.2 20140904". I searched the mailing lists archives but I can't seem to find a similar problem. I tried changing the uart port I was using, in case it was printing in another port, but nothing changed. Any ideas/suggestions on what could go be going wrong and/or how can I solve it? Thank you for your time, Manolis The output of u-boot: reading uImage 970816 bytes read in 108 ms (8.6 MiB/s) reading initramfs.cpio.gz 128 bytes read in 17 ms (6.8 KiB/s) reading devicetree.dtb 9331 bytes read in 16 ms (569.3 KiB/s) ## Booting kernel from Legacy Image at 03000000 ... Image Name: L4 Image #2 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 970752 Bytes = 948 KiB Load Address: 01000000 Entry Point: 01000000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 02000000 ... Image Name: Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 64 Bytes = 64 Bytes Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02a00000 Booting using the fdt blob at 0x2a00000 Loading Kernel Image ... OK Loading Ramdisk to 0f31d000, end 0f31d040 ... OK Loading Device T^H.��.\\Build: #2 Fri Dec 11 14:35:25 EET 2015, 4.9.2 20140904 (prerelease) Scanning up to 512 MB RAM, starting at offset 32MB

2 1

real time app on l4linux
by cem akpolat 14 Dec '15

14 Dec '15

Hi, I want to ask, if you have any guide or documentation, how to write a real time app on l4linux. As you know, l4llinux doesn't guarantee whether the application .which run on top of it, will be close to real time or not. In this case, should we write an separate l4 app and communicate with l4linux over IPC? If yes, again, how can I implement this kind of an app. For instance, if we take the server-client app under examples folder, can we apply the same scenario? How can I communicate with L4Linux? Sincerely, Cem Akpolat

2 3

Reminder: Microkernel-devroom CfP deadline is on this Sunday
by Jakub Jermar 07 Dec '15

07 Dec '15

Hi folks, the CfP deadline for the Microkernel devroom at FOSDEM 2016 is due this Sunday. See the original CfP [1] for information on what to do if you would like to give a talk about some microkernel-related topic. At the same time, I would like to encourage you to submit a talk proposal. It would be shame not to let the wider microkernel community know about the latest and greatest developments in your project. Lastly, please forward this reminder to whoever you think may want to give a talk in the devroom and is not among the recipients of this message. Thanks, Jakub [1] http://trac.helenos.org/wiki/Devroom2016

1 0

L4Re halts at boot, waiting for console input
by Arttu Pulli 28 Nov '15

28 Nov '15

Hello hackers, the subject line summarizes my problem pretty well. To expand, the halting happens first when Ned begins booting the user space services defined in the modules.list config, after it has loaded the Lua config script file. First I thought that my setup is just wrong, but feeding some amount of newlines through the serial console causes the boot to continue normally. The system is still waiting for input during this, though, as can be seen from the fact that the boot will go forward to starting Io with a couple of newlines, then it halts after that again, then newlines start my own user space modules, the system halting between every module if no input is given. This only happens on warm boots. When powering the board for the first time, the boot goes all the way to the finish without any user input. I'm using a custom i.MX6Q based board. So, with that background, my question is is there some general place where this kind of behaviour can be configured? Or is it just that my setup is somehow broken, and this is not any kind of feature of Fiasco.OC/L4? BR, Arttu Pulli

2 1

Re: L4Linux update? Driver support
by li94575 28 Nov '15

28 Nov '15

At 2015-11-22 23:42:55, "Adam Lackorzynski" <adam(a)os.inf.tu-dresden.de> wrote: >hi, > >On Sun Nov 22, 2015 at 22:07:46 +0800, li94575 wrote: >> hello Adam, >> I also have a question about the Interrupt mechanism in l4linux. I want to move some interrupts to specified cpu core. When I try to write to "/proc/irq/*/smp_affinity" with cpu bitmask, it will call the function l4lx_irq_dev_set_affinity(), which attachs the irq to corresponding vcpu thread. After that, I find the irq is still staying on previous cpu core through linux proc system. So I doubt whether linux proc filesystem's view is synchronized with the interrupt settings of the L4 kernel, or it can not be achieved in l4linux? (I use genode for the runtime environment of fiasco.oc) > >The l4lx_irq_dev_set_affinity function that is called by Linux >interrupt code, i.e. I think all the book keeping shall be done by the >Linux code, including the output of /proc/interrupts. >You should check in the jdb to which thread the interrupt is attached. >You can see this in the object list, use shift-Q to see it. >WIth CONFIG_L4_DEBUG_REGISTER_NAMES=y enabled in L4Linux, you'll have >proper descriptions of the objects, so you'll find the interrupt you're >looking for: l4lx.irqXX with XX being the same number as in >/proc/interrupts. >Then, look for the T= value of that particular interrupt, it points to >the thread the interrupt is attached to. Pressing TAB brings you to the >thread in the list. Is it the right onw? >I have tried your methed in the jdb, and find all the irqs we used is on the same thread( on cpu0 ) which has no name.But CONFIG_L4_DEBUG_REGISTER_NAMES is enabled in L4Linux. Regardless of how the irq setting in L4Linux, it alwaysstays the same in the jdb, this makes me so confused.

2 3

Qt on L4
by Nancy Joshua 27 Nov '15

27 Nov '15

Hi all i wanna port QT to l4.The documentation and tutorial in www.trolltech.com is not available any more. I have no idea how to start porting either. Any help in this regard is highly appreciated. -- Thanks and Regard Nancy Joshua

2 1

QT on L4re
by Nancy 27 Nov '15

27 Nov '15

hi, am trying to port qt on l4re, but i wasn't able to find any qt resources in the tudos website.The documentation and tutorial from trolltech.com seem to have been removed. So any help in this regard will be appreciated. thank you Nancy Josh

1 0

Problem when testing the "ex_isr" example on an ARMv7 Cortex-A9 based board.
by Mahdi Aichouch 16 Nov '15

16 Nov '15

Hello, I tried to run the "ex_isr" example on a Freescale i.MX6 Quad Cortex A9 Sabre SD board. And I got an error saying: "Binding IRQ1 to the ICU failed". Does someone has an idea of what might be wrong. Below is the trace from the "ex_isr" example, followed by my globalconfig.h file: Thank you very much in advance. Best regards, Mahdi L4 Bootstrapper Build: #53 Thu Nov 12 11:18:21 CET 2015, 4.8.3 20140320 (prerelease) Scanning up to 1024 MB RAM, starting at offset 32MB Memory size is 1024MB (10000000 - 4fffffff) RAM: 0000000010000000 - 000000004fffffff: 1048576kB Total RAM: 1024MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 5 modules behind 11100000 moving module 02 { 110b4000-110ed63f } -> { 111a4000-111dd63f } [235072] moving module 01 { 110aa000-110b338b } -> { 1119a000-111a338b } [37772] moving module 00 { 11044000-110a97cb } -> { 11134000-111997cb } [415692] moving module 04 { 1102a000-11043597 } -> { 1111a000-11133597 } [103832] moving module 03 { 11010000-11029473 } -> { 11100000-11119473 } [103540] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x10002000 Regions of list 'regions' [ 10000000, 100000e7] { e8} Root mbi_rt [ 10001000, 10001aff] { b00} Kern fiasco [ 10002000, 10072fff] { 71000} Kern fiasco [ 10090000, 10096edf] { 6ee0} Sigma0 sigma0 [ 10098000, 1009e177] { 6178} Sigma0 sigma0 [ 10140000, 10171d77] { 31d78} Root moe [ 10178000, 101934ab] { 1b4ac} Root moe [ 11000000, 1100f4ff] { f500} Boot bootstrap [ 11100000, 11133fff] { 34000} Root Module API Version: (87) experimental Sigma0 config ip:10090100 sp:00000000 Roottask config ip:10140260 sp:00000000 Starting kernel fiasco at 100012c8 Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf0062510-0xf0062ed8) Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl L2: ID=410000c7 Type=9e340340 Aux=32070000 WMask=ffff S=0 L2: Type L2C-310 Size = 1024kB Ways=16 Waysize=64 SERIAL ESC: allocated IRQ 58 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rexported compiled with gcc 4.8.3 for i.MX6 [] Build: #192 Tue Nov 10 18:06:43 CET 2015 Per_cpu_data_alloc: (orig: 0xf0062510-0xf0062ed8) KERNEL: Warning: Buddy::alloc: Size mismatch: 9c8 v 1000 Allocate 2504 bytes (2KB) for CPU[4] local storage (offset=1187af0, 0xf11ea000-0xf11ea9c8) Number of CPUs: 4 Calibrating timer loop... Per_cpu_data_alloc: (orig: 0xf0062510-0xf0062ed8) done. KERNEL: Warning: Buddy::alloc: Size mismatch: 9c8 v 1000 Allocate 2504 bytes (2KB) for CPU[1] local storage (offset=1189af0, 0xf11ec000-0xf11ec9c8) MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 10002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:10000000;10000fff] [0:10073000;1008ffff] [0:10097000;10097fff] [0:1009f000;1013ffff] [4:10140000;10171fff] [0:10172000;10177fff] [4:10178000;10193fff] [0:10194000;110fffff] [4:11100000;11133fff] [0:11134000;4effffff] IOMEM:---------------------- [0:0;fffffff] [0:50000000;ffffffff] MOE: Hello world FPU1: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl MPer_cpu_data_alloc: (orig: 0xf0062510-0xf0062ed8) O KERNEL: Warning: Buddy::alloc: Size mismatch: 9c8 v 1000 E: fCache config: ON ouAllocate 2504 bytes (2KB) for CPU[2] local storage (offset=1140af0, 0xf11a3000-0xf11a39c8) nd ID_PFR[01]: 00001231 000000111031156 ID_[DA]FR0: 00010444 00000000 KID_MMFR[04]: 00100103 20000000 01230000 00102111 ByCPU[1]: goes to idle loop te free memory MOE: found RAM from 10000000 to 4f000000 MOE: allocated 1008 KByte for the page array @0x10194000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [11100000-11119474] [C:503000] l4re BOOTFS: [1111a000-11133598] [C:504000] ex_isr MOE: cmdline: moe --init=rom/ex_isr MOE: Starting: rom/ex_isFPU2: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl rPer_cpu_data_alloc: (orig: 0xf0062510-0xf0062ed8) Cache config: ON KERNEL: Warning: Buddy::alloc: Size mismatch: 9c8 v 1000 ID_PFR[01]: 00001231 00000011M ID_[DA]FR0: 00010444 00000000 OID_MMFR[04]: 00100103 20000000 01230000 00102111 EAllocate 2504 bytes (2KB) for CPU[3] local storage (offset=1144af0, 0xf11a7000-0xf11a79c8) : lCPU[2]: goes to idle loop oading 'rom/ex_isr' Binding IRQ1 to the ICU failed MOE: task 270000679 exited with 1 FPU3: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl Cache config: ON ID_PFR[01]: 00001231 00000011 ID_[DA]FR0: 00010444 00000000 ID_MMFR[04]: 00100103 20000000 01230000 00102111 CPU[3]: goes to idle loop /* * * Automatically generated file; DO NOT EDIT. * Fiasco configuration * */ #define CONFIG_PERF_CNT 1 #define CONFIG_BIT32 1 #define CONFIG_MP_MAX_CPUS 4 #define CONFIG_EXPERIMENTAL 1 #define CONFIG_ARM_CORTEX_A9 1 #define CONFIG_ARM_CACHE_L2CXX0 1 #define CONFIG_CAN_ARM_CACHE_L2CXX0 1 #define CONFIG_ABI "vf" #define CONFIG_CXX "g++" #define CONFIG_LABEL "" #define CONFIG_CAN_ARM_CPU_CORTEX_A9 1 #define CONFIG_ARM_ENABLE_SWP 1 #define CONFIG_ARM_V7 1 #define CONFIG_ARM 1 #define CONFIG_JDB 1 #define CONFIG_FPU 1 #define CONFIG_BSP_NAME "imx" #define CONFIG_SCHED_FIXED_PRIO 1 #define CONFIG_CONTEXT_4K 1 #define CONFIG_HOST_CC "gcc" #define CONFIG_MP 1 #define CONFIG_ABI_VF 1 #define CONFIG_NO_FRAME_PTR 1 #define CONFIG_ARM_V6PLUS 1 #define CONFIG_WARN_ANY 1 #define CONFIG_INLINE 1 #define CONFIG_SERIAL 1 #define CONFIG_PF_IMX_UART_NR 1 #define CONFIG_PF_IMX_UART_NR_1 1 #define CONFIG_PF_ARM_MP_CAPABLE 1 #define CONFIG_PF_IMX_RAM_PHYS_BASE 0x10000000 #define CONFIG_PF_IMX_6 1 #define CONFIG_XARCH "arm" #define CONFIG_CC "gcc" #define CONFIG_HOST_CXX "g++" #define CONFIG_ARM_CPU_ERRATA 1 #define CONFIG_PF_IMX 1 #define CONFIG_WARN_LEVEL 2 #define CONFIG_VIRT_OBJ_SPACE 1 #define CONFIG_ARM_EM_STD 1

2 1

How is network stack implemented in Fiasco/l4Re
by Yuxin Ren 06 Nov '15

06 Nov '15

Hi, I have a few questions about network stack in Fiasco/L4Re. Is network stack implemented in the kernel or user level? If in user level, are different protocols (IP/TCP) implemented in a single server or different servers? If in different servers, how do they communicate with each other? Is there any example code to show how to use network? How to send and receive TCP or UDP packets? How can I set up the network environment on bare metal machine? Is there documentation or instruction? Thanks a lot! Yuxin

2 3

Microkernel Meetup
by Bjoern Doebel 02 Nov '15

02 Nov '15

Hi all, as the last Dresden Microkernel Meetup took place already more than 6 months ago, we surely need to set up a new one! Please chose a date: http://dudle.inf.tu-dresden.de/mks1115/ I am going to pick a location once we settled on a date. (Most likely: Shamrock Irish Pub, but select something else on Mondays...) Bjoern

1 1

Re: Porting i.MX6 FEC ethernet device driver to L4Linux (l4re-snapshot-2014092821)
by Mahdi Aichouch 30 Oct '15

30 Oct '15

Hello Martin, Thank you very much for your help! Your correction fixed the issue. Best regards, Mahdi >put the l4x_register_platform_device_callback behind the #endif. > l4x_register_platform_device_callback("aaci", aaci_cb); > #endif > l4x_register_platform_device_callback("imx6q-fec.dev", imx6q_device_cb_fec); > } On Thu, Oct 29, 2015 at 3:09 PM, Martin Schröder < martin.schroeder(a)openlimit.com> wrote: > Hi, > > Am 29.10.2015 um 14:42 schrieb Mahdi Aichouch: > >> Hello, >> >> Starting from a previous work [1] , I ported the i.MX6 FEC ethernet >> device driver to L4Linux (l4re-snapshot-2014092821). >> >> There is no compilation error, but when I tested on the Freescale i.MX6 >> Sabre SDB, it seems that L4Linux does not start the device. >> Below are the boot messages of L4 Fiasco + L4Linux. >> >> Does someone have an idea of what might be missing or wrong. >> >> To reproduce the test case using l4re-snapshot-2014092821, all >> configuration files and patches are given below. >> >> Thank you very much in advance. >> > > > > [...] > > > >> static int dev_init_done; >> @@ -238,6 +307,7 @@ >> l4x_register_platform_device_callback("compactflash", >> realview_device_cb_pata); >> l4x_register_platform_device_callback("smsc911x", >> realview_device_cb_smsc); >> l4x_register_platform_device_callback("aaci", aaci_cb); >> +l4x_register_platform_device_callback("imx6q-fec.dev", >> imx6q_device_cb_fec); >> #endif >> } >> > > put the l4x_register_platform_device_callback behind the #endif. > > > l4x_register_platform_device_callback("aaci", aaci_cb); > > #endif > > l4x_register_platform_device_callback("imx6q-fec.dev", > imx6q_device_cb_fec); > > } > > > Martin >

1 0

Porting i.MX6 FEC ethernet device driver to L4Linux (l4re-snapshot-2014092821)
by Mahdi Aichouch 29 Oct '15

29 Oct '15

Hello, Starting from a previous work [1] , I ported the i.MX6 FEC ethernet device driver to L4Linux (l4re-snapshot-2014092821). There is no compilation error, but when I tested on the Freescale i.MX6 Sabre SDB, it seems that L4Linux does not start the device. Below are the boot messages of L4 Fiasco + L4Linux. Does someone have an idea of what might be missing or wrong. To reproduce the test case using l4re-snapshot-2014092821, all configuration files and patches are given below. Thank you very much in advance. Best regards, Mahdi [1] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/006462.html L4 Bootstrapper Build: #10 Thu Oct 29 12:00:00 CET 2015, 4.8.3 20140320 (prerelease) Scanning up to 1024 MB RAM, starting at offset 32MB Memory size is 1024MB (10000000 - 4fffffff) RAM: 0000000010000000 - 000000004fffffff: 1048576kB Total RAM: 1024MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 10 modules behind 11100000 moving module 02 { 11928000-1196163f } -> { 11a18000-11a5163f } [235072] moving module 01 { 1191e000-1192738b } -> { 11a0e000-11a1738b } [37772] moving module 00 { 118b8000-1191d98b } -> { 119a8000-11a0d98b } [416140] moving module 09 { 115b8000-118b7fff } -> { 116a8000-119a7fff } [3145728] moving module 08 { 111d6000-115b7497 } -> { 112c6000-116a7497 } [4068504] moving module 07 { 111d5000-111d517b } -> { 112c5000-112c517b } [380] moving module 06 { 1107e000-111d446f } -> { 1116e000-112c446f } [1401968] moving module 05 { 1107d000-1107d35b } -> { 1116d000-1116d35b } [860] moving module 04 { 1102a000-1107cc1f } -> { 1111a000-1116cc1f } [338976] moving module 03 { 11010000-11029473 } -> { 11100000-11119473 } [103540] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x10002000 Regions of list 'regions' [ 10000000, 1000015f] { 160} Root mbi_rt [ 10001000, 10001aff] { b00} Kern fiasco [ 10002000, 10072fff] { 71000} Kern fiasco [ 10090000, 10096edf] { 6ee0} Sigma0 sigma0 [ 10098000, 1009e177] { 6178} Sigma0 sigma0 [ 10140000, 10171d77] { 31d78} Root moe [ 10178000, 101934ab] { 1b4ac} Root moe [ 11000000, 1100f58f] { f590} Boot bootstrap [ 11100000, 119a7fff] { 8a8000} Root Module API Version: (87) experimental Sigma0 config ip:10090100 sp:00000000 Roottask config ip:10140260 sp:00000000 Starting kernel fiasco at 100012c8 Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf0062390-0xf0062d58) Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl L2: ID=410000c7 Type=9e340340 Aux=32070000 WMask=ffff S=0 L2: Type L2C-310 Size = 1024kB Ways=16 Waysize=64 GIC: Switching IRQ 9 to secure GIC: Switching IRQ 8 to secure GIC: Switching IRQ 10 to secure GIC: Switching IRQ 11 to secure GIC: Switching IRQ 58 to secure SERIAL ESC: allocated IRQ 58 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rexported compiled with gcc 4.8.3 for i.MX6 [] Build: #173 Thu Oct 29 11:16:01 CET 2015 Per_cpu_data_alloc: (orig: 0xf0062390-0xf0062d58) KERNEL: Warning: Buddy::alloc: Size mismatch: 9c8 v 1000 Allocate 2504 bytes (2KB) for CPU[4] local storage (offset=1187c70, 0xf11ea000-0xf11ea9c8) GIC: Switching IRQ 29 to secure Number of CPUs: 4 Calibrating timer loop... Per_cpu_data_alloc: (orig: 0xf0062390-0xf0062d58) done. KERNEL: Warning: Buddy::alloc: Size mismatch: 9c8 v 1000 Allocate 2504 bytes (2KB) for CPU[1] local storage (offset=1189c70, 0xf11ec000-0xf11ec9c8) MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 10002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:10000000;10000fff] [0:10073000;1008ffff] [0:10097000;10097fff] [0:1009f000;1013ffff] [4:10140000;10171fff] [0:10172000;10177fff] [4:10178000;10193fff] [0:10194000;110fffff] [4:11100000;119a7fff] [0:119a8000;4effffff] IOMEM:---------------------- [0:0;fffffff] [0:50000000;ffffffff] MOE: Hello world FPU1: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl MGIC: Switching IRQ 29 to secure OCache config: ON EID_PFR[01]: 00001231 00000011: foPer_cpu_data_alloc: (orig: 0xf0062390-0xf0062d58) und ID_[DA]FR0: 00010444 00000000 ID_MMFR[04]: 00100103 20000000 01230000 00102111 1CPU[1]: goes to idle loop 0 KERNEL: Warning: Buddy::alloc: Size mismatch: 9c8 v 1000 2250Allocate 2504 bytes (2KB) for CPU[2] local storage (offset=113fc70, 0xf11a2000-0xf11a29c8) 0 KByte free memory MOE: found RAM from 10000000 to 4f000000 MOE: allocated 1008 KByte for the page array @0x10194000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [11100000-11119474] [C:503000] l4re BOOTFS: [1111a000-1116cc20] [C:504000] ned BOOTFS: [1116d000-1116d35c] [C:505000] l4lx.cfg BOOTFS: [1116e000-112c4470] [C:506000] io BOOTFS: [112c5000-112c517c] [C:507000] arm-imx6.io BOOTFS: [112c6000-116a7498] [C:50800FPU2: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl 0GIC: Switching IRQ 29 to secure ] vmlinCache config: ON Per_cpu_data_alloc: (orig: 0xf0062390-0xf0062d58) uzID_PFR[01]: 00001231 00000011.ar KERNEL: Warning: Buddy::alloc: Size mismatch: 9c8 v 1000 m ID_[DA]FR0: 00010444 00000000 Allocate 2504 bytes (2KB) for CPU[3] local storage (offset=1149c70, 0xf11ac000-0xf11ac9c8) ID_MMFR[04]: 00100103 20000000 01230000 00102111 CPU[2]: goes to idle loop BOOTFS: [116a8000-119a8000] [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' IO | Io service IO | Verboseness level: 4 FPU3: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl IC: Switching IRQ 29 to secure [Cache config: ON 3ID_PFR[01]: 00001231 000000113mIO ID_[DA]FR0: 00010444 00000000 ID_MMFR[04]: 00100103 20000000 01230000 00102111 CPU[3]: goes to idle loop | unused physical memory space: IO | [00000000000000-0000000fffffff] IO | [00000050000000-000000ffffffff] IO | Loading: config 'rom/arm-imx6.io' IO | l4linux: [N12_GLOBAL__N_112Virtual_sbusE] IO | Resources: ==== start ==== IO | Resources: ===== end ===== IO | L4ICU: [N2Vi6Sw_icuE] IO | Resources: ==== start ==== IO | Resources: ===== end ===== IO | imx6q-fec.dev: [N2Vi9Proxy_devE] IO | Resources: ==== start ==== IO | IOMEM [00000002188000-0000000218bfff 4000] non-pref (32bit) (align=3fff flags=2) IO | IRQ [00000000000096-00000000000096 1] none (32bit) (align=0 flags=1) IO | IRQ [00000000000097-00000000000097 1] none (32bit) (align=0 flags=1) IO | Resources: ===== end ===== IO | dmamem: [N2Vi9Proxy_devE] IO | Resources: ==== start ==== IO | IOMEM [00000010430000-000000104affff 80000] non-pref (32bit) (align=7ffff flags=2) IO | Resources: ===== end ===== IO | Real Hardware ----------------------------------- IO | System Bus: hid= IO | Resources: ==== start ==== IO | Resources: ===== end ===== IO | NIC: hid=imx6q-fec.0 IO | Clients: ===== start ==== IO | imx6q-fec.dev: [N2Vi9Proxy_devE] IO | Clients: ===== end ==== IO | Resources: ==== start ==== IO | IOMEM [00000002188000-0000000218bfff 4000] non-pref (32bit) (align=3fff flags=2) IO | IRQ [00000000000096-00000000000096 1] none (32bit) (align=0 flags=1) IO | IRQ [00000000000097-00000000000097 1] none (32bit) (align=0 flags=1) IO | Resources: ===== end ===== IO | DMAMEM: hid=dmamem IO | Clients: ===== start ==== IO | dmamem: [N2Vi9Proxy_devE] IO | Clients: ===== end ==== IO | Resources: ==== start ==== IO | IOMEM [00000010430000-000000104affff 80000] non-pref (32bit) (align=7ffff flags=2) IO | Resources: ===== end ===== IO | warning: could not register control interface at cap 'platform_ctl' IO | Ready. Waiting for request. l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=02486494 l4linux | phys=02000000 ephys=02486494 l4linux | f_sz=003c339c memsz=00486494 flgs=rwx l4linux | L4LINUX: Ma DBG: Virtual Address 02000000 End 02486494 l4linux | Physical Address 02000000 End 02486494 l4linux | PH 1 (t: 4) offs=00373e1c vaddr=0236be1c vend=0236be40 l4linux | phys=0236be1c ephys=0236be40 l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | L4LINUX: Ma DBG: Virtual Address 0236be1c End 0236be40 l4linux | Physical Address 0236be1c End 0236be40 l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | L4LINUX: Ma DBG: Virtual Address 00000000 End 00000000 l4linux | Physical Address 00000000 End 00000000 l4linux | L4LINUX: Ma DBG: Starting binary at 0x2000360, argc=13 argv=0xafff4f74 *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa800075c l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.16.0-l4 (aichouch@aichouch-ThinkCentre-M90) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #41 SMP Thu Oct 29 11:59:28 CET 2015 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (12 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 rw init=/linuxrc earlyprintk=1 showpfexc=1 showghost=1 print-fatal-signals=1 ip=dhp l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 020000a0 - 02600000 [6143 KiB]. l4linux | Areas: Text: 020000a0 - 02396000 [3671kB] (a bit longer) l4linux | Data: 02396000 - 023be4a0 [161kB] l4linux | Initdata: 0236c000 - 02395900 [166kB] l4linux | BSS: 023c339c - 02486494 [780kB] l4linux | Device scan: l4linux | Device: L4ICU l4linux | Device: imx6q-fec.dev l4linux | MEM: 02188000 - 0218bfff l4linux | IRQ: 00000096 - 00000096 l4linux | IRQ: 00000097 - 00000097 l4linux | Device: dmamem l4linux | MEM: 10430000 - 104affff l4linux | Device scan done. l4linux | L4LINUX: Ma DBG: l4lx_thread_create: Created thread 415 (cpu0) (u:b3000e00, v:b3000c00, sp:02397fa4) l4linux | main thread will be 415 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4747264 l4linux | section-with-init: Virt: 0x2000000 to 0x2486493 [4633 KiB] l4linux | section-with-init: Phys: 0x104bb000 to 0x10941493, [4633 KiB] l4linux | Main thread running, waiting... l4linux | Main thread running, waiting... l4linux | stext virt 020000a0, phys 104bb0a0 l4linux | etext virt 02396000, phys 10851000 l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 02000000 l4linux | Main memory: Virt: 0x2600000 to 0x65fffff [65536 KiB] l4linux | Main memory: Phys: 0x11a00000 to 0x159fffff, [65536 KiB] l4linux | l4x: vmalloc area: 06600000 - 0e600000 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4747264 l4linux | text: Virt: 0x2000000 to 0x2486493 [4633 KiB] l4linux | text: Phys: 0x104bb000 to 0x10941493, [4633 KiB] l4linux | Booting Linux on physicl CPU 0x0 Linux version 3.16.0-l (aichouch@aichouch-ThinCentre-M90) (gcc versionm 4.8.3 20140320 (prerelease) (Sourcery CodeBenc Lite 2014.05-29) ) #41 MP Thu Oct 29 11:59:28 CmET 2015 CPU: Fiasco [412fc09a]revision 10 (ARMv7), cr=0000000 CPU: PIPT / VIPT nonalasing data cache, VIPT nnaliasing instruction camche Machine: L4 Ignoring unrecognised ag 0x00000000 bootconsole [earlykdb0 enabled Forcing write-allocatecache policy for SMP Forcing shared mapping for SMP Memory policy: Data cahe writealloc Page fault: addr = bffff003 pc = 0236fb80 (rw, T) l4linux | Forward PF to our pager l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | INITRD: 00002000 - 0030000 l4x_virt_to_phys: Could not translate virt. address 0x2000 l4linux | v2p: 0: v:00000000-00001000 p:00000000-00001000 sz:00001000 l4linux | v2p: 1: v:02000000-02486494 p:104bb000-10941494 sz:00486494 l4linux | v2p: 2: v:02600000-06600000 p:11a00000-15a00000 sz:04000000 l4linux | v2p: 3: v:02000000-02486494 p:104bb000-10941494 sz:00486494 l4linux | ------------[ cut here ------------ WARNING: CPU: 0 PID: 0at /home/aichouch/dev/l4e-snapshot-2014092821/srmc/l4linux/arch/l4/kernel/main.c:392 l4x_virt_tophys+0x7c/0xac() Modules linked in: CPU: 0 PID: 0 Comm: swpper Not tainted 3.16.0-4 #41 [<020109b4>] (unwind_bcktrace) from [<02007684] (show_stack+0x10/0x14)m [<02007684>] (show_stak) from [<0228f2ec>] (dup_stack+0x84/0x94) [<0228f2ec>] (dump_stak) from [<02020f5c>] (wan_slowpath_common+0x6c/0mx88) [<02020f5c>] (warn_slopath_common) from [<0202014>] (warn_slowpath_nulml+0x1c/0x24) [<02021014>] (warn_slopath_null) from [<0200298>] (l4x_virt_to_phys+0xm7c/0xac) [<02002908>] (l4x_virtto_phys) from [<0236ef4c] (l4x_load_initrd+0x208m/0x240) [<0236ef4c>] (l4x_loadinitrd) from [<02370860> (setup_arch+0x89c/0x8d4m) [<02370860>] (setup_arh) from [<0236c5c8>] (strt_kernel+0x8c/0x370) [<0236c5c8>] (start_kenel) from [<00000000>] ( (null)) ---[ end trace 3406ff2bd97382e ]--- l4x_virt_to_phys: Could not translate virt. address 0x302000 l4linux | v2p: 0: v:00000000-00001000 p:00000000-00001000 sz:00001000 l4linux | v2p: 1: v:02000000-02486494 p:104bb000-10941494 sz:00486494 l4linux | v2p: 2: v:02600000-06600000 p:11a00000-15a00000 sz:04000000 l4linux | v2p: 3: v:02000000-02486494 p:104bb000-10941494 sz:00486494 l4linux | ------------[ cut here ------------ WARNING: CPU: 0 PID: 0at /home/aichouch/dev/l4e-snapshot-2014092821/srmc/l4linux/arch/l4/kernel/main.c:392 l4x_virt_tophys+0x7c/0xac() Modules linked in: CPU: 0 PID: 0 Comm: swpper Tainted: G W 3.16.0-l4 #41 [<020109b4>] (unwind_bcktrace) from [<02007684] (show_stack+0x10/0x14)m [<02007684>] (show_stak) from [<0228f2ec>] (dup_stack+0x84/0x94) [<0228f2ec>] (dump_stak) from [<02020f5c>] (wan_slowpath_common+0x6c/0mx88) [<02020f5c>] (warn_slopath_common) from [<0202014>] (warn_slowpath_nulml+0x1c/0x24) [<02021014>] (warn_slopath_null) from [<0200298>] (l4x_virt_to_phys+0xm7c/0xac) [<02002908>] (l4x_virtto_phys) from [<0236ef58] (l4x_load_initrd+0x214m/0x240) [<0236ef58>] (l4x_loadinitrd) from [<02370860> (setup_arch+0x89c/0x8d4m) [<02370860>] (setup_arh) from [<0236c5c8>] (strt_kernel+0x8c/0x370) [<0236c5c8>] (start_kenel) from [<00000000>] ( (null)) ---[ end trace 3406ff2bd97382f ]--- RAMdisk from 00002000 (00002000) to 00302000 (00302000) [3072KiB] l4linux | PERCPU: Embedded 7 page/cpu @06521000 s6400 r812 d14080 u32768 Built 1 zonelists in Zne order, mobility groupng on. Total pages: 177m16 Kernel command line: mm=64M console=ttyLv0 l4xrd=rom/ramdisk-arm.rd romot=1:0 ramdisk_size=4000 rw init=/linuxrc earlyrintk=1 showpfexc=1 showhost=1 print-fatal-signamls=1 ip=dhcp L4LINUX CEA version PID hash table entries 512 (order: -1, 2048 byes) Dentry cache hash tabl entries: 16384 (order: , 65536 bytes) Inode-cache hash tableentries: 8192 (order: 3,32768 bytes) Memory: 64776K/71680K vailable (2739K kernel cde, 161K rwdata, 764K romdata, 166K init, 780K bss, 6904K reserved) Virtual kernel memory ayout: vector : 0xbffff00 - 0xc0000000 ( 4 k) fixmap : 0xffc0000 - 0xffe00000 (2048 k) vmalloc : 0x0660000 - 0x0e600000 ( 128 M) lowmem : 0x0000000 - 0x06600000 ( 102 M) modules : 0x0101000 - 0x02000000 ( 15 M) .text : 0x0200000 - 0x0236be40 (3504 k) .init : 0x0236c00 - 0x02395900 ( 167 k) .data : 0x0239600 - 0x023be4a0 ( 162 k) .bss : 0x023c33c - 0x02486494 ( 781 k) Hierarchical RCU impleentation. l4linux RCU restricting CPUs rom NR_CPUS=4 to nr_cpu_ds=1. RCU: Adjusting geometr for rcu_fanout_leaf=16,nr_cpu_ids=1 NR_IRQS:220 l4timer: Using IRQ210 L4LINUX: Ma DBG: l4lx_thread_create: Created thread 41b (timer0) (u:b3000a00, v:00000000, sp:0241dfa0) l4linux | sched_clock: 64 bits at1000kHz, resolution 1000s, wraps every 214748364m8000ns Console: colour dummy evice 80x30 console [ttyLv0] enabled console [ttyLv0] enabld bootconsole [earlykdb0] disabled bootconsole [earlykdb0 disabled Calibrating delay loop... 1574.50 BogoMIPS (lpj=7872512) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Setting up static identity map for 0x2294850 - 0x2294850 Brought up 1 CPUs SMP: Total of 1 processors activated. CPU: All CPU(s) started in SVC mode. VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations Added static device 'L4ICU' with 0 resources. Added static device 'imx6q-fec.dev' with 3 resources. DMA mem phys at 10430000 - 104affff DMA mem virt at 00302000 - 00381fff pps_core: LinuxPPS API ver. 1 registered pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti < giometti(a)linux.it> PTP clock support registered Switched to clocksource l4kipclk NET: Registered protocol family 2 TCP established hash table entries: 1024 (order: 0, 4096 bytes) TCP bind hash table entries: 1024 (order: 1, 8192 bytes) TCP: Hash tables configured (established 1024 bind 1024) TCP: reno registered UDP hash table entries: 256 (order: 1, 8192 bytes) UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (junk in compressed archive); looks like an initrd INITRD: Freeing memory. l4x: Checks passed. NetWinder Floating Point Emulator V0.97 (double precision) futex hash table entries: 256 (order: 2, 16384 bytes) msgmni has been set to 126 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) L4 serial driver ttyLv0 at MMIO 0x1 (irq = 211, base_baud = 230400) is a L4 l4ser_shm: L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded l4bdds: No name given, not starting. mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 3072KiB [1 disk] into ram disk... done. EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities EXT4-fs (ram0): mounting ext2 file system using the ext4 subsystem EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) VFS: Mounted root (ext2 filesystem) on device 1:0. Freeing unused kernel memory: 164K (0236c000 - 02395000) mount: mounting proc on /proc failed: Device or resource busy mount: mounting devtmpfs on /dev failed: No such device ifconfig: SIOCSIFADDR: No such device Please press Enter to activate this console. #/ - Modification to L4Linux: ------------------------------------------------------------------------------------------------------------------------------- 1- mach_setup.c patch: ------------------------------------------------------------------------------------------------------------------------------- --- /home/aichouch/l4re-snapshot-2014092821/src/l4linux/arch/l4/kernel/arch-arm/mach_setup.c 2014-09-28 21:51:04.000000000 +0200 +++ l4linux/arch/l4/kernel/arch-arm/mach_setup.c 2015-10-28 14:57:04.831851872 +0100 @@ -5,15 +5,84 @@ #include <linux/platform_device.h> #include <linux/ata_platform.h> #include <linux/smsc911x.h> +#include <linux/fec.h> #include <linux/slab.h> #include <linux/list.h> + #include <asm/generic/devs.h> #ifdef CONFIG_L4_DMAPOOL #include <asm/l4x/dma.h> #endif +#define PHY_ID_AR8031 0x004dd074 + +static struct resource imx6q_fec_resources[] = { + { + .start = 0x02188000, + .end = 0x0218BFFF, + .name = "imx6q-fec mem", + .flags = IORESOURCE_MEM + }, + { + .start = 150, + .end = 151, + .name = "imx6q-fec irq", + .flags = IORESOURCE_IRQ + } +}; + +static struct fec_platform_data imx6q_fec_pd = { + .phy = PHY_INTERFACE_MODE_RGMII +}; + +static struct platform_device imx6q_fec_dev = { + .name = "imx6q-fec", + .id = 0, + .resource = imx6q_fec_resources, + .num_resources = ARRAY_SIZE(imx6q_fec_resources), + .dev = { + .platform_data = &imx6q_fec_pd, + }, +}; + +static int ar8031_phy_fixup(struct phy_device *dev) +{ + u16 val; + + /* to enable AR8031 output a 125Mhz clk from CLK_25M */ + phy_write(dev, 0xd, 0x7); + phy_write(dev, 0xe, 0x8016); + phy_write(dev, 0xd, 0x4007); + + val = phy_read(dev, 0xe); + val &= 0xffe3; + val |= 0x18; + phy_write(dev, 0xe, val); + + /* introduce tx clock delay */ + phy_write(dev, 0x1d, 0x5); + val = phy_read(dev, 0x1e); + val |= 0x0100; + phy_write(dev, 0x1e, val); + + return 0; +} + +static void __init imx6q_enet_phy_init(void) +{ + if (IS_BUILTIN(CONFIG_PHYLIB)) { + phy_register_fixup_for_uid(PHY_ID_AR8031, 0xffffffff, ar8031_phy_fixup); + } +} + +static L4X_DEVICE_CB(imx6q_device_cb_fec) +{ + platform_device_register(&imx6q_fec_dev); + imx6q_enet_phy_init(); +} + static int dev_init_done; @@ -238,6 +307,7 @@ l4x_register_platform_device_callback("compactflash", realview_device_cb_pata); l4x_register_platform_device_callback("smsc911x", realview_device_cb_smsc); l4x_register_platform_device_callback("aaci", aaci_cb); + l4x_register_platform_device_callback("imx6q-fec.dev", imx6q_device_cb_fec); #endif } ------------------------------------------------------------------------------------------------------------------------------- 2- fec.h patch: ------------------------------------------------------------------------------------------------------------------------------- --- /home/aichouch/l4re-snapshot-2014092821/src/l4linux/drivers/net/ethernet/freescale/fec.h 2014-09-28 21:51:04.000000000 +0200 +++ l4linux/drivers/net/ethernet/freescale/fec.h 2015-10-28 15:02:26.943851538 +0100 @@ -19,7 +19,7 @@ #if defined(CONFIG_M523x) || defined(CONFIG_M527x) || defined(CONFIG_M528x) || \ defined(CONFIG_M520x) || defined(CONFIG_M532x) || \ - defined(CONFIG_ARCH_MXC) || defined(CONFIG_SOC_IMX28) + defined(CONFIG_ARCH_MXC) || defined(CONFIG_SOC_IMX28) || CONFIG_L4 /* * Just figures, Motorola would have to change the offsets for * registers in the same peripheral device on different models @@ -147,7 +147,7 @@ /* * Define the buffer descriptor structure. */ -#if defined(CONFIG_ARCH_MXC) || defined(CONFIG_SOC_IMX28) +#if defined(CONFIG_ARCH_MXC) || defined(CONFIG_SOC_IMX28) || defined(CONFIG_L4) struct bufdesc { unsigned short cbd_datlen; /* Data length */ unsigned short cbd_sc; /* Control and status info */ ------------------------------------------------------------------------------------------------------------------------------- 3- fec_main.c patch: ------------------------------------------------------------------------------------------------------------------------------- --- /home/aichouch/l4re-snapshot-2014092821/src/l4linux/drivers/net/ethernet/freescale/fec_main.c 2014-09-28 21:51:04.000000000 +0200 +++ l4linux/drivers/net/ethernet/freescale/fec_main.c 2015-10-28 15:04:41.011851399 +0100 @@ -61,6 +61,12 @@ #include "fec.h" +#ifdef CONFIG_L4 +//ahb clock +#define clk_get_rate(x) 132000000 + +#endif + static void set_multicast_list(struct net_device *ndev); #if defined(CONFIG_ARM) @@ -2535,12 +2541,22 @@ fep->phy_interface = ret; } +#ifdef CONFIG_L4 + //Do not setup Clocks or regulator + fep->clk_ahb = NULL; + fep->clk_ipg = NULL; + fep->clk_enet_out = NULL; + fep->clk_ptp = NULL; + fep->reg_phy = NULL; +#else + fep->clk_ipg = devm_clk_get(&pdev->dev, "ipg"); if (IS_ERR(fep->clk_ipg)) { ret = PTR_ERR(fep->clk_ipg); goto failed_clk; } + fep->clk_ahb = devm_clk_get(&pdev->dev, "ahb"); if (IS_ERR(fep->clk_ahb)) { ret = PTR_ERR(fep->clk_ahb); @@ -2576,6 +2592,8 @@ fep->reg_phy = NULL; } +#endif + fec_reset_phy(pdev); if (fep->bufdesc_ex) ------------------------------------------------------------------------------------------------------------------------------- 4- fec_ptp.c patch: ------------------------------------------------------------------------------------------------------------------------------- --- /home/aichouch/l4re-snapshot-2014092821/src/l4linux/drivers/net/ethernet/freescale/fec_ptp.c 2014-09-28 21:51:04.000000000 +0200 +++ l4linux/drivers/net/ethernet/freescale/fec_ptp.c 2015-10-28 14:39:23.863852973 +0100 @@ -48,6 +48,9 @@ #include "fec.h" +//ahb clock +#define clk_get_rate(x) 132000000 + /* FEC 1588 register bits */ #define FEC_T_CTRL_SLAVE 0x00002000 #define FEC_T_CTRL_CAPTURE 0x00000800 ------------------------------------------------------------------------------------------------------------------------------- 5- Freescale Kconfig patch: ------------------------------------------------------------------------------------------------------------------------------- --- /home/aichouch/l4re-snapshot-2014092821/src/l4linux/drivers/net/ethernet/freescale/Kconfig 2014-09-28 21:51:04.000000000 +0200 +++ l4linux/drivers/net/ethernet/freescale/Kconfig 2015-10-28 14:34:45.955853261 +0100 @@ -7,7 +7,7 @@ default y depends on FSL_SOC || QUICC_ENGINE || CPM1 || CPM2 || PPC_MPC512x || \ M523x || M527x || M5272 || M528x || M520x || M532x || \ - ARCH_MXC || ARCH_MXS || (PPC_MPC52xx && PPC_BESTCOMM) + ARCH_MXC || ARCH_MXS || (PPC_MPC52xx && PPC_BESTCOMM) || L4 ---help--- If you have a network (Ethernet) card belonging to this class, say Y and read the Ethernet-HOWTO, available from @@ -23,7 +23,7 @@ config FEC tristate "FEC ethernet controller (of ColdFire and some i.MX CPUs)" depends on (M523x || M527x || M5272 || M528x || M520x || M532x || \ - ARCH_MXC || SOC_IMX28) + ARCH_MXC || SOC_IMX28) || L4 default ARCH_MXC || SOC_IMX28 if ARM select PHYLIB select PTP_1588_CLOCK ------------------------------------------------------------------------------------------------------------------------------- 6- L4Linux KConfig patch: ------------------------------------------------------------------------------------------------------------------------------- --- /home/aichouch/l4re-snapshot-2014092821/src/l4linux/arch/l4/Kconfig 2014-09-28 21:51:04.000000000 +0200 +++ l4linux/arch/l4/Kconfig 2015-10-28 14:39:21.515852975 +0100 @@ -63,16 +63,21 @@ config L4_PLATFORM_GENERIC bool "Generic" select CLKDEV_LOOKUP - select L4_CLK_NOOP + select HAVE_CLK_PREPARE + select HAVE_MACH_CLKDEV + select COMMON_CLK config L4_PLATFORM_REALVIEW bool "Realview" select CLKDEV_LOOKUP select OUTER_CACHE - select L4_CLK_NOOP + endchoice +config L4_CLK_NOOP + bool "L4 Clock Noop" + depends on (L4_PLATFORM_GENERIC || L4_PLATFORM_REALVIEW) menu "Features" - Note that the L4_CLK_NOOP option should be disabled otherwise a link error occurs when compiling L4Linux. ------------------------------------------------------------------------------------------------------------------------------- 7- arm-imx6.io file: ------------------------------------------------------------------------------------------------------------------------------- hw-root { NIC => new Device() { .hid = "imx6q-fec.0"; new-res Mmio(0x02188000 .. 0x0218BFFF); new-res Irq(150); new-res Irq(151); } DMAMEM => new Device() { .hid = "dmamem"; new-res Mmio_ram(0x80000, 0); } } l4linux => new System_bus() { #NIC => wrap(hw-root.NIC); "imx6q-fec.dev" => wrap(hw-root.NIC); "dmamem" => wrap(hw-root.DMAMEM); } ------------------------------------------------------------------------------------------------------------------------------- 8- l4lx.cfg file: ------------------------------------------------------------------------------------------------------------------------------- -- vim:set ft=lua: loader = L4.default_loader; vbus_l4linux = loader:new_channel(); local lxname = "vmlinuz"; if L4.Info.arch() == "arm" then lxname = "vmlinuz.arm"; end loader:start( { caps = { sigma0 = L4.cast(L4.Proto.Factory, L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; l4linux = vbus_l4linux:svr(); }, log = { "IO", "y" }, l4re_dbg = L4.Dbg.Warn, }, "rom/io -vvv rom/arm-imx6.io"); L4.default_loader:start( { caps = { vbus = vbus_l4linux; log = L4.Env.log:m("rws"), }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, }, "rom/" .. lxname .. " mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 ramdisk_size=4000 rw init=/linuxrc earlyprintk=1 showpfexc=1 showghost=1 print-fatal-signals=1 ip=dhc\ p");

2 1

Sharing one ethernet network device between two L4Linux instances
by Mahdi Aichouch 27 Oct '15

27 Oct '15

Hello, I was able to run two L4linux instances on top of L4 Fiasco OC using a Qemu emulator of a versatile express-a9 board . I would like to make these two instances share one ethernet network device. I would like also to switch between the two L4Linux shell, because in Qemu only one shell is accessible. I followed this guide[1] to connect two L4Linux instances using "l4shmnet", and this thread [2] to get access to the shell when testing on Qemu. However, the "l4shmnet" is not working correctly, both L4Linux display this message: shmns: Requesting, Shmsize 1024 Kbytes shmns: Failed to establish communication Could someone help me building such a working configuration. Is it possible to share a working Qemu command with the right option for the network? This is my Qemu command $> qemu-system-arm -cpu cortex-a9 -M vexpress-a9 -smp 1 -no-reboot -m 1024M -kernel bin/arm_armv7a/bootstrap_L4Linux_ARM.elf -nographic -net nic,model=lan9118 -net user Is it also possible to share a working lua configuration file? This is my lua l4lx.cfg file: -- vim:set ft=lua: local lxname = "vmlinuz"; if L4.Info.arch() == "arm" then lxname = "vmlinuz.arm"; end local shmns = L4.default_loader:create_namespace({ shm = "placeholder" }); L4.default_loader:start( { { ldr_flags = L4.Ldr_flags.eager_map }, caps = { log = L4.Env.log:m("rws"), }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, shmns = shmns:mode("rw"), }, "rom/" .. lxname .. " earlyprintk=1 showpfexc=1 showghost=1 mem=64M l4shmnet.add=shmns,macpart=1,create console=ttyLv0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 ramdisk_size=32768 init=/li\ nuxrc print-fatal-signals=1"); L4.default_loader:start( { { ldr_flags = L4.Ldr_flags.eager_map }, caps = { log = L4.Env.log:m("rws"), }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux2", "green" }, shmns = shmns:mode("rw"), }, "rom/" .. lxname .. " earlyprintk=1 showpfexc=1 showghost=1 mem=64M l4shmnet.add=shmns,macpart=2 console=ttyLv0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 ramdisk_size=32768 init=/linuxrc p\ rint-fatal-signals=1"); Thank you very much in advance. Best regards, Mahdi [1] http://wiki.tudos.org/L4Linux/shmnet [2] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2013/005775.html

3 5

Application on top of L4re
by Yuxin Ren 27 Oct '15

27 Oct '15

Hi, Are there any relative complex and non-trivial applications on top of Fiasco and l4Re? If so, where can I get the source code? Thanks a lot. Yuxin

3 4

make clean (really!)
by ba_f 12 Oct '15

12 Oct '15

Hello, i try to build the newest snapshot while still having an old one on the disk. Unfortunately, 'make setup' crashes when looking for Cross Tools. Anyway, i don't think it has something to do with the new snapshot, but some hidden setup files storing my old config. Because, when i rename my old snapshot and then try to rebuild it, it crashes as well. So, how do i make the setup really clean? 'make clean' seems not enough, since it still knows some old configs. Where are those hidden files, and how to remove them? Thanks.

2 6

Re: make uimage error
by Shabnam Engineer 05 Oct '15

05 Oct '15

Hi Adam,I built l4linux successfully and again I got this error : ******************************************************************************---> my command : make uimage E="L4Linux ARM" MODULE_SEARCH_PATH=/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/kernel/fiasco/mybuild/ O=/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/ ---> the message : make[1]: Entering directory `/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4' Could not find 'vmlinuz.arm' with path '/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/kernel/fiasco/mybuild/:/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/bin/arm_armv7a:/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/bin/arm_armv7a/l4f:/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/lib/arm_armv7a:/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/lib/arm_armv7a/l4f' Processing of /home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/conf/modules.list failed! make[3]: *** No rule to make target `mod.make.inc', needed by `bootstrap.ld'. Stop. make[2]: *** [/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/pkg/bootstrap/server/src/OBJ-arm_armv7a] Error 2 make[1]: *** [uimage] Error 2 make[1]: Leaving directory `/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4' make: *** [uimage] Error 2 ******************************************************************************thank you for your considering my question.Regards, Shabnam On Monday, September 14, 2015 2:44 AM, Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> wrote: hi, On Sat Sep 12, 2015 at 19:45:44 +0000, Shabnam Engineer wrote: > Hi Adam ,Thanks a lot for helping me.Your solution is ok but now I get this error : > ************************************************************************* > Could not find 'l4lx.cfg' with path '/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/kernel/fiasco/mybuild/:/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/bin/arm_armv7a:/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/bin/arm_armv7a/l4f:/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/lib/arm_armv7a:/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/lib/arm_armv7a/l4f' > > Processing of /home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/conf/modules.list failed! > > make[2]: *** No rule to make target `mod.make.inc', needed by `bootstrap.ld'. Stop. > make[1]: *** [/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/pkg/bootstrap/server/src/OBJ-arm_armv7a] Error 2 > make: *** [uimage] Error 2**************************************************************and the l4lx.cfg file is in src/l4/conf/examples path and when I copied it to the one of the pathes that said in the above, I then got this error for another file like "vmlinuz.arm" that this file does not exist in any folder. > thank you for considering my questio.Regards, Shabnam vmlinuz.arm is the binary of L4Linux. Did you build L4Linux? By the way, the paths can be configured in src/l4/conf/Makeconf.boot Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

2 3

Error when building L4RE
by Mahdi Aichouch 29 Sep '15

29 Sep '15

Hello, I tried to build L4 Fiasco O.C + L4RE on Ubuntu 14.04 LTS x86_64 host, but I get the following error: Checking for needed programs and tools make ... ok gcc ... ok g++ ... ok ld ... ok gawk ... ok perl ... ok pkg-config ... ok Checking for needed cross programs and tools arm-linux-gcc ... ok arm-linux-cpp ... ok arm-linux-nm ... ok arm-linux-g++ ... ok arm-linux-ld ... ok Checking optional programs and tools doxygen ... NOT DETECTED but optional Some optional command is missing on your system, don't worry. doxygen Creating build directories... make[1]: Entering directory `/home/mahdi/OS/l4re-core-2014092821/src/kernel/fiasco' Creating build directory "../../../obj/fiasco/arm-mp-rv-a9-vexpress"... done. make[1]: Leaving directory `/home/mahdi/OS/l4re-core-2014092821/src/kernel/fiasco' make[1]: Entering directory `/home/mahdi/OS/l4re-core-2014092821/obj/fiasco/arm-mp-rv-a9-vexpress' make -C /home/mahdi/OS/l4re-core-2014092821/src/kernel/fiasco/src/../tool/kconfig O=/home/mahdi/OS/l4re-core-2014092821/obj/fiasco/arm-mp-rv-a9-vexpress Kconfig=Kconfig KCONFIG_AUTOHEADER=globalconfig.h KCONFIG_TRISTATE=include/config/tristate.conf KCONFIG_CONFIG=globalconfig.out KCONFIG_AUTOCONFIG=include/config/auto.conf KERNELVERSION=SVN MENUCONFIG_COLOR=blackbg INCLUDE_PPC32= INCLUDE_SPARC= fiasco_srcdir=/home/mahdi/OS/l4re-core-2014092821/src/kernel/fiasco/src/.. olddefconfig make[2]: Entering directory `/home/mahdi/OS/l4re-core-2014092821/src/kernel/fiasco/tool/kconfig' make[1]: Entering directory `/home/mahdi/OS/l4re-core-2014092821/obj/fiasco/arm-mp-rv-a9-vexpress' HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/zconf.lex.c SHIPPED scripts/kconfig/zconf.hash.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf scripts/kconfig/conf --olddefconfig Kconfig # # configuration written to globalconfig.out # make[2]: Leaving directory `/home/mahdi/OS/l4re-core-2014092821/src/kernel/fiasco/tool/kconfig' make[1]: Leaving directory `/home/mahdi/OS/l4re-core-2014092821/obj/fiasco/arm-mp-rv-a9-vexpress' make[1]: Entering directory `/home/mahdi/OS/l4re-core-2014092821/src/l4' All build tools checked ok. Creating build directory "../../obj/l4/arm-ca"... make[2]: Entering directory `/home/mahdi/OS/l4re-core-2014092821/src/l4' make[1]: Entering directory `/home/mahdi/OS/l4re-core-2014092821/obj/l4/arm-ca' HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/zconf.lex.c SHIPPED scripts/kconfig/zconf.hash.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf scripts/kconfig/conf --oldconfig /home/mahdi/OS/l4re-core-2014092821/obj/l4/arm-ca/Kconfig.generated # # configuration written to .kconfig # scripts/kconfig/conf --silentoldconfig /home/mahdi/OS/l4re-core-2014092821/obj/l4/arm-ca/Kconfig.generated All build tools checked ok. gcc -fPIC -Wall -pedantic -g -m64 -c /home/mahdi/OS/l4re-core-2014092821/src/l4/tool/gendep/deptrack.c -o /home/mahdi/OS/l4re-core-2014092821/obj/l4/arm-ca/tool/gendep/deptrack.64.o gcc -fPIC -Wall -pedantic -g -m64 -c /home/mahdi/OS/l4re-core-2014092821/src/l4/tool/gendep/syscall.c -o /home/mahdi/OS/l4re-core-2014092821/obj/l4/arm-ca/tool/gendep/syscall.64.o mkdir -p /home/mahdi/OS/l4re-core-2014092821/obj/l4/arm-ca/tool/gendep/64 gcc -m64 -shared -Wl,--no-as-needed -Wl,-soname,/home/mahdi/OS/l4re-core-2014092821/obj/l4/arm-ca/tool/gendep/64/libgendep.so -ldl -o /home/mahdi/OS/l4re-core-2014092821/obj/l4/arm-ca/tool/gendep/64/libgendep.so /home/mahdi/OS/l4re-core-2014092821/obj/l4/arm-ca/tool/gendep/deptrack.64.o /home/mahdi/OS/l4re-core-2014092821/obj/l4/arm-ca/tool/gendep/syscall.64.o ERROR: ld.so: object 'libgendep.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored. ERROR: ld.so: object 'libgendep.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored. ERROR: ld.so: object 'libgendep.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored. make[6]: *** [Makeconf.bid.local-internal-names] Error 1 make[5]: *** [Makeconf.bid.local-helper] Error 2 make[4]: *** [DROPSCONF_CONFIG_MK_POST_HOOK] Error 1 make[3]: *** [/home/mahdi/OS/l4re-core-2014092821/obj/l4/arm-ca/.config.all] Error 2 make[2]: *** [oldconfig] Error 2 make[2]: Leaving directory `/home/mahdi/OS/l4re-core-2014092821/src/l4' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/mahdi/OS/l4re-core-2014092821/src/l4' make: *** [setup] Error 1 Does someone have an idea of how to resolve this. Thank you very much in advance. Best regards, Mahdi

2 1

l4linux building error
by Shabnam Engineer 21 Sep '15

21 Sep '15

Hi l4-hackersIn bulding l4linux , I got an error :************************************************************the command : make O=/tmp/buildpath L4ARCH=arm CROSS_COMPILE=arm-linux- the error : make[1]: Entering directory `/tmp/buildpath' Package libio-io was not found in the pkg-config search path. Perhaps you should add the directory containing `libio-io.pc' to the PKG_CONFIG_PATH environment variable Package 'libio-io', required by 'libio', not found Getting required compilation flags failed. L4OBJ: /home/shabnam/Desktop/l4re-core-2014092821/src/l4/builddir/ L4_REQUIRED_MODS: libc_be_minimal_log_io libc_minimal libc_minimal_l4re libsupc++_minimal log l4re_c-util libio libvcpu shmc /home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4linux/arch/l4/Makefile:361: *** Aborting.. Stop. make: *** [sub-make] Error 2 *************************************************************thank you for considering my questionRegards, Shabnam

2 1

make uimage error
by Shabnam Engineer 14 Sep '15

14 Sep '15

Hi L4hackersI successfully build both Fiasco.OC and l4re but when I want to make image file I get this error : ****************************************************************** ---> my command : ~/Desktop/snapshot/l4re-snapshot-2014092821/src/l4$ make uimage E=hello MODULE_SEARCH_PATH=./../kernel/fiasco/mybuild/ O=./builddir/ ----> the message : =========== Updating RAM_BASE for platform rpi_b to 0x0 ========= ... Regenerating RAM_BASE settings ... Building Makefile.inc ==> Linking sigma0 ==> "sigma0" built ==> Installing sigma0 to local build-tree ... Building Makefile.inc ==> Linking moe ==> "moe" built ==> Installing moe to local build-tree Could not find 'fiasco' with path './../kernel/fiasco/mybuild/:/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/bin/arm_armv7a:/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/bin/arm_armv7a/l4f:/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/lib/arm_armv7a:/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/lib/arm_armv7a/l4f' ... Building Dependencies ... Building Makefile.inc Processing of /home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/conf/modules.list failed! Could not find 'fiasco' with path './../kernel/fiasco/mybuild/:/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/bin/arm_armv7a:/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/bin/arm_armv7a/l4f:/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/lib/arm_armv7a:/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/lib/arm_armv7a/l4f' Processing of /home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/conf/modules.list failed! make[2]: *** No rule to make target `mod.make.inc', needed by `bootstrap.ld'. Stop. make[1]: *** [/home/shabnam/Desktop/snapshot/l4re-snapshot-2014092821/src/l4/builddir/pkg/bootstrap/server/src/OBJ-arm_armv7a] Error 2 make: *** [uimage] Error 2 ****************************************************************** but the fiasco file exists in ./../kernel/fiasco/mybuild path.thank you for considering my question.regards, Shabnam

3 7

make error
by Shabnam Engineer 31 Aug '15

31 Aug '15

Hi l4-hackers,I want to build fiasco.OC for my rpi , but in "make" command I have faced this error : ******************************************make: arm-linux-g++: Command not found /bin/sh: 1: arm-linux-g++: not found /bin/sh: 1: arm-linux-g++: not found make: arm-linux-g++: Command not found make srcdir=/home/shabnam/Desktop/fiasco1/l4re-core-2014092821/src/kernel/fiasco/src objbase=/home/shabnam/Desktop/fiasco1/l4re-core-2014092821/src/kernel/fiasco/mybuild -f /home/shabnam/Desktop/fiasco1/l4re-core-2014092821/src/kernel/fiasco/src/Makefile.sub1 make[1]: arm-linux-g++: Command not found make[1]: Entering directory `/home/shabnam/Desktop/fiasco1/l4re-core-2014092821/src/kernel/fiasco/mybuild' /bin/sh: 1: arm-linux-g++: not found /bin/sh: 1: arm-linux-g++: not found make[1]: arm-linux-g++: Command not found Checking compiler config... unchanged. /bin/sh: 1: arm-linux-ld: not found No known ld emulation found make[1]: *** [.Host-config] Error 1 make[1]: Leaving directory `/home/shabnam/Desktop/fiasco1/l4re-core-2014092821/src/kernel/fiasco/mybuild' make: *** [create-sources] Error 2 ******************************************************************************************and also in /bin/sh route we have the arm-linux-g++ file , and I attach the screenshots of this route .I don't know what to do .thank you for considering my question . regards, shabnam

2 3

Question about JDB in Fiasco
by yang.wei9＠zte.com.cn 30 Aug '15

30 Aug '15

Hi, Adam I have some questions about JDB in Fiasco. 1). Is there any latest manual about JDB? I can only find <Fiasco Kernel Debugger Manual>( http://os.inf.tu-dresden.de/fiasco/doc/jdb.pdf) which is written in 2008. This manual does not conform to the current fiasco version(l4re-snapshot-2014092821)。 2). Does JDB support bt(dump backtrace)? There are some descriptions about "bt" command in <Fiasco Kernel Debugger Manual>. But I can not find it in current version. Does older version fiasco support it? 3). How can I get the older version fiasco code？ Best Regards， Albin -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

2 1

Re: l4-hackers Digest, Vol 148, Issue 3
by Raja Sekhar 24 Aug '15

24 Aug '15

Thanks for your kid reply. I've done changes according to you suggestions. But still getting same issue.... Thanks, Sekhar On Wed, Aug 5, 2015 at 3:30 PM, <l4-hackers-request(a)os.inf.tu-dresden.de> wrote: > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. Re: L4Re: unhandled exception while building Fiasco.OC-L4Re > for ARM platform (Adam Lackorzynski) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 4 Aug 2015 21:35:09 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: Re: L4Re: unhandled exception while building Fiasco.OC-L4Re > for ARM platform > Message-ID: <20150804193509.GB4565(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > Hi, > > On Mon Aug 03, 2015 at 12:33:05 +0530, Raja Sekhar wrote: > > I'm getting unhandled exception while running clntsrv example > > > > > > I've build Fiasco-L4Re system with the following specifications > > *Fiasco.OC:* > > Architecture (ARM processor family) > > Platform (ARM RealView Platform) > > Realview Platform (PBX) > > Start of RAM (physical address) (0x00000000) > > CPU (ARM Cortex-A9 CPU) > > *L4Re:* > > Target Architecture (ARM architecture) > > CPU variant (ARMv4 type CPU) > > Could you switch to ARMv7 here as this is the corresponding version for > a Cortex-A9. > > > Platform Selection (ARM Realview PBX) > > > > and *trying to run examples/clntsrv* by adding the following entry in > > module.list > > > > entry clntsrv > > bootstrap bootstrap -serial > > kernel fiasco -serial_esc > > roottask moe rom/clntsrv.cfg > > module clntsrv.cfg > > module l4re > > module ned > > module ex_clntsrv-server > > module ex_clntsrv-client > > > > Creating image: > > > > make elfimage E=clntsrv > > MODULE_SEARCH_PATH=`pwd`/../Fiasco.OC:`pwd`/source/pkg/examples/clntsrv > > > > Running image on QEMU: > > > > qemu-system-arm -M realview-pbx-a9 --kernel images/bootstrap_clntsrv > > -m 256M -serial /dev/pts/4 > > > > L4 Bootstrapper > > Build: #56 Thu Jul 30 23:21:33 IST 2015, 4.7.3 20130226 (prerelease) > > Scanning up to 256 MB RAM > > Memory size is 256MB (00000000 - 0fffffff) > > RAM: 0000000000000000 - 000000000fffffff: 262144kB > > Total RAM: 256MB > > mod07: 0113d000-011565bc: ex_clntsrv-client > > mod06: 01123000-0113c5c0: ex_clntsrv-server > > mod05: 010d0000-01122bf4: ned > > mod04: 010b6000-010cf49c: l4re > > mod03: 010b5000-010b52a6: clntsrv.cfg > > mod02: 01083000-010b4668: moe > > mod01: 01079000-01082380: sigma0 > > mod00: 01015000-01078770: fiasco > > Moving up to 8 modules behind 1100000 > > moving module 00 { 1015000-107876f } -> { 1242000-12a576f } [407408] > > moving module 01 { 1079000-108237f } -> { 12a6000-12af37f } [37760] > > moving module 02 { 1083000-10b4667 } -> { 12b0000-12e1667 } [202344] > > moving module 03 { 10b5000-10b52a5 } -> { 1157000-11572a5 } [678] > > moving module 04 { 10b6000-10cf49b } -> { 1158000-117149b } [103580] > > moving module 05 { 10d0000-1122bf3 } -> { 1172000-11c4bf3 } [338932] > > moving module 06 { 1123000-113c5bf } -> { 1100000-11195bf } [103872] > > moving module 07 { 113d000-11565bb } -> { 111a000-11335bb } [103868] > > moving module 03 { 1157000-11572a5 } -> { 1134000-11342a5 } [678] > > moving module 04 { 1158000-117149b } -> { 1135000-114e49b } [103580] > > moving module 05 { 1172000-11c4bf3 } -> { 114f000-11a1bf3 } [338932] > > Scanning fiasco -serial_esc > > Scanning sigma0 > > Scanning moe rom/clntsrv.cfg > > Relocated mbi to [0x100e000-0x100e140] > > Loading fiasco > > Loading sigma0 > > Loading moe > > find kernel info page... > > found kernel info page at 0x2000 > > Regions of list 'regions' > > [ 1000, 1abf] { ac0} Kern fiasco > > [ 2000, 72fff] { 71000} Kern fiasco > > [ 90000, 9643b] { 643c} Sigma0 sigma0 > > [ 98000, 9e17b] { 617c} Sigma0 sigma0 > > [ 140000, 16becb] { 2becc} Root moe > > [ 170000, 186f0f] { 16f10} Root moe > > [ 1000000, 10143f7] { 143f8} Boot bootstrap > > [ 100e000, 100e23d] { 23e} Root Multiboot info > > [ 1100000, 11a1bf3] { a1bf4} Root Module > > API Version: (87) experimental > > Sigma0 config ip:00090100 sp:01013de4 > > Roottask config ip:001401fc sp:00000000 > > Starting kernel fiasco at 000012b4 > > Realview System ID: Rev=0 HBI=178 Build=0 Arch=5 FPGA=00 > > Hello from Startup::stage2 > > Per_cpu_data_alloc: (orig: 0xf00605e8-0xf0060f68) > > Number of IRQs available at this GIC: 96 > > Cache config: ON > > ID_PFR[01]: 00001031 00000001 ID_[DA]FR0: 00000000 00000000 > > ID_MMFR[04]: 00100103 20000000 01230000 00002111 > > L2: ID=410000c8 Type=1c100100 Aux=30520000 WMask=ff S=0 > > L2: Type L2C-310 Size = 128kB > > SERIAL ESC: allocated IRQ 44 for serial uart > > Not using serial hack in slow timer handler. > > Welcome to Fiasco.OC (arm)! > > L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden > > Rev: rexported compiled with gcc 4.7.3 for Realview [] > > Build: #4 Tue Jul 28 22:46:31 IST 2015 > > > > Per_cpu_data_alloc: (orig: 0xf00605e8-0xf0060f68) > > Allocate 2432 bytes (2KB) for CPU[4] local storage (offset=1187a18, > > 0xf11e8000-0xf11e8980) > > Number of CPUs: 1 > > Calibrating timer loop... done. > > SIGMA0: Hello! > > KIP @ 2000 > > allocated 4KB for maintenance structures > > SIGMA0: Dump of all resource maps > > RAM:------------------------ > > [0:0;fff] > > [0:73000;8ffff] > > [0:97000;97fff] > > [0:9f000;13ffff] > > [4:140000;16bfff] > > [0:16c000;16ffff] > > [4:170000;186fff] > > [0:187000;100dfff] > > [4:100e000;100efff] > > [0:100f000;10fffff] > > [4:1100000;11a1fff] > > [0:11a2000;effffff] > > IOMEM:---------------------- > > [0:10000000;ffffffff] > > MOE: Hello world > > MOE: found 244324 KByte free memory > > MOE: found RAM from 73000 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: [1134000-11342a6] [C:503000] clntsrv.cfg > > BOOTFS: [1135000-114e49c] [C:504000] l4re > > BOOTFS: [114f000-11a1bf4] [C:505000] ned > > BOOTFS: [1100000-11195c0] [C:506000] ex_clntsrv-server > > BOOTFS: [111a000-11335bc] [C:507000] ex_clntsrv-client > > MOE: cmdline: moe rom/clntsrv.cfg > > MOE: Starting: rom/ned rom/clntsrv.cfg > > MOE: loading 'rom/ned' > > Ned says: Hi World! > > ****I am in luaK_prefix()**** > > L4Re: unhandled exception: pc=0x1021984 > > > > I have gone through the code flow for "ned" and I found that the > > exception is raising while loading ned.lua script, > > At certain point luaK_prefix() is trying to call codearith() but > > failed to call codearith(). > > both the function are located at l4re/pkg/lua/lib/contrib/src/lcode.c > > > > I'm able to get print statement which I placed before calling the > > codearith() in luaK_prefix(), > > But not printing the statement which I placed inside the codearith() > > > > Can you please get me out from this issue. > > Please check whether this persists after recompiling for ARMv7. > If not, I'd like to know which instruction/code is at 0x1021984. > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > > ------------------------------ > > End of l4-hackers Digest, Vol 148, Issue 3 > ****************************************** > -- *Thanks & Regards* Raja Sekhar Reddy. B

2 1

Re: Solution of the previous thread "Running L4Linux + Fiasco on Freescale i.MX 6 Sabre SD"
by Le Guan 17 Aug '15

17 Aug '15

Hello Adam, Thanks for your reply and I'm sorry for the ambiguity of my description. In fact, I have followed that thread and have solved many problems until the last step. ( http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007551.html). You guessed that it was the problem of the ramdisk, which I downloaded at http://os.inf.tu-dresden.de/download/ramdisk-arm.rd . After that, you and Mahdi no longer posted messages in this mailing list at this subject. So, I want to know how you address this problem. The output of the execution now appears like this: >* RAMDISK: ext2 filesystem found at block 0 *>* RAMDISK: Loading 3072KiB [1 disk] into ram disk... done. *>* EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities *>* EXT4-fs (ram0): mounting ext2 file system using the ext4 subsystem *>* EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) *>* VFS: Mounted root (ext2 filesystem) readonly on device 1:0. *>* Freeing unused kernel memory: 116K (02312000 - 0232f000) *>* potentially unexpected fatal signal 4. *> >* CPU: 0 PID: 1 Comm: sh Not tainted 3.16.0-l4 #3 *>* task: 05c23ac0 ti: 05c26000 task.ti: 05c26000 *>* PC is at 0xc4c0 *>* LR is at 0x0 *>* pc : [<0000c4c0>] lr : [<00000000>] psr: 00000010 *>* sp : bfa42ef0 ip : 00000000 fp : 00000000 *>* r10: 00000000 r9 : 00000000 r8 : 00000000 *>* r7 : 00000000 r6 : 00000000 r5 : 00000000 r4 : 00000000 *>* r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : 00000000 *>* vcpu: b3000c00 vcpu-state: 00000001 *>* Flags: nzcv IRQs on FIQs on Mode USER_32 ISA ARM Segment user *>* CPU: 0 PID: 1 Comm: sh Not tainted 3.16.0-l4 #3 *>* [<02000>] (unwind_backtrace) from [<02005924>] (show_stack+0x10/0x14) *>* [<02005924>] (show_stack) from [<02028c50>] *>* (get_signal_to_deliver+0x240/0x4cc) *>* [<02028c50>] (get_signal_to_deliver) from [<02006fb4>] *>* (do_signal+0x118/0x464) *>* [<02006fb4>] (do_signal) from [<020073a0>] (do_work_pending+0xa0/0xe8) *>* [<020073a0>] (do_work_pending) from [<02008d50>] *>* (l4x_pre_iret_work.isra.31.part.32+0x60/0x104) *>* [<02008d50>] (l4x_pre_iret_work.isra.31.part.32) from [<02009e38>] *>* (l4x_vcpu_entry_c+0x274/0x1ddc) *>* [<02009e38>] (l4x_vcpu_entry_c) from [<00000000>] ( (null)) *>* Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 *> >* CPU: 0 PID: 1 Comm: sh Not tainted 3.16.0-l4 #3 *>* [<02000>] (unwind_backtrace) from [<02005924>] (show_stack+0x10/0x14) *>* [<02005924>] (show_stack) from [<022486c0>] (panic+0x8c/0x1dc) *>* [<022486c0>] (panic) from [<0201e0b0>] (complete_and_exit+0x0/0x1c) *>* [<0201e0b0>] (complete_and_exit) from [<00000001>] (0x1) *>* ---[ end Kernel panic - not syncing: Attempted to kill init! *>* exitcode=0x00000004 *> >* panic: going to sleep forever, bye *>* panic: going to sleep forever, bye* Thanks a lot for your help! Regards, Le Guan Date: Fri, 14 Aug 2015 00:00:09 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: Re: Solution of the previous thread "Running L4Linux + Fiasco > on Freescale i.MX 6 Sabre SD" > Message-ID: <20150813220009.GA4552(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > On Thu Aug 13, 2015 at 10:43:33 -0400, Le Guan wrote: > > Hi l4-hackers, > > > > Greetings! I encountered exactly the same problem as Mahdi's. His > original > > thread can be found at > > http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007491.html. > > AS Mahdi and Adam communicated using private email later, I don't know if > > the problem has been solved. If it has been solved, can anybody give me > > some hint on it? > > When 'swp' is trapping then it's not enabled in the CPU. You can do so by > enabling it in Fiasco's config. > Alternative: Why is 'swp' used at all on an ARMv7 architecture as the > imx6? Did you compile L4Linux for ARMv7? > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ >

2 3

using math lua module
by AVK 16 Aug '15

16 Aug '15

Quick question, How can i use the math module in lua ? I see that it is there in the contrib folder of lua pkg so it should be built hopefully. Whenever i require("math") in lua, i get an error like Ned: ERROR: rom/json.lua:32: module 'math' not found: no field package.preload['math'] no file 'rom/math.lua' no file './math.so' no file '/usr/local/lib/lua/5.1/math.so' no file '/usr/local/lib/lua/5.1/loadall.so' -- --- Avinash Kundaliya avinash(a)avinash.com.np http://avinash.com.np

2 1

Solution of the previous thread "Running L4Linux + Fiasco on Freescale i.MX 6 Sabre SD"
by Le Guan 14 Aug '15

14 Aug '15

Hi l4-hackers, Greetings! I encountered exactly the same problem as Mahdi's. His original thread can be found at http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007491.html. AS Mahdi and Adam communicated using private email later, I don't know if the problem has been solved. If it has been solved, can anybody give me some hint on it? Many thanks! Regards, Le Guan

2 1

Re: porting linux driver in Fiasco.OC
by Shabnam Engineer 10 Aug '15

10 Aug '15

Hi thanks for your answersI want to implement Fiasco.OC on a board and test some RTOS beside other non realtime OS .. at first I want to be sure that if I need a driver for our special tests and the Fiasco.OC does not support that, Could I choose it from linux drivers and port it to Fiasco.OC microkernel?does someone do this work?thanks for your considering my question.regards, shabnam On Saturday, August 8, 2015 10:39 AM, Shabnam Engineer <shabnam.engineer72(a)yahoo.com> wrote: Hi thanks for your answerI want to implement Fiasco.OC on a board and test some RTOS beside other non realtime OS .. at first I want to be sure that if I need a driver for our special tests and the Fiasco.OC does not support that, Could I choose it from linux drivers and port it to Fiasco.OC microkernel?does someone do this work?thanks for your considering my question.regards, shabnam On Thursday, July 30, 2015 5:53 PM, Jorge Alberto Garcia <jorge.garcia.gonzalez(a)gmail.com> wrote: Hi!This is very interesting!, is there any resource about what needs to be done for a user space component handling hw ?Thanks! On Thu, Jul 30, 2015 at 1:51 AM, Matthias Lange <matthias.lange(a)kernkonzept.com> wrote: Hi, On 07/29/2015 12:29 PM, Shabnam Engineer wrote: > hi > I have a question about porting linux drivers in Fiasco.OC. > Can I port linux drivers into Fiasco.OC ? In a microkernel system device drivers are implemented as isolated user space components. No devices drivers, except from selected very low level devices like timer and interrupt controller, are implemented in the kernel. Matthias. -- Matthias Lange, matthias.lange(a)kernkonzept.com, +49 - 351 - 41 88 86 14 Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129. Geschäftsführer: Dr.-Ing. Michael Hohmuth _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

3 3

L4Linux interface to convert physical address to machine address
by Olujide Adeola 06 Aug '15

06 Aug '15

Hi guys, Apologies if this question has already been answered elsewhere on this mailing list. We are porting our driver to L4Linux but having issues with the page_to_phys() Linux function, what's the L4Linux API to map a VM physical address to a machine address which can be programmed into the DMA registers of a peripheral device on the system bus. Note on terminology, (virtual address <-> physical address <-> machine address). Regards,Olujide

2 1

L4Re: unhandled exception while building Fiasco.OC-L4Re for ARM platform
by Raja Sekhar 04 Aug '15

04 Aug '15

Hello L4-Hackers, I'm getting unhandled exception while running clntsrv example I've build Fiasco-L4Re system with the following specifications *Fiasco.OC:* Architecture (ARM processor family) Platform (ARM RealView Platform) Realview Platform (PBX) Start of RAM (physical address) (0x00000000) CPU (ARM Cortex-A9 CPU) *L4Re:* Target Architecture (ARM architecture) CPU variant (ARMv4 type CPU) Platform Selection (ARM Realview PBX) and *trying to run examples/clntsrv* by adding the following entry in module.list entry clntsrv bootstrap bootstrap -serial kernel fiasco -serial_esc roottask moe rom/clntsrv.cfg module clntsrv.cfg module l4re module ned module ex_clntsrv-server module ex_clntsrv-client Creating image: make elfimage E=clntsrv MODULE_SEARCH_PATH=`pwd`/../Fiasco.OC:`pwd`/source/pkg/examples/clntsrv Running image on QEMU: qemu-system-arm -M realview-pbx-a9 --kernel images/bootstrap_clntsrv -m 256M -serial /dev/pts/4 L4 Bootstrapper Build: #56 Thu Jul 30 23:21:33 IST 2015, 4.7.3 20130226 (prerelease) Scanning up to 256 MB RAM Memory size is 256MB (00000000 - 0fffffff) RAM: 0000000000000000 - 000000000fffffff: 262144kB Total RAM: 256MB mod07: 0113d000-011565bc: ex_clntsrv-client mod06: 01123000-0113c5c0: ex_clntsrv-server mod05: 010d0000-01122bf4: ned mod04: 010b6000-010cf49c: l4re mod03: 010b5000-010b52a6: clntsrv.cfg mod02: 01083000-010b4668: moe mod01: 01079000-01082380: sigma0 mod00: 01015000-01078770: fiasco Moving up to 8 modules behind 1100000 moving module 00 { 1015000-107876f } -> { 1242000-12a576f } [407408] moving module 01 { 1079000-108237f } -> { 12a6000-12af37f } [37760] moving module 02 { 1083000-10b4667 } -> { 12b0000-12e1667 } [202344] moving module 03 { 10b5000-10b52a5 } -> { 1157000-11572a5 } [678] moving module 04 { 10b6000-10cf49b } -> { 1158000-117149b } [103580] moving module 05 { 10d0000-1122bf3 } -> { 1172000-11c4bf3 } [338932] moving module 06 { 1123000-113c5bf } -> { 1100000-11195bf } [103872] moving module 07 { 113d000-11565bb } -> { 111a000-11335bb } [103868] moving module 03 { 1157000-11572a5 } -> { 1134000-11342a5 } [678] moving module 04 { 1158000-117149b } -> { 1135000-114e49b } [103580] moving module 05 { 1172000-11c4bf3 } -> { 114f000-11a1bf3 } [338932] Scanning fiasco -serial_esc Scanning sigma0 Scanning moe rom/clntsrv.cfg Relocated mbi to [0x100e000-0x100e140] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list 'regions' [ 1000, 1abf] { ac0} Kern fiasco [ 2000, 72fff] { 71000} Kern fiasco [ 90000, 9643b] { 643c} Sigma0 sigma0 [ 98000, 9e17b] { 617c} Sigma0 sigma0 [ 140000, 16becb] { 2becc} Root moe [ 170000, 186f0f] { 16f10} Root moe [ 1000000, 10143f7] { 143f8} Boot bootstrap [ 100e000, 100e23d] { 23e} Root Multiboot info [ 1100000, 11a1bf3] { a1bf4} Root Module API Version: (87) experimental Sigma0 config ip:00090100 sp:01013de4 Roottask config ip:001401fc sp:00000000 Starting kernel fiasco at 000012b4 Realview System ID: Rev=0 HBI=178 Build=0 Arch=5 FPGA=00 Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf00605e8-0xf0060f68) Number of IRQs available at this GIC: 96 Cache config: ON ID_PFR[01]: 00001031 00000001 ID_[DA]FR0: 00000000 00000000 ID_MMFR[04]: 00100103 20000000 01230000 00002111 L2: ID=410000c8 Type=1c100100 Aux=30520000 WMask=ff S=0 L2: Type L2C-310 Size = 128kB SERIAL ESC: allocated IRQ 44 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rexported compiled with gcc 4.7.3 for Realview [] Build: #4 Tue Jul 28 22:46:31 IST 2015 Per_cpu_data_alloc: (orig: 0xf00605e8-0xf0060f68) Allocate 2432 bytes (2KB) for CPU[4] local storage (offset=1187a18, 0xf11e8000-0xf11e8980) Number of CPUs: 1 Calibrating timer loop... done. SIGMA0: Hello! KIP @ 2000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:0;fff] [0:73000;8ffff] [0:97000;97fff] [0:9f000;13ffff] [4:140000;16bfff] [0:16c000;16ffff] [4:170000;186fff] [0:187000;100dfff] [4:100e000;100efff] [0:100f000;10fffff] [4:1100000;11a1fff] [0:11a2000;effffff] IOMEM:---------------------- [0:10000000;ffffffff] MOE: Hello world MOE: found 244324 KByte free memory MOE: found RAM from 73000 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: [1134000-11342a6] [C:503000] clntsrv.cfg BOOTFS: [1135000-114e49c] [C:504000] l4re BOOTFS: [114f000-11a1bf4] [C:505000] ned BOOTFS: [1100000-11195c0] [C:506000] ex_clntsrv-server BOOTFS: [111a000-11335bc] [C:507000] ex_clntsrv-client MOE: cmdline: moe rom/clntsrv.cfg MOE: Starting: rom/ned rom/clntsrv.cfg MOE: loading 'rom/ned' Ned says: Hi World! ****I am in luaK_prefix()**** L4Re: unhandled exception: pc=0x1021984 I have gone through the code flow for "ned" and I found that the exception is raising while loading ned.lua script, At certain point luaK_prefix() is trying to call codearith() but failed to call codearith(). both the function are located at l4re/pkg/lua/lib/contrib/src/lcode.c I'm able to get print statement which I placed before calling the codearith() in luaK_prefix(), But not printing the statement which I placed inside the codearith() Can you please get me out from this issue. Thanks, Rajasekhar

2 1

issues in creating an elf binary
by AVK 31 Jul '15

31 Jul '15

Hello, I am trying to create an elf binary for the hello package (to start with) and when i run the `make elfimage` command, it fails with the following error make[3]: *** No rule to make target `mod.make.inc', needed by `bootstrap.ld'. Stop. While i am trying to look into the issue, maybe there is a quick fix for this, or someone has come across this issue already. Or maybe there is a better/easier way to create an elfimage. Regards, Avinash Kundaliya avinash(a)avinash.com.np http://avinash.com.np

2 3

porting linux driver in Fiasco.OC
by Shabnam Engineer 30 Jul '15

30 Jul '15

hi I have a question about porting linux drivers in Fiasco.OC.Can I port linux drivers into Fiasco.OC ? if so , which drivers?all of drivers?thank you for considering my question.regards,shabnam

4 3

Fiasco.OC device driver
by Shabnam Engineer 22 Jul '15

22 Jul '15

Hi ,is fiasco.oc like other L4 family about supporting driver of devices ? does Fiasco run device drivers as normal user-mode application? thanks for your considering my question regards,shabnam

2 1

issues in building l4re
by AVK 20 Jul '15

20 Jul '15

Hello community, I have been trying to build l4re and have the following issue. I am building l4re snapshot with some other modules not included in the package. The issue is when i am building moe, and it has not been changed and is the one that is included in the package. I am building it on a virtualbox running xubuntu 15.04 (in case it helps to find the issue or could be the problem). I am not sure how to move ahead with this problem and am curious if anyone has ideas or pointers to look for/at. /obj/l4/x86/include/l4/re/error_helper:64:26: error: ‘L4_UNLIKELY’ was not declared in this scope if (L4_UNLIKELY(err < 0)) ^ /home/avk/Thesis/l4re-snapshot-2014092821/obj/l4/x86/include/l4/re/error_helper: In function ‘long int L4Re::chksys(const l4_msgtag_t&, const char*, l4_utcb_t*, long int)’: /home/avk/Thesis/l4re-snapshot-2014092821/obj/l4/x86/include/l4/re/error_helper:86:32: error: ‘L4_UNLIKELY’ was not declared in this scope if (L4_UNLIKELY(t.has_error())) ^ /home/avk/Thesis/l4re-snapshot-2014092821/src/l4/mk/binary.inc:818: recipe for target 'main.o' failed The build output can be seen here : http://pastebin.com/Xuu0eKAY -- --- Avinash Kundaliya avinash(a)avinash.com.np http://avinash.com.np

2 3

Adding more functionality on top of L4Linux
by Thotheolh Tay 19 Jul '15

19 Jul '15

Hi, Are there any guides which I can add the following features onto L4Linux ? - GCC, Make, CCID, PCSC If the features do not exist in L4Linux, how do I build my own L4Linux image with these features and what do I need to modify to ensure they work properly on L4Linux ? -- +---------------------------------------------------------+ | PGP Secure Email Key ID:6FBFC19D | +---------------------------------------------------------+

2 3

Some questions about L4 operating system
by Qing Wei 16 Jul '15

16 Jul '15

Hi, I am a beginner to L4, and very interested in it. I think it is great in terms of its minimality and security. However, I have some questions about it, (1) How is its performance compared to other monolithic kernel, say, Linux. Could it make use of multicore, multiprocessor to enjoy the performance scalability? (2) How is its ecosystem, fox example, how to support new hardware, does it need write the driver from scratch or could it make use of Linux driver? And how to write application on it, or, could it run Linux application without modification? (3) How is its virtualization support, could it run Linux vm, and does it need any modification to the guest os? Cheers, Qing Wei

3 3

Problem in final step
by Vlad Sof 16 Jul '15

16 Jul '15

Hi guys, So, I'm having a problem with the final step in booting and running the Fiasco.OC.I've gone through the building steps on L4Re -- The L4 Runtime Environment | | | | | | | | | L4Re -- The L4 Runtime EnvironmentThe L4 Runtime Environment: informations and more | | | | View on os.inf.tu-dresden.de | Preview by Yahoo | | | | | and The Fiasco microkernel - Building and Using | | | | | | | | | | | The Fiasco microkernel - Building and UsingThe Fiasco microkernel: prerequisites, compilation, booting | | | | View on os.inf.tu-dresden.de | Preview by Yahoo | | | | | When I try "make grub2iso E=hello MODULE_SEARCH_PATH=~/projects/src/kernel/fiasco/mybuild" I get the following error: make[1]: Entering Directory `/home/johng/projects/src/l4'Processing entry 'hello'Could not find 'bootstrap' with path '/home/johng/projects/src/kernel/fiasco/mybuild:/home/johng/projects/src/l4/mybuild/bin/x86_586:/home/johng/projects/src/l4/mybuild/bin/x86_586/l4f:/home/johng/projects/src/l4/mybuild/lib/x86_586:/home/johng/projects/src/l4/mybuild/lib/x86_586/l4f'make[1]: *** [grub2iso] Error 1make[1]: Leaving directory `/home/johng/projects/src/l4'make: *** [grub2iso] Error 2 A brief explanation: I'm running Ubuntu 14.04.1 as a virtualmachine guest on a Mac OSX host.I've configured l4re with : Target Architecture: x86-32 architecture CPU variant: 586 type CPUPlatform Selection: PC On the fiasco kernel configuration I just saved it without changing any of the settings. I've been trying to get this work for the past week and I don't know where I'm going wrong. I've followed all the steps up to this point, but for some reason this last step just wont work. Please help !

2 1

how does Fiasco achieve C++ support
by Yuxin Ren 07 Jul '15

07 Jul '15

HI, My big question is how Fiasco can support C++? I think in order to build Fiasco, we need some kind of c++ cross-compiler (in this case, it is gcc), this is because we build Fiasco and its applications on Linux. But on the other hand, I did not see any special configuration or modification of gcc when I build Fiasco. I want to know how Fiasco is build without a cross-compiler. In particular, I know gcc uses some its internal libraries to support exception handing, threads/locking and STL in C++. And those libraries may include libgcc, libstdc++. But I also do not find that hose libraries are ported to Fiasco. Without poring those libraries, how to support C++ in Fiasco? As those libraries may use some lock mechanisms like mutex and C library functions like malloc, I cannot understand how Fiasco provides such support (locks, C library) to those libraries. Thank you very for any help and explanation. Yuxin

2 9

TrustZone example on i.MX6
by Markku Ahvenjärvi 07 Jul '15

07 Jul '15

Hello hackers, I'm trying to run Fiasco.OC in secure world and Linux in non-secure world on i.MX6Q. For this I'm using the TrustZone example (pkg/examples/sys/vm-tz). To secure world I have given 128MB RAM starting from 0x10000000 and I modified the example to give NS world 256MB starting from 0x20000000. I've replaced atags with dtb of my board and it is copied to NS side like kernel and initrd. At first I encountered runtime exception, which I fixed by implementing following to arm_em_tz builds Thread::arch_ext_vcpu_enabled() { return true; } Now I'm having problems at early stages of NS boot, where Linux kernel is checking for the dtb magic. The code loads the dtb magic from the address I'm giving in r2 register (0x21000000), but the magic value usually have one byte or all of them incorrect. I've used JDB to dump the area of dtb after hitting that error and it shows the dtb magic properly. So for some reason the NS-world gets mangled value. Any idea what might be causing this? Thanks, Markku

5 29

Fwd: Running L4Linux + Fiasco on Freescale i.MX 6 Sabre SD
by Mahdi Aichouch 06 Jul '15

06 Jul '15

Hello, Thank you very much Mattias for you help. Now L4Linux goes further but it stops after mounting the root filesystem. Do you have an idea of what might be wrong. Thank you in advance. Best regards, Mahdi L4 Bootstrapper Build: #81 Thu May 28 10:36:41 CEST 2015, 4.8.3 20140320 (prerelease) Scanning up to 256 MB RAM, starting at offset 32MB Memory size is 256MB (10000000 - 1fffffff) RAM: 0000000010000000 - 000000001fffffff: 262144kB Total RAM: 256MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 10 modules behind 11100000 moving module 02 { 118aa000-118e363f } -> { 1199a000-119d363f } [235072] moving module 01 { 118a0000-118a938b } -> { 11990000-1199938b } [37772] moving module 00 { 11848000-1189fb17 } -> { 11938000-1198fb17 } [359192] moving module 09 { 11548000-11847fff } -> { 11638000-11937fff } [3145728] moving module 08 { 111d6000-11547497 } -> { 112c6000-11637497 } [3609752] moving module 07 { 111d5000-111d50bc } -> { 112c5000-112c50bc } [189] moving module 06 { 1107e000-111d446f } -> { 1116e000-112c446f } [1401968] moving module 05 { 1107d000-1107d17b } -> { 1116d000-1116d17b } [380] moving module 04 { 1102a000-1107cc1f } -> { 1111a000-1116cc1f } [338976] moving module 03 { 11010000-11029473 } -> { 11100000-11119473 } [103540] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x10002000 Regions of list 'regions' [ 10000000, 1000015f] { 160} Root mbi_rt [ 10001000, 10001aff] { b00} Kern fiasco [ 10002000, 10066fff] { 65000} Kern fiasco [ 10090000, 10096edf] { 6ee0} Sigma0 sigma0 [ 10098000, 1009e177] { 6178} Sigma0 sigma0 [ 10140000, 10171d77] { 31d78} Root moe [ 10178000, 101934ab] { 1b4ac} Root moe [ 11000000, 1100f58f] { f590} Boot bootstrap [ 11100000, 11937fff] { 838000} Root Module API Version: (87) experimental Sigma0 config ip:10090100 sp:00000000 Roottask config ip:10140260 sp:00000000 Starting kernel fiasco at 100012c8 Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl L2: ID=410000c7 Type=9e340340 Aux=02070000 WMask=ffff S=0 L2: Type L2C-310 Size = 1024kB Ways=16 Waysize=64 GIC: Switching IRQ 58 to secure SERIAL ESC: allocated IRQ 58 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rexported compiled with gcc 4.8.3 for i.MX6 [] Build: #15 Thu May 28 10:35:21 CEST 2015 GIC: Switching IRQ 29 to secure Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 10002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:10000000;10000fff] [0:10067000;1008ffff] [0:10097000;10097fff] [0:1009f000;1013ffff] [4:10140000;10171fff] [0:10172000;10177fff] [4:10178000;10193fff] [0:10194000;110fffff] [4:11100000;11937fff] [0:11938000;1effffff] IOMEM:---------------------- [0:0;fffffff] [0:20000000;ffffffff] MOE: Hello world MOE: found 236564 KByte free memory MOE: found RAM from 10000000 to 1f000000 MOE: allocated 240 KByte for the page array @0x1009f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [11100000-11119474] [C:503000] l4re BOOTFS: [1111a000-1116cc20] [C:504000] ned BOOTFS: [1116d000-1116d17c] [C:505000] l4lx.cfg BOOTFS: [1116e000-112c4470] [C:506000] io BOOTFS: [112c5000-112c50bd] [C:507000] arm-rv.io BOOTFS: [112c6000-11637498] [C:508000] vmlinuz.arm BOOTFS: [11638000-11938000] [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' l4linux | libio: Warning: Query of 'vbus' failed! l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=023defa8 l4linux | phys=02000000 ephys=023defa8 l4linux | f_sz=00359394 memsz=003defa8 flgs=rwx l4linux | PH 1 (t: 4) offs=0031afe0 vaddr=02312fe0 vend=02313004 l4linux | phys=02312fe0 ephys=02313004 l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x20002b0, argc=6 argv=0xafff4f8c *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa8000788 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.16.0-l4 (aichouch@aichouch-ThinkCentre-M90) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #1 Wed May 27 18:04:14 CEST 2015 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (5 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 02000000 - 02400000 [4096 KiB]. l4linux | Areas: Text: 02000000 - 02332000 [3272kB] (a bit longer) l4linux | Data: 02332000 - 023543a0 [136kB] l4linux | Initdata: 02314000 - 02331024 [116kB] l4linux | BSS: 02359394 - 023defa8 [535kB] l4linux | Device scan: l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:02333fa4) l4linux | main thread will be 413 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4059136 l4linux | section-with-init: Virt: 0x2000000 to 0x23defa7 [3963 KiB] l4linux | section-with-init: Phys: 0x1025a000 to 0x10638fa7, [3963 KiB] l4linux | Main thread running, waiting... l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 02000000 l4linux | Main memory: Virt: 0x2400000 to 0x63fffff [65536 KiB] l4linux | Main memory: Phys: 0x11a00000 to 0x159fffff, [65536 KiB] l4linux | l4x: vmalloc area: 06400000 - 0e400000 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4059136 l4linux | text: Virt: 0x2000000 to 0x23defa7 [3963 KiB] l4linux | text: Phys: 0x1025a000 to 0x10638fa7, [3963 KiB] l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] l4linux | l4lx_thread_create: Created thread 418 (timer0) (u:b3000a00, v:00000000, sp:02377fa0) Booting Linux on physical CPU 0x0 Linux version 3.16.0-l4 (aichouch@aichouch-ThinkCentre-M90) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #1 Wed May 27 18:04:14 CEST 2015 CPU: Fiasco [412fc09a] revision 10 (ARMv7), cr=00000000 CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: L4 Ignoring unrecognised tag 0x00000000 Memory policy: Data cache uncached INITRD: 00002000 - 00302000 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 17209 Kernel command line: mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 64808K/69636K available (2460K kernel code, 136K rwdata, 688K rodata, 116K init, 535K bss, 4828K reserved) Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xffe00000 (2048 kB) vmalloc : 0x06400000 - 0x0e400000 ( 128 MB) lowmem : 0x00000000 - 0x06400000 ( 100 MB) modules : Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xffe00000 (2048 kB) vmalloc : 0x06400000 - 0x0e400000 ( 128 MB) lowmem : 0x00000000 - 0x06400000 ( 100 MB) moNR_IRQS:220 l4timer: Using IRQ210 sched_clock: 64 bits at 1000kHz, resolution 1000ns, wraps every 2147483648000ns Console: colour dummy device 80x30 console [ttyLv0] enabled Calibrating delay loop... 1574.50 BogoMIPS (lpj=7872512) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok Setting up static identity map for 0x22509d8 - 0x22509d8 VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations Failed to create "l4x" debugfs directory: 1 Switched to clocksource l4kipclk NET: Registered protocol family 2 TCP established hash table entries: 1024 (order: 0, 4096 bytes) TCP bind hash table entries: 1024 (order: 0, 4096 bytes) TCP: Hash tables configured (established 1024 bind 1024) TCP: reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (junk in compressed archive); looks like an initrd INITRD: Freeing memory. l4x: Checks passed. NetWinder Floating Point Emulator V0.97 (double precision) futex hash table entries: 256 (order: -1, 3072 bytes) msgmni has been set to 126 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) L4 serial driver ttyLv0 at MMIO 0x1 (irq = 211, base_baud = 230400) is a L4 l4ser_shm: L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded l4bdds: No name given, not starting. mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 3072KiB [1 disk] into ram disk... done. EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities EXT4-fs (ram0): mounting ext2 file system using the ext4 subsystem EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) VFS: Mounted root (ext2 filesystem) readonly on device 1:0. Freeing unused kernel memory: 116K (02314000 - 02331000) Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b CPU: 0 PID: 1 Comm: init Not tainted 3.16.0-l4 #1 [<0200cc68>] (unwind_backtrace) from [<020057e4>] (show_stack+0x10/0x14) [<020057e4>] (show_stack) from [<0224ad50>] (panic+0x7c/0x1d0) [<0224ad50>] (panic) from [<0201dcdc>] (do_exit+0x7b8/0x7f0) [<0201dcdc>] (do_exit) from [<0201e858>] (do_group_exit+0x40/0xa0) [<0201e858>] (do_group_exit) from [<02028700>] (get_signal_to_deliver+0x148/0x4b4) [<02028700>] (get_signal_to_deliver) from [<02006e1c>] (do_signal+0x118/0x454) [<02006e1c>] (do_signal) from [<0200a4d4>] (l4x_vcpu_entry_c+0xa74/0x1dd4) [<0200a4d4>] (l4x_vcpu_entry_c) from [<0000c548>] (0xc548) ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye On Thu, May 28, 2015 at 8:23 AM, Matthias Lange < matthias.lange(a)kernkonzept.com> wrote: > Hi, > > On 05/27/2015 06:43 PM, Mahdi Aichouch wrote: > > Hello, > > > > I tried to run L4Linux + Fiasco on a Freescale i.mx <http://i.mx> 6 > > Sabre SD board. > > > > The L4Linux is started but it stops at loading the ramdisk, as shown in > > the debug messages below. > > > > Does someone has an idea of what might be wrong. > > > > Thank you very much in advance. > > > > Best regards, > > > > Mahdi > > > > [...] > > > l4linux | l4x_register_pointer_section: addr = 02000000 size = 4059136 > > l4linux | text: Virt: 0x2000000 to 0x23defa7 [3963 KiB] > > l4linux | text: Phys: 0x1025a000 to 0x10638fa7, [3963 KiB] > > l4linux | Loading: rom/ramdisk-arm.rd > > l4linux | INITRD: Size of RAMdisk is 3072KiB > > l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] > > l4linux | 'swp(b)' instruction at 0224f728 and faulting. > > Have you enabled CONFIG_ARM_ENABLE_SWP in your Fiasco config? > > Matthias. > > > -- > Matthias Lange, matthias.lange(a)kernkonzept.com, +49 - 351 - 41 88 86 14 > > Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129. > Geschäftsführer: Dr.-Ing. Michael Hohmuth > >

3 12

Difficulty Booting L4RE on Raspberry Pi
by Robert Lowe 30 Jun '15

30 Jun '15

Hello, I've done some research and have been trying to get L4RE + Fiasco.OC to boot on my raspberry pi. I've managed to get the bootable image onto the PI, but the boot halts just after the kernel is loaded. I've tried different compiler toolchains, both linaro(which I hear there are issues with) and genode. Unfortunately I was unable to acquire the sourcery toolchain. In every case, it halts at the same point. Here is a serial dump: L4 Bootstrapper Build: #3 Sat Jun 27 23:26:20 EDT 2015, 4.7.1 20120402 (prerelease) Scanning up to 512 MB RAM, starting at offset 32MB Memory size is 512MB (00000000 - 1fffffff) RAM: 0000000000000000 - 000000001fffffff: 524288kB Total RAM: 512MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 5 modules behind 1100000 moving module 02 { 10a0000-10d163f } -> { 1191000-11c263f } [202304] moving module 01 { 1096000-109f357 } -> { 1187000-1190357 } [37720] moving module 00 { 1043000-1095ae7 } -> { 1134000-1186ae7 } [338664] moving module 04 { 1029000-1042597 } -> { 111a000-1133597 } [103832] moving module 03 { 100f000-1028473 } -> { 1100000-1119473 } [103540] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list 'regions' [ 1000, 19bf] { 9c0} Kern fiasco [ 2000, 62fff] { 61000} Kern fiasco [ 63000, 630e3] { e4} Root mbi_rt [ 90000, 966bb] { 66bc} Sigma0 sigma0 [ 98000, 9e177] { 6178} Sigma0 sigma0 [ 140000, 16daaf] { 2dab0} Root moe [ 170000, 186f13] { 16f14} Root moe [ 1000000, 100e4ff] { e500} Boot bootstrap [ 1100000, 1133fff] { 34000} Root Module API Version: (87) experimental Sigma0 config ip:00090100 sp:00000000 Roottask config ip:00140264 sp:00000000 Starting kernel fiasco at 000011a8 Hello from Startup::stage2 Attached is my kernel config, if it is of any help. Thanks for any assistance Robert Lowe

2 1

Open source development
by teclis High Elf 26 Jun '15

26 Jun '15

Hi, This is more just a general comment, but compared to other open source project I have contributed to Fiasco L4Re is difficult to work with. In most GNU open source projects new features and improvements are discussed actively on a mailing list and/or IRC channel so its easy to follow what is being done and jump in. While I very much appreciate that developers have taken the time to answer my questions, the l4-hackers mailing list seems to be just Q and A there is no discussion on what is currently being worked on for Fiasco and L4Re as there is in the Linux kernel or drivers. Also the svn logs just have generic import messages like: r67 | l4check | 2015-01-12 16:57:36 -0500 (Mon, 12 Jan 2015) | 1 line So it looks like all the core development is being done privately and then exported to a public repository. This makes it difficult in my opinion to build an open source development community. You can't look back through the svn logs messages and diffs to see the evolution of the system and get up to speed on the state of the art. For example, who is the committer? How would I go about submitting a patch for L4Re or Fiasco?

2 1

Re: Testing Fiasco.OC+L4re on ODROID-X2(Exynos4412)
by Reinier Millo Sánchez 25 Jun '15

25 Jun '15

Hi Adam and L4 community I've been testing somethings on the Odroid-X2(Exynos4412). It seems that the IRQ handler only handles the first IRQ and disables the IRQs. I have added the following code to check the IRQs in the function Kernel_thread::bootstrap() in the file src/kernel/fiasco/src/kern/kernel_thread.cpp Per_cpu_data::run_late_ctors(Cpu::invalid()); bootstrap_arch(); Timer_tick::enable(current_cpu()); Proc::sti(); ++ Proc::Status st = Proc::interrupts(); ++ if(st & Proc::Status_interrupts_disabled) ++ printf("IRQs are enabled\n"); ++ else ++ printf("IRQs are disabled\n"); Watchdog::enable(); I'm trying to check that the IRQs are enabled. The Proc::sti() must activate the IRQs in the CPSR registers, and Proc::interrupts() must return if the interrupts are enabled, but always i'm getting "IRQs are disabled". I have tested the hardware with a Linux kernel and it's working fine. I have tested "CPSIE i" and "CPSIE f" to enable the interrupts and get the same result. I have incremented the warn level on Fiasco.OC, i'm getting: KERNEL: Warning Buddy:alloc Size mismatch: a80 v 1000 I have also tested the local timers on the Exynos4412. The local timer at CPU0 is working fine. It has been configured to auto-reload with 12000 as interval. The local counter decrements the value and reload when arrives zero, but don't raises the interrupt. To test the interrupts have created an small buffer to store the Kip::k()->clock on every interrupt. I have used the buffer to avoid the call of an interrupt inside another interrupt. I have tried to print the values on the function Delay::mesaure(), but it only stores one value. The same thing happens if I use a interrupt counter. Now i'm trying to check the IRQ handler caller, from the general mechanism to the specific interrupt handler, to catch the point where the IRQs are been disabled. Anyone have any suggestions? Best regards -- Lic. Reinier Millo Sánchez Centro de Estudios de Informática Universidad Central "Marta Abreu" de Las Villas Carretera a Camajuaní Km 5 1/2 Santa Clara, Villa Clara, Cuba CP 54830 "antes de discutir ... respira; antes de hablar ... escucha; antes de escribir ... piensa; antes de herir ... siente; antes de rendirte ... intenta; antes de morir ... vive"

2 7

question about libgcc, libspuc++ in the l4re
by Yuxin Ren 25 Jun '15

25 Jun '15

Hi, I find in the src/l4/pkg directory, there are some libraries -- libgcc, libstdc++-v3, and libsupc++. But in those libraries, I just found very little source code. Instead, they include many makefiles. Where is the source code of those libraries? And why are there those makefiles? Thanks a lot. Yuxin

2 1

why fiasco use -fno-rtti compile option?
by liu.xiaodong2＠zte.com.cn 25 Jun '15

25 Jun '15

Hi, Guys! I want to use typeid() and dynamic_cast() in fiasco, but failed, because of the -fno-rtti option. Why fiasco disable rtti? Are there some bad effects if we enable it? thanks! -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

3 3

Debugging Fiasco OC + L4Re + L4Linux together
by Mahdi Aichouch 09 Jun '15

09 Jun '15

Hello, I tried to debug Fiasco OC + L4Re + L4Linux using a DS-5 IDE and a DSTREAM JTAG on an i.MX 6 device. I was able to do a step-by-step through the source code of L4RE until I reach the " *virtual* *void* boot_kernel(unsigned long entry) " function in support.h (see screenshot 1) which is the function in L4Re that enters the Fiasco kernel, from there when I execute a "step into" action in order to execute the next instruction which is in Fiasco kernel the debugger go into "running" mode (see screenshot 2). I am unable to do a step-by-step walk neither in the Fiasco kernel nor in l4linux source code. Stopping the debugger after that do only give a disassembly information. Is it possible to debug all the Fiasco OC + L4Re + L4Linux together? Are there any debugger configurations that I might be missing? Many thanks in advance. Best regards, Mahdi

2 1

Thread monitoring
by Biermans Joeri 09 Jun '15

09 Jun '15

Hey everyone, Is there a way available to perform some thread monitoring? Like for instance get some information about on which CPU a thread is running, when they're suspended, completed, etc. Thanks in advance and kind regards, Joeri

2 1

Using a second Ethernet connector in L4Linux
by Mahdi Aichouch 03 Jun '15

03 Jun '15

Hello, I have a Freescale i.MX 6 Sabre SD board. It is equipped with one Ethernet RJ45 connector. I need to add a second Ethernet RJ45 connector to the board. The board has a micro-USB OTG port that allow to connect a plugable USB OTG Micro-B to Ethernet adapter like for instance this one: http://plugable.com/products/usb2-otge100 I would like to know if L4Linux might access such a second Ethernet device connected through micro-USB. Does anyone has tried this before. Could someone points me to a tutorial or a guide that shows what are the configurations steps that I should follow to build up a working test case. Thank you very much in advance. Best regards, Mahdi

2 1

Cann't access git://git.l4android.org/build_script.git
by 刘海剑 02 Jun '15

02 Jun '15

When I run this command, git clone git://git.l4android.org/build_script.git, I got some error info: fatal: unable to connect to l4android.org: l4android.org[0: 141.76.48.99]: errno=Connection refused Thanks.

2 1

Implementing a few real time scheduling algorithms on Fiasco.OC
by Biermans Joeri 30 May '15

30 May '15

Hi everyone, I'm a student at the university of Antwerp and I'm currently working on my master's thesis. My project is about comparing the performance of a few global multicore scheduling algorithms (G-RM, G-EDF, ...) on an embedded system. A part of my thesis is to make an implementation on a real embedded system equipped with a quadcore processor (i.MX6). To do that I need an RTOS. Fiasco with the l4re at a first sight seems an interesting candidate. To test the performance of the above algorithms I will schedule a bunch of randomly generated tasksets comprising some periodic tasks having implicit deadlines* with each of the algorithms and try to detect if any deadlines are missed. * Such a task is executed repeatedly after a fixed amount of time and its deadline is equal to its period, which is the point of time when the next invocation of the task takes place. This brings me to my first question: Would this be achievable with the fiasco kernel? I've been trying to interpret the project of the fiasco kernel during the last days, but this seems easier said than done. As a first step I've been trying to figure out how the scheduler works and how exactly the scheduling policies are implemented. (I have read somewhere the current scheduling policy is fixed priority round robin) Is there perhaps a more documented version of the code or an overview of the different classes, their functions and the way they interact available? It's really hard to figure out a bunch of code without any leads on how exactly the project has been implemented. Besides that I don't really have a clue about how to start developing on the fiasco kernel. Some tips about how to start working on the kernel are always welcome. Has anyone got experience with developing on the fiasco kernel? It would be nice to get some directions on this matter because I'm quite stuck on this. Thanks in advance! Kind regards, Joeri

3 2

Booting error of L4Linux enabled SMP surpport
by Xiefeng (Stephen) 29 May '15

29 May '15

Hi all, I use entry L4Linux-mag-x86 in modules.list to start a L4Linux on L4Re successfully. The codes is l4re-snapshot-2014092821. L4Linux use x86-native_deconfig complie, use l4lx-gfx.cfg to start L4Linux. This config is just set one cpu for L4Linux. If I set l4x_cpus=2 in l4lx-gfx.cfg, use x86-mp_vPCI_defconfig and set CONFIG_NR_CPUS=2 to compile the L4Linux, when I start L4Linux, a kernel panic happened: l4linux | Loading: rom/ramdisk-x86.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 88d70000 to 89070000 [3072KiB] l4linux | rtc not found l4linux | l4lx_thread_create: Created thread 41f (timer0) (u:b3000a00, v:00000000, sp:008e1fa8) l4linux | WARNING: Unknown wrmsr: 0000008b at 0x414bad l4linux | WARNING: Unknown rdmsr: 00000186 at 0x85e1d6 l4linux | WARNING: Unknown rdmsr: 00000187 at 0x85e1d6 l4linux | WARNING: Unknown wrmsr: 000000c1 at 0x85e2a7 l4linux | Launching cpu1 on pcpu 1 at 0x4024e0 l4linux | l4lx_thread_create: Created thread 420 (cpu1) (u:b3000800, v:b3000600, sp:008c7fa8) l4linux | WARNING: Unknown wrmsr: 0000008b at 0x414bad l4linux | l4lx_thread_create: Created thread 424 (timer1) (u:b3000400, v:00000000, sp:008e3fa8) l4linux | Spurious IPI on CPU0: 4 l4linux | panic: going to sleep forever, bye Has anyone encountered this problem? Stephen

3 4

Boot L4Linux Error
by 刘海剑 28 May '15

28 May '15

Hello everyone, after building l4re-snapshot-2014092821 on my Ubuntu-14.04(32bit), I run L4Linux-mag-x86, and get some errors. The information is as follows: qemu-system-i386 -kernel /home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/bootstrap -append "bootstrap -modaddr 0x01100000" -initrd "/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco -serial_esc,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/sigma0 ,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/l4re ,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/ned ,/home/lhj/L4Linux/l4re-snapshot-2014092821/src/l4/conf/examples/l4lx-gfx.cfg ,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/io ,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/fb-drv ,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/mag ,/home/lhj/L4Linux/l4re-snapshot-2014092821/files/cfg/x86-legacy.devs ,/home/lhj/L4Linux/l4re-snapshot-2014092821/src/l4/conf/examples/l4lx-x86.io ,/tmp/QEVRyiQlKD/vmlinuz ,/home/lhj/L4Linux/l4re-snapshot-2014092821/files/ramdisk-x86.rd " -m 256 -serial stdio L4 Bootstrapper Build: #1 Tue May 26 16:48:47 CST 2015, x86-32, 4.8.2 RAM: 0000000000000000 - 000000000009fbff: 639kB RAM: 0000000000100000 - 000000000fffdfff: 261112kB Total RAM: 255MB Scanning /home/lhj/L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco -serial_esc Scanning /home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/sigma0 Scanning /home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg need 1368 bytes to copy MBI reserved 1368 bytes at 0x2000 Moving up to 13 modules behind 1100000 moving module 12 { 2266400-25663ff } -> { 3085000-3384fff } [3145728] moving module 11 { 1e8e400-2265919 } -> { 2cad000-3084519 } [4027674] moving module 10 { 1e8d400-1e8d626 } -> { 2cac000-2cac226 } [551] moving module 09 { 1e8c400-1e8c63e } -> { 2cab000-2cab23e } [575] moving module 08 { 1a29400-1e8ba0b } -> { 2848000-2caa60b } [4597260] moving module 07 { 189f400-1a28598 } -> { 26be000-2847198 } [1610137] moving module 06 { 98e400-189ee03 } -> { 17ad000-26bda03 } [15796740] moving module 05 { 98d400-98d96a } -> { 17ac000-17ac56a } [1387] moving module 04 { 736400-98ce09 } -> { 1555000-17aba09 } [2451978] moving module 03 { 5fc400-735b2c } -> { 141b000-155472c } [1283885] moving module 02 { 3a9400-5fb7eb } -> { 11c8000-141a3eb } [2434028] moving module 01 { 353400-3a928a } -> { 1172000-11c7e8a } [351883] moving module 00 { 2e1400-352677 } -> { 1100000-1171277 } [463480] Loading /L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco Loading re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/sigma0 Loading /l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/moe find kernel info page... found kernel info page at 0x400000 Regions of list 'regions' [ 0, fff] { 1000} Arch BIOS [ 1000, 1fff] { 1000} Kern /L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco [ 2000, 2557] { 558} Root mbi_rt [ 9fc00, 9ffff] { 400} Arch BIOS [ f0000, fffff] { 10000} Arch BIOS [ 100000, 10b193] { b194} Sigma0 re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/sigma0 [ 140000, 193363] { 53364} Root /l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/moe [ 2d0400, 2df43f] { f040} Boot bootstrap [ 300000, 38ffff] { 90000} Kern /L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco [ 400000, 475fff] { 76000} Kern /L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco [ 141b000, 3384fff] { 1f6a000} Root Module [ fffe000, fffffff] { 2000} Arch BIOS [ fffc0000, ffffffff] { 40000} Arch BIOS API Version: (87) experimental Sigma0 config ip:0010021c sp:00000000 Roottask config ip:001401f6 sp:00000000 Starting kernel /L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco at 003007b8 Welcome to Fiasco.OC (ia32)! L4/Fiasco.OC ia32 microkernel (C) 1998-2013 TU Dresden Rev: unknown compiled with gcc 4.8.2 for Intel Pentium [] Build: #1 Tue May 26 16:33:03 CST 2015 Performance-critical config option(s) detected: CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off Superpages: yes Kmem:: cpu page at fffd000 (4096Bytes) ACPI-Init ACPI: RSDP[0xf09e0]r00 OEM:BOCHS. ACPI: RSDT[0x203ffbc1]r01 OEM:BOCHS. OEMTID:BXPCRSDT ACPI: FACP[0x203ff1c0]r01 OEM:BOCHS. OEMTID:BXPCFACP ACPI: SSDT[0x203ff234]r01 OEM:BOCHS. OEMTID:BXPCSSDT ACPI: APIC[0x203ffb11]r01 OEM:BOCHS. OEMTID:BXPCAPIC ACPI: HPET[0x203ffb89]r01 OEM:BOCHS. OEMTID:BXPCHPET IO-APIC: MADT = 0x203ffb11 IO-APIC[ 0]: struct: 0x203ffb45 adr=fec00000 IO-APIC[ 0]: pins 24 PIN[ 0m]: vector=20, del=0, dm=physical, dest=0 (high, edge) PIN[ 1m]: vector=21, del=0, dm=physical, dest=0 (high, edge) PIN[ 2m]: vector=22, del=0, dm=physical, dest=0 (high, edge) PIN[ 3m]: vector=23, del=0, dm=physical, dest=0 (high, edge) PIN[ 4m]: vector=24, del=0, dm=physical, dest=0 (high, edge) PIN[ 5m]: vector=25, del=0, dm=physical, dest=0 (high, edge) PIN[ 6m]: vector=26, del=0, dm=physical, dest=0 (high, edge) PIN[ 7m]: vector=27, del=0, dm=physical, dest=0 (high, edge) PIN[ 8m]: vector=28, del=0, dm=physical, dest=0 (high, edge) PIN[ 9m]: vector=29, del=0, dm=physical, dest=0 (high, edge) PIN[10m]: vector=2a, del=0, dm=physical, dest=0 (high, edge) PIN[11m]: vector=2b, del=0, dm=physical, dest=0 (high, edge) PIN[12m]: vector=2c, del=0, dm=physical, dest=0 (high, edge) PIN[13m]: vector=2d, del=0, dm=physical, dest=0 (high, edge) PIN[14m]: vector=2e, del=0, dm=physical, dest=0 (high, edge) PIN[15m]: vector=2f, del=0, dm=physical, dest=0 (high, edge) PIN[16m]: vector=30, del=0, dm=physical, dest=0 (high, edge) PIN[17m]: vector=31, del=0, dm=physical, dest=0 (high, edge) PIN[18m]: vector=32, del=0, dm=physical, dest=0 (high, edge) PIN[19m]: vector=33, del=0, dm=physical, dest=0 (high, edge) PIN[20m]: vector=34, del=0, dm=physical, dest=0 (high, edge) PIN[21m]: vector=35, del=0, dm=physical, dest=0 (high, edge) PIN[22m]: vector=36, del=0, dm=physical, dest=0 (high, edge) PIN[23m]: vector=37, del=0, dm=physical, dest=0 (high, edge) IO-APIC: dual 8259: yes IO-APIC: ovr[ 0] 00 -> 2 0 IO-APIC: ovr[ 1] 05 -> 5 d IO-APIC: ovr[ 2] 09 -> 9 d IO-APIC: ovr[ 3] 0a -> a d IO-APIC: ovr[ 4] 0b -> b d Allocate cpu_mem @ 0xfdbf9400 FPU0: SSE Local APIC[00]: version=11 max_lvt=5 APIC ESR value before/after enabling: 00000000/00000000 Using the Local APIC timer on vector 90 (Periodic Mode) for scheduling ACPI: FACS phys=fffe000 virt=0x203fe000 ACPI: HW sig=0 SERIAL ESC: allocated IRQ 4 for serial uart Absolute KIP Syscalls using: Sysenter Enable MSI support: chained IRQ mgr @ 0xfdbf9150 SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. CPU[0]: GenuineIntel (6:6:3:0)[00000663] Model: QEMU Virtual CPU version 2.0.0 at 2507MHz 32 KB L1 I Cache (8-way associative, 64 bytes per line) 32 KB L1 D Cache (8-way associative, 64 bytes per line) 2048 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) Calibrating timer loop... done. MDB: use page size: 22 MDB: use page size: 12 SIGMA0: Hello! KIP @ 400000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:2000;2fff] [0:3000;9efff] [0:10c000;13ffff] [4:140000;193fff] [0:194000;3fffff] [0:470000;141afff] [4:141b000;3384fff] [0:3385000;eb8afff] IOMEM:---------------------- [0:0;fff] [0:9f000;fffff] [0:fffe000;febfffff] [0:fec01000;fedfffff] [0:fee01000;ffffffff] IO PORTS-------------------------- [0:0;fffffff] MOE: Hello world MOE: found 207796 KByte free memory MOE: found RAM from 2000 to eb8b000 MOE: allocated 235 KByte for the page array @0x3000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [141b000-155472d] [C:503000] l4re BOOTFS: [1555000-17aba0a] [C:504000] ned BOOTFS: [17ac000-17ac56b] [C:505000] l4lx-gfx.cfg BOOTFS: [17ad000-26bda04] [C:506000] io BOOTFS: [26be000-2847199] [C:507000] fb-drv BOOTFS: [2848000-2caa60c] [C:508000] mag BOOTFS: [2cab000-2cab23f] [C:509000] x86-legacy.devs BOOTFS: [2cac000-2cac227] [C:50a000] l4lx-x86.io BOOTFS: [2cad000-308451a] [C:50b000] vmlinuz BOOTFS: [3085000-3385000] [C:50c000] ramdisk-x86.rd MOE: cmdline: /home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg MOE: Starting: rom/ned rom/l4lx-gfx.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx-gfx.cfg' io | Io service io | Find root Pointer io | Find root Pointer: f09e0 io | ACPI: RSDP 0xf09e0 00014 (v00 BOCHS ) io | ACPI: RSDT 0xffffbc1 00034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001) io | ACPI: FACP 0xffff1c0 00074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001) io | ACPI: DSDT 0xfffe040 01180 (v01 BOCHS BXPCDSDT 00000001 BXPC 00000001) io | ACPI: FACS 0xfffe000 00040 io | ACPI: SSDT 0xffff234 008DD (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001) io | ACPI: APIC 0xffffb11 00078 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001) io | ACPI: HPET 0xffffb89 00038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001) io | Parsing all Control Methods: io | Table [DSDT](id 0001) - 144 Objects with 18 Devices 52 Methods 8 Regions io | Parsing all Control Methods: io | Table [SSDT](id 0002) - 155 Objects with 32 Devices 42 Methods 1 Regions io | tbxfload-0274 [02] TbLoadNamespace : ACPI Tables successfully acquired io | evxfevnt-0175 [02] Enable : Transition to ACPI mode successful io | evgpeblk-0523 [04] EvCreateGpeBlock : GPE 00 to 0F [_GPE] 2 regs on int 0x9 io | Completing Region/Field/Buffer/Package initialization:..................................... io | Initialized 9/9 Regions 2/2 Fields 21/21 Buffers 5/5 Packages (308 nodes) io | Initializing Device/Processor/Thermal objects by executing _INI methods: io | Executed 0 _INI methods requiring 1 _STA executions (examined 53 objects) io | ACPICA-Version:20121018, System in ACPI MODE, 32bit timer io | evgpeblk-0615 [03] EvInitializeGpeBlock : Enabled 16 GPEs in this block io | IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=40201) io | IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=40201) io | rom/l4lx-x86.io:17.28-36: warning: could not find 'PNP0100' io | Ready. Waiting for request. mag | Hello from MAG fb-drv | Trying execution of ``set VBE mode'' using x86emu fb-drv | Found VESA BIOS version 3.0 fb-drv | OEM SeaBIOS VBE(C) 2011 fb-drv | VBE mode 0x117 successfully set. fb-drv | Framebuffer memory: phys: fc000000 - fc400000 fb-drv | virt: 400000 - 800000 fb-drv | Starting server loop mag | mapped frame buffer at 0x400000 mag | View::Info: mag | flags: 0 mag | size: 1024x768 pos: 0, 0 mag | bytes_per_line: 2048 mag | buffer_offset: 0 mag | RGBA(2): 5(11):6(5):5(0):0(0) mag | memory 400000-800000 mag | Plugin: Mag_client service started mag | Plugin: Frame-buffer service started mag | L4INPUT native mode activated mag | L4INPUT: !!! W A R N I N G !!! mag | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. mag | L4INPUT: !!! W A R N I N G !!! mag | serio: i8042 AUX port at 0x60,0x64 irq 12 mag | serio: i8042 KBD port at 0x60,0x64 irq 1 mag | input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1 mag | input: AT Translated Set 2 keyboard on isa0060/serio0 mag | connect "ImExPS/2 Generic Explorer Mouse", isa0060/serio1/input0 mag | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 l4linux | PH 0 (t: 1) offs=00001000 vaddr=00400000 vend=006dc000 l4linux | phys=00400000 ephys=006dc000 l4linux | f_sz=002dc000 memsz=002dc000 flgs=r-x l4linux | PH 1 (t: 1) offs=002dd000 vaddr=006dc000 vend=007d8000 l4linux | phys=006dc000 ephys=007d8000 l4linux | f_sz=00050f30 memsz=000fc000 flgs=rw- l4linux | PH 2 (t: 4) offs=0023cd64 vaddr=0063bd64 vend=0063bd88 l4linux | phys=0063bd64 ephys=0063bd88 l4linux | f_sz=00000024 memsz=00000024 flgs=--- l4linux | Starting binary at 0x400000, argc=6 argv=0xafff4f90 *argv=0xb1007ff4 argv0=rom/vmlinuz l4linux | External resolver is at 0xa8000730 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.16.0-l4 (lhj@ubuntu) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #1 Tue May 26 16:58:34 CST 2015 l4linux | Binary name: rom/vmlinuz l4linux | Linux kernel command line (5 args): mem=64M console=tty0 l4x_rd=rom/ramdisk-x86.rd root=1:0 ramdisk_size=4000 l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 00400000 - 007d8000 [3936 KiB]. l4linux | Areas: Text: 00400000 - 006dc000 [2928kB] (a bit longer) l4linux | Data: 006dc000 - 00706ac0 [170kB] l4linux | Initdata: 00709000 - 0072d000 [144kB] l4linux | BSS: 0072e000 - 007c2000 [592kB] l4linux | gs=43 fs=43 l4linux | Device scan: l4linux | Device: L4ICU l4linux | Device: PCI0 l4linux | Device: pci_l4x[0000] l4linux | PORT: 0000c040 - 0000c04f l4linux | PORT: 000001f0 - 000001f7 l4linux | PORT: 000003f6 - 000003f6 l4linux | IRQ: 0000000e - 0000000e l4linux | PORT: 00000170 - 00000177 l4linux | PORT: 00000376 - 00000376 l4linux | IRQ: 0000000f - 0000000f l4linux | Device: pci_l4x[0001] l4linux | IRQ: 0000000b - 0000000b l4linux | MEM: febc0000 - febdffff l4linux | PORT: 0000c000 - 0000c03f l4linux | Device scan done. l4linux | l4x_fiasco_gdt_entry_offset = 9 l4linux | rtc not found l4linux | WARNING: RTC server does not seem to be there! l4linux | l4lx_thread_create: Created thread 417 (cpu0) (u:b3000e00, v:b3000c00, sp:006ddfac) l4linux | main thread will be 417 l4linux | l4x_register_pointer_section: addr = 006dc000 size = 1032192 l4linux | section-with-init: Virt: 0x6dc000 to 0x7d7fff [1008 KiB] l4linux | section-with-init: Phys: 0x0090f000 to 0x00a0afff, [1008 KiB] l4linux | Main thread running, waiting... l4linux | WARNING: Unknown wrmsr: 0000008b at 0x411f0d l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 00400000 l4linux | Main memory: Virt: 0x800000 to 0x47fffff [65536 KiB] l4linux | Main memory: Phys: 0x03400000 to 0x073fffff, [65536 KiB] l4linux | l4x: vmalloc area: 04800000 - 0c800000 l4linux | Filling lower ptabs... l4linux | Done (1062 entries). l4linux | l4x_register_pointer_section: addr = 00400000 size = 2998272 l4linux | text: Virt: 0x400000 to 0x6dbfff [2928 KiB] l4linux | text: Phys: 0x00614000 to 0x008effff, [2928 KiB] l4linux | Loading: rom/ramdisk-x86.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 0c91b000 to 0cc1b000 [3072KiB] l4linux | rtc not found l4linux | l4lx_thread_create: Created thread 41f (timer0) (u:b3000a00, v:00000000, sp:0075bfa8) l4linux | WARNING: Unknown wrmsr: 0000008b at 0x411f0d l4linux | WARNING: Unknown rdmsr: 00000186 at 0x710579 l4linux | WARNING: Unknown rdmsr: 00000187 at 0x710579 l4linux | WARNING: Unknown wrmsr: 000000c1 at 0x71064a mag | Input: new pointer device (src='<Input_source userdata: 1D80C>' stream='userdata: 0x3abb4') mag | bus='i8042' vendor=0x2 product=0x6 version=0 mag | Input: new keyboard device (src='<Input_source userdata: 1D80C>' stream='userdata: 0x3b358') mag | bus='i8042' vendor=0x1 product=0x1 version=43841 And I printed my screen. See attached png-file. Thanks for any reply!

2 1

Running L4Linux + Fiasco on Freescale i.MX 6 Sabre SD
by Mahdi Aichouch 28 May '15

28 May '15

Hello, I tried to run L4Linux + Fiasco on a Freescale i.mx 6 Sabre SD board. The L4Linux is started but it stops at loading the ramdisk, as shown in the debug messages below. Does someone has an idea of what might be wrong. Thank you very much in advance. Best regards, Mahdi L4 Bootstrapper Build: #80 Wed May 27 18:22:31 CEST 2015, 4.8.3 20140320 (prerelease) Scanning up to 256 MB RAM, starting at offset 32MB Memory size is 256MB (10000000 - 1fffffff) RAM: 0000000010000000 - 000000001fffffff: 262144kB Total RAM: 256MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 10 modules behind 11100000 moving module 02 { 118aa000-118e363f } -> { 1199a000-119d363f } [235072] moving module 01 { 118a0000-118a938b } -> { 11990000-1199938b } [37772] moving module 00 { 11848000-1189fb17 } -> { 11938000-1198fb17 } [359192] moving module 09 { 11548000-11847fff } -> { 11638000-11937fff } [3145728] moving module 08 { 111d6000-11547497 } -> { 112c6000-11637497 } [3609752] moving module 07 { 111d5000-111d50bc } -> { 112c5000-112c50bc } [189] moving module 06 { 1107e000-111d446f } -> { 1116e000-112c446f } [1401968] moving module 05 { 1107d000-1107d17b } -> { 1116d000-1116d17b } [380] moving module 04 { 1102a000-1107cc1f } -> { 1111a000-1116cc1f } [338976] moving module 03 { 11010000-11029473 } -> { 11100000-11119473 } [103540] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x10002000 Regions of list 'regions' [ 10000000, 1000015f] { 160} Root mbi_rt [ 10001000, 10001aff] { b00} Kern fiasco [ 10002000, 10066fff] { 65000} Kern fiasco [ 10090000, 10096edf] { 6ee0} Sigma0 sigma0 [ 10098000, 1009e177] { 6178} Sigma0 sigma0 [ 10140000, 10171d77] { 31d78} Root moe [ 10178000, 101934ab] { 1b4ac} Root moe [ 11000000, 1100f58f] { f590} Boot bootstrap [ 11100000, 11937fff] { 838000} Root Module API Version: (87) experimental Sigma0 config ip:10090100 sp:00000000 Roottask config ip:10140260 sp:00000000 Starting kernel fiasco at 100012c8 Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl L2: ID=410000c7 Type=9e340340 Aux=02070000 WMask=ffff S=0 L2: Type L2C-310 Size = 1024kB Ways=16 Waysize=64 GIC: Switching IRQ 58 to secure SERIAL ESC: allocated IRQ 58 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rexported compiled with gcc 4.8.3 for i.MX6 [] Build: #14 Wed Apr 29 13:37:03 CEST 2015 GIC: Switching IRQ 29 to secure Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 10002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:10000000;10000fff] [0:10067000;1008ffff] [0:10097000;10097fff] [0:1009f000;1013ffff] [4:10140000;10171fff] [0:10172000;10177fff] [4:10178000;10193fff] [0:10194000;110fffff] [4:11100000;11937fff] [0:11938000;1effffff] IOMEM:---------------------- [0:0;fffffff] [0:20000000;ffffffff] MOE: Hello world MOE: found 236564 KByte free memory MOE: found RAM from 10000000 to 1f000000 MOE: allocated 240 KByte for the page array @0x1009f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [11100000-11119474] [C:503000] l4re BOOTFS: [1111a000-1116cc20] [C:504000] ned BOOTFS: [1116d000-1116d17c] [C:505000] l4lx.cfg BOOTFS: [1116e000-112c4470] [C:506000] io BOOTFS: [112c5000-112c50bd] [C:507000] arm-rv.io BOOTFS: [112c6000-11637498] [C:508000] vmlinuz.arm BOOTFS: [11638000-11938000] [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' l4linux | libio: Warning: Query of 'vbus' failed! l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=023defa8 l4linux | phys=02000000 ephys=023defa8 l4linux | f_sz=00359394 memsz=003defa8 flgs=rwx l4linux | PH 1 (t: 4) offs=0031afe0 vaddr=02312fe0 vend=02313004 l4linux | phys=02312fe0 ephys=02313004 l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x20002b0, argc=6 argv=0xafff4f8c *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa8000788 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.16.0-l4 (aichouch@aichouch-ThinkCentre-M90) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #1 Wed May 27 18:04:14 CEST 2015 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (5 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 02000000 - 02400000 [4096 KiB]. l4linux | Areas: Text: 02000000 - 02332000 [3272kB] (a bit longer) l4linux | Data: 02332000 - 023543a0 [136kB] l4linux | Initdata: 02314000 - 02331024 [116kB] l4linux | BSS: 02359394 - 023defa8 [535kB] l4linux | Device scan: l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:02333fa4) l4linux | main thread will be 413 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4059136 l4linux | section-with-init: Virt: 0x2000000 to 0x23defa7 [3963 KiB] l4linux | section-with-init: Phys: 0x1025a000 to 0x10638fa7, [3963 KiB] l4linux | Main thread running, waiting... l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 02000000 l4linux | Main memory: Virt: 0x2400000 to 0x63fffff [65536 KiB] l4linux | Main memory: Phys: 0x11a00000 to 0x159fffff, [65536 KiB] l4linux | l4x: vmalloc area: 06400000 - 0e400000 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4059136 l4linux | text: Virt: 0x2000000 to 0x23defa7 [3963 KiB] l4linux | text: Phys: 0x1025a000 to 0x10638fa7, [3963 KiB] l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] l4linux | 'swp(b)' instruction at 0224f728 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? ...

2 1

Utcb in syscall
by watermirror 27 May '15

27 May '15

hi ,in sys_ipc_wrapper, the code first get the current thread's syscall entry frame: .... Thread *curr=current_thread(); Syscall_frame *f = curr-regs(); ... according to the Syscall_frame's implemention, it can get the Utcb by Syscall_frame::utcb(). but the following code get the Utcb in another way: Utcb *utcb = curr->utcb().access(true); what's the difference between those two Utcb?

4 4

Re: Booting error in L4android for Exynos 5250.
by Youren Shen 27 May '15

27 May '15

> > > > I'm trying to booting L4Android in Exynos 5250 platform. I got some > > > questions. If anyone can give me any direction or document, It will be > > very > > > helpful. > > > > > > 1, How to edit this vbus and devs file to match my platform? > > > For example, if I want replace the MOUSE in vbus with TOUCHSCREEN, what > > > should I write to determine the driver of the touchscreen, and the > > register > > > address of the driver? > > > It seems the .hid can assign the driver? And the MMio can remap the > > address > > > of the IO for driver? > > > > A vbus defines the resources (IRQs and MMIO) for a whole client, i.e. > > it's not per driver but per client (e.g. L4Linux). For the touchscreen > > you need to give the MMIO regions and IRQs that the touchscreen driver > > is using. > > > > > 2, As for GUI driver, what the mag and fb-drv do ? Should I write one > > > > The fb-drv is the framebuffer driver, i.e. the driver that maps some > > memory in such a way to the framebuffer hardware that something appears > > on the screen. mag is a small window manager that makes multiple > > windows, that you can drag around, out of the single hardware > > framebuffer. > > > > > driver in L4RE or I can reuse the driver in Linux? > > > > Reusing the driver from L4Linux is possible but typically framebuffer > > drivers are reasonable small to be implemented standalone. > > For the driver reuse: I read the User Guide of rearview platform, it seems that the MMIO should set as the register Address in memory map. And the IRQs should be the interrupt number + 32. I know how to write LCD driver and framebuffer in native Linux System. But for L4Linux, I still have some question. I am not sure how to reuse the driver of Linux or rewrite the fb-drv. Here is the situation: The folder in arch/arm/mach-exynos has plenty code to initial the platform, so I added config L4_PLATFORM_EXYNOS in arch/l4/Kconfig and PLATFORMNAME-$(CONFIG_L4_PLATFORM_EXYNOS) = exynos in arch/l4/Makefile. However, when build the kernel, there is some error. It seems like the L4Linux startup invoke some variables defined in Realview or Generic platform like NR_IRQS_HW. Is this rectifiable? I found that there is l4fb.c as driver in driver/video, what's different with the module in l4/pkg? And last question, how to run the driver I want to use? Thank you very much! -- Best Regards. Youren Shen.

2 1

Re: Booting error in L4android for Exynos 5250.
by Youren Shen 27 May '15

27 May '15

Thank you very much for your reply. > > On Wed May 13, 2015 at 22:23:18 +0800, Youren Shen wrote: > > I'm trying to booting L4Android in Exynos 5250 platform. I got some > > questions. If anyone can give me any direction or document, It will be > very > > helpful. > > > > 1, How to edit this vbus and devs file to match my platform? > > For example, if I want replace the MOUSE in vbus with TOUCHSCREEN, what > > should I write to determine the driver of the touchscreen, and the > register > > address of the driver? > > It seems the .hid can assign the driver? And the MMio can remap the > address > > of the IO for driver? > > A vbus defines the resources (IRQs and MMIO) for a whole client, i.e. > it's not per driver but per client (e.g. L4Linux). For the touchscreen > you need to give the MMIO regions and IRQs that the touchscreen driver > is using. > > > 2, As for GUI driver, what the mag and fb-drv do ? Should I write one > > The fb-drv is the framebuffer driver, i.e. the driver that maps some > memory in such a way to the framebuffer hardware that something appears > on the screen. mag is a small window manager that makes multiple > windows, that you can drag around, out of the single hardware > framebuffer. > > > driver in L4RE or I can reuse the driver in Linux? > > Reusing the driver from L4Linux is possible but typically framebuffer > drivers are reasonable small to be implemented standalone. > > > *For this two question I just need some guide*, I can't find details > > explanation of the file or tutorial in Wiki page. > > > > Thank you very much! > > > > Also I got some new error when booting. The system mount failed. Would > you > > mind to take a look? > > > > RAMDISK: Loading 1024KiB [1 disk] into ram disk... done. > > > > EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities > > > > EXT4-fs (ram0): mounting ext2 file system using the ext4 subsystem > > > > EXT4-fs warning (device ram0): ext4_update_dynamic_rev:701: updating to > rev > > 1 bd > > EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) > > > > VFS: Mounted root (ext2 filesystem) on device 1:0. > > > > Freeing unused kernel memory: 164K (02356000 - 0237f000) > > > > init: cannot open '/initlogo.rle' > > > > EXT4-fs (ram0): re-mounted. Opts: (null) > > > > init: Unable to open persistent property directory /data/property errno: > 2 > > > > init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj > > inste. > > init: cannot find '/system/bin/servicemanager', disabling > 'servicemanager' > > init: cannot find '/system/bin/vold', disabling 'vold' > > Looks like the system partition could not be mounted. Where should it > be? > > I'm using the image and config files that L4Android.org supplied. I copied the two image file(root-arm-ginger.img and system-arm-ginger.img) to l4/build/bin/$arch/l4f So here is the module list: *entry l4android-arm* *roottask moe rom/l4_gingerbread-arm.cfg* *kernel fiasco -serial_esc* *module l4re* *module ned* *module io* *module mag* *module fb-drv* *module l4_gingerbread-arm.cfg* *module arm-rv-eb.devs* *module l4_android-arm.vbus* *module vmlinuz.android* *module root-arm-ginger.img* *module system-arm-ginger.img* And here is the parameter of loader:start in ned script. *"rom/" .. lxname .. " console=ttyLv0 androidboot.console=ttyLv0 mem=256M l4bdds.add=rom/system-arm-ginger.img,rw boot=local android.ril=ttyLv1 ip=dhcp l4x_rd=rom/root-arm-ginger.img rw root=1:0 ramdisk_size=1500 init=/init --debug l4fb.touchscreen=1* In the root-arm-ginger.img file, the init script should mount the /system: *mount cramfs /l4bdds0 /system **mount cramfs /l4bdds0 /system ro remount **mount tmpfs tmpfs /data size=32M* But it failed. I check the CRAMFS and it's enable in Linux kernel. Then I have no idea about what can cause this /system mount error. Thank you very much for your help! -- Best Regards. Youren Shen.

2 1

Kobject_h::invoke
by watermirror 27 May '15

27 May '15

hi, in what situation, the fiasco will call method Kobject_h::invoke?

2 1

Re: l4-hackers Digest, Vol 145, Issue 7
by Reinier Millo Sánchez 26 May '15

26 May '15

Hi Adam On 05/11/2015 06:00 AM, l4-hackers-request(a)os.inf.tu-dresden.de wrote: > On Tue May 05, 2015 at 01:28:46 -0400, Reinier Millo S?nchez wrote: >> > >> >Hi Adam >>>>> > >>> FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, >>>>> > >>> p: dbl/sngl >>>>> > >>> >>>>> > >>> KERNEL: Warning: No page-fault handler for 0xee202214, error >>>>> > >>> 0x94000848, pc f0039420 >>>>> > >>> >>>>> > >>>Somebody have tested Fiasco.OC+L4re on ODROID-X2 or another Exynos 4412 >>>>> > >>>platform? >>> > >On this platform this seems to be some pattern. However, last time I >>> > >tried it worked for me. So, hmm, could you try another compiler version >>> > >and see if it changes behavior? Maybe this gives us some hints. >> >I'm using a linaro toolchain >> >(gcc-linaro-arm-linux-gnueabihf-4.8-2014.03_x86_64). I have tried the >> >arm-none-eabi toolchain in Debian repository but fails compiling the >> >snapshot. >> >I have made some progress trying to run FiascoOC+L4re on Odroid-X2. There >> >are some changes that I have made: >> >I have modified the file "l4/mk/platforms/exynos4.conf" adapting Exynos4's >> >platform to Odroid-X2. In this case the RAM size differs (Odroid-X2 have >> >2Gb). In this file I have configured the UART for serial output (I'm using >> >UART 1). >> > >> > PLATFORM_RAM_BASE = 0x40000000 >> > - PLATFORM_RAM_SIZE_MB = 1024 >> > + PLATFORM_RAM_SIZE_MB = 2047 >> > + PLATFORM_UART_NR = 1 >> > >> >Booting the generated image I have detected that bootstrap's server is not >> >using UART 1 for output. I have modified the "init" function on >> >"l4/pkg/bootstrap/server/src/platform/exynos.cc" to use the configured UART >> >on the platform file modified above. >> > >> > unsigned long uart_base; >> > - unsigned uart_nr = 2; >> > + unsigned uart_nr = PLATFORM_UART_NR; >> > >> >I have tried to compile and test the image on the Odroid-X2, but fails the >> >execution, this is the serial output: >> > >> > L4 Bootstrapper >> > Build: #18 Sat May 2 15:56:00 CDT 2015, 4.8.3 20140303 (prerelease) >> > Scanning up to 2047 MB RAM, starting at offset 32MB >> > Memory size is 2047MB (40000000 - bfefffff) >> > Limiting 'RAM' region [ 40000000, bfefffff] { 7ff00000} to [ >> > 40000000, bcffffff] { 7d000000} due to 3024 MB address limit >> > RAM: 0000000040000000 - 00000000bcffffff: 2048000kB >> > Total RAM: 2000MB >> > Scanning fiasco >> > Scanning sigma0 >> > Scanning moe >> > Moving up to 5 modules behind 41100000 >> > moving module 02 { 410b4000-410e565f } -> { 411a5000-411d665f } >> > [202336] >> > moving module 01 { 410aa000-410b3377 } -> { 4119b000-411a4377 } >> > [37752] >> > moving module 00 { 41043000-410a9daf } -> { 41134000-4119adaf } >> > [421296] >> > moving module 04 { 41029000-410425b3 } -> { 4111a000-411335b3 } >> > [103860] >> > moving module 03 { 4100f000-41028493 } -> { 41100000-41119493 } >> > [103572] >> > Loading fiasco >> > Loading sigma0 >> > Loading moe >> > find kernel info page... >> > found kernel info page at 0x40002000 >> > Regions of list 'regions' >> > [ 40000000, 400000e3] { e4} Root mbi_rt >> > [ 40001000, 40001aff] { b00} Kern fiasco >> > [ 40002000, 40076fff] { 75000} Kern fiasco >> > [ 40090000, 4009681b] { 681c} Sigma0 sigma0 >> > [ 40098000, 4009e177] { 6178} Sigma0 sigma0 >> > [ 40140000, 4018b4ab] { 4b4ac} Root moe >> > [ 41000000, 4100e4ff] { e500} Boot bootstrap >> > [ 41100000, 41133fff] { 34000} Root Module >> > API Version: (87) experimental >> > Sigma0 config ip:40090100 sp:00000000 >> > Roottask config ip:4014020c sp:00000000 >> > Starting kernel fiasco at 400012c8 >> > Hello from Startup::stage2 >> > Per_cpu_data_alloc: (orig: 0xf0063a50-0xf00644d0) >> > Number of IRQs available at this GIC: 160 >> > FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, >> > p: dbl/sngl >> > >> > KERNEL: Warning: No page-fault handler for 0xee202214, error >> > 0x94000848, pc f0039420 >> > >> >I have been testing and changing the compiling configuration. Using the >> >below configuration to compile Fiasco.OC, the system boots and hangs at >> >"Calibrating timer loop...": >> > >> > Platform Timer -> Multi-core timer >> > Use ExtGic -> True >> > Execution Model -> TrustZone normal side >> > Secure Monitor Interface -> Mobicore >> > Enable multi processor support -> True >> > Maximal supported number of CPUs -> 4 > Interesting. What's the difference to the previos config? In the first configuration i was using: Platform Timer -> Multi-core timer Use ExtGic -> True Execution Model -> Standard mode Enable multi processor support -> False >> >This is the serial output when tested the image on Odroid-X2: >> > Calibrating timer loop... >> > >> >I think that the problem now is with the Exynos4's Timers, but i have been >> >reviewing the implementations and it seems fine. >> >Is there anything wrong on my configuration or somebody have any idea? > Does the counter of the timer count, i.e. multiple reads return > different values? We have checked and the system clock at Kip (Kip::k()->clock) is updating on every tick in the function "Timer::update_system_clock", but multiple reads of the clock in the function "Delay::measure" returns the same value. We have made another small changes to test the snapshot on the Odroid-X2 board. We have compiled Fiasco.OC using this configuration: Execution Model ->TrustZone Normal side Secure Monitor Interface ->none Enable multi processor support ->Disable We have commented the "Delay:init();" line in the Kernel_thread::bootstrap() in the "src/kernel/fiasco/src/kern/kernel_thread.cpp" file. When test the compiled image on the board, we have the following output with one "Hello World" and then stops in the sleep. We remain thinking that the problem is in the timers implementation. U-Boot 2010.12-svn (Dec 21 2012 - 19:44:04) for Exynox4412 CPU: S5PC220 [Samsung SOC on SMP Platform Base on ARM CortexA9] APLL = 1000MHz, MPLL = 880MHz DRAM: 2047 MiB PMIC VERSION : 0x00, CHIP REV : 2 TrustZone Enabled BSP BL1 version: 20121128 Checking Boot Mode ... SDMMC MMC Device 0: 7695 MB MMC Device 1 not found ModeKey Check... run normal_boot Net: No ethernet found. Partition1: Start Address(0xc00), Size(0x40400) reading hello.raw 741376 bytes read Boot with zImage Starting kernel ... L4 Bootstrapper Build: #32 Fri May 8 15:32:04 EDT 2015, 4.8.3 20140303 (prerelease) Scanning up to 1023 MB RAM, starting at offset 32MB Memory size is 1023MB (40000000 - 7fefffff) RAM: 0000000040000000 - 000000007fefffff: 1047552kB Total RAM: 1023MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 5 modules behind 41100000 moving module 02 { 41083000-410b465f } -> { 41174000-411a565f } [202336] moving module 01 { 41079000-41082377 } -> { 4116a000-41173377 } [37752] moving module 00 { 41043000-410782bb } -> { 41134000-411692bb } [217788] moving module 04 { 41029000-410425b3 } -> { 4111a000-411335b3 } [103860] moving module 03 { 4100f000-41028493 } -> { 41100000-41119493 } [103572] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x40002000 Regions of list 'regions' [ 40000000, 400000e3] { e4} Root mbi_rt [ 40001000, 40001aff] { b00} Kern fiasco [ 40002000, 4003efff] { 3d000} Kern fiasco [ 40090000, 4009681b] { 681c} Sigma0 sigma0 [ 40098000, 4009e177] { 6178} Sigma0 sigma0 [ 40140000, 4016ef97] { 2ef98} Root moe [ 40170000, 4018b4ab] { 1b4ac} Root moe [ 41000000, 4100e4ff] { e500} Boot bootstrap [ 41100000, 41133fff] { 34000} Root Module API Version: (87) experimental Sigma0 config ip:40090100 sp:00000000 Roottask config ip:4014020c sp:00000000 Starting kernel fiasco at 400012c8 Hello from Startup::stage2 Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl Watchdog initialized SERIAL ESC: allocated IRQ 85 for serial uart Not using serial hack in slow timer handler. \0x1b[1;32mWelcome to Fiasco.OC (arm)! \0x1b[0;32mL4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: unknown compiled with gcc 4.8.3 for Samsung Exynos [] Build: #109 Fri May 8 15:25:47 EDT 2015 \0x1b[0m Timer for CPU0 is at IRQ 28 Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 40002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:40000000;40000fff] [0:4003f000;4008ffff] [0:40097000;40097fff] [0:4009f000;4013ffff] [4:40140000;4016efff] [0:4016f000;4016ffff] [4:40170000;4018bfff] [0:4018c000;410fffff] [4:41100000;41133fff] [0:41134000;7eefffff] IOMEM:---------------------- [0:0;3fffffff] [0:7ff00000;ffffffff] MOE: Hello world MOE: found 1030352 KByte free memory MOE: found RAM from 40000000 to 7ef00000 MOE: allocated 1007 KByte for the page array @0x4018c000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [41100000-41119494] [C:503000] l4re BOOTFS: [4111a000-411335b4] [C:504000] hello MOE: cmdline: moe --init=rom/hello MOE: Starting: rom/hello MOE: loading 'rom/hello' Hello World! Somebody have any suggestion? Best regards -- Lic. Reinier Millo Sánchez Centro de Estudios de Informática Universidad Central "Marta Abreu" de Las Villas Carretera a Camajuaní Km 5 1/2 Santa Clara, Villa Clara, Cuba CP 54830 "antes de discutir ... respira; antes de hablar ... escucha; antes de escribir ... piensa; antes de herir ... siente; antes de rendirte ... intenta; antes de morir ... vive"

2 3

Does Fiasco support floating point?
by Yuxin Ren 19 May '15

19 May '15

Hi All, Does Fiasco support floating point processing? If it supports, where is code to initialize and save/store floating point registers? Thanks a lot. Yuxin

3 2

Fiasco.OC-UX and recent Linux kernels
by Paul Boddie 18 May '15

18 May '15

Hello, I have been experimenting a little with L4/Fiasco.OC and have been trying to gradually build up my skills by looking at Fiasco.OC-UX. However, there are a few things that aren't really very clear to me from looking at the documentation. Looking at the L4Re and Fiasco documentation, it appears that I first build L4Re normally... http://l4re.org/build.html ...and then I need to build Fiasco.OC... http://os.inf.tu-dresden.de/fiasco/build.html ...but indicating the "Linux Usermode Platform" in the "Platform" section of the "Target configuration" when doing "make config". The documentation mentions doing "make ux E=hello", but I found that a MODULE_SEARCH_PATH was required. Otherwise, the Makefile directs a script to look in directories of the L4Re build hierarchy that don't exist... http://os.inf.tu-dresden.de/fiasco/ux-using.html Having got this far, running "make ux" with the necessary options gave me the following error: openpty: No such file or directory Problems setting up timer interrupt! Aborted I did start to wonder whether there might be permission issues, whether the UX mode is no longer supported, or whether it isn't supported on Linux 3.x kernels. (I use User Mode Linux a lot and never have to do so as a privileged user, by the way.) The documentation seems to indicate that a 2.6 kernel is required... http://os.inf.tu-dresden.de/fiasco/ux-status.html ...which probably few people run on a desktop or laptop any more, but for the record I am using the 32-bit x86 architecture and not amd64/x86-64, and my distribution is Debian Wheezy. Am I trying something which I shouldn't expect to work? A perusal of the mailing list archives didn't really provide any obvious answers. Thanks for any help in advance, Paul

2 2

Booting error in L4android for Exynos 5250.
by Youren Shen 18 May '15

18 May '15

Hi, L4Hackers: I'm trying to booting L4Android in Exynos 5250 platform. I got some questions. If anyone can give me any direction or document, It will be very helpful. 1, How to edit this vbus and devs file to match my platform? For example, if I want replace the MOUSE in vbus with TOUCHSCREEN, what should I write to determine the driver of the touchscreen, and the register address of the driver? It seems the .hid can assign the driver? And the MMio can remap the address of the IO for driver? 2, As for GUI driver, what the mag and fb-drv do ? Should I write one driver in L4RE or I can reuse the driver in Linux? *For this two question I just need some guide*, I can't find details explanation of the file or tutorial in Wiki page. Thank you very much! Also I got some new error when booting. The system mount failed. Would you mind to take a look? ## Starting application at 0x41000000 ... L4 Bootstrapper Build: #4 Tue May 5 18:39:47 CST 2015, 4.6.4 Scanning up to 2047 MB RAM, starting at offset 256MB Memory size is 2047MB (40000000 - bfefffff) Limiting 'RAM' region [ 40000000, bfefffff] { 7ff00000} to [ 40000000, t RAM: 0000000040000000 - 00000000bcffffff: 2048000kB Total RAM: 2000MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 14 modules behind 41100000 moving module 02 { 4fbec000-4fc255ef } -> { 4fcdb000-4fd145ef } [234992] moving module 01 { 4fbe2000-4fbeb33b } -> { 4fcd1000-4fcda33b } [37692] moving module 00 { 4fb7e000-4fbe127f } -> { 4fc6d000-4fcd027f } [406144] moving module 13 { 41794000-4fb7df5b } -> { 41883000-4fc6cf5b } [238985052] moving module 12 { 41694000-41793fff } -> { 41783000-41882fff } [1048576] moving module 11 { 412ca000-41693487 } -> { 413b9000-41782487 } [3970184] moving module 10 { 412c9000-412c9109 } -> { 413b8000-413b8109 } [266] moving module 09 { 412c8000-412c84c0 } -> { 413b7000-413b74c0 } [1217] moving module 08 { 412c7000-412c765e } -> { 413b6000-413b665e } [1631] moving module 07 { 4129d000-412c65ef } -> { 4138c000-413b55ef } [169456] moving module 06 { 411ed000-4129cc0f } -> { 412dc000-4138bc0f } [719888] moving module 05 { 41086000-411ec44f } -> { 41175000-412db44f } [1467472] moving module 04 { 4102b000-41085bcf } -> { 4111a000-41174bcf } [371664] moving module 03 { 41011000-4102a427 } -> { 41100000-41119427 } [103464] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x40002000 Regions of list 'regions' [ 40000000, 40000203] { 204} Root mbi_rt [ 40001000, 40001c3f] { c40} Kern fiasco [ 40002000, 40072fff] { 71000} Kern fiasco [ 40090000, 40096f0b] { 6f0c} Sigma0 sigma0 [ 40098000, 4009e177] { 6178} Sigma0 sigma0 [ 40140000, 40174a53] { 34a54} Root moe [ 40178000, 4018ef03] { 16f04} Root moe [ 41000000, 410105f7] { 105f8} Boot bootstrap [ 41100000, 4fc6cfff] { eb6d000} Root Module API Version: (87) experimental Sigma0 config ip:40090100 sp:00000000 Roottask config ip:40140198 sp:00000000 Starting kernel fiasco at 40001360 Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf005ff90-0xf0060990) Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv4(4), Part: VFPv3(30), r: 0, v: f, i: 41, t: hard, p: dbl/sngl Watchdog initialized SERIAL ESC: allocated IRQ 85 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: unknown compiled with gcc 4.6.4 for Samsung Exynos [] Build: #1 Tue May 5 16:52:03 CST 2015 Per_cpu_data_alloc: (orig: 0xf005ff90-0xf0060990) Allocate 2560 bytes (3KB) for CPU[4] local storage (offset=118b070, 0xf11eb000-) Timer for CPU0 is at IRQ 152 Number of CPUs: 1 Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 40002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:40000000;40000fff] [0:40073000;4008ffff] [0:40097000;40097fff] [0:4009f000;4013ffff] [4:40140000;40174fff] [0:40175000;40177fff] [4:40178000;4018efff] [0:4018f000;410fffff] [4:41100000;4fc6cfff] [0:4fc6d000;bbffffff] IOMEM:---------------------- [0:0;3fffffff] [0:bd000000;ffffffff] MOE: Hello world MOE: found 1789720 KByte free memory MOE: found RAM from 40000000 to bc000000 MOE: allocated 1984 KByte for the page array @0x4018f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [41100000-41119428] [C:503000] l4re BOOTFS: [4111a000-41174bd0] [C:504000] ned BOOTFS: [41175000-412db450] [C:505000] io BOOTFS: [412dc000-4138bc10] [C:506000] mag BOOTFS: [4138c000-413b55f0] [C:507000] fb-drv BOOTFS: [413b6000-413b665f] [C:508000] l4_gingerbread-arm.cfg BOOTFS: [413b7000-413b74c1] [C:509000] arm-rv-eb.devs BOOTFS: [413b8000-413b810a] [C:50a000] l4_android-arm.vbus BOOTFS: [413b9000-41782488] [C:50b000] vmlinuz.android BOOTFS: [41783000-41883000] [C:50c000] root-arm-ginger.img BOOTFS: [41883000-4fc6cf5c] [C:50d000] system-arm-ginger.img MOE: cmdline: moe rom/l4_gingerbread-arm.cfg MOE: Starting: rom/ned rom/l4_gingerbread-arm.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4_gingerbread-arm.cfg' io | Io service io | Ready. Waiting for request. mag | Hello from MAG fb | Using LCD driver: ARM AMBA PrimeCell 11x fb | Unknown LCD: periphid = 00000000, cellid = 00000000 fb | Video memory is at virtual 0x5000 (size: 0x96000 Bytes) fb | Physical video memory is at 0x40654000 fb | Color mode: 10:5:0 5:5:5 fb | Detected a 'Unknown' device. fb | Configure 3.8 CLCD fb | Starting server loop mag | mapped frame buffer at 0x200000 mag | View::Info: mag | flags: 0 mag | size: 640x480 pos: 0, 0 mag | bytes_per_line: 1280 mag | buffer_offset: 0 mag | RGBA(2): 5(10):5(5):5(0):0(0) mag | memory 200000-296000 mag | Plugin: Mag_client service started mag | Plugin: Frame-buffer service started mag | L4INPUT native mode activated mag | L4INPUT: !!! W A R N I N G !!! mag | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. mag | L4INPUT: !!! W A R N I N G !!! android | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=0246e454 android | phys=02000000 ephys=0246e454 android | f_sz=003ab5bc memsz=0046e454 flgs=rwx android | PH 1 (t: 4) offs=0035ddb8 vaddr=02355db8 vend=02355ddc android | phys=02355db8 ephys=02355ddc android | f_sz=00000024 memsz=00000024 flgs=r-x android | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 android | phys=00000000 ephys=00000000 android | f_sz=00000000 memsz=00000000 flgs=rwx android | Starting binary at 0x2000358, argc=15 argv=0xafff4f6c *argv=0xb1007fed android | External resolver is at 0xa800070c android | ======> L4Linux starting... <======== android | Linux version 3.16.0-l4 (shenyouren@Dell-Shen) (gcc version 4.6.x-goo5 android | Binary name: rom/vmlinuz.android android | This is an AEABI build. android | Linux kernel command line (14 args): console=ttyLv0 androidboot.conso1 android | CPU mapping (l:p)[1]: 0:0 android | Image: 020000a0 - 02600000 [6143 KiB]. android | Areas: Text: 020000a0 - 02380000 [3583kB] (a bit longer) android | Data: 02380000 - 023a6fa0 [155kB] android | Initdata: 02356000 - 0237f900 [166kB] android | BSS: 023ab5bc - 0246e454 [779kB] android | Device scan: android | Device: L4ICU android | Device scan done. android | l4lx_thread_create: Created thread 416 (cpu0) (u:b3000e00, v:b3000c00) android | main thread will be 416 android | l4x_register_pointer_section: addr = 02000000 size = 4648960 android | section-with-init: Virt: 0x2000000 to 0x246e453 [4537 KiB] android | section-with-init: Phys: 0x407fa000 to 0x40c68453, [4537 KiB] android | Main thread running, waiting... android | L4x: Memory size: 256MB android | L4x: Setting superpages for main memory android | L4x: Adjusted memory start: 02000000 android | Main memory: Virt: 0x2600000 to 0x125fffff [262144 KiB] android | Main memory: Phys: 0x4fe00000 to 0x5fdfffff, [262144 KiB] android | l4x: vmalloc area: 12600000 - 1a600000 android | l4x_register_pointer_section: addr = 02000000 size = 4648960 android | text: Virt: 0x2000000 to 0x246e453 [4537 KiB] android | text: Phys: 0x407fa000 to 0x40c68453, [4537 KiB] android | Loading: rom/root-arm-ginger.img android | INITRD: Size of RAMdisk is 1024KiB android | RAMdisk from 00002000 to 00102000 [1024KiB] android | l4lx_thread_create: Created thread 41c (timer0) (u:b3000a00, v:000000) Booting Linux on physical CPU 0x0 Linux version 3.16.0-l4 (shenyouren@Dell-Shen) (gcc version 4.6.x-google 2012015 CPU: Fiasco [410fc0f4] revision 4 (ARMv7), cr=00000000 CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache Machine: L4 Ignoring unrecognised tag 0x00000000 Forcing write-allocate cache policy for SMP Forcing shared mappings for SMP Memory policy: Data cache writealloc INITRD: 00002000 - 00102000 PERCPU: Embedded 7 pages/cpu @123a0000 s6400 r8192 d14080 u32768 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 66484 Kernel command line: console=ttyLv0 androidboot.console=ttyLv0 mem=256M l4bdds.) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 259556K/268288K available (2687K kernel code, 155K rwdata, 728K rodata,) Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xffe00000 (2048 kB) vmalloc : 0x12600000 - 0x1a600000 ( 128 MB) lowmem : 0x00000000 - 0x12600000 ( 294 MB) modules : Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xffe00000 (2048 kB) vmalloc : 0x12600000 - 0x1a600000 ( 128 MB) lowmem : 0x00000000 - 0x12600000 ( 294 MB) moHierarchical RCU implementation. RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1. RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 NR_IRQS:220 l4timer: Using IRQ210 sched_clock: 64 bits at 1000kHz, resolution 1000ns, wraps every 2147483648000ns Console: colour dummy device 80x30 console [ttyLv0] enabled Calibrating delay loop... 1987.37 BogoMIPS (lpj=9936896) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Setting up static identity map for 0x2287610 - 0x2287610 Brought up 1 CPUs SMP: Total of 1 processors activated. CPU: All CPU(s) started in SVC mode. VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0 NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations Added static device 'L4ICU' with 0 resources. Failed to create "l4x" debugfs directory: 1 l4vbus: is running Switched to clocksource l4kipclk NET: Registered protocol family 2 TCP established hash table entries: 4096 (order: 2, 16384 bytes) TCP bind hash table entries: 4096 (order: 3, 32768 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP: reno registered UDP hash table entries: 256 (order: 1, 8192 bytes) UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (junk in compressed archive); looks like an initrd INITRD: Freeing memory. l4x: Checks passed. NetWinder Floating Point Emulator V0.97 (double precision) futex hash table entries: 256 (order: 2, 16384 bytes) msgmni has been set to 506 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) l4fb.0: looking for capability 'fb' as goos session l4fb l4fb.0: 640x480@16 2bypp, size: 614400 @ 200000 l4fb l4fb.0: 5:5:5 10:5:0 linelen=1280 visual=2 l4fb l4fb.0: l4fb L4 frame buffer device (refresh: 10jiffies) Console: switching to colour frame buffer device 80x30 L4 serial driver ttyLv0 at MMIO 0x1 (irq = 211, base_baud = 230400) is a L4 l4ser_shm: L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded *l4bdds: Disk 'rom/system-arm-ginger.img' size = 233384 KB (227 MB) flags=101 ad0* * l4bdds0: unknown partition table * *[sched_delayed] sched: RT throttling activated * *l4bdds: Disk 'rom/system-arm-ginger.img' size = 233384 KB (227 MB) flags=101 ad4* mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 Registering SWP/SWPB emulation handler RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 1024KiB [1 disk] into ram disk... done. EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities EXT4-fs (ram0): mounting ext2 file system using the ext4 subsystem EXT4-fs warning (device ram0): ext4_update_dynamic_rev:701: updating to rev 1 bd EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) VFS: Mounted root (ext2 filesystem) on device 1:0. Freeing unused kernel memory: 164K (02356000 - 0237f000) init: cannot open '/initlogo.rle' EXT4-fs (ram0): re-mounted. Opts: (null) init: Unable to open persistent property directory /data/property errno: 2 init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj inste. init: cannot find '/system/bin/servicemanager', disabling 'servicemanager' init: cannot find '/system/bin/vold', disabling 'vold' init: cannot find '/system/bin/netd', disabling 'netd' init: cannot find '/system/bin/debuggerd', disabling 'debuggerd' init: cannot find '/system/bin/rild', disabling 'ril-daemon' init: cannot find '/system/bin/app_process', disabling 'zygote' init: cannot find '/system/bin/mediaserver', disabling 'media' init: cannot find '/system/bin/dbus-daemon', disabling 'dbus' init: cannot find '/system/bin/installd', disabling 'installd' init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' init: cannot find '/system/bin/keystore', disabling 'keystore' init: cannot find '/system/bin/sh', disabling 'console' random: adbd urandom read with 6 bits of entropy available Thank you very much. -- Best Regards. Youren Shen.

2 1

Question about ext2 in Fiasco/L4re
by yang.wei9＠zte.com.cn 17 May '15

17 May '15

Hi, Does Fiasco/L4re can support for ext2 filesystem and flash drivers? If it hasn't, then how hard will to implement it or to port an existing implementation? Could provide some guides? -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

2 1

Question about RCU subsystem in Fiasco kernel.
by deng.chao1＠zte.com.cn 17 May '15

17 May '15

Hi, I find Fiasco has a implementation of RCU(Read-Copy Update)synchronization mechanism, but I did not find there was any usage of it in Fiasco kernel.. Is this implementation of RCU complete? Will there be any RCU's application in Fiasco kernel?

2 1

question about file mapping
by yang.wei9＠zte.com.cn 17 May '15

17 May '15

Hi, I create a file on tmpfs, and it read/write works fine. However, it cannot mmap, and returns EINVAL. I found the reason is that dataspace of the file is not valid. L4::Cap<L4Re::Dataspace> fds = fi->data_space() if (!fds.is_valid()) { return -EINVAL; } How to make it valid? Is there another method to do file mapping? Here is an example code snippet: ========================== const char* filename = "/tmp/testfile"; ret = mount("/", "tmp", "tmpfs", 0, 0); fd = open(filename, O_RDWR|O_CREAT); write 10K data into file addr = mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0); //return -1, and errno is EINVAL -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

2 1

anything wrong when call Thread::do_ipc?
by watermirror 17 May '15

17 May '15

hi. in the Thread_object::invoke, it call Thread::do_ipc like this: ct->do_ipc(f->tag(), partner, partner, have_rcv, sender, f->timeout(), f, rights); the second parameter's type is Thread*. but the Thread::do_ipc's implemention is like this: Thread::do_ipc(L4_msg_tag const &tag, bool have_send, Thread *partner, bool have_receive, Sender *sender, L4_timeout_pair t, Syscall_frame *regs, L4_fpage::Rights rights) {...} the second parameter's type is bool. is there anything wrong with the code, or i have make some mistakes?

2 1

the Thread::do_ipc's parameter
by watermirror 17 May '15

17 May '15

Hi, in the method Thread::do_ipc, there's a parameter named 'partner'.what is the 'partner' used for?

2 1

Fiasco & L4 boot performance
by Arttu Pulli 11 May '15

11 May '15

Hi, I'm working on optimizing the boot time of our Fiasco/L4Re based system. So far I've implemented some simple optimizations, like using fixed delay loop calibration value, disabling prints (is there some centralized way to disable all printing for the whole system?), and removing all unnecessary IO configurations which helped quite a bit. However, I'm pretty new to L4 and Fiasco, so I wanted to ask if you'd have some tips & tricks (no matter how arcane) on improving either the boot performance or reducing the resulting image size? My current boot time on an iMX6Q board from after U-Boot gives execution to L4 to my own L4 app is ~225 ms, and the resulting image size is 2.8 MB (1.2 MB LZO'ed). Do those numbers sound like there is anything to be gained anymore, or are those close to some maybe-known lower limits already? Regarding IO initialization, is there any way to perform some of the IO inits later on instead of when IO starts during boot time? My goal is to have my own L4 app running as fast as possible, and boot L4Linux after that. The problem is, the IO configs for the L4Linux take a lot of time, so I'd much rather invoke them at the latest possible moment. I've also removed all unnecessary modules from the modules.list configuration file, I take it that this means no unnecessary stuff is added to the image even though most everything is compiled at build time? Best regards, Arttu

2 1

Re: Testing Fiasco.OC+L4re on ODROID-X2(Exynos4412)
by Reinier Millo Sánchez 11 May '15

11 May '15

Hi Adam >> > FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, >> > p: dbl/sngl >> > >> > KERNEL: Warning: No page-fault handler for 0xee202214, error >> > 0x94000848, pc f0039420 >> > >> >Somebody have tested Fiasco.OC+L4re on ODROID-X2 or another Exynos 4412 >> >platform? > On this platform this seems to be some pattern. However, last time I > tried it worked for me. So, hmm, could you try another compiler version > and see if it changes behavior? Maybe this gives us some hints. I'm using a linaro toolchain (gcc-linaro-arm-linux-gnueabihf-4.8-2014.03_x86_64). I have tried the arm-none-eabi toolchain in Debian repository but fails compiling the snapshot. I have made some progress trying to run FiascoOC+L4re on Odroid-X2. There are some changes that I have made: I have modified the file "l4/mk/platforms/exynos4.conf" adapting Exynos4's platform to Odroid-X2. In this case the RAM size differs (Odroid-X2 have 2Gb). In this file I have configured the UART for serial output (I'm using UART 1). PLATFORM_RAM_BASE = 0x40000000 - PLATFORM_RAM_SIZE_MB = 1024 + PLATFORM_RAM_SIZE_MB = 2047 + PLATFORM_UART_NR = 1 Booting the generated image I have detected that bootstrap's server is not using UART 1 for output. I have modified the "init" function on "l4/pkg/bootstrap/server/src/platform/exynos.cc" to use the configured UART on the platform file modified above. unsigned long uart_base; - unsigned uart_nr = 2; + unsigned uart_nr = PLATFORM_UART_NR; I have tried to compile and test the image on the Odroid-X2, but fails the execution, this is the serial output: L4 Bootstrapper Build: #18 Sat May 2 15:56:00 CDT 2015, 4.8.3 20140303 (prerelease) Scanning up to 2047 MB RAM, starting at offset 32MB Memory size is 2047MB (40000000 - bfefffff) Limiting 'RAM' region [ 40000000, bfefffff] { 7ff00000} to [ 40000000, bcffffff] { 7d000000} due to 3024 MB address limit RAM: 0000000040000000 - 00000000bcffffff: 2048000kB Total RAM: 2000MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 5 modules behind 41100000 moving module 02 { 410b4000-410e565f } -> { 411a5000-411d665f } [202336] moving module 01 { 410aa000-410b3377 } -> { 4119b000-411a4377 } [37752] moving module 00 { 41043000-410a9daf } -> { 41134000-4119adaf } [421296] moving module 04 { 41029000-410425b3 } -> { 4111a000-411335b3 } [103860] moving module 03 { 4100f000-41028493 } -> { 41100000-41119493 } [103572] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x40002000 Regions of list 'regions' [ 40000000, 400000e3] { e4} Root mbi_rt [ 40001000, 40001aff] { b00} Kern fiasco [ 40002000, 40076fff] { 75000} Kern fiasco [ 40090000, 4009681b] { 681c} Sigma0 sigma0 [ 40098000, 4009e177] { 6178} Sigma0 sigma0 [ 40140000, 4018b4ab] { 4b4ac} Root moe [ 41000000, 4100e4ff] { e500} Boot bootstrap [ 41100000, 41133fff] { 34000} Root Module API Version: (87) experimental Sigma0 config ip:40090100 sp:00000000 Roottask config ip:4014020c sp:00000000 Starting kernel fiasco at 400012c8 Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf0063a50-0xf00644d0) Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl KERNEL: Warning: No page-fault handler for 0xee202214, error 0x94000848, pc f0039420 I have been testing and changing the compiling configuration. Using the below configuration to compile Fiasco.OC, the system boots and hangs at "Calibrating timer loop...": Platform Timer -> Multi-core timer Use ExtGic -> True Execution Model -> TrustZone normal side Secure Monitor Interface -> Mobicore Enable multi processor support -> True Maximal supported number of CPUs -> 4 This is the serial output when tested the image on Odroid-X2: L4 Bootstrapper Build: #56 Tue May 5 01:08:40 CDT 2015, 4.8.3 20140303 (prerelease) Scanning up to 2047 MB RAM, starting at offset 32MB Memory size is 2047MB (40000000 - bfefffff) Limiting 'RAM' region [ 40000000, bfefffff] { 7ff00000} to [ 40000000, bcffffff] { 7d000000} due to 3024 MB address limit RAM: 0000000040000000 - 00000000bcffffff: 2048000kB Total RAM: 2000MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 5 modules behind 41100000 moving module 02 { 41090000-410c165f } -> { 41181000-411b265f } [202336] moving module 01 { 41086000-4108f377 } -> { 41177000-41180377 } [37752] moving module 00 { 41043000-4108534f } -> { 41134000-4117634f } [271184] moving module 04 { 41029000-410425b3 } -> { 4111a000-411335b3 } [103860] moving module 03 { 4100f000-41028493 } -> { 41100000-41119493 } [103572] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x40002000 Regions of list 'regions' [ 40000000, 400000e3] { e4} Root mbi_rt [ 40001000, 40001aff] { b00} Kern fiasco [ 40002000, 4004efff] { 4d000} Kern fiasco [ 40090000, 4009681b] { 681c} Sigma0 sigma0 [ 40098000, 4009e177] { 6178} Sigma0 sigma0 [ 40140000, 4018b4ab] { 4b4ac} Root moe [ 41000000, 4100e4ff] { e500} Boot bootstrap [ 41100000, 41133fff] { 34000} Root Module API Version: (87) experimental Sigma0 config ip:40090100 sp:00000000 Roottask config ip:4014020c sp:00000000 Starting kernel fiasco at 400012c8 Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf0040110-0xf0040b18) Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl Watchdog initialized SERIAL ESC: allocated IRQ 85 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: unknown compiled with gcc 4.8.3 for Samsung Exynos [] Build: #68 Tue May 5 01:08:28 CDT 2015 Per_cpu_data_alloc: (orig: 0xf0040110-0xf0040b18) KERNEL: Warning: Buddy::alloc: Size mismatch: a08 v 1000 Allocate 2568 bytes (3KB) for CPU[4] local storage (offset=13a4ef0, 0xf13e5000-0xf13e5a08) Timer for CPU0 is at IRQ 28 Number of CPUs: 4 Calibrating timer loop... Per_cpu_data_alloc: (orig: 0xf0040110-0xf0040b18) KERNEL: Warning: Buddy::alloc: Size mismatch: a08 v 1000 Allocate 2568 bytes (3KB) for CPU[1] local storage (offset=13a6ef0, 0xf13e7000-0xf13e7a08) FPU1: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl Per_cpu_data_alloc: (orig: 0xf0040110-0xf0040b18) Timer for CPU1 is at IRQ 28 KERNEL: Warning: Buddy::alloc: Size mismatch: a08 v 1000 CPU[1]: goes to idle loop Allocate 2568 bytes (3KB) for CPU[2] local storage (offset=13a9ef0, 0xf13ea000-0xf13eaa08) FPU2: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl Per_cpu_data_alloc: (orig: 0xf0040110-0xf0040b18) Timer for CPU2 is at IRQ 28 KERNEL: Warning: Buddy::alloc: Size mismatch: a08 v 1000 CPU[2]: goes to idle loop Allocate 2568 bytes (3KB) for CPU[3] local storage (offset=13acef0, 0xf13ed000-0xf13eda08) FPU3: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl Timer for CPU3 is at IRQ 28 CPU[3]: goes to idle loop I think that the problem now is with the Exynos4's Timers, but i have been reviewing the implementations and it seems fine. Is there anything wrong on my configuration or somebody have any idea? Best regards -- Lic. Reinier Millo Sánchez Centro de Estudios de Informática Universidad Central "Marta Abreu" de Las Villas Carretera a Camajuaní Km 5 1/2 Santa Clara, Villa Clara, Cuba CP 54830 "antes de discutir ... respira; antes de hablar ... escucha; antes de escribir ... piensa; antes de herir ... siente; antes de rendirte ... intenta; antes de morir ... vive"

2 1

Re: Using a second UART to control a serial device
by Pflaum, Clemens 10 May '15

10 May '15

Hi L4 Hackers, Since i sadly still cant get the uart to work i have some more questions. 1. I've noticed that the offsets of all the registers in the /drivers-frst/uart/src/uart_pxa.cc are are incorrect by a multiple of 4. So if IER is defined to be at 0x01 it is actually at 0x04, respectivly the LCR which is said to be at 0x03 is actually at 0x0C. After I changed these values to reflect the allwinner A20 manual, the kernel stopped loading properly. It gets stuck on bootup at "Starting kernel...". In fact it does continue although at a pace of one character every 5 to 6 minutes. So after 30mins i had "L4 Bootstra" in the next line. My assumption is that my UART0 from which i run the console on my linux pc actually uses the uart_pxa driver with the incorrect register offset and it works for it. By changing the registers I somehow break my UART0. If I'm correct then I should be able to find the routine which the kernel uses to initilize UART0, to help me understand how to get UART3 to work. Sadly I couldn't find anything alike. 2.So i went on by writing a new uart_16550bananapi.cc with changed registers. It did infact solve the kernel not starting issue. I can now access and write to all of the uart registers... apart from the Line Control Register(LCR). It starts off with 0x03 written to it although it has a default of 0x00(in the a20 manual) as soon as i write 0x00 to it my console starts throwing out seemingly random chars: This code in the uart startup() function: scratch = _regs->read<unsigned char>(LCR); printf("\ncurrent LCR: %#010x\n", scratch); printf("Setting LCR to 0\n"); printf("This gets overritten\n"); _regs->write<unsigned char>(LCR, 0); /* clear line control register */ printf("It worked\n"); gives me this outpot on console: Maestro | Maestro | current LCR: 0x00000003 Maestro | Setting LCR to 0 Maese|iw�k�{m{[e|{m{[e|pp`'br�l�z{mos�pppppn{m{[e��r|{m{[e p�ot[ lLzppppp{m{[e|pq`�rppppp{m{ێm[e|pqlNzppppv{m{[e|pq`�rppppp{m{ێm[e q The same thing happens if i write 0x80 to it to add the DLAB bit that i need to access the two Divisor Latch registers to initilize the Baudrate for the first time. The 0x03 in LCR means that i run my Uart in 8N1 mode setting which my UART0 console is running aswell. Setting it to 0 means to run 5N1. So I assume for some reason it might somehow change my UART0 settings if i write to UART3 LCR reg. But the same error occurs if i write 0x83 to it to leave 8N1 on and set the DLAB bit, so that cant be the case can it? Without setting Baudrate however i obviously cant hope for UART3 to work. Thanks for any answers in advance, Clemens

3 8

about Ram_quota
by watermirror 08 May '15

08 May '15

hi, what is Ram_quota used for?

2 1

Static_object::construct
by watermirror 08 May '15

08 May '15

hi, template< typename T > class Static_object { public: .... template< typename... A > T *construct(A&&... args) { return new (_i) T(cxx::forward<A>(args)...); } ... }; this template class is defined in fiasco/src/types.h, what does the method 'construct' mean? i have tried to move this class to eclipse cdt project, but it can not be compiled correctly. how does this class be compiled in fiasco?

2 1

Testing Fiasco.OC+L4re on ODROID-X2(Exynos4412)
by Reinier Millo Sánchez 04 May '15

04 May '15

Hi comunity I'm trying to test the hello application on the ODROID-X2(Exynos4412) board. I'm using the Fiasco.OC+L4re snapshot(l4re-snapshot-2014092821). I have configured and compiled Fiasco.OC with support to Samsung Exynos4412: export SYSTEM_TARGET=arm-linux-gnueabihf- make BUILDDIR=build-foc make menuconfig make -j16 After that, I have compiled the entire L4re for armv7a (SamsungExynos4) make B=build-l4re make O=build-l4re ARCH=arm SYSTEM_TARGET=arm-linux-gnueabihf- menuconfig make O=build-l4re ARCH=arm SYSTEM_TARGET=arm-linux-gnueabihf- -j16 To generate the raw image have modified the conf/Makeconf.boot to set the Fiasco.OC build path and executed: make O=build-l4re ARCH=arm SYSTEM_TARGET=arm-linux-gnueabihf- rawimage E=hello I have copied the generated image into the SD card and tried to boot from u-boot: fatload mmc 0:1 0x41000000 hello.raw bootm 0x41000000 The system starts but stops execution. This is the serial output: Partition1: Start Address(0xc00), Size(0x40400) reading hello.raw 942080 bytes read Boot with zImage Starting kernel ... Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf0063a50-0xf00644d0) Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl KERNEL: Warning: No page-fault handler for 0xee202214, error 0x94000848, pc f0039420 Somebody have tested Fiasco.OC+L4re on ODROID-X2 or another Exynos 4412 platform? Best regards -- Lic. Reinier Millo Sánchez Centro de Estudios de Informática Universidad Central "Marta Abreu" de Las Villas Carretera a Camajuaní Km 5 1/2 Santa Clara, Villa Clara, Cuba CP 54830 "antes de discutir ... respira; antes de hablar ... escucha; antes de escribir ... piensa; antes de herir ... siente; antes de rendirte ... intenta; antes de morir ... vive"

2 1

Experimenting the vm-tz example on the Freescale i.mx6 SDB
by Mahdi Aichouch 04 May '15

04 May '15

Hello, I am trying to experiment the "vm-tz" example on the Freescale i.mx6 SDB board. At first, my goal is to understand the example, thus I am interested in running a simple test kernel instead of a full linux kernel. Specifically, I am trying to reproduce the experimentation of the article related to the trustzone implementation on Fiasco.OC L4re, "ARM Trustzone as a Virtualization Technique in Embedded Systems". In particular, it is mentioned in the article at the "Implementation" paragraph that "Multiplexing two or more OS is supported by our design." I would like to investigate this point. I created a new entry to generate the vm-tz binary. I added the following entry to the "src/l4/conf/modules.list" file : entry tz_vm roottask moe --init=rom/vm-tz module l4re module vm-tz Is my configuration entry correct, is there any missing modules that are required by the example? I tested the binary on the board using tftp, and I obtained the following results: L4 Bootstrapper Build: #12 Tue Mar 17 12:10:02 CET 2015, 4.8.3 20140320 (prerelease) Scanning up to 1024 MB RAM, starting at offset 32MB Memory size is 1024MB (10000000 - 4fffffff) RAM: 0000000010000000 - 000000004fffffff: 1048576kB Total RAM: 1024MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 5 modules behind 11100000 moving module 02 { 110a5000-110de63f } -> { 11195000-111ce63f } [235072] moving module 01 { 1109b000-110a438b } -> { 1118b000-1119438b } [37772] moving module 00 { 11044000-1109a0c7 } -> { 11134000-1118a0c7 } [352456] moving module 04 { 1102a000-11043597 } -> { 1111a000-11133597 } [103832] moving module 03 { 11010000-11029473 } -> { 11100000-11119473 } [103540] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x10002000 Regions of list 'regions' [ 10000000, 100000e3] { e4} Root mbi_rt [ 10001000, 10001aff] { b00} Kern fiasco [ 10002000, 10062fff] { 61000} Kern fiasco [ 10090000, 10096edf] { 6ee0} Sigma0 sigma0 [ 10098000, 1009e177] { 6178} Sigma0 sigma0 [ 10140000, 10171d77] { 31d78} Root moe [ 10178000, 101934ab] { 1b4ac} Root moe [ 11000000, 1100f4ff] { f500} Boot bootstrap [ 11100000, 11133fff] { 34000} Root Module API Version: (87) experimental Sigma0 config ip:10090100 sp:00000000 Roottask config ip:10140260 sp:00000000 Starting kernel fiasco at 100012c8 Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl L2: ID=410000c7 Type=9e340340 Aux=02070000 WMask=ffff S=0 L2: Type L2C-310 Size = 1024kB Ways=16 Waysize=64 SERIAL ESC: allocated IRQ 58 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rexported compiled with gcc 4.8.3 for i.MX6 [] Build: #3 Wed Mar 11 16:43:41 CET 2015 Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 10002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:10000000;10000fff] [0:10063000;1008ffff] [0:10097000;10097fff] [0:1009f000;1013ffff] [4:10140000;10171fff] [0:10172000;10177fff] [4:10178000;10193fff] [0:10194000;110fffff] [4:11100000;11133fff] [0:11134000;4effffff] IOMEM:---------------------- [0:0;fffffff] [0:50000000;ffffffff] MOE: Hello world MOE: found 1031220 KByte free memory MOE: found RAM from 10000000 to 4f000000 MOE: allocated 1008 KByte for the page array @0x10194000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [11100000-11119474] [C:503000] l4re BOOTFS: [1111a000-11133598] [C:504000] vm-tz MOE: cmdline: moe --init=rom/vm-tz MOE: Starting: rom/vm-tz MOE: loading 'rom/vm-tz' Vmm started terminate called after throwing an instance of 'N2L413Runtime_errorE' MOE: task 270000679 exited with 127 The code stops at the beginning when it tries to create a VM : L4Re::chksys(env->factory()->create_vm(vm)); After reading through the code, I saw that the code example is expecting a linux-image and an initrd to be provided. Is it possible to tell me where these should be added in the build directory? In my test case, the linux-image will be replaced by a simple kernel image. Could someone help me to correct my test case. Many thanks in advance. Best regards, Mahdi

2 19

context::regs
by watermirror 03 May '15

03 May '15

hi,the implemention of Context::regs() is like this: return reinterpret_cast<Entry_frame*>(Cpu::stack_align(reinterpret_cast<Mword>(this + Size)) -1; how this algorithm came out?i think the memory of the object is allocated by c++ compiler, but why '(this + Size)' could get Entry_frame of a thread?

2 1

the syscall stack frame and Context::regs method
by watermirror 28 Apr '15

28 Apr '15

hi, i am reading the code about system call. after the sys_ipc_wrapper (in file kern/syscalls.cpp) is called.it get the thread's pointer by current_thread and then get the Syscall_frame. the code is like this: ... Thread *curr=current_thread(); Syscall_frame *f = curr->regs(); ... i can not understand the relationship between curr->regs() and the system call's stack frame.

2 1

about sysenter
by watermirror 28 Apr '15

28 Apr '15

hi ,in the file :l4re/pkg/l4sys/include/ARCH-x86/ipc-invoke.h, the comments says: We use ecx to store the user-level espand save eip onto the stack. but where could if find the corresponding code?

2 1

the first instruction in entry_sys_fast_ipc_c
by watermirror 28 Apr '15

28 Apr '15

hi, after entered the entry_sys_fast_ipc_c through sysenter, why the first instruction is 'pop %esp'?

2 1

How to solve the problem about multiple definition of clk_enable?
by Youren Shen 28 Apr '15

28 Apr '15

Hi, L4 hackers, To solve the problem about "undefined reference to `clk_get_rate'", I select COMMON_CLK in config L4_PLATFORM_GENERIC. But when I build the L4Linux this occurs: multiple definition of `clk_enable' l4linux/arch/l4/kernel/arch-arm/l4.c:63: first defined here So, Should I disable L4_CLK_NOOP in L4_PLATFORM_GENERIC? Thank you very much! Best Regards! Youren Shen

2 1

Re: How L4Linux Linked the header file?
by Youren Shen 28 Apr '15

28 Apr '15

Hi, Adam, Sorry to disturb you again. I find the reason of this problem is because the "config GENERIC_CLOCKEVENTS" is removed from file arch/arm/Kconfig after Kernel 3.4. As a result, the GENERIC_CLOCKEVENTS is not defined in the arch/l4/kconfig.arm. And the CONFIG_SMP depends on GENERIC_CLOCKEVENTS. So the CONFIG_GENERIC_CLOCKEVENTS and CONFIG_SMP will be unmask in build processes. Is there any way to get previous version of L4Linux? For instance, If I can get the source code of the L4Linux 3.4, it will be very helpful. Thank you very much for your help! On Sun, Apr 26, 2015 at 12:18 AM, Youren Shen <shenyouren(a)gmail.com> wrote: > Hi, Adam > I'm not so sure how to reply the mail in L4-hackers-list, So I CC to both > the List mail address and thread mail address. > > Thank you for your reply, and that really helps. > > I find that those error occurred because the CONFIG_SMP and > CONFIG_GENERIC_CLOCKEVENTS_BUILD is not set in .config. > > I try to config them by 'make menuconfig' but there is none entry about > CONFIG_SMP or CONFIG_GENERIC_CLOCKEVENTS_BUILD appeared in menuconfig. So > I change the .config file directly, but once I invoke "make", the .config > will be rewrite. > > Would you mind give me any guide about how to set them? > > Thank you very much. > >> >> >> Hi, >> >> On Sat Apr 18, 2015 at 22:26:15 +0800, Youren Shen wrote: >> > I'm trying to port L4Linux 3.14 to Linux Kernel 3.4. But when I complied >> > the kernel, this error happened: >> > >> /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/main.c: >> > In function 'cpu0_startup': >> > >> /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/main.c:2124:2: >> > error: implicit declaration of function 'set_my_cpu_offset' >> > [-Werror=implicit-function-declaration] >> > >> > I checked main.c file: >> > >> > #include <asm/unistd.h> >> > #include <asm/percpu.h> >> > #include <asm/generic/l4lib.h> >> > >> > So I add one percpu.h file with definition of 'set_my_cpu_offset' in >> > >> /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/include/asm/arch-arm/, >> > however this error still happened. >> > >> > Then I add the definition of this function to >> > >> /home/shenyouren/workspace/kernel/kernel_exynos5250/include/linux/percpu.h, >> > then the error message will not show. >> > >> > Also, discard the change in $(src)/include/linux/percpu.h, then I change >> > the main.c file to include absolute path of percpu.h. >> > >> > #include <asm/unistd.h> >> > #include >> > >> </home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/include/asm/arch-arm/percpu.h> >> > #include <asm/generic/l4lib.h> >> > >> > It passed the complied to. >> >> When you put a header file in arch/l4/include/asm/arch-arm/ including it >> via <asm/foo.h> should work. >> >> > So that is say, the #include <asm/percpu.h> is reference to >> > src/include/linux/percpu.h. That really strange. >> >> So, include <linux/percpu.h> in main.c right away? >> >> The L4 part of L4Linux you're looking at is for 3.14 and you apply it to >> Linux 3.4, please expect that things are different and need adaption. >> >> > I do not change the Makefile in arch/l4, and I really confused about >> this >> > error. >> > Now this problem occurs to me again, when complied the >> > arch/l4/kernel/timer.c file, this error happened: >> > >> > >> /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/timer.c:153:35: >> > warning: 'struct clock_event_device' declared inside parameter list >> > [enabled by default] >> > >> /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/timer.c:153:35: >> > warning: its scope is only this definition or declaration, which is >> > probably not what you want [enabled by default] >> > >> > but the definition of this to file should be defined in clockchips.h >> which >> > is include in timer.c: >> > >> > #include <linux/timex.h> >> > #include <linux/clockchips.h> >> > #include <linux/irq.h> >> > >> > Thank you for your reading, I just want to know what's the rule of >> L4Linux >> > header file linking, and solve this problem. >> > I'd be so appreciated if anyone can give me some help! >> >> There's a #ifdef CONFIG_GENERIC_CLOCKEVENTS_BUILD in clockchips.h. >> Not defined? >> >> >> >> Adam >> -- >> Adam adam(a)os.inf.tu-dresden.de >> Lackorzynski http://os.inf.tu-dresden.de/~adam/ >> >> -- > Best Regards. > Youren Shen. > -- Best Regards. Youren Shen.

2 1

Re: How L4Linux Linked the header file?
by Youren Shen 25 Apr '15

25 Apr '15

Hi, Adam I'm not so sure how to reply the mail in L4-hackers-list, So I CC to both the List mail address and thread mail address. Thank you for your reply, and that really helps. I find that those error occurred because the CONFIG_SMP and CONFIG_GENERIC_CLOCKEVENTS_BUILD is not set in .config. I try to config them by 'make menuconfig' but there is none entry about CONFIG_SMP or CONFIG_GENERIC_CLOCKEVENTS_BUILD appeared in menuconfig. So I change the .config file directly, but once I invoke "make", the .config will be rewrite. Would you mind give me any guide about how to set them? Thank you very much. > > > Hi, > > On Sat Apr 18, 2015 at 22:26:15 +0800, Youren Shen wrote: > > I'm trying to port L4Linux 3.14 to Linux Kernel 3.4. But when I complied > > the kernel, this error happened: > > > /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/main.c: > > In function 'cpu0_startup': > > > /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/main.c:2124:2: > > error: implicit declaration of function 'set_my_cpu_offset' > > [-Werror=implicit-function-declaration] > > > > I checked main.c file: > > > > #include <asm/unistd.h> > > #include <asm/percpu.h> > > #include <asm/generic/l4lib.h> > > > > So I add one percpu.h file with definition of 'set_my_cpu_offset' in > > > /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/include/asm/arch-arm/, > > however this error still happened. > > > > Then I add the definition of this function to > > > /home/shenyouren/workspace/kernel/kernel_exynos5250/include/linux/percpu.h, > > then the error message will not show. > > > > Also, discard the change in $(src)/include/linux/percpu.h, then I change > > the main.c file to include absolute path of percpu.h. > > > > #include <asm/unistd.h> > > #include > > > </home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/include/asm/arch-arm/percpu.h> > > #include <asm/generic/l4lib.h> > > > > It passed the complied to. > > When you put a header file in arch/l4/include/asm/arch-arm/ including it > via <asm/foo.h> should work. > > > So that is say, the #include <asm/percpu.h> is reference to > > src/include/linux/percpu.h. That really strange. > > So, include <linux/percpu.h> in main.c right away? > > The L4 part of L4Linux you're looking at is for 3.14 and you apply it to > Linux 3.4, please expect that things are different and need adaption. > > > I do not change the Makefile in arch/l4, and I really confused about this > > error. > > Now this problem occurs to me again, when complied the > > arch/l4/kernel/timer.c file, this error happened: > > > > > /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/timer.c:153:35: > > warning: 'struct clock_event_device' declared inside parameter list > > [enabled by default] > > > /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/timer.c:153:35: > > warning: its scope is only this definition or declaration, which is > > probably not what you want [enabled by default] > > > > but the definition of this to file should be defined in clockchips.h > which > > is include in timer.c: > > > > #include <linux/timex.h> > > #include <linux/clockchips.h> > > #include <linux/irq.h> > > > > Thank you for your reading, I just want to know what's the rule of > L4Linux > > header file linking, and solve this problem. > > I'd be so appreciated if anyone can give me some help! > > There's a #ifdef CONFIG_GENERIC_CLOCKEVENTS_BUILD in clockchips.h. > Not defined? > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > -- Best Regards. Youren Shen.

1 0

(no subject)
by deng.chao1＠zte.com.cn 24 Apr '15

24 Apr '15

Hi: I am reading the code of fiasco kernel.I have a question about the function "Context::schedule". At line 894 in kernel/fiasco/src/kern/context.cpp： "while (EXPECT_FALSE(current_cpu != access_once(&_home_cpu)))" As I know, the variable "_home_cpu" indicates the CPU number which the thread that invokes the “schedue ” as a member function is running on。And the variable “current cpu” indicates the CPU number now this code fragment is running on。 The condition test tells me that it seems the class Context's member function "schedule" will run on a different cpu some time . If it does so, some extra work will need to be done in the "schedule" function. I have searched all of the fiasco kernel sources, but I did not find this special context. So would anybody please tell me whether there has a situation that the "schedule" function will run on different CPU， why does it happen？ Thanks！

2 1

where is the call_bootstrap?
by 水镜 24 Apr '15

24 Apr '15

Hi, in the file main-ia32-32.cpp, there's a line(line 60): call call_bootstrap where could i find the implemention of the call_bootstrap?

2 1

Static_object in fiasco kernel
by 水镜 23 Apr '15

23 Apr '15

hi, what is the Static_object in fiasco kernel used for?

2 1

How L4Linux Linked the header file?
by Youren Shen 23 Apr '15

23 Apr '15

Hi, I'm trying to port L4Linux 3.14 to Linux Kernel 3.4. But when I complied the kernel, this error happened: /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/main.c: In function 'cpu0_startup': /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/main.c:2124:2: error: implicit declaration of function 'set_my_cpu_offset' [-Werror=implicit-function-declaration] I checked main.c file: #include <asm/unistd.h> #include <asm/percpu.h> #include <asm/generic/l4lib.h> So I add one percpu.h file with definition of 'set_my_cpu_offset' in /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/include/asm/arch-arm/, however this error still happened. Then I add the definition of this function to /home/shenyouren/workspace/kernel/kernel_exynos5250/include/linux/percpu.h, then the error message will not show. Also, discard the change in $(src)/include/linux/percpu.h, then I change the main.c file to include absolute path of percpu.h. #include <asm/unistd.h> #include </home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/include/asm/arch-arm/percpu.h> #include <asm/generic/l4lib.h> It passed the complied to. So that is say, the #include <asm/percpu.h> is reference to src/include/linux/percpu.h. That really strange. I do not change the Makefile in arch/l4, and I really confused about this error. Now this problem occurs to me again, when complied the arch/l4/kernel/timer.c file, this error happened: /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/timer.c:153:35: warning: 'struct clock_event_device' declared inside parameter list [enabled by default] /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/timer.c:153:35: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default] but the definition of this to file should be defined in clockchips.h which is include in timer.c: #include <linux/timex.h> #include <linux/clockchips.h> #include <linux/irq.h> Thank you for your reading, I just want to know what's the rule of L4Linux header file linking, and solve this problem. I'd be so appreciated if anyone can give me some help! -- Best Regards. Youren Shen.

2 1

How to compile the fiasco kernel test directory?
by Liu Xiaodong 23 Apr '15

23 Apr '15

Hi,I got a tar ball(l4re-snapshot-2014092821.tar.bz2) from fiasco website. I see a directory for test under the fiasco kernel source path: /l4re-snapshot-2014092821/src/kernel/fiasco/src/test/. But I can't compile them in the normal way, such as that you discrbed in the website http://os.inf.tu-dresden.de/fiasco/build.html. I really want to do some kernel tests on fiaso. If you can tell me how to compile the fiasco kernel test directory, it will be very helpful, and I will appreciate it. By the way, the test source code seems to not be included completely. Such as /l4re-snapshot-2014092821/src/kernel/fiasco/src/test/space/space.t.cc #include <iostream> #include <iomanip> #include <cassert> using namespace std; #include <flux/page.h> #include "space.h" int main() { // // Make task 4 the chief of task 5 // assert (space_index_t (5).lookup () == 0); assert (space_index_t (5).chief () == 0); assert (space_index_t (5).set_chief (space_index_t(0), space_index_t(4))); assert (space_index_t (5).lookup () == 0); assert (space_index_t (5).chief () == 4); ...... } I can't find headfile "space.h" in the tar ball, and there is no define about "space_index_t" too. can you tell me why? thanks again! -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

2 3

How to do quickly in order to starting fiasco with a console shell?
by zhou.li9＠zte.com.cn 23 Apr '15

23 Apr '15

How to do quickly in order to starting fiasco with a console shell? After copying src/l4/conf/examples/x86-fb.list to src/l4/conf/modules.list,I use QEMU to boot,the boot process appears to be normal: ....... fbdrv | Starting server loop mag | mapped frame buffer at 0x200000 mag | View::Info: mag | flags: 0 mag | size: 1280x1024 pos: 0, 0 mag | bytes_per_line: 2560 mag | buffer_offset: 0 mag | RGBA(2): 5(11):6(5):5(0):0(0) mag | memory 200000-600000 mag | Plugin: Mag_client service started mag | Plugin: Frame-buffer service started mag | L4INPUT native mode activated mag | L4INPUT: !!! W A R N I N G !!! mag | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. mag | L4INPUT: !!! W A R N I N G !!! mag | serio: i8042 AUX port at 0x60,0x64 irq 12 mag | serio: i8042 KBD port at 0x60,0x64 irq 1 mag | input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1 mag | input: AT Translated Set 2 keyboard on isa0060/serio0 mag | connect "ImExPS/2 Generic Explorer Mouse", isa0060/serio1/input0 mag | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 spectrum| x:640 y:480 bit/pixel:16 bytes/line:1280 But How can I input some shell command? -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

3 4

Re: Using a second UART to control a serial device
by Pflaum, Clemens 20 Apr '15

20 Apr '15

Thank you for your fast response, I've adapted your code to my needs (using the uart_pxa driver in drivers-frst). It compiles and starts up fine on the BananaPi but sadly I'm not getting any response on the uart3 pins... It seems to have a problem in the l4\pkg\drivers-frst\uart\src\uart_pxa.cc when calling the Uart_16550::startup(regs). I get a few wierd boxlike characters on the console and then "failed to startup uart regs". This is my init() : #define IRQ_NUM 86 #define UART_BASE 0x01C28C00 . . . bool Maestro_server::init() { l4_addr_t virt_base = 0; if (l4io_request_iomem((l4_addr_t)UART_BASE, 0x1000, L4IO_MEM_NONCACHED, &virt_base)) { printf("maestro-drv: request io-memory from l4io failed.\n"); return false; } printf("maestro-drv: virtual base at:%lx\n", virt_base); L4::Io_register_block_mmio *regs = new L4::Io_register_block_mmio(virt_base); _uart = new (malloc(sizeof(L4::Uart_16550))) L4::Uart_16550((unsigned long) 115200); if(!(_uart->startup(regs))){ printf("failed to startup uart regs!"); } if(!(_uart->change_mode(0x00 | 0x03 | 0x00, 115200))){ printf("failed to change uart mode!"); } the rest of it is equal to the serial-drv example. Any idea what i couldve done wrong? regard, Clemens

1 0

Using multiple NICs within one application
by Stark, Josef 19 Apr '15

19 Apr '15

Hello, is it possible to use more than one network card in one L4Re-application and how would I do that? I would guess from the example lwip lua-script that I had to create a separate shm-area and/or communication channel (for ankh-sessions) for each device that my app wants to access, but I don't know how I would supply these additional channels to ankh and if this would be enough to enable multi-NIC networking. Any help would be appreciated. Regards, Josef

1 0

Re: Using a second UART to control a serial device
by Reinier Millo Sánchez 18 Apr '15

18 Apr '15

Hi Clemens I have been testing something similar in other board (YSE5250-Exynos5). First you must guarantee that the UART device driver is compatible with the hardware or you must write an specific device driver. I have tried to make a GPS device driver using the S3C2410 UART based on the serial-drv package. To connect the uart on the user land with my server i have configured the HW.Device in a vbus with the IO server using this configuration: -- File: yse5250.devs local Hw = Io.Hw local Res = Io.Res Io.hw_add_devices { UART3 = Hw.Device { hid = "UART3"; Res.irq(86); Res.mmio(0x12C30000, 0x12C3ffff); } } To create the vbus, i have created the file yse5250.io: -- File: yse5250.io Io.add_vbusses { -- Create a virtual bus for a client and give access to UART3 uart03 = Io.Vi.System_bus(function () dev = wrap(Io.system_bus():match("UART3")); end); } To run my server using the UART3 on the vbus have used this configuration -- gps-drv.cfg -- Run GPS Driver for YSE5250 (Exynos 5250) require("L4"); -- Shortcuts local ld = L4.default_loader; local vbus_uart03 = ld:new_channel(); local platform_ctl = ld:new_channel(); local gps_srv = ld:new_channel(); -- Start the IO Server ld:start( { caps = { sigma0 = L4.cast(L4.Proto.Factory, L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; platform_ctl = platform_ctl:svr(); uart03 = vbus_uart03:svr(); }, log = { "IO Server", "green" }, l4re_dbg = L4.Dbg.Warn, }, "rom/io rom/yse5250.devs rom/yse5250.io"); -- Start the GPS Driver Server conected to UART3 ld:start( { caps = { gps_srv = gps_srv:svr(); vbus = vbus_uart03; }, log = {"GPS Driver","blue"} }, "rom/gps_drv"); The server code is very similar to: /pkg/serial-drv/server/src/main.cc But in my case i have adjusted the UART to use the S3C2410 uart. Best regards On 04/18/2015 06:00 AM, l4-hackers-request(a)os.inf.tu-dresden.de wrote: > Message: 1 > Date: Fri, 17 Apr 2015 12:03:46 +0200 > From: "Pflaum, Clemens"<clemens.pflaum(a)mytum.de> > To:l4-hackers@os.inf.tu-dresden.de > Subject: Using a second UART to control a serial device > Message-ID:<4a79357eec3b3359e8b09e16a3fe0994(a)roundcube.lrz.de> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > Hi L4 Hackers, > Im currently running Fiasco.OC with L4Re on my BananaPi. I'm trying to > control a serial device (Pololu Servo Controller) by sending a small > series of Bytes over a second UART ( not UART 0 since im getting the > console from there ). Via documentation I've found out that UART 3 is at > 0x01C28C00 and is a U6_16550A, so I'm hoping the driver in > /pkg/drivers-frst/uart/src/uart_pxa.cc will be compatible with that. > Where and how would I have to go about initiating my UART 3? By writing > a new platform for BPi in /pkg/bootstrap/server/src/platform? The > function set_stdio_uart(&_uart); made me think its only the "console" > UART. Or do I have to instantiate some kind of Hw.Device like the gpio > in /pkg/io/config/arm-omap3.devs and put it on a new vBus like in > /pkg/io/doc/example.io ? > > Or am I thinking way too complicated and it is as simple as editing the > /pkg/serial-drv/server/src/main.cc : > > bool > Serial_drv::init() > { > int irq_num = 37; > // How can i find out what this number refers to/do i have to > change it at all? > l4_addr_t phys_base = 0x1000a000; > // change to 0x01C28C00 > #if 0 > int irq_num = 74; > l4_addr_t phys_base = 0x49020000; > #endif > l4_addr_t virt_base = 0; > > if (l4io_request_iomem(phys_base, 0x1000, L4IO_MEM_NONCACHED, > &virt_base)) > { > printf("serial-drv: request io-memory from l4io failed.\n"); > return false; > } > printf("serial-drv: virtual base at:%lx\n", virt_base); > > L4::Io_register_block_mmio *regs = new > L4::Io_register_block_mmio(virt_base); > _uart = new (malloc(sizeof(L4::Uart_pl011))) L4::Uart_pl011(24019200); > //change to L4::Uart_pxa(what does this number mean?) > _uart->startup(regs); > > > Thanks for any answers in advance. > > Regards, > Clemensc...(a)mytum.de -- Lic. Reinier Millo Sánchez Centro de Estudios de Informática Universidad Central "Marta Abreu" de Las Villas Carretera a Camajuaní Km 5 1/2 Santa Clara, Villa Clara, Cuba CP 54830 "antes de discutir ... respira; antes de hablar ... escucha; antes de escribir ... piensa; antes de herir ... siente; antes de rendirte ... intenta; antes de morir ... vive"

1 0

Using a second UART to control a serial device
by Pflaum, Clemens 17 Apr '15

17 Apr '15

Hi L4 Hackers, Im currently running Fiasco.OC with L4Re on my BananaPi. I'm trying to control a serial device (Pololu Servo Controller) by sending a small series of Bytes over a second UART ( not UART 0 since im getting the console from there ). Via documentation I've found out that UART 3 is at 0x01C28C00 and is a U6_16550A, so I'm hoping the driver in /pkg/drivers-frst/uart/src/uart_pxa.cc will be compatible with that. Where and how would I have to go about initiating my UART 3? By writing a new platform for BPi in /pkg/bootstrap/server/src/platform? The function set_stdio_uart(&_uart); made me think its only the "console" UART. Or do I have to instantiate some kind of Hw.Device like the gpio in /pkg/io/config/arm-omap3.devs and put it on a new vBus like in /pkg/io/doc/example.io ? Or am I thinking way too complicated and it is as simple as editing the /pkg/serial-drv/server/src/main.cc : bool Serial_drv::init() { int irq_num = 37; // How can i find out what this number refers to/do i have to change it at all? l4_addr_t phys_base = 0x1000a000; // change to 0x01C28C00 #if 0 int irq_num = 74; l4_addr_t phys_base = 0x49020000; #endif l4_addr_t virt_base = 0; if (l4io_request_iomem(phys_base, 0x1000, L4IO_MEM_NONCACHED, &virt_base)) { printf("serial-drv: request io-memory from l4io failed.\n"); return false; } printf("serial-drv: virtual base at:%lx\n", virt_base); L4::Io_register_block_mmio *regs = new L4::Io_register_block_mmio(virt_base); _uart = new (malloc(sizeof(L4::Uart_pl011))) L4::Uart_pl011(24019200); //change to L4::Uart_pxa(what does this number mean?) _uart->startup(regs); Thanks for any answers in advance. Regards, Clemens c...(a)mytum.de

1 0

the kernel's output
by 水镜 17 Apr '15

17 Apr '15

hi , there're a lot of printf in fiasco kernel, but i can not seen any output on the screen. how could i turn these things on?

2 1

the ldscripts of L4Re
by 水镜 16 Apr '15

16 Apr '15

hi, the L4Re has three ldscripts: main_dyn.ld main.rel.ld main.stat.ld what are the differences?

2 1

How to track execution process of fiasco user mode applications？
by zhou.li9＠zte.com.cn 16 Apr '15

16 Apr '15

I found that fiasco does not support GDB, in order to track execution process of fiasco user mode applications,what method can be used? -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

2 1

mmu in bootstrap
by 水镜 16 Apr '15

16 Apr '15

hi, i want to know, whether the bootstrap in l4re(x86) will initialize the MMU, setup pagetable? i am trying to debug the fiasco with gdb and qemu. when i attach to the qemu before system startup, i can check memory like 0x1100000.after the system startup, the gdb tell me can not access memory if i check 0x1100000 again.

2 1

IPC stream magic
by teclis High Elf 11 Apr '15

11 Apr '15

I have a complex nested structure that looks something like this: typedef struct struct_A { int i; struct struct_B[5]; int j; } using an IPC stream I do: struct_A a; ios.put(a); and then in the server process I do: struct_A b; ios.get(b); ( ios is a L4::Ipc::Iostream ) and magically my complex nested structure reappears with all the data intact in the server process running in another address space. As the IPC Streams are not well documented would someone be able to explain to me how my complex nested structure got automatically marshalled in the client and unmarshalled in the server process?

2 1

Re: ARM with Qemu
by Nicolas VARONA 09 Apr '15

09 Apr '15

Hi, Thanks for your answer and your help. >Could also be the uart issue? But entering jdb always works for me. Even if I can't give inputs to the bare metal application on Qemu, I can also enter into the JDB. Is that mean that all interruptions are well handled? So the uart issue seems more probable. >Which kind of panic? I firstly tested my L4linux on Qemu for the Zinq board and the boot finishes well (with the problem of inputs that I told you before). Nonetheless, with the same image on the board, I have this message: [...] Freeing unused kernel memory: 116K (0230f000 - 0232c000) potentially unexpected fatal signal 11. CPU: 0 PID: 1 Comm: init Not tainted 3.16.0-l4 #152 task: 05c23ac0 ti: 05c26000 task.ti: 05c26000 PC is at 0x0 LR is at 0x0 pc : [<00000000>] lr : [<00000000>] psr: 60000010 sp : bf73cef0 ip : 00000000 fp : 00000000 r10: 00000000 r9 : 00000000 r8 : 00000000 r7 : 00000000 r6 : 00000000 r5 : 00000000 r4 : 00000000 r3 : 0000c50c r2 : 00000000 r1 : 00000000 r0 : 00000000 vcpu: b3000c00 vcpu-state: 00000001 Flags: nZCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user CPU: 0 PID: 1 Comm: init Not tainted 3.16.0-l4 #152 [<0200c9c8>] (unwind_backtrace) from [<020055e8>] (show_stack+0x10/0x14) [<020055e8>] (show_stack) from [<0202844c>] (get_signal_to_deliver+0x204/0x490) [<0202844c>] (get_signal_to_deliver) from [<02006be8>] (do_signal+0x114/0x448) [<02006be8>] (do_signal) from [<0200a210>] (l4x_vcpu_entry_c+0xa94/0x1da8) [<0200a210>] (l4x_vcpu_entry_c) from [<00000000>] ( (null)) Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b CPU: 0 PID: 1 Comm: init Not tainted 3.16.0-l4 #152 [<0200c9c8>] (unwind_backtrace) from [<020055e8>] (show_stack+0x10/0x14) [<020055e8>] (show_stack) from [<022441a4>] (panic+0x7c/0x1e0) [<022441a4>] (panic) from [<0201e6a8>] (do_exit+0x708/0x7a0) [<0201e6a8>] (do_exit) from [<0201e80c>] (do_group_exit+0x3c/0x9c) [<0201e80c>] (do_group_exit) from [<02028390>] (get_signal_to_deliver+0x148/0x490) [<02028390>] (get_signal_to_deliver) from [<02006be8>] (do_signal+0x114/0x448) [<02006be8>] (do_signal) from [<0200a210>] (l4x_vcpu_entry_c+0xa94/0x1da8) [<0200a210>] (l4x_vcpu_entry_c) from [<00000000>] ( (null)) ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye Thanks in advance for your help, Nicolas >Hi, > >On Mon Mar 02, 2015 at 15:10:04 +0100, Nicolas VARONA wrote: >> I am trying to set up a simulator with Qemu and l4linux ARM to >> simulate the Zynq board. I have successfully compiled Fiasco and L4 >> with the tool chain "arm-linux-gnueabi-gcc". I succeeded to launch >> l4linux but I have no input on l4linux when it's running on Qemu. >> Nevertheless, the fiasco jdb can be invoked. After reading the mailing >> list I changed the hello world program to take inputs and tried a bare >> metal application with l4re with the same result (I didn't modify the >module list). >> >> So, I tried to do the same thing with the board and I have inputs with >> the l4 bare metal application > >So I looked a bit at this and it seems to me that there's something strange >with uart rx in Qemu, or at least which only shows up in Qemu. >I need to investigate that further. > >> and a kernel panic for the l4linux. > >Which kind of panic? > >> I boot >> with the uboot image on it. Nonetheless, using uImage for qemu doesn't >> change anything: >> >> ./qemu-system-arm -M arm-generic-fdt-plnx -m 512M -kernel >> /path/bootstrap.uimage -dtb /path/devicetree.dtb -serial mon:stdio >> >> I tried to compile the u-boot from Xilinx and Qemu freezes when I >> launch the l4 application. > >Could also be the uart issue? But entering jdb always works for me. > >> To be sure I have done things right, I also tried the modified hello >> world program on x86 intel and it works well. Then I launched a >> Petalinux with Qemu and a uImage with uboot and it works. >> >> My Qemu is from Xilinx: QEMU emulator version 2.0.50 > >Oh, good to know. I tried the normal one.

2 12

Question about L4/Fiasco running the kernel with interrupts disable
by deng.chao1＠zte.com.cn 09 Apr '15

09 Apr '15

Hi all， I have read the wikipedia website of L4 kernel(http://en.wikipedia.org/wiki/L4_microkernel_family), it says that L4/Fiasco was designed "fully preemptible to achieve a low interrupt latency " at first, however "the complexities of a fully preemptible design resulted in later versions of Fiasco to return to the traditional L4 approach of running the kernel with interrupts disabled ". I am very interested in the kernel's interrupt latency. I have check the latest versions of Fiasco kernel in running, and it keeps interrupts disabled indeed. So I wonder whether there was any early version of L4/Fiasco which supported fully preemptible? Or was there any article talked about this ? Thanks！

2 1

Question about L4/Fiasco running the kernel with interrupts disable
by cui.yunfeng＠zte.com.cn 08 Apr '15

08 Apr '15

Hi all， I have read the wikipedia website of L4 kernel(http://en.wikipedia.org/wiki/L4_microkernel_family), it says that L4/Fiasco was designed "fully preemptible to achieve a low interrupt latency " at first, however "the complexities of a fully preemptible design resulted in later versions of Fiasco to return to the traditional L4 approach of running the kernel with interrupts disabled ". I am very interested in the kernel's interrupt latency. I have check the latest versions of Fiasco kernel in running, and it keeps interrupts disabled indeed. So I wonder whether there was any early version of L4/Fiasco which supported fully preemptible? Or was there any article talked about this ? Thanks！

1 0

about ".initcall.text" and ".initcall.data"
by 水镜 07 Apr '15

07 Apr '15

hi ,there are ".initcall.data" and ".initcall.data" in the kernel.ia32.ld, what are these two sections for?

2 1

Microkernel Meetup
by Björn Döbel 04 Apr '15

04 Apr '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, it is time for another Microkernel Meetup! As many regulars seem to be travelling mid/late April, I suggest we go to B'liebig, Liebigstraße 24 http://b-liebig.de/ either on April 7 or on April 9. Please participate in the Dudle so I can reserve a table: https://dudle.inf.tu-dresden.de/uks0415/ Also, please distribute this email to anyone you think might be interested in coming. Cheers, Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlUSfX0ACgkQP5ijxgQLUNmsjQCeP07bdeWG7cANxiaT2U1DqT+N 9+EAmQH4tcieJL4S1VAiOkOCJaGQqsJG =XTl6 -----END PGP SIGNATURE-----

1 1

Denial of service in microkernel
by Gayathri Nagarajan 01 Apr '15

01 Apr '15

I executed fork bomb(a process continually replicates itself to deplete the system resources), a denial of service attack in Linux kernel and the kernel got crashed. This is because of the depletion of resources and starvation. But, upon executing the same application in L4linux under the Fiasco.oc with L4re microkernel architecture, no crashing occurs. What is the reason behind this stability? How does the microkernel(Fiasco.OC) handle the system calls ? # Code for the fork bomb application : #include<unistd.h> int main(void) { while(1) fork(); //system call }

2 1

Fiasco testcase And L4RE API
by cui.yunfeng＠zte.com.cn 31 Mar '15

31 Mar '15

hi L4 hacker: I am learning Fiasco, there are some question about Fiasco and L4RE. Is there unit test case (such as TDD test case) on development of Fiasco? How to get the unit test case? Is there document about L4RE API interface? I want to compare the L4RE POSIX interface and Linux POSIX interface. Thanks a lot.

2 1

(no subject)
by zhou.li9＠zte.com.cn 31 Mar '15

31 Mar '15

Now I want to debug Fiasco.OC kernel with JDB, the version of Fiasco.OC is 2014092821. Mentioned in a jdb.pdf document section 4.14, need to use RMGR to load the symbol table, but I did not find any manpage on the RMGR. where is the manpage or how to load the symbol table? -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

2 1

L4 and Lua interaction
by daniel krefft 30 Mar '15

30 Mar '15

Hi there, please can you give us a short overview about the L4 and Lua interaction/integration? The most important aspect is to understand how Lua-Scripts are used to create/manage the VBus. In particular from which module/component are the Lua-Scripts read/processed (NED, SIGMA0)? We found an example about Ankh (ankh.vbus, aw.lua, lwip.lua). Maybe it is possible to exemplify it via Ankh. Regards, Daniel -- Mit freundlichen Grüßen Daniel Krefft ***************************************************************** * Daniel Krefft M.Sc. * * T: +49-89-289-18791 * * * Technische Universitaet Muenchen * Fakultaet fuer Informatik - F13 (Prof. Baumgarten) * Boltzmannstr. 3 * D-85748 Garching bei Muenchen * Germany *****************************************************************

2 1

microkernel as an instance in oracle virtual box
by Gayathri Nagarajan 24 Mar '15

24 Mar '15

Is it possible to run the microkernel Fiasco.oc directly as an instance in Oracle virtual box (just like other operating systems like Ubuntu, windows etc that are executed) ? If so, how do I do it?

2 1

Support for Raspberry Pi 2 B and/or Odroid C1
by daniel krefft 24 Mar '15

24 Mar '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, we're are interested in running Fiasco.OC on the Raspberry Pi 2 (Broadcom BCM2836 ARM Cortex-A7) or Odroid C1 (Amlogic S805 Cortex A5). Is there any support for the boards yet? Best regards, Daniel - -- Mit freundlichen Grüßen Daniel Krefft ***************************************************************** * Daniel Krefft M.Sc. * * T: +49-89-289-18791 * * * Technische Universitaet Muenchen * Fakultaet fuer Informatik - F13 (Prof. Baumgarten) * Boltzmannstr. 3 * D-85748 Garching bei Muenchen * Germany ***************************************************************** -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVD+5AAAoJEJwTN+De5ZtpDfgH/1x7WIHYutLEWJmP23lhSnAm jp1NLmUL1kaFPGrsTr0Q4WfBtn6iVTFYbmoDXoMZxmen4Ne0SomuftSAHePkBwOm SH6udmQir5b6C0hWJSGdQ0CkY+YemcR3LvM3poNzpJtNAJvTiCRNE6qeI4WZn5TY ocNb3AzzNZ4ruZ6QBdtiwfkpAAABZQSiWM6xtcHIVckGezWuW+qC3ZLfvNK08U/i 4Up0eHIc2dldgrGCvzotC0j6LW7urinVG0e6rBFImrup1wLnTlJAJwua0wzf5uGT omkS1dE4u5RQ7BkYHWfwaAApI0Cm5vNVu90ObfVsBKSLPE1fluxmZ+SNLWEhgt0= =TBGn -----END PGP SIGNATURE-----

2 1

the implemention of l4_ipc_send
by 水镜 24 Mar '15

24 Mar '15

hi, where could i find the implemention of l4_ipc_send?

2 1

Help with RaspberryPI USB on Fiasco.OC+Genode
by Reinier Millo Sánchez 23 Mar '15

23 Mar '15

Hi GenodeOS and L4-Hackers community I'm trying to use DWC_OTG USB Driver for RaspberryPI, using Fiasco.OC as microkernel with Genode. I have tested the USB driver using Genode bare metal hardware on RaspberryPI and works fine. I have reviewed the post published by Simon Arlott about the FIQ and Bell IRQ: http://permalink.gmane.org/gmane.linux.kernel.rpi/438 Also I have reviewed the correction implemented by Norman Feske in the IRQ controller for Genode bare metal hardware: repos/base-hw/src/core/include/spec/rpi/pic.h To use Fiasco.OC as microkernel in Genode I have adapted the patch published in: http://sourceforge.net/p/genode/mailman/message/33071769/ Based on it, i have tried to use the same idea of Norman Feske, modifying the Fiasco.OC's IRQ's controller as shown below: ------ kernel/fiasco/src/kern/arm/bsp/bcm2835/mem_layout-arm-bcm2835.cpp ------ index aab5906..4385ebe 100644 @@ -8,5 +8,6 @@ public: Pic_phys_base = 0x2000b200, Watchdog_phys_base = 0x20100000, Uart_phys_base = 0x20201000, + Usb_dwc_otg_base = 0x20980000, }; }; ---------- kernel/fiasco/src/kern/arm/bsp/bcm2835/pic-arm-bcm2835.cpp ---------- index 20ed280..13fa623 100644 @@ -7,6 +7,83 @@ IMPLEMENTATION [arm && bcm2835]: #include "irq_mgr.h" #include "mmio_register_block.h" #include "kmem.h" +#include "warn.h" + +class Usb_dwc_otg : Mmio_register_block{ +private: + enum{ + Core_irq_status_reg = 0x14, + Guid_reg = 0x3c, + Host_frame_number_reg = 0x408, + }; + bool is_sof() const { return read<Mword>(Core_irq_status_reg)&0x8; } +}; + +PUBLIC +Usb_dwc_otg::Usb_dwc_otg() +: Mmio_register_block(Kmem::mmio_remap(Mem_layout::Usb_dwc_otg_base)) +{ + + write<Mword>(read<Mword>(Guid_reg)&0x3FFFC000, Guid_reg); +} + +PRIVATE +static bool +Usb_dwc_otg::need_trigger_sof(Mword host_frame, Mword scheduled_frame) +{ + Mword const max_frame = 0x3fff; + + if (host_frame < scheduled_frame) { + if (scheduled_frame - host_frame < max_frame / 2) + return false; /* scheduled frame not reached yet */ + else + return true; /* scheduled frame passed, host frame wrapped */ + } else { + if (host_frame - scheduled_frame < max_frame / 2) + return true; /* scheduled frame passed */ + else + return false; /* scheduled frame wrapped, not reached */ + } +} + +PUBLIC +bool +Usb_dwc_otg::handle_sof() +{ + if (!is_sof()) + return false; + + static Mword cnt, stat_cnt, filter_cnt, kick_cnt, trigger_cnt; + + stat_cnt++; + if (stat_cnt == 8000) { + WARN("kicked: %d filtered: %d triggered: %d", kick_cnt, filter_cnt, trigger_cnt); + stat_cnt = 0; + } + + cnt++; + if (cnt == 8*20) { + cnt = 0; + return false; + } + + if (read<Mword>(Guid_reg)&0x40000000) + kick_cnt++; + + if ((!read<Mword>(Guid_reg)&0x80000000) || (read<Mword>(Guid_reg)&0x40000000)) + return false; + + if (Usb_dwc_otg::need_trigger_sof(read<Mword>(Host_frame_number_reg)&0x3fff, read<Mword>(Guid_reg)&0x3fff)) { + trigger_cnt++; + return false; + } + + filter_cnt++; + + write<Mword>(read<Mword>(Core_irq_status_reg)|0x8, Core_irq_status_reg); + + return true; +} class Irq_chip_bcm : public Irq_chip_gen, Mmio_register_block { @@ -29,6 +106,9 @@ public: bool is_edge_triggered(Mword) const { return false; } void set_cpu(Mword, Cpu_number) {} void ack(Mword) { /* ack is empty */ } + +private: + Usb_dwc_otg _usb; }; PUBLIC @@ -97,6 +177,11 @@ Irq_chip_bcm::irq_handler() { b = 0; p = read<Mword>(Irq_pending_1); + if(p==8){ + if(_usb.handle_sof()){ + return; + } + } } else if (p & 0x200) { I have tried to test the *usb_hid *example on Genode using Fiasco.OC as microkernel make run/usb_hid The example compiles fine. When I test it in the emulator QEMU get the following output KERNEL: Warning: kicked: 0 filtered: 0 triggered: 7950 KERNEL: Warning: kicked: 0 filtered: 0 triggered: 15900 KERNEL: Warning: kicked: 0 filtered: 0 triggered: 23850 KERNEL: Warning: kicked: 0 filtered: 0 triggered: 31800 When have tested it on real hardware never get the kernel warning. It seems that the *Kick* and *Num_valid* bits are not modified by the USB driver. After that, I have tried to log the USB driver IRQ, setting #define DEBUG_IRQ 1 in the file repos/dde_linux/src/lib/usb/include/lx_emul.h Setting this value, the USB driver will log every IRQ handled by the function *_handle()* and *_handle_one()***in the USB driver. In the Genode bare metal hardware it works fine, but when tried it with Fiasco.OC, the IRQ handler *_handle()* and *_handle_one()* are never logged. There's something wrong in my implementation? Someone has tested the USB driver using Fiasco.OC and Genode together? Why Fiasco.OC's IRQ's controller is not calling the IRQ's handler defined in the USB driver? I'm using Genode commit 63293950261bfb17497433c36a3d62e6e1d813b3, Fiasco.OC r56 and DWC_OTG commit d08b205cfe01925667f3591117b6d3e1087b4e19. Best regards -- Lic. Reinier Millo Sánchez Centro de Estudios de Informática Universidad Central "Marta Abreu" de Las Villas "antes de discutir ... respira; antes de hablar ... escucha; antes de escribir ... piensa; antes de herir ... siente; antes de rendirte ... intenta; antes de morir ... vive"

2 1

Help to measure the Fiasco.OC's real-time capabilities
by Reinier Millo Sánchez 23 Mar '15

23 Mar '15

Hi L4 Hackers community I want to use Fiasco.OC to construct real-time's systems. I want to do some benchmarks over Fiasco.OC, to measure the performance in different hardware platforms and compare the results with tests made to others solutions based maybe on Linux Kernel. For now i want to test the real-time capabilities on some platforms, measuring some aspects of Fiasco.OC (in time or cycles): - Execution mode switch (user-kernel) - Thread/Context switch on the CPU - Scheduler algorithm - IPC Mechanism - Thread/Task creation/destruction Somebody have measured this elements in Fiasco.OC or can give me some ideas? Best regards -- Lic. Reinier Millo Sánchez Centro de Estudios de Informática Universidad Central "Marta Abreu" de Las Villas "antes de discutir ... respira; antes de hablar ... escucha; antes de escribir ... piensa; antes de herir ... siente; antes de rendirte ... intenta; antes de morir ... vive"

2 1

Moe::Boot_fs::init_stage1()
by 水镜 22 Mar '15

22 Mar '15

Hi, i am reading the source of the moe. there's a line: Moe::Boot_fs::init_stage1();‍ what it is for? when i comment it. the hello example can still run correctly.‍

2 1

the editor for Fiasco.OC
by cui.yunfeng＠zte.com.cn 19 Mar '15

19 Mar '15

I am reading Fiasco.OC source code, but didn't find a suitable editor. As the following code, the eclipse or Source Insight can't identify the class hierarchy. I want to know which editor is used by Fiasco.OC developer, Thanks ! class Kernel_uart { public: }; .... EXTENSION class Kernel_uart : public Uart { private: };

2 1

L4Re Hello World Qemu vs Hardware
by André Bispo 17 Mar '15

17 Mar '15

Hello guys,I was trying to run Fiasco and L4 and i successfully created the ISO image and ran it on QEMU.How can i run it on my pc hardware? Can you guys provide me some steps on how to do it? Thank you in advance,André Bispo.

2 1

Checkpoint/Restore on L4Re
by Stark, Josef 16 Mar '15

16 Mar '15

Hello, I am interested in Checkpoint/Restore-functionality on L4Re. I found the paper "Stay Strong, Stay Safe – Enhancing Reliability of a Secure Operating System" (http://os.inf.tu-dresden.de/papers_ps/vogtdoebel-IIDS2010.pdf), where it is written that such a mechanism was already developed for L4Re. However, I couldn't find such a thing inside the L4Re snapshot. Could someone tell me what the current state of this is, and where to find it (if it's publicly available)? Sincerely, Josef

2 1

Running a task without region manager
by Stark, Josef 16 Mar '15

16 Mar '15

Hey, I am wondering what would happen (i.e. which disadvantages I get) if I tried to run a task directly, without l4re_kernel. More precisely: Ned, file lua_exec.cc, line 408: '_l.launch(&am, "rom/l4re", ldr);': What would happen, if the second argument ("rom/l4re") was replaced by a variable holding the actual binary name that should be started (e.g. "rom/hello"), which thus would be started without l4re? Best regards, Josef

2 2

Disable log color
by teclis High Elf 16 Mar '15

16 Mar '15

Is there a way to disable the log color so that the logger doesn't insert control codes for color into the output stream.

4 4

Networking issues (ankh/lwip/drivers/?)
by Stark, Josef 13 Mar '15

13 Mar '15

Hi all, while experimenting with network apps in L4Re, I experienced some issues: 1. (not important) DHCP isn't working: The lwip example (ankh/examples/lwip) doesn't seem to work, neither with the integrated DHCP-Server of QEMU, nor with a dnsmasq running on a tap interface plugged into a vde_switch. Workaround: Replacing "dhcp_start(&my_netif);" with "netif_set_default(&my_netif); netif_set_up(&my_netif);" and, beforehand, setting the adress manually with "IP4_ADDR()" (#include <ipv4/lwip/ip4_addr.h>). I also couldn't get DNS to work. 2. (not so important) some NIC-drivers aren't working: QEMU-x86 can emulate the following interfaces: ne2k_pci, i82551, i82557b, i82559er, rtl8139, e1000, pcnet and virtio. According to its Makefile, ankh supports the following interfaces: NE2K, LOOP, RTL8139, RTL8169, PCNET, E100, E1000, E1000E and UX. However, of the intersection (ne2k_pci, rtl8139, pcnet und e1000) only ne2k_pci seems to work somewhat reliably. The others simply don't work with or without some errors being shown by ankh. With ne2k_pci I can only get a throughput of about 1MB/s, I'm guessing because the card is pretty old. 3. Sporadic delays/ errors: Although this didn't happen too often, sometimes, when a client tried to send some small data to a server in another QEMU-instance, I experienced delays in the range of about 1 second before the receiver got the data. On other occassions, a connection could not be established at all. However, no error messages were shown. 4. Multithreaded server issues: I couldn't manage to get a multithreaded server to work. Neither a server, a) which receives data on two different ports, each handled in a separate thread, nor b) which receives data on a single port, handles however multiple clients simultaneously via separate threads, did work. Since a) and b) seem somewhat related I will elaborate only on b): As long as just one client is connected to the server, sending and receiving on both ends works fine. As soon as a second client (in another QEMU-instance, all connected via a vde_switch) tries to send data after connecting, both connections from server to the first and second client break down and no data gets through anymore. No errors shown. Finally the write() calls timeout. Just as I wrote this, it did one time actually work, both clients connected, able to send and receive data. But I couldn't reproduce this success. After removing the L4Re-specific parts of the code I compiled and ran it on Linux, where it does work flawlessly, even with 6 simultaneous client processes, not just 2. I'm not sure why these issues occur, either there are bugs somewhere in L4Re's network stack or the NIC drivers, but it's also perfectly possible that I made some mistakes or that vde_switch doesn't work correctly (Although I did test whichever was possible (e.g. 4.a ) also only using simple QEMU TCP sockets). In order to be able to reproduce the results, I attached my configuration (see below and attachments). Hopefully, someone can tell me what's going on here. I would really be glad. Thank you! Josef ---------------------------------------- Configuration: First of all, I run "sudo vde_switch -daemon -mod 660 -group users". This is only neccessary once; the vde_switch is then used by all QEMU-instances. To start the scenario, I use a simple script (see attachment run.sh), which starts all the QEMU-instances and sets different MAC-adresses for each instance (in cooperation with Makeconf.boot). server.c and client.c are heavily based on the lwip example. While server_linux.c and client_linux.c are the stripped-down files I used for testing the network code on linux, all the other attached files are needed for running the L4Re-scenario.

1 0

dde kit
by Daniel Krefft 13 Mar '15

13 Mar '15

Hi there, we want to use the ddekit in one of our courses next summer term. So, to get comfortable with the setup and the toolchain I would like to ask if a step by step guide to get the ddekit up and running exists? Best regards, Daniel -- ***************************************************************** * Daniel Krefft M.Sc. * * T: +49-89-289-18791 * * * Technische Universitaet Muenchen * Fakultaet fuer Informatik - F13 (Prof. Baumgarten) * Boltzmannstr. 3 * D-85748 Garching bei Muenchen * Germany *****************************************************************

2 3

Re: Porting Fiasco.OC to RISC-V - Questions
by Hesham ALMatary 12 Mar '15

12 Mar '15

Hi Adam, Thanks for your reply. I thought it would be a good idea to start with L4Re to familiarize myself with Fiasco.OC/L4Re structure, and chose to start with L4Re because it doesn't need a lot of architecture dependent code. So, after your reply, I'd work on getting bootstrap working and loading the "to-be-evolved" Fiasco.OC RISC-V kernel. This would allow me to debug and test Fiasco.OC/risc-v as I add new code/features their. Best, Hesham On Thu, Mar 12, 2015 at 12:48 PM, Hesham ALMatary <heshamelmatary(a)gmail.com> wrote: > Hi Adam, > > Thanks for your reply. I thought it would be a good idea to start with > L4Re to familiarize myself with Fiasco.OC/L4Re structure, and chose to > start with L4Re because it doesn't need a lot of architecture > dependent code. So, after your reply, I'd work on getting bootstrap > working and loading the "to-be-evolved" Fiasco.OC RISC-V kernel. This > would allow me to debug and test Fiasco.OC/risc-v as I add new > code/features their. > > Best, > Hesham > > On Wed, Mar 11, 2015 at 11:14 PM, Adam Lackorzynski > <adam(a)os.inf.tu-dresden.de> wrote: >> Hi, >> >> On Wed Mar 11, 2015 at 17:53:58 +0000, Hesham ALMatary wrote: >>> I'm considering porting Fiasco.OC/L4Re to RISC-V architecture (for >>> both my research and GSoC). So, I started reading the documentation >>> and building the environment (For Fiasco.OC and RISC-V tools), and >>> QEMU (the emulator that I'll use initially) is running Hello World >>> example just fine. >>> >>> After some reading, I wanted to start adding support for building L4Re >>> for RISC-V (is this a good start?), and I came up with some questions. >>> >>> There are two variants of RISC-V ABI (32 and 64 bit) should I provide >>> both or just 64-bit version? >> >> For starting, just choose one. The other type could be done later. >> >>> What are the minimal packages and/or Fiasco.OC system components that >>> need to be implemented to get Hello World working? Please correct me >>> if the following L4Re list is not right (contains more than needed, or >>> lack others): >>> >>> "bootstrap, sigma0, moe, Log, libc, libc_minimal, cxx_util, cxx_io, >>> cxx_base, cxx_io_kdebug,l4sys-direct, l4sys" >> >> Good list. To find out the exact list you can just do >> "make O=... sigma0 moe bootstrap l4re_kernel hello" and then see in the >> build directory what was actually built. >> >> But actually for starting, you just need boostrap because then comes the >> kernel that needs to work before anything more needs to be done for the >> user level components. >> >>> Some of the packages are architecture dependent which need some code >>> from other projects (like uclibc), should I add them all? FYI, newlib >>> has support for riscv, but uclibc doesn't, >> >> True that uclibc does not support riscv natively. But there's nearly no >> architecture dependent code needed, so this is not really an issue. >> >>> how can I make the build >>> system choose specific packages for the target architecture (riscv in >>> this case) and maybe neglect building others? >> >> One way is putting 'broken' files in to package's root directory (e.g. >> l4/pkg/hello/broken). Then there's the SYSTEMS variable which defines >> for which architecture a library/program can be compiled for. Its >> default is all architecture, so by not changing the default and just >> adding riscv-l4f where you want it could also be a way. >> >> >> >> 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 > > > > -- > Hesham -- Hesham

2 1

Porting Fiasco.OC to RISC-V - Questions
by Hesham ALMatary 12 Mar '15

12 Mar '15

Hi all, I'm considering porting Fiasco.OC/L4Re to RISC-V architecture (for both my research and GSoC). So, I started reading the documentation and building the environment (For Fiasco.OC and RISC-V tools), and QEMU (the emulator that I'll use initially) is running Hello World example just fine. After some reading, I wanted to start adding support for building L4Re for RISC-V (is this a good start?), and I came up with some questions. There are two variants of RISC-V ABI (32 and 64 bit) should I provide both or just 64-bit version? What are the minimal packages and/or Fiasco.OC system components that need to be implemented to get Hello World working? Please correct me if the following L4Re list is not right (contains more than needed, or lack others): "bootstrap, sigma0, moe, Log, libc, libc_minimal, cxx_util, cxx_io, cxx_base, cxx_io_kdebug,l4sys-direct, l4sys" Some of the packages are architecture dependent which need some code from other projects (like uclibc), should I add them all? FYI, newlib has support for riscv, but uclibc doesn't, how can I make the build system choose specific packages for the target architecture (riscv in this case) and maybe neglect building others? Any other feedback or comments are welcomed. -- Hesham

2 1

shared dataspace for l4re_kernel/ registering additional caps in ned
by Stark, Josef 12 Mar '15

12 Mar '15

Hello all, for a project, I want to be able to load (elf-)binaries not only from the filesystem, but also from the network (receive binary, then start it.) For this, I will write a L4 app (let's call it "manager" for now) which handles the network part and then tells ned to start the received binary via a special "filename". I already modified ned so that its LUA-interface is exposed to other apps via a capability. But here comes the first problem: Normally you specify the capability table of a task and an IPC channel in the lua-config file, which ned reads. Ned then prepares the channel and the caps table and starts the task, which then can register the capability. Otherwise, registering fails (the example would do a printf("Could not register my service, is there a 'calc_server' in the caps table?\n");) So... how do I specify which capabilities ned itself can have/register? Currently, I need to have a lua-config which tells ned to start another instance of ned with the required permission to register the capability. But is there any way to avoid having two ned instances and making the first (and only) instance able to register the cap? Second problem: I found out, that ned (also moe) doesn't start the desired app directly but instead starts the l4re binary (source located in src/l4/pkg/l4re_kernel), passing it the filename of the desired binary. l4re, once started, gets the dataspace of this file and then ultimately starts the app. For my purpose, I would modify l4re_kernel so that if it detects the special "filename" mentioned above, it does not read the file from the filesystem but loads the binary that the "manager" received over the network. To get the data from the manager to the l4re_kernel instance, I thought that a shared dataspace or a shared memory area l4shmc_area_t like in prdocons.c example would be suitable. However, again, both of these things normally require special parameters in the lua config file (as can be seen in the examples), but I have no clue how to do this to l4re_kernel since it is not loaded from such a file, but loaded implicitly each time a new task is started. (so I guess this makes it even harder than the problem with ned since ned is only started once.) Does anyone have ideas on how to solve these? If someone finds that I phrased this too opaque, please let me know. Best regards, Josef Stark

3 16

add new package
by 水镜 11 Mar '15

11 Mar '15

hi ,i want to add a new package which is a lib. i use the log package as my base. now my package can be compiled. but when i want to use it in the moe, i got this errors: Library dependencies missing: libdbgobj in directory '/home/watermirror/source/src/l4re/pkg/moe/server/src'; aborting. /home/watermirror/source/src/l4re/mk/binary.inc:363: *** Cflags dependencies missing: libdbgobj in directory '/home/watermirror/source/src/l4re/pkg/moe/server/src'; aborting.. how to solve this problem?

2 1

seL4 and mysql
by André Bispo 06 Mar '15

06 Mar '15

Hello guys, I'm a student and i'm looking at the possibility of using an L4 microkernel in my thesis, my goal is to take advantage of isolation mechanism to in order to increase privacy in databases. But i have a couple of questions. 1) How feasible is the idea of having a MySQL database with a libOS running on top of seL4 microkernel? If it can be done, where should i start? Any tutorial? 2) if seL4 does not allow me to do it, is there another microkernel in the family of L4 better suited for this task? Thank you in advance. Best regards, Andre Bispo.

2 1

Where could i found the class implemention
by 水镜 05 Mar '15

05 Mar '15

hi, i am reading the source of clntsrv in pkg/examples directory. there are a lot of classes in the server.cc and client.cc which i could not found the implemention file, such as L4::Server_object. How could i get these?

2 1

how to get the log from serial
by 水镜 05 Mar '15

05 Mar '15

hi, how to get all the output log when startup helloworld example? i have build the iso file use command :make grub2iso.then boot this iso using vmware.‍ i can get the output log from serial when startup linux.

2 1

ARM with Qemu
by Nicolas VARONA 04 Mar '15

04 Mar '15

Hi l4Hackers, I am trying to set up a simulator with Qemu and l4linux ARM to simulate the Zynq board. I have successfully compiled Fiasco and L4 with the tool chain "arm-linux-gnueabi-gcc". I succeeded to launch l4linux but I have no input on l4linux when it's running on Qemu. Nevertheless, the fiasco jdb can be invoked. After reading the mailing list I changed the hello world program to take inputs and tried a bare metal application with l4re with the same result (I didn't modify the module list). So, I tried to do the same thing with the board and I have inputs with the l4 bare metal application and a kernel panic for the l4linux. I boot with the uboot image on it. Nonetheless, using uImage for qemu doesn't change anything: ./qemu-system-arm -M arm-generic-fdt-plnx -m 512M -kernel /path/bootstrap.uimage -dtb /path/devicetree.dtb -serial mon:stdio I tried to compile the u-boot from Xilinx and Qemu freezes when I launch the l4 application. To be sure I have done things right, I also tried the modified hello world program on x86 intel and it works well. Then I launched a Petalinux with Qemu and a uImage with uboot and it works. My Qemu is from Xilinx: QEMU emulator version 2.0.50 This is my program (taken from the mailing list: http://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/006337.html <http://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/006337.html> ): Main.c: #include <stdio.h> int main(void) { printf("Press some key: "); char c = getchar(); printf("\nYour input: %c (%d)\n", c, c); printf("Enter a number: "); int number; scanf("%x", &number); printf("Your number: %d\n", number); return 0; } Makefile: PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. TARGET = hello SRC_C = main.c EQUIRES_LIBS = libc_be_file_stdin include $(L4DIR)/mk/prog.mk Module list: entry hello-cfg kernel fiasco -serial_esc roottask moe rom/hello.cfg module l4re module ned module hello.cfg module hello hello-cfg: require("L4"); L4.default_loader:start({caps={},log = L4.Env.log,},"rom/hello"); Could it be an interruption problem? Where is my mistake? Thanks in advance for your help, Nicolas

2 1

no such object found: rom/l4re backtrace
by 水镜 04 Mar '15

04 Mar '15

Hi, i have build the l4re,l4linux,fiasco for x86 successfully. when i boot try to boot l4linux, an error came out: FATAL exception in MOE: Exception: No such object found: rom/l4re: backtrace ... i use the vmware and ubuntu 14.04 to test the l4linux, here is the steps how i do my job: 1.create a directory 'l4linux' in /boot. 2.copy the bootstrap to '/boot/l4linux' from 'l4re_build/bin/x86_586' 3.copy all the file to '/boot/l4linux' in 'l4re_build/bin/x86_586/l4f' 4.copy the fiasco to '/boot/l4linux' from 'fiasco_build/bin' 5.copy the vmlinuz to '/boot/l4linux' form 'l4linux_build' 6.download the drops-rd.rd to '/boot/l4linux' 7.create the l4linux.cfg in '/boot/l4linux' 8.create the modules.list in '/boot/l4linux' the 'modules.list' is like this: entry L4Linux kernel fiasco -serial_esc roottask moe rom/l4linux.cfg module l4linux.cfg module l4re module ned module vmlinuz module drops-rd.rd the 'l4linux.cfg' is like this: L4.default_loader:start({}, "rom/vmlinuz mem=64M console=ttyLv0 l4x_rd=rom/drops-rd.rd root=1:0 ramdisk_size=4000 init=/bin/sh"); 9.modify the grub.cfg, add the following lines: menuentry 'L4Linux' { multiboot /boot/l4linux/bootstrap -modaddr 0x02000000 module /boot/l4linux/fiasco -serial_esc module /boot/l4linux/sigma0 module /boot/l4linux/moe rom/l4linux.cfg module /boot/l4linux/l4linux.cfg module /boot/l4linux/l4re module /boot/l4linux/ned module /boot/l4linux/vmlinuz } after this job is done. i reboot the system. the error came out. please give me some help to sovle the problem. thanks.

2 3

Blocking Read
by teclis High Elf 02 Mar '15

02 Mar '15

Hi, Would someone be able to point me to an example L4Re driver that does a blocking read? thanks,

2 1

Troubles testing UART3 on Exynos5
by Reinier Millo Sánchez 27 Feb '15

27 Feb '15

Hi I'm testing Fiasco.OC+L4re on YSE5250 (Exynos 5250) Board. I have compiled and tested some examples. I'm testing a GPS Driver for the board. The GPS is conected over UART3 at 9600 baudrate, first I'm testing UART3 port comunicating the UART1 serial output with UART3. I'm following as example the serial-drv package on L4re. I have adapted the source code to my uart driver >>> gps_drv.cc #include <l4/drivers/uart_s3c2410.h> #include <l4/io/io.h> #include <l4/re/env> #include <l4/re/error_helper> #include <l4/re/namespace> #include <l4/re/util/cap_alloc> #include <l4/re/util/object_registry> #include <l4/re/util/icu_svr> #include <l4/re/util/vcon_svr> #include <l4/sys/irq> #include <l4/util/util.h> #include <cstdlib> #include <cstdio> #define IRQ_NUM 86 #define UART_BASE 0x12C30000 static L4::Cap<void> srv_rcv_cap; class Loop_hooks : public L4::Ipc_svr::Ignore_errors, public L4::Ipc_svr::Default_timeout, public L4::Ipc_svr::Compound_reply { public: void setup_wait(L4::Ipc::Istream &istr, bool) { istr.reset(); istr << L4::Ipc::Small_buf(srv_rcv_cap.cap(), L4_RCV_ITEM_LOCAL_ID); l4_utcb_br_u(istr.utcb())->bdr = 0; } }; using L4Re::Env; using L4Re::Util::Registry_server; static Registry_server<Loop_hooks> server(l4_utcb(), Env::env()->main_thread(), Env::env()->factory()); using L4Re::Util::Vcon_svr; using L4Re::Util::Icu_cap_array_svr; class GPS_server : public Vcon_svr<GPS_server>, public Icu_cap_array_svr<GPS_server>, public L4::Server_object { public: GPS_server(); virtual ~GPS_server() throw() {} bool running() const { return _running; } int vcon_write(const char *buffer, unsigned size); unsigned vcon_read(char *buffer, unsigned size); L4::Cap<void> rcv_cap() { return srv_rcv_cap; } int handle_irq(); bool init(); int dispatch(l4_umword_t obj, L4::Ipc::Iostream &ios); private: bool _running; L4::Uart *_uart; L4::Cap<L4::Irq> _uart_irq; Icu_cap_array_svr<GPS_server>::Irq _irq; }; GPS_server::GPS_server() : Icu_cap_array_svr<GPS_server>(1, &_irq), _running(false), _uart(0), _uart_irq(L4_INVALID_CAP), _irq() { if (init()) _running = true; } int GPS_server::vcon_write(const char *buffer, unsigned size) { _uart->write(buffer, size); return -L4_EOK; } unsigned GPS_server::vcon_read(char *buffer, unsigned size) { unsigned i = 0; while (_uart->char_avail() && size) { int c = _uart->get_char(false); if (c >= 0) { buffer[i++] = (char)c; size--; } else break; } // if there still some data available send this info to the client if (_uart->char_avail()) i++; else _uart_irq->unmask(); return i; } int GPS_server::handle_irq() { if (_irq.cap().is_valid()) _irq.cap()->trigger(); return L4_EOK; } bool GPS_server::init() { l4_addr_t virt_base = 0; // Mapeando memoria de registros del UART if (l4io_request_iomem((l4_addr_t)UART_BASE, 0x1000, L4IO_MEM_NONCACHED, &virt_base)) { printf("gps-drv: request io-memory from l4io failed.\n"); return false; } printf("gps-drv: virtual base at:%lx\n", virt_base); // Inicializando memoria de los registros del UART L4::Io_register_block_mmio *regs = new L4::Io_register_block_mmio(virt_base); // Inicializando UART _uart = new (malloc(sizeof(L4::Uart_s5pv210))) L4::Uart_s5pv210; _uart->startup(regs); /** * FIX - Ajustando el BaudRate del UART * Valores calculados experimentalmente a través del UART1 * SCLK_UART = 100 MHz * TODO - Hacer el ajuste del BaudRate en el propio UART */ regs->write<unsigned int>(0x28,0x28a); regs->write<unsigned int>(0x2C,0x0); _uart_irq = L4Re::Util::cap_alloc.alloc<L4::Irq>(); if (!_uart_irq.is_valid()) { printf("gps-drv: Alloc capability for uart-irq failed.\n"); return false; } if (l4io_request_irq(IRQ_NUM, _uart_irq.cap())) { printf("gps-drv: request uart-irq from l4io failed\n"); return false; } /* setting IRQ type to L4_IRQ_F_POS_EDGE seems to be wrong place */ if (l4_error(_uart_irq->attach((l4_umword_t)static_cast<L4::Server_object *>(this), L4Re::Env::env()->main_thread()))) { printf("gps-drv: attach to uart-irq failed.\n"); return false; } if ((l4_ipc_error(_uart_irq->unmask(), l4_utcb()))) { printf("gps-drv: unmask uart-irq failed.\n"); return false; } _uart->enable_rx_irq(true); srv_rcv_cap = L4Re::Util::cap_alloc.alloc<void>(); if (!srv_rcv_cap.is_valid()) { printf("serial-drv: Alloc capability for rcv-cap failed.\\n"); return false; } return true; } int GPS_server::dispatch(l4_umword_t obj, L4::Ipc::Iostream &ios) { l4_msgtag_t tag; ios >> tag; switch (tag.label()) { case L4_PROTO_IRQ: if (!L4Re::Util::Icu_svr<GPS_server>::dispatch(obj, ios)) return handle_irq(); case L4_PROTO_LOG: return L4Re::Util::Vcon_svr<GPS_server>::dispatch(obj, ios); default: return -L4_EBADPROTO; } } int main() { char buffer[100]; int tmp; static GPS_server gps_srv; // Register calculation server if (!server.registry()->register_obj(&gps_srv, "gps_srv").is_valid()) { printf("Could not register GPS service, is there a 'gps_srv' in the caps table?\n"); return 1; } if (!gps_srv.running()) { printf("Failed to initialize serial driver; Aborting.\n"); return 1; } gps_srv.vcon_write("Hola Mundo\n",11); while(1){ tmp = gps_srv.vcon_read(buffer,11); if(tmp>0) printf("Readed data: %s\n",buffer); } // Wait for client requests server.loop(); return 0; } I have created my run config file >>> gps-drv.cfg require("L4"); -- Shortcuts local ld = L4.default_loader; local vbus_uart03 = ld:new_channel(); local platform_ctl = ld:new_channel(); local gps_srv = ld:new_channel(); -- Start the IO Server ld:start( { caps = { sigma0 = L4.cast(L4.Proto.Factory, L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; platform_ctl = platform_ctl:svr(); uart03 = vbus_uart03:svr(); }, log = { "IO Server", "green" }, l4re_dbg = L4.Dbg.Warn, }, "rom/io rom/yse5250.devs rom/yse5250.io"); -- Start the GPS Driver Server conected to UART3 ld:start( { caps = { gps_srv = gps_srv:svr(); vbus = vbus_uart03; }, log = {"GPS Driver","blue"} }, "rom/gps_drv"); And have created the yse5250.devs and yse5250.io to put the UART3 on a virtual BUS >>> yse5250.devs local Hw = Io.Hw local Res = Io.Res Io.hw_add_devices { UART3 = Hw.Device { hid = "UART3"; Res.irq(86); Res.mmio(0x12C30000, 0x12C3ffff); } } >>> yse5250.io Io.add_vbusses { -- Create a virtual bus for a client and give access to UART3 uart03 = Io.Vi.System_bus(function () dev = wrap(Io.system_bus():match("UART3")); end); } On modules.list have added an entry for my example entry GPS-Driver kernel fiasco -serial_esc roottask moe rom/gps-drv.cfg module l4re module ned module gps-drv.cfg module gps_drv module io module yse5250.devs module yse5250.io After that i have compiled and uploaded the example to the board. At runtime, i got the "Hola Mundo" over UART3 but when I write in the UART3 I never read the written information. Something is wrong with my code? -- Lic. Reinier Millo Sánchez Centro de Estudios de Informática Universidad Central "Marta Abreu" de Las Villas "antes de discutir ... respira; antes de hablar ... escucha; antes de escribir ... piensa; antes de herir ... siente; antes de rendirte ... intenta; antes de morir ... vive"

2 1

Re: Ethernet on l4linux
by taeung 27 Feb '15

27 Feb '15

On 02/26/2015 02:11 PM, Harini Balachandran wrote: > For getting ethernet on l4linux, what are the packages and network > elements I should copy to ramdisk? > As of now, my ramdisk has only the basic programs.I got this from l4re > snapshot ie ramdisk-x86.rd.I have copied my target application > program(compiled statically) alone to this ramdisk additionally. > I tired copying /proc,/sys and /etc from ubuntu but the size goes > beyond 1.5 GB.What are the essential packages for getting ethernet on > l4linux? > Thank you. > Files in /proc and /sys aren't general files. They are a virtual filesystem provided by Linux. sysfs is http://en.wikipedia.org/wiki/Sysfs procfs is http://en.wikipedia.org/wiki/Procfs So, it isn't needed that you copy them to ramdisk. But if procfs isn't mounted , you can manually mount procfs. For example $ mount -t proc proc proc/ $ mount -t sysfs sys sys/ And the ramdisk already has enough packages and files to connect network. Important thing is to successfully load ethernet driver on L4/L4linux environment. If you succeed in working ethernet driver, you can use commands 'ifup' and 'ifdown','ifconfig' to connect network. And you can check whether ethernet driver is loaded or not if you do 'dmesg | grep ethernet'. Thanks, Taeung > > Regards, > Harini

1 0

2025

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