users December 2021

users@lists.genode.org

11 participants
8 discussions

Roadmap 2022
by Norman Feske 01 Feb '22

01 Feb '22

Dear Genode community, it is the time of the year again to reflect and make plans for the foreseeable future. Hereby, I'd like to kick off our traditional brainstorming about Genode's road map for the year ahead of us. What happened in the previous episode... ---------------------------------------- I have two perspectives to share. One is the look at Genode as our project, and the other one is my personal view. Let's start with the first one. When reviewing the past twelve months, I am immensely proud of the accomplishments of our team. Together, we conquered the territory of GPU support that was ridden with uncertainties and seemed almost impenetrable when we started. Now, our Intel GPU multiplexer has landed in Sculpt like it always belonged there. The next highlight was witnessing the puzzle pieces of our new Linux device-driver environment coming together, replacing former confusion and chaos with knowledge and order, ultimately uncovering the treasure of Linux drivers for Genode with very little friction. The third highlight was witnessing the growing sophistication of Genode-native workloads, with the media features of the Chromium-based browser on 64-bit ARM being the most impressive example. Apart from the apparent functional benefits for Genode and Sculpt OS, this is the long outstanding validation of some arguably risky design decisions we took many year ago, in particular the role and architecture of the VFS and its interplay with the libc. When reviewing the road map for 2021 [1], some items remained uncovered. In particular the seL4-related topics became stale. One year ago when I assembled the road map, there was a tangible prospect of a paying customer funding this work. However, those plans were repeatedly deferred and we don't know whether or when they will come to fruition. I was too optimistic. Also, there are some items that have seen healthy doses of progress - like the topics related to Ada/SPARK or Goa - but received less attention than anticipated. On the other hand, the four releases [2,3,4,5] of this year covered quite a few topics not advertised at the road map, e.g., webcam support, Xilinx Zynq, or RISC-V. Priorities shift. That's fine. [1] https://genode.org/about/road-map [2] https://genode.org/documentation/release-notes/21.02 [3] https://genode.org/documentation/release-notes/21.05 [4] https://genode.org/documentation/release-notes/21.08 [5] https://genode.org/documentation/release-notes/21.11 >From my personal perspective, I've wholly enjoyed the work on the Pinephone as documented in my "Pine fun" article series at Genodians.org [6]. Much of the enjoyment came from the _process_, in particular the co-development of the new DDE-Linux together with Stefan, the mutual cross-validation of ideas and code, and our joint sense of great care. Granted, feature-wise, I missed my original goal of being able to issue phone calls with Genode on the Pinephone by now. But the collateral effects of the work in terms of tooling (dts_extract), interfaces (Genode-C-API), and documentation ("Genode Platforms") deserved the attention they got. [6] https://genodians.org What's up for next year? ------------------------ I'm in full swing with the Pinephone. So I will keep moving full steam ahead. With the touchscreen and display tamed now, the next topics are telephony, mobile-data connectivity, Sculpt, browser, and a simple user interface. Over the year, I will increasingly focus on non-functional aspects as well, in particular power management (battery life) and quality of service (UI latency, audio latency). By the end of the year, I want to be able to casually use a video-chat solution like Jitsi on the phone. Besides the Pinephone, I am planning to simplify and solidify Genode's base framework by gradually removing complexity (like C++ exceptions [7]), increasing the strictness of the coding style (like the aftermath of [8]), and attending the most-neglected corners of our issue tracker [9]. [7] https://genodians.org/nfeske/2021-11-26-attempt-no-exceptions [8] https://genodians.org/nfeske/2021-12-07-wconversion [9] https://github.com/genodelabs/genode/issues What about you? --------------- My point of view outlined above is only one way to look at the picture. Now I would be interested in your perspective! What's your reflection of Genode's past year? What are the topics you deem as most interesting to work on? Do you already have tangible plans you can share with us? Are there road blocks that stand in the way of your plans? What is your vision of using Genode at the end of 2022? I hope that this posting spawns a fruitful discussion of potential topics for the next episode. Please be considerate to avoid dropping mere proposals or wish lists. It's best to present suggestions together with actionable steps that you are willing to take. In mid of January, I am going to update the official road map. Cheers, Norman -- Dr.-Ing. Norman Feske Genode Labs https://www.genode-labs.com · https://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

11 36

now you can run http web server based on golang in genode 21.11
by Alexander Tormasov 23 Dec '21

23 Dec '21

I have a progress in porting of golang from gcc 10.3 to genode 21.11. Seems that now it suitable for external testing. More details in https://github.com/tor-m6/genode-world/blob/21.11/src/test/go_app/README.go… In particular, it is possible to run most of the golang programs, including tcp network (http server from net/http package) in SMP mode (tested on 4 cpu) on genode for nova, foc and linux, run inside qemu (or on linux), for x86_64. May be some other platforms works as well (except sel4- see below). To run you need 2 repos: https://github.com/tor-m6/genode.git Need to checkout 21.11 branch - while it have only one commit introducing .go as a target for compilation. support code is in repos/world (don’t forget to uncomment it) https://github.com/tor-m6/genode-world.git (Need to checkout 21.11 branch) I successfully run some tests with channels/async goroutines - some of them (Like Hanoi towers or barber serving) inside https://github.com/tor-m6/genode-world/blob/21.11/src/test/go_app/main.go also you can run network code like this: package main import ( "fmt" "log" "net/http" ) func main() { http.HandleFunc("/", HelloServer) fmt.Println("Server started at port 80") log.Fatal(http.ListenAndServe(":80", nil)) } func HelloServer(w http.ResponseWriter, r *http.Request) { fmt.Fprintf(w, "Hello, %s!\n", r.URL.Path[1:]) } Future plan: - add arm64 support - check sel4 problem - add automated generation of part of run file (all shared libs/binaries need to appears in appropriate places to unwind process works correctly) - check performance problems on sel4 and foc (probably timeouts/timer, waits too long in the very beginning) - try to integrate it in native mode to create workable «go build» code inside genode as native compilation. Note1: currently it can’t run on x86_64 sel4 because during initial golang stack unwind process it touch stack guard page, deeply inside _Unwind_Backtrace libgcc function (not sure why - probably this is compiler flags/optimisation issue). Once I have workable version with different debug options… Note2: May be it worth to add patch below permanently to main genode? diff --git a/repos/base/mk/generic.mk b/repos/base/mk/generic.mk index 66e5c309c..aea75e342 100644 --- a/repos/base/mk/generic.mk +++ b/repos/base/mk/generic.mk @@ -7,7 +7,7 @@ # Collect object files and avoid duplicates (by using 'sort') # SRC_O += $(addprefix binary_,$(addsuffix .o,$(notdir $(SRC_BIN)))) -SRC = $(sort $(SRC_C) $(SRC_CC) $(SRC_ADB) $(SRC_ADS) $(SRC_RS) $(SRC_S) $(SRC_O)) +SRC = $(sort $(SRC_C) $(SRC_CC) $(SRC_ADB) $(SRC_ADS) $(SRC_RS) $(SRC_S) $(SRC_O) $(SRC_GO)) OBJECTS = $(addsuffix .o,$(basename $(SRC))) # @@ -69,6 +69,16 @@ endif $(MSG_ASSEM)$@ $(VERBOSE)$(CC) $(CC_DEF) $(CC_C_OPT) $(INCLUDES) -c $< -o $@ +# +# Compiling Go sources +# +%.o: %.go + $(MSG_COMP)$@ + $(VERBOSE)$(GOLANG) $(CUSTOM_GO_FLAGS) -c -o $@ $< + +CUSTOM_GO ?= $(CROSS_DEV_PREFIX)gccgo +GOLANG = $(CUSTOM_GO) + # # Compiling Ada source codes #

3 4

Genode and sign-conversion warnings.
by Piotr Tworek 21 Dec '21

21 Dec '21

Hello, Since Wconversion got enabled on Genode master branch I'm wondering if there are any plans WRT Wsign-conversion warnings? I presonally find it a bit strange GCC Wconversion does not also enable Wsign-conversion. IMO implicit conversions between signed and unsigned types are as often as bad as implicit conversion between types of different size. /ptw

2 2

CBE key encryption
by Stefan Thöni 19 Dec '21

19 Dec '21

Hello Genodians, we are still working to add hardware-based encryption to CBE. To this end, we have implemented a custom trust anchor and crypto engine. Generating a key, encrypting this key on behalf of cbe_init and decrypting it again on behalf of the vfs_cbe plugin works fine. But then the vfs_cbe requests to have a all zero key encrypted which due to the ICV added by hardware black key handling fails. We cannot seam to find out where the request originates or why vfs_cbe would ever encrypt any key, let alone a key of all zeros. Any pointer or idea would by very welcome. Kind regards Stefan

4 4

Silly Sculpt Build Problem
by John J. Karcher 16 Dec '21

16 Dec '21

Hello, Recent updates to Debian Unstable seem to be causing a few minor build problems in Genode. Automake being updated from 1.15 to 1.16 was simple to solve, but I have another problem that I'm not sure how to solve. Depending of whether I'm building a disk image or an ISO, I get one of the following errors: Error: 'e2mkdir' command could be not found. or: Error: 'xorriso' command could be not found. But both of those commands are available, and worked up until recently. Does anyone have any thoughts on what might cause this? Thanks! -- John J. Karcher devuser(a)alternateapproach.com

4 7

VFS plug-in that requires early libc initialization (for FUSE)
by ttcoder＠netcourrier.com 08 Dec '21

08 Dec '21

Hey Genode team, fellow Genodians, I'm trying to modify FUSE-server to become a VFS plug-in (see genode-world#193) but it seems "with_libc()" no longer works, when in a plug-in attached to the test-libc_vfs test harness: [init -> test-libc_vfs] ---->open_Dir [init -> test-libc_vfs] Error: Uncaught exception of type 'Libc::Kernel::Kernel_called_prior_initialization' [init -> test-libc_vfs] Warning: abort called - thread: ep Questions: --------- Seems a VFS plug-in is initialized first, before libc has had a chance to be initialized ? While digging in the code, here is what I can gather: in the previous incarnation of the code, where FUSE is an FS server, the server would call Libc::Component::construct() early, which would initialize the libc/kernel: kernel = *unmanaged_singleton<Libc::Kernel>(..) and then subsequent calls to libc would work. But now, the VFS plug-in (and its libc-using code) is called first. Is that the right explanation for my problem? Alternative explanation: maybe the libc framework from the _host_ component is not shared with its child VFS plug-in at all ? Tracing: ------- I then removed calls to libc, and added some tracing to the now free-flowing code, to get some sense of chronology, determine who is called when. The result was interesting: it seems when a VFS plug-in is instantiated, its hooks are called before anything else is called (I'm not the one calling them, as my code is still at an early "skeleton" stage yet, I make no call to opendir() etc, so someone else is doing that), including even before the host "Main" : [init -> test-libc_vfs] ---->open_Dir [init -> test-libc_vfs] ---->num_dirent [init -> test-libc_vfs] ---->directory [init -> test-libc_vfs] ---->directory [init -> acpi_drv] SMBIOS table (entry point: 0x165700 structures: 0xf5720) [init -> platform_drv] ECAM/MMCONF range 00000000:00000000.0-000000ff:0000001f.7 - addr [00000000b0000000,00000000c0000000) [init -> test-libc_vfs] test-libc-vfs: ctor of struct Main : reading config ROM [init -> test-libc_vfs] test-libc-vfs: entering with_libc() [init -> test-libc_vfs] test-libc-vfs: calling test() from libc context [init -> test-libc_vfs] ---->leaf_path [init -> test-libc_vfs] Error: Uncaught exception of type 'Test_failed' So based on that 'evidence' alone, it would seem the event chronology is somewhat like this: - test-harness is loaded by LD - LD looks for its plugins, loads them, and executes them first (even if they require libc) - test-harness / struct Main is called, initializing libc etc Maybe my FUSE plug-in should detect when libc is not yet initialized, reject all calls to its hooks done at that early time, and only honor them later on ? Cedric

2 3

RISC-V Genode availability ?
by Turlough Suilleabhain 08 Dec '21

08 Dec '21

Question: Is the RISC-V seL4 implementation only available for the Hensoldt Cyber MIG-V processor as Trentos-G or is that source tree branch intended for wider public release and other RISC-V processors ? Thank you in advance..

2 1

CfP: Microkernel and Component-based OS Devroom at FOSDEM 2022 (fwd)
by Christian Helmuth 07 Dec '21

07 Dec '21

Hey Genodians, FOSDEM 2022 will be an online event (again), but the traditional Microkernel devroom will be part of it. Thanks to Martin Decky for engagement! The original Call for Papers follows. Best regards Christian Date: Mon, 6 Dec 2021 16:55:45 +0100 From: Martin Decky <martin(a)decky.cz> To: microkernel-devroom(a)lists.fosdem.org Subject: CfP: Microkernel and Component-based OS Devroom at FOSDEM 2022 Microkernel and Component-based OS Devroom at FOSDEM 2022 CALL FOR PARTICIPATION On-line version of this CfP: http://fosdem.microkernel.info/ The developers and users of several free and open source microkernel-based and component-based operating systems will meet on-line as part of FOSDEM 2022 [1] and will share a developer room. The devroom is currently looking for content in the form of talks and activities related to the area of microkernel-based, unikernel-based, component-based operating systems and similar topics. The devroom has been preliminarily scheduled to Saturday February 5th 2022. The devroom will take place during European day hours. Possible topics of the devroom include, but are not limited to: * introduction of a specific OS or framework * design of subsystems and the general architecture of an OS * languages, tools and toolchains used * enabling support for hardware (architectures, device drivers) and programming languages * development processes, debugging * maintenance, testing and release engineering * safety, security and robustness * trends and challenges * research and open questions * community and governance * use cases, experiences and status updates * best practices and lessons learned * demos This is a call for your participation. We kindly ask you to submit your proposals no later than on December 28th 2021. Please use the Pentabarf web site [2] to submit your proposals. If you already have a user account in Pentabarf, please do not create a new one. Addtionally, make sure to select the Microkernel and Component-based OS Devroom as the track when submitting your talk and include at least the following information in your proposal: * title of your talk * your full name * short abstract of your talk (one or two paragraphs) * duration of your talk (at least 20 minutes and no longer than 50 minutes) * your short bio * your photo The talks will be pre-recorded in advance in January and streamed automatically during the event. This means that you will need to complete and submit your talk recording by January 15th 2022. However, each speaker should be also present on-line just after the streaming of their talk for a live Q&A. You can specify your prefered time slot of your talk. The communication language of the devroom is English. The official devroom schedule (along with the accepted talks) will be announced on December 31st 2021 on the devroom's mailing list [3] and the speakers will be notified via e-mail. The schedule will also be published on the FOSDEM web site. For any comments, questions and suggestions (e.g. suggestions for a different type of event during the devroom), please do not hesitate to use the devroom's mailing list [3]. About the Devroom Since the first Microkernel OS Devroom at FOSDEM 2012 [4], this devroom has been a part of each following FOSDEM (with slight variations of the name). The focus gradually widened to include component-based, unikernel-based and other operating systems. By now, it has become a somewhat institutionalized tradition for the open source operating systems community and it is one of the few places where microkernel enthusiasts and people with different views on how operating systems should work meet regularly. To this date, over a dozen projects have participated in one way or another. Many of the projects face similar challenges but come up with partially different solutions. Therefore, the goal of the devroom is to bring the various projects together, let them exchange ideas, cross-pollinate and socialize. Extraordinary Circumstances in 2022 (Again) Due to the extraordinary mode of organization of FOSDEM 2022 (being an on-line event again), the devroom talks will be required to be pre-recorded in January and streamed during the event (with a live Q&A). The talk videos will be published under Creative Commons license by FOSDEM. By submitting a recorded talk, the speaker agrees to have it made available publicly indefinitively. For organizational purposes, we also need contact information of the speakers of accepted talks. Please check the official CfP page [5] of the devroom regularly. We will keep updating it as technical guidelines will be set by the FOSDEM organizers. Microkernel Dinner Sadly, it will not be possible to arrange our traditional microkernel dinner and other in-person social gatherings in Brussels this time again. However, we plan a closing event of the devroom as a loose approximation of the microkernel dinner. The details will be announced later. We encourage the on-line participats to bring their own food and beverages. About FOSDEM FOSDEM [6] is a two-day event organized by volunteers to promote the widespread use of free and open source software. FOSDEM is widely recognized as one of the best such conferences worldwide. FOSDEM covers a wide spectrum of free and open source software and hardware projects and offers a platform for people to collaborate. To this end, FOSDEM has set up developer rooms (devrooms) 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 proposals. Besides developer rooms, FOSDEM also offers main tracks, lightning talks, certification exams and project stands. In recent years, FOSDEM has been hosting more than 5000 developers annually at the ULB Solbosch campus. Due to the circumstances, FOSDEM 2022 will be organized as an on-line event. The participation in FOSDEM is totally free, although the organizers gratefully accept donations and sponsorship. No registration is necessary, but attendees are expected to follow the FOSDEM's code of conduct [7]. Important Dates Recap * 2021-12-28: Deadline for talk proposal submission * 2021-12-31: Schedule published and speakers notified of acceptance * 2022-01-15: Deadline for talk pre-recoding submission * 2022-02-05: Devroom taking place on-line Contact In case of any comments, questions and suggestions, please do not hesitate to contact the devroom organizers via the devroom's mailing list [3]. The primary organizers of the devroom in 2022 are: * Sebastian Sumpf * Martin Decky Links [1] https://fosdem.org/2022/ [2] https://penta.fosdem.org/submission/FOSDEM22/ [3] https://lists.fosdem.org/listinfo/microkernel-devroom [4] https://archive.fosdem.org/2012/schedule/track/microkernel_os_devroom.html [5] http://fosdem.microkernel.info/ [6] https://fosdem.org/ [7] https://fosdem.org/2022/practical/conduct/ _______________________________________________ microkernel-devroom mailing list microkernel-devroom(a)lists.fosdem.org https://lists.fosdem.org/listinfo/microkernel-devroom ----- End forwarded message ----- -- Christian Helmuth Genode Labs https://www.genode-labs.com/ · https://genode.org/ https://twitter.com/GenodeLabs · https://www.genodians.org/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users December 2021