- l4-hackers - example.com Site

Genode 18.08 brings modern hardware support
by Stefan Kalkowski 30 Aug '18

30 Aug '18

Dear l4-hackers, the community and team around the Genode OS framework proudly presents release 18.08, which is at the same time the 10th anniversary of our project. With this release we follow our ambition to sculpt a general-purpose OS using the Genode framework. It adds support for a lot of different recent hardware, the ability to apply Intel microcode updates in a kernel agnostic fashion, and extends the interactive usability of the system. Readers of this mailing list might be especially interested in the update of the NOVA and Fiasco.OC kernels used by the framework to recent versions. The highlights of Genode 18.08 are: - Sculpt OS with live runtime view - Device drivers - Linux device-driver environment based on kernel 4.16.3 - Updated and enhanced Intel framebuffer and wireless drivers - De-componentized USB stack, support for isochronous devices - Improved device compatibility of NIC and PS/2 drivers - Experimental runtime for Zircon-based drivers - Base framework and OS-level infrastructure - NIC-router support for multiple uplinks - New VFS plugin for using LwIP as TCP/IP stack - Cached file-system-based ROM service - VFS plugin for importing initial content - Enhanced Ada language support - Libraries and applications - Python 3 - VirtualBox 5.1.38 - Platforms - New Intel Microcode update mechanism - Multiprocessor support for our custom kernel on x86 - Updated NOVA and Fiasco.OC kernels All of these and more improvements can be read in detail in the release documentation: https://genode.org/documentation/release-notes/18.08 We are looking forward for your feedback. Happy hacking! -- Stefan Kalkowski Genode labs https://github.com.skalk | https://genode.org

1 0

L4Re Build Failure on i386 (Revision 80)
by Paul Boddie 12 Aug '18

12 Aug '18

Hello, I thought I'd try and get L4Re and the UX variant of Fiasco.OC working again. Various errors with the actual compiler - not typical compilation errors - have previously occurred, but system updates come along every so often and I saw that new revisions of L4Re/Fiasco.OC have also arrived fairly recently. Unfortunately, the L4Re build fails with complaints about the linking process. Here is the verbose build output at the point of failure: [fb-drv] ==> Linking fb-drv LD_PRELOAD=libgendep.so LD_LIBRARY_PATH=:/home/paulb/L4/UX/src/l4/mybuild/tool/gendep/32:/home/paulb/L4/UX/src/l4/mybuild/tool/gendep GENDEP_TARGET=fb-drv GENDEP_BINARY=ld GENDEP_BINARY_ALT1=ld /home/paulb/L4/UX/src/l4/tool/bin/l4-bender -t ld - Dl4obj=/home/paulb/L4/UX/src/l4/mybuild -Dl4dir=/home/paulb/L4/UX/src/l4 - Dgcclibdir="/usr/lib/gcc/i686-linux-gnu/7/ /usr/lib/gcc/i686-linux- gnu/7/../../../../i686-linux-gnu/lib/i686-linux-gnu/7/ /usr/lib/gcc/i686- linux-gnu/7/../../../../i686-linux-gnu/lib/i386-linux-gnu/ /usr/lib/gcc/i686- linux-gnu/7/../../../../i686-linux-gnu/lib/../lib/ /usr/lib/gcc/i686-linux- gnu/7/../../../i686-linux-gnu/7/ /usr/lib/gcc/i686-linux-gnu/7/../../../i386- linux-gnu/ /usr/lib/gcc/i686-linux-gnu/7/../../../../lib/ /lib/i686-linux- gnu/7/ /lib/i386-linux-gnu/ /lib/../lib/ /usr/lib/i686-linux-gnu/7/ /usr/lib/i386-linux-gnu/ /usr/lib/../lib/ /usr/lib/gcc/i686-linux- gnu/7/../../../../i686-linux-gnu/lib/ /usr/lib/gcc/i686-linux-gnu/7/../../../ /lib/ /usr/lib/" -Dl4system=x86_gen -Dl4api=l4f -Dlinker="ld -m elf_i386" -- spec=/home/paulb/L4/UX/src/l4/mk/bid-bender.spec -- -o fb-drv -MD -MF ./.fb- drv.pcs.d -PClibc_support_misc -PClibio-vbus -PCx86emu_int10 -PCx86emu_int10 - PCstdlibs -static -gc-sections -Ttext-segment=0x01000000 --defsym __L4_KIP_ADDR__=0xaffff000 --defsym __L4_STACK_ADDR__=0xb0000000 -L /home/paulb/L4/UX/src/l4/mybuild/lib/x86_gen/l4f -L /home/paulb/L4/UX/src/l4/mybuild/lib/x86_gen -L /home/paulb/L4/UX/src/l4/mybuild/lib --warn-common -Ttext-segment=0x01000000 main.o dummy.o splash.o vesa.o ld: section `.note.gnu.property' assigned to non-existent phdr `interp' ld: section `.rel.dyn' assigned to non-existent phdr `interp' I know that the ldscripts have been changed, but I struggle to see how the above relates to them or whether they are even involved in this particular outcome. Might there be something obviously wrong somewhere in the recent changes? Paul

2 7

L4Re development version available on GitHub
by Jakub Jermar 04 Jul '18

04 Jul '18

Dear L4 hackers, we in Kernkonzept are happy to announce the release of our L4Re operating system framework on GitHub. Today we release 6 new repositories: https://github.com/kernkonzept/mk https://github.com/kernkonzept/manifest https://github.com/kernkonzept/l4re-core https://github.com/kernkonzept/hello https://github.com/kernkonzept/drivers-frst https://github.com/kernkonzept/bootstrap Together with the Fiasco.OC repository released earlier this year[1], these repositories represent a frequently updated foundation for building operating systems with real-time, security, safety and virtualization requirements. The manifest repository contains a Wiki with detailed instructions on building[2] L4Re and contributing[3] to it. Happy hacking! Jakub [1] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2018/008224.html [2] https://github.com/kernkonzept/manifest/wiki/BUILDING [3] https://github.com/kernkonzept/manifest/wiki/CONTRIBUTING

1 0

Building programs with MODE=shared in L4Re
by Paul Boddie 04 Jul '18

04 Jul '18

Hello, I have been busy writing libraries and programs for L4Re and recently had to think about the size of the payloads I have been deploying. It appears that in the build system, one can use MODE=shared to build dynamically-linked programs, and there is a shared version of the hello example in the examples package. However, I don't see any recipe for doing this for other programs. My impression is that the dynamic linker must have all the required libraries deployed as modules, and so I wrote a script to generate a list of such modules using readelf. In addition, it appears that libl4sys-direct.so is required (which readelf does not detect). Adding these modules to my conf/modules.list should yield success, but within my constrained debugging environment, I only see that "shared" programs fail to start. I really need to see if they start but then experience some initialisation problem, or whether they actually crash but Mag keeps their viewports around. Are there any other things that I need to consider when building and deploying such programs? I searched for guidance on this topic and only found the following: http://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/007094.html http://os.inf.tu-dresden.de/pipermail/l4-hackers/2016/007830.html Both of these discussion threads only provide some details and are obviously not tutorials. Thanks for any clues you might be able to provide! Paul P.S. I guess I could also see if the CI20 produces useful console-level details, perhaps indicating an architecture-related problem. Usually, however, the problem is caused by some simple mistake I have made, so I suspect that there is merely some detail I have forgotten.

2 9

Release of Sculpt TC
by Alexander Boettcher 15 Jun '18

15 Jun '18

Hi l4-hackers, we are happy to announce the release of Sculpt TC [0], a Genode based incarnation of a microkernel based operating system. It is the second out of four Sculpt OS releases planned in 2018 [1]. Under https://genode.org/download/sculpt you find the downloadable image, which is a live system and installer all in one. Once booted you can download further packages to play around with, e.g several native Genode applications and VMs on several VMMs. Have fun. Cheers, Alex B. [0] https://lists.genode.org/pipermail/users/2018-June/006115.html [1] https://genode.org/about/road-map#2018_-_The_year_of_Sculpt -- Alexander Boettcher Genode Labs http://www.genode-labs.com - http://www.genode.org Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

2 3

Issues about webserver on L4Re
by 李鼎基 08 Jun '18

08 Jun '18

Hi, I’ve been trying to find or write a webserver directly on L4Re (*NO* L4Linux involved) based on snapshot “l4re-snapshot-17.12”. At first, I noticed that there was already a web server in “l4re-snapshot-17.12/src/l4/pkg/ankh”. But it was broken, even if I removed the “broken” file to make, nothing was generated under “/path/to/build/pkg/ankh” except “Makefile”. Then I intend to write a simple webserver (1st step a socket demo). Although there are socket APIs, I don’t know how to solve the NIC driver issues. The same code works well on Linux but failed on L4Re. Therefore: 1. Is there any way to revive the “ankh”? 2. If not, is there any way/demo to write a simple webserver directly on L4Re? Or how to solve the NIC driver issues? -- Thanks

2 1

Porting L4Re and Fiasco.OC to the Ben NanoNote and Letux 400
by Paul Boddie 30 May '18

30 May '18

As promised, I wrote up my experiences porting L4Re and Fiasco.OC to the Ben NanoNote: https://blogs.fsfe.org/pboddie/?p=2147 There are, in fact, nine articles describing the process, which I accept might be a bit too much reading for the casual inquirer, especially as the narrative wanders from one problem to be solved to the next. But the summary should cover the main tasks that need to be done in this kind of work. Since getting things working on the Ben, I have also persuaded the software to work on the Letux 400 notebook computer, which is a variant of the Skytone Alpha-400 product that did the rounds almost ten years ago (although I was probably completely unaware of it at that time): http://blogs.fsfe.org/pboddie/?p=2175 I hope that some of the information I have shared is useful to others and perhaps encourages someone else to port the software to a device of their choosing. Good luck to that person! Paul P.S. As noted before, the patches are here: http://www.boddie.org.uk/paul/L4Re-Fiasco.OC.html

2 5

Input driver configuration and use in L4Re
by Paul Boddie 25 May '18

25 May '18

Hello again, I have been implementing input drivers for the keypad/keyboard provided by the Ben NanoNote and Letux 400 notebook computer, and although I appear to have implemented something that works (tested using specialised example code), using the existing OMAP3 keypad code as a guide (in pkg/drivers/input), I wondered whether it is possible to connect such drivers to other components in a convenient way. I see that the input package is the thing that provides the device registry that I use when employing the arm_input_register macro, and in that package is a framework that supposedly exports input drivers as serial I/O devices using the "l4drv" driver. But I can't find anything obvious that uses the connect operation which would need to occur to probe, enable, and attach my driver to this framework. Is it possible to integrate my input drivers to things like Mag, which seems to use input events, or to fbterminal or other things? I haven't seen any documentation or code that demonstrates this, but I suppose that I may have missed something somewhere. Thanks for any help that is offered! Paul

2 4

Re: Assertion failure error in kernel vgic interrupt processing
by nico.hacker 14 May '18

14 May '18

Hi, The previous test is not enough to cause error, this error is not related to peripherals, I have removed almost all peripheral drivers In the previous test, I added a delay operation before the vm2 start, so that vm1 completely up and then start vm2, this will greatly reduce the probability of the error. Now I removed this delay, vm1 and vm2 started simultaneously, then the error will occur frequently (about 1/10 probability). The error is generated when kernel processes vtimer interrupts. Under normal circumstances, after processing a vtimer interrupt, the vcpu thread will return to uvmm and then execute prepare_guest_entry(). This operation will eventually enter the kernel through the system call to set the state of vcpu thread, but when the error occurs, I find that the vcpu thread does not execute vcpu_resume, it processes two consecutive vtimer interrupts. As a result, the assertion fails.  Is the kernel able to guarantee that the complete process of handling vgic and vtimer interrupts (including the process in uvmm) is not interrupted by a new interrupt?  Here's my configuration: ------------------------------------------------------------------------- uvmm.ned vmm.start_vm{   id=1,   mem=256,   vbus=io_busses.vm_hw,   bootargs=common_bootargs .. " ramdisk_size=9100 root=/dev/ram",   kernel="rom/Image.gz",   rd="rom/ramdisk-arm.rd",   fdt="rom/virt-board.dtb",   prio=nil, cpus=0x1 }; vmm.start_vm{   id=2,   mem=256,   vbus=io_busses.vm_nohw,   bootargs=common_bootargs .. " ramdisk_size=9100 root=/dev/ram",   kernel="rom/Image.gz",   rd="rom/ramdisk-arm.rd",   fdt="rom/virt-board.dtb",   prio=nil, cpus=0x1 }; -------------------------------------------------------------------------- io.cfg -- vi:ft=lua local Res = Io.Res local Hw = Io.Hw local add_children = Io.Dt.add_children add_children(Io.system_bus(), function()   VGIC = Hw.Device(function()     Property.hid = "arm-gicc";     Resource.reg0 = Res.mmio(0x12006000, 0x12007fff);     Property.flags = Io.Hw_device_DF_multi_vbus;   end)   VM1_DEV = Hw.Device(function()     Property.hid = "vm1_dev";     Resource.reg0 = Res.mmio(0x70100000, 0x70100FFF); --UART   end)   VM2_DEV = Hw.Device(function()     Property.hid = "vm2_dev";     Resource.reg0 = Res.mmio(0x70100000, 0x70100FFF); --UART   end) end) ---------------------------------------------------------------------------- vm_hw.vbus Io.add_vbusses {   vm_hw = Io.Vi.System_bus(function()     VGIC = wrap(Io.system_bus():match("arm-gicc"));     VM1_DEV = wrap(Io.system_bus():match("vm1_dev"));   end); } ---------------------------------------------------------------------------- vm_nohw.vbus Io.add_vbusses {   vm_nohw = Io.Vi.System_bus(function()     VGIC = wrap(Io.system_bus():match("arm-gicc"));     VM2_DEV = wrap(Io.system_bus():match("vm2_dev"));   end); }---------------------------------------------------------------------------- Nico 于 2018-04-11 05:59:58,Adam Lackorzynski<adam os="" inf="" tu-dresden="" de="">写道:</adam><blockquote style="padding-left:1ex;margin:0px 0px 0px 0.8ex;border-left:#ccc 1px solid"><pre>On Mon Apr 09, 2018 at 22:26:38 +0800, nico wrote: > Sorry, the last email did not specify this information. > I gave VM1 all the hardware resources, and it used eight cores. VM2 only has > uart resources (also timer, gic resources), using a single core. I tried to > give both VM1 and VM2 only the necessary hardware resources( uart, timer, gic), > and that error won't happen. Ok, that's interesting. So that means that some of the passed through hardware is causing this. Would you be able to find out which device is causing this, by selectively enabling/disabling devices? Adam > On 4/9/2018 06:28ï¼ Adam Lackorzynski<adam os="" inf="" tu-dresden="" de=""> wroteï¼ > > Hi Nico, > > On Fri Mar 30, 2018 at 10:15:33 +0800, nico wrote: > > Hi Adam, I'm using an eight-core Cortex-A53 processor. The vm is > running 64bit Linux. It is recommended to start two or three vms, that > will be easier to reproduce this problem. > > > So, I tried several things but cannot reproduce this issue. I assume > this are single-core VMs only? Any hardware passed through? > Just trying to narrow it down... _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers </adam></pre></blockquote><div style="height:30px;"></div><div style="height:2px;width:298px;border-bottom:solid 2px #e5e5e5"></div><div style="height:20px;"></div><a target="_blank" style="background-image:url(http://r.g.tom.com/kwap/r/app/other/suixinyou.png);bac… center;font-size:14px;background-size: 20px;height: 39px;line-height: 39px;padding-left: 25px;display:block;color:#333333;text-decoration: none;" href="http://mail.tom.com/webmail-static/welcomesxy.html" onmouseover="this.style.cssText='background-image:url(http://r.g.tom.com/kwap/r/app/other/suixinyou.png);bac… center;font-size:14px;background-size: 20px;height: 39px;line-height: 39px;padding-left: 27px;display:block;color:#4c4c4c; text-decoration:underline;'" onmouseout="this.style.cssText='background-image:url(http://r.g.tom.com/kwap/r/app/other/suixinyou.png);bac… center;font-size:14px;background-size: 20px;height: 39px;line-height: 39px;padding-left: 27px;display:block;color:#4c4c4c;text-decoration:none'">随心邮-在微信里收发邮件，及时省电又安心</a>

2 1

Assertion failure error in kernel vgic interrupt processing
by nico 10 Apr '18

10 Apr '18

2 5