- l4-hackers - example.com Site

Re: clang-5.0 is not supported. Please use one of the following versions
by Leslie Zhai 06 Jun '17

06 Jun '17

Dear Rui, ご回答有難うございます！ > I believe the LLD's linker script is now fairly decent that you can expect it should work in most cases. -- Regards, Leslie Zhai https://reviews.llvm.org/p/xiangzhai/

1 0

Re: clang-5.0 is not supported. Please use one of the following versions
by Leslie Zhai 05 Jun '17

05 Jun '17

Hi Adam, Thanks for your reply! > we tend to defer to enable versions until they're actually released. Please remove 5.0 :) And what about LLVM's lld? I found it is only for ld https://svn.l4re.org/repos/oc/l4re/trunk/kernel/fiasco/src/kernel.amd64.ld correct? -- Regards, Leslie Zhai https://reviews.llvm.org/p/xiangzhai/

4 4

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

05 Jun '17

在 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 https://drive.google.com/open?id=0ByE8c-y74l_uLUdKWG9NWndnSUk and https://drive.google.com/open?id=0ByE8c-y74l_udUtJOTZvc3BycG8 > 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+ > 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 */ > ... > 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: > > 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 05 Jun '17

05 Jun '17

在 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 > 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+ > 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 */ > ... > 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: > > 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. Thanks for your help! worked :) addr2line -p -i -e bin/amd64_K8/l4f/ned -a 100398d 0x000000000100398d: /home/zhaixiang/project/l4re/l4/pkg/l4re-core/ned/server/src/main.cc:38 (inlined by) /home/zhaixiang/project/l4re/l4/pkg/l4re-core/ned/server/src/main.cc:77 and I need to carefully read JDB manual. > > I hope this helps, > Jean > > > -- Regards, Leslie Zhai - a LLVM hacker https://reviews.llvm.org/p/xiangzhai/

1 1

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