users

users@lists.genode.org

2285 discussions

pager in Genode
by Chen Tian - SISA 13 May '11

13 May '11

Hello, I am trying to understand the memory management and pager implementation in Genode. I am stuck on Rm_client::pager function in rm_session_component.cc. Can somebody explain to me the main idea behind it, especially the reverse_lookup function? I must have missed some important data structures or designs of the memory management in RAM or Rm. Thanks. Regards, Chen

2 1

lwip examples
by Amadeo Cuadrado 13 May '11

13 May '11

Hello, I have not been able to run any of the lwip examples (I am using 32 bits): loopback hangs in socket() call, and http_srv hangs in the lwip_nic_init() call. I am using the Nic driver from dde_gpxe, since I got compilation errors when building the linux_drivers: .../genode/linux_drivers/src/linux26/arch/i386/lib/bitops.c: In function 'find_next_zero_bit': .../genode/linux_drivers/include/linux26-x86/asm/bitops.h:283: error: can't find a register in class 'BREG' while reloading 'asm' .../genode/linux_drivers/include/linux26-x86/asm/bitops.h:283: error: 'asm' operand has impossible constraints Any clue what I could be missing here to make these examples work? Let me know if you need more info about my environment. Thanks. Amadeo

5 9

Multiple TCP/IP apps
by Александр Домо 12 May '11

12 May '11

Hello, again! Could you please suggest the proper way to use the lwip library in multiple processes, especially, with libc_lwip_nic_dhcp? From my point of view, lwip alone should work ok in multiple processes, as long as a static IP-address is assigned. Those processes start communicating with the nic driver and just work along. Or they don't? As for the dhcp part, it gets more complicated. Do they all get the same IP address? As far as I know DHCP, they do. But I don't think this is really nice, when all the applications start querying for IP addresses. Maybe I should write a real, hard-core, independent TCP/IP module, which would offer IP services to everyone else, like it's done in QNX, for example? But that's not so easy, right? I'd prefer the easy way first ;) Thanks!!

2 1

malloc/free functions.
by Chen Tian - SISA 10 May '11

10 May '11

Hi, I found that malloc/free functions have been implemented in at least three different libraries: cxx, mini_c and libc. I assume cxx is used for genode base and core implementations, mini_c for demos and libc for porting. However, I am not able to use any of them in my own application. When using malloc defined in mini_c or libc, I got a compiler error " reference to 'size_t' is ambiguous". It looks like both stdlib.h in mini_c (or libc) directory and stdint.h in base directory have defined "size_t" type. And I cannot get rid of the use of stdint.h as it has been included in many genode base and core files. On the other hand, if I wanted to use the malloc in cxx by putting "cxx" into LIB in my application's target.mk, malloc cannot be recognized by the compiler. To solve this problem, I currently have to define my own malloc/free by copying the implementation from cxx and it works. However, I really wonder which malloc/free defined in genode should I use and how? By the way, the implementation of heap()->alloc() is thread-safe, right? Thanks. Chen

2 1

Another Genode on Fiasco.OC issue...
by Guess Who? 13 Apr '11

13 Apr '11

I loaded the toolchain, as detailed in the Genode on Fiasco.OC site and when I built the L4Re environment I got this: ==> Installing crti.o to local build-tree ... Compiling crtn.o initfini.c: Assembler messages: initfini.c:29: Error: .size expression for _init does not evaluate to a constant initfini.c:29: Error: .size expression for _fini does not evaluate to a constant make[3]: *** [crtn.o] Error 1 make[3]: Leaving directory `/home/wegrzyn/Fiasco/L4re-build/pkg/ldscripts/OBJ-x86_core2' make[2]: *** [/home/wegrzyn/Fiasco/L4re-build/pkg/ldscripts/OBJ-x86_core2] Error 2 make[2]: Leaving directory `/home/wegrzyn/Fiasco/src/l4/pkg/ldscripts' make[1]: *** [ldscripts] Error 2 make[1]: Leaving directory `/home/wegrzyn/Fiasco/src/l4/pkg' make: *** [pkg] Error 2 Can anyone venture a guess what I need to correct? Peace, Chance

3 2

Building Genode on Fiasco.OC - problem
by Guess Who? 13 Apr '11

13 Apr '11

I followed the instructions on "Genode on Fiasco.OC" (http://genode.org/community/wiki/GenodeOnFiascoOC) and ran into a problem. When I got to the step to building L4Re I got the following: *** No rule to make target '.../lib32/crtendS.o', needed by 'libl4sys.so'. I am building this on an x86_64 system, and I am sure it is looking for a 32-bit obj on a 64 bit system. Does anyone know how to fix this problem? Peace, Chance

2 5

Newbie question booting fiasco0C x64 with genode
by Robert Holvast 12 Apr '11

12 Apr '11

Dear all I got as far as building fiascoOC on x86-64 L4Re build successful Can create the iso to boot ok Genode fiascoOC build successful (note in foc.conf generated by create_bulddir to many spaces, blocked correctly including the L4_DIR includes aka in my case: Org: L4_DIR = /Projects/FiascoOC/src/l4/build Changed to:L4_DIR=/Projects/FiascoOC/src/l4/build) Newbie questions How to create boot cd genode How to create a qemu image that can boot on virtual qemu disk volume aka partition filetype ext2 fat15 fat32 ? I want to port ClickRouter to Genode framework Which option would be the best if not wanting to use L4Linux What i mean is the polling mechanism of clickrouter as i use some of my own modules in clickrouter Regards Robert

2 1

New challenges ahead
by Norman Feske 26 Mar '11

26 Mar '11

Hello, with each new Genode release, we find ourself inspired to reach out for a growing number of use cases of the framework. There is a dedicated Wiki page for documenting those ideas: http://genode.org/community/wiki/Challenges However, this Wiki page received not much love during the last year. Now, after having released the version 11.02, we took the chance to reiterate over the many ideas that popped up recently. We are actually pretty excited about all the prospects that have become feasible now. So if you are curious about what kinds of projects we have in mind in the mid term, have fun browsing through the project proposals. If one of these topics catches your interest, we'd be happy about you joining in with the development. Also, if you have additional ideas, please do not hesitate to tell us more. Here are the challenges that we just added, sorted by category: Applications ============ Chrome web browser ~~~~~~~~~~~~~~~~~~ The Chrome web browser promises to address the most pressing security concerns of web application by isolation measures, in particular the sandboxing of plugins and the confinement of individual web applications. As we demonstrated with the Genode Live CD 10.11, Genode facilitates a more natural way to pursue such techniques compared with current commodity operating systems. Furthermore, the use of Genode as base platform for Chrome would strengthen the web-browser security by dwarfing its trusted computing base by two orders of magnitude compared to the use of Linux as base platform. This would allow Chrome to be considered as a secure interface to the web for use cases in the high-assurance domain. VNC server implementing Genode's framebuffer session interface ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ With 'Input' and 'Framebuffer', Genode provides two low-level inter- faces used by interactive applications. For example, the Nitpicker GUI server uses these interfaces as a client and, in turn, exports multiple virtual 'Framebuffer' and 'Input' interfaces to its clients. This enables a highly modular use of applications such as the nesting of GUIs. By implementing the 'Framebuffer' and 'Input' interfaces with a VNC server implementation, all graphical workloads of Genode would become available over the network. One immediate application of this implementation is the remote testing of graphical Genode applications running on a headless server. Tiled window manager ~~~~~~~~~~~~~~~~~~~~ At Genode Labs, we pursue the goal to shape Genode into an general- purpose operating system suitable for productive work. The feature set needed to achieve this goal largely depends on the tools and applications daily used by the Genode engineers. As one particularly important tool for being highly productive, we identified a tiled user interface. Currently, all developers at Genode Labs embrace either the Ion3 window manager or the tiled Terminator terminal emulator. Hence, we desire to have a similar mode of user interaction on Genode as well. The goal of this challenge is to identify the most important usage patters and the implementation of a tiled GUI that multiplexes the framebuffer into a set of tiled and tabbed virtual framebuffers. Related to this work, the low-level 'Framebuffer' and 'Input' interfaces should be subject to a revision, for example for enabling the flexible change of framebuffer sizes as needed by a tiled user interface. Interactive sound switchbox based on the Audio_out session interface ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Since version 10.05, Genode features a highly flexible configuration concept that allows the arbitrary routing of session requests throughout the hierarchic process structure. Even though primarily designed for expressing mandatory-access control rules, the concept scales far beyond this use case. For example, it can be used to run an arbitrary number of processes implementing the same interface and connecting the different interface implementations. One special case of this scenario is a chain of audio filters with each using the 'Audio_out' session interface for both roles client and server. Combined with the Nitpicker GUI server and Genode's support for real-time priorities, this base techniques enable the creation of flexible audio mixer / switchboard applications, which require dedicated frameworks (e.g., Jack audio) on traditional operating systems. The goal of this project is to create a show case implementation demonstrating the feasibility for creating high- quality audio applications on Genode. Furthermore, we wish for feedback regarding the current design of our bulk streaming interface when used for low-latency applications. PDF reader for E-Government use ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A facility for reading PDF and E-Book documents is one of the indispensable features Genode has to provide to be considered for general-purpose computing. The goal of this work is to identify a suitable open-source PDF engine and port it as native application to Genode. The challenging part is to keep the complexity of this application as low as possible in order to enable the use of this application as a trusted document reader. Further ideas envision the use of PDF files as medium for sensitive documents combined with measures for protecting the integrity of the displayed information. For example, when processing contracts or similar sensitive documents in E-Government scenarios, the consumer of such documents expects the correct display of all the information as expressed by the creator of the document. In the event of a compromised PDF engine or a man-in-the middle attacker manipulating the PDF file, the consumer of the document requires a way to identify such security breaches. In this context, running the PDF engine in a sandboxed Genode subsystem has two incentives. First, the attack surface for manipulating the PDF engine gets dramatically reduced, and second, the integrity of the result of the PDF engine can be measured by an independent trusted component facilitating Genode secure GUI server (Nitpicker). Graphical on-target IPC tracing tool using Qt4 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Analysing the interaction of components of a multi-server operating system such as Genode is important to discover bottlenecks of the system and for debugging highly complex usage scenarios involving many processes. Currently, Genode handles this problem with two approaches. First, Genode's recursive structure enables the integration of a subsystem in a basic OS setup featuring only those drivers and components used for the particular subsystem. After the successful integration of such a subsystem, it can be embedded into a far more complex application scenario without any changes. With this approach, the subject to analyse can be kept at a reasonable level at integration time. For debugging purposes, the current approach is using the debugging facilities of the respective base platforms (e.g., using GDB on Linux, the Fiasco kernel debugger, the OKL4 kernel debugger). However, in many cases, bottlenecks do not occur when integrating individual sub systems but after integrating multiple of such subsystems into a large application scenario. For such scenarios, existing debugging methodologies do not scale. A tool is desired that is able to capture the relationships between processes of a potentially large process hierarchy, to display communication and control flows between those processes, and to visualize the interaction of threads with the kernel's scheduler. Since Qt4 is available natively on Genode, the creation of both offline and on-target analysis tools has become feasible. The first step of this project is creating an interactive on-target tool, that displays the interaction of communicating threads as captured on the running system. The tool should work on a selected kernel that provides a facility for tracing IPC messages. Application frameworks ====================== Running the Meego application stack on Genode using Qt4 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ With Genode 11.02, Qt4 4.7.1 has become available. The most prominent feature of this version is the new QML language to design GUIs using a declarative language. This technique is targeted specifically to mobile applications and other touch-based devices. The goal of this project is to run the Meego application stack natively on Genode. First, the software components and Meego-specific Linux customizations must be identified. For each such component, it must be decided whether to port its code or to reimplement its interface. The immediate goal of the first step is running one Meego example application natively on Genode. Python Qt4 bindings ~~~~~~~~~~~~~~~~~~~ With the Python interpreter and the port of the Qt4 framework, the principle components for Python-based GUIs on Genode are available. However, the glue between both components is missing. The incentive of this work is supplementing our Python port with the modules needed for real applications and porting the Qt4 bindings to Genode. This would bring Genode one step closer to executing modern Python-based GUI applications (in particular KDE4 applications). Evaluation of porting GTK+ to Genode ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ With Qt4, we have demonstrated the feasibility to run a highly-complex application framework via Genode on a wide range of microkernels. That leaves the question of looking into the other major toolkit in town, namely GTK+ as used by Firefox and the Gnome desktop. Cairographics ~~~~~~~~~~~~~ Cairo is a high-quality 2D vector graphics engine used by a large number of open-source projects, in particular GTK+. Hence the port of Cairo is a prerequisite for the GTK+ challenge. In addition, it would enable the use of further libraries such as Poppler. Device drivers ============== SATA block driver ~~~~~~~~~~~~~~~~~ Genode already features a session interface for accessing block devices. Currently, there exist two implementations of this interface, which are the ATAPI block driver for accessing CDROMs and a loopback block driver. The goal of this project is a working SATA driver that enables the persistent storage of data on disk. It is a prerequisite for enabling the use of real file systems with Genode. We regard our ATAPI driver as a suitable starting point for such an undertaking. Gallium3D ~~~~~~~~~ Genode 10.08 introduced Gallium3D including the GPU driver for Intel GMA CPUs. With this initial version, we demonstrated that the powerful software stack for running hardware-accelerated 3D applications can be deployed on Genode. At the same time, it motivates us to reach out for even more ambitious goals: First, the current approach executes the GPU driver alongside the complete Gallium3D software stack and the application code in one address space. To enable the use of multiple hardware-accelerated applications running at the same time, the GPU driver must run separated from the Gallium3D code as done on Linux. The preliminary interfaces for this decomposition are already in place but there are several open questions. Most importantly, the page-fault handling of buffer objects mapped in the application's address space. Second, we'd like to complement our current Intel GMA GPU driver with interrupt-based synchronization, namely vblank handling. This requires an understanding of the Intel GMA interrupt code and the enhancement of our driver environment. Third, we desire the use of further Gallium3D drivers, in particular the Nouveau and r300 drivers. The basic approach to bring these drivers to Genode is the same as for Intel GMA but the respective driver environments are yet to be developed. If you are interested in low-level graphics hacking, GPUs, and high-performance graphics, this project is ideal to get you on track. Split USB core from USB device drivers ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Genode's current USB support is based on the Linux USB stack running as a single process on Genode. This process includes the USB core logic, USB host controller driver as well as the USB device drivers such as HID or USB storage. This monolithic USB process is rather inflexible. Hence, we desire a decomposition of this solution such that the USB host driver and each USB device driver runs in a separate process. IOMMU support on the NOVA Hypervisor ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The NOVA hypervisor is the first open-source microkernel with thorough support for IOMMUs, which principally enables the use of untrusted device drivers alongside sensitive software on one machine. Without an IOMMU, each device driver for a device that operates with DMA, is able to indirectly access the whole physical memory through programming the device. With IOMMU, the physical memory addressable by DMA operations can be restrained per device. The goal of this challenge is to enhance Genode with I/O protection when running on the NOVA kernel. This would clear the way towards reusing complex untrusted device drivers running in dedicated device-driver OS instances. I/O Kit ~~~~~~~ I/O Kit is the device-driver framework as used by the Darwin operating system, which forms the basis for Mac OS X. The port of I/O Kit would enable the easy re-use of the library of I/O-Kit-based device drivers on Genode. As foundation of this project, we recommend to use the DDE Kit API featured by Genode. Support for multi-touch input devices ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The efforts towards enabling mobile application stacks such as Meego and Android on Genode must be accompanied by a revision of Genode's 'Input' session interface to accommodate multi-touch input devices. First, existing APIs such as multi-touch support in X11, Qt4, and Android should be analysed. Based on these findings, we expect a proposal for changing Genode's input interface. The interface extension should be validated by a example driver implementing the interface as well as an example applications. System services =============== Copy-on-write memory manager ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Genode's managed dataspaces provide a generalized page-table concept, enabling servers to provide on-demand paged memory objects (dataspaces) to clients. This concept is showcased by the ISO9660 driver, which provides on-demand paged ROM dataspaces to its clients. Depending on the access pattern of the client, the ISO9660 server loads the used parts of the ROM file from CDROM. Managed dataspaces principally allow for a wide variety of interesting applications such as the transparent migration of non-local and local memory in a NUMA system, sparse dataspaces, swapping, and copy-on-write dataspaces. The goal of this project is a dataspace manager that implements copy-on- write semantics combined with a merging technique optimizing the memory footprint at runtime. Pages of two managed dataspaces that share the same content should be provided via read-only page sharing. If one client attempts to change the content of a shared page, a new physical copy of the page get created. Vice versa, if the content of different pages converge, the sharing should be re-established. This work is a follow-up of the diploma thesis "Cloning L4Linux" of Sebastian Sumpf http://os.inf.tu-dresden.de/papers_ps/sumpf-diplom.pdf On the course of this project, the managed dataspace concept of Genode will be refined, in particular regarding the creation of read-only dataspaces from read-write dataspaces. HalVM ~~~~~ [http://halvm.org - HalVM] is an operating-system runtime that allows for implementing low-level OS components in Haskell. Currently, HalVM uses Xen as underlying kernel. The goal of this project is running HalVM directly on Genode, which would enable the adoption of this approach by the L4 community. Dbus emulation ~~~~~~~~~~~~~~ Dbus is a popular inter-process communication mechanism on Linux, which enables user applications to respond to global system events and announce state changes to other applications. It is extensively used by modern desktop environments. To enable such applications to integrate well with Genode, a Dbus emulation solution has to be developed. Wayland ~~~~~~~ With the availability of Gallium3D on Genode, the prospect for incorporating further projects of the Linux graphics ecosystem into Genode arises. [http://wayland.freedesktop.org/ - Wayland] is a window server especially designed to be used with Gallium3D. Its design has many similarities with Genode's Nitpicker GUI server, in particular the decision to move window handling policies to the client and thereby minimize the complexity of the GUI server. Whereas Nitpicker was designed for high security, Wayland is targeted to creating GUIs with fluid and tearless animations using hardware-accelerated graphics. We believe that because of the many conceptual parallels with Nitpicker, Wayland would fit very well into the Genode system. However, as a prerequisite for this project, Genode's Gallium3D support must be decomposed first. See the challenges regarding our Gallium3D support for further information. Runtime environments ==================== Terminal emulation for Noux ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Noux is an emulation environment for executing command-line-based GNU applications on Genode. It was introduced with Genode 11.02. With the current state, Noux is able to run several GNU coreutils without modification, but it supports non-interactive applications only. The goal of this work is the creation of a Nitpicker GUI client or framebuffer client implementing a terminal emulator to be connected with the stdio channels of Noux. This would enable us to go forward with porting interactive GNU applications, in particular a shell, to Genode. Android's Dalvik VM natively on Genode ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dalvik is a Java virtual machine that is used for executing applications on Android. By running Dalvik directly on Genode, the Linux kernel could be removed from the trusted computing base of Android, facilitating the use of this mobile OS in high-assurance settings. Vancouver VMM for Genode on the NOVA hypervisor ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Vancouver is the user-level virtual-machine monitor accompanying the NOVA hypervisor. It combines a VT-based CPU virtualization with a rich set of device models to run unmodified guest operating systems at near-native performance. Since NOVA is a supported base platform of Genode, running Vancouver in the dynamic Genode environment has become feasible. By running Vancouver on Genode instead of NOVA's original static userland would open up new use cases where the combination of faithful virtualization with dynamic applications is desired. Runtime for the D programming language ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The D systems programming language was designed to overcome many gripes that exists with C++. In particular, it introduces a sane syntax for meta programming, supports unit tests, and contract-based programming. These features make D a compelling language to explore when implementing OS components. Even though D is a compiled language, it comes with a runtime providing support for exception handling and garbage collection. The goal of the project is to explore the use of D for Genode programs, porting the runtime to Genode, adapting the Genode build system to accommodate D programs, and interfacing D programs with other Genode components written in C++. Platforms ========= Multi-processor support on different base platforms ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Several of Genode's supported base platforms come with multi-processor support, i.e., Linux, NOVA, L4ka::Pistachio, Codezero, and Fiasco.OC. Each of these kernels follows a different approach for utilizing multiple CPUs. For example, Linux and Codezero manage the association of threads with CPUs largely transparent for user-level programs. In contrast, NOVA makes the use of multiple CPUs explicit and constraints the modes of IPC interaction of threads running on different CPUs. Furthermore, kernels differ with regard to thread migration and scheduling. The goal of this project is to identify ways to support the SMP features of the respective kernels at Genode's API level such that SMP can be easily utilized by Genode programs in a largely kernel agnostic way. Microkernelizing Linux ~~~~~~~~~~~~~~~~~~~~~~ Thanks to Genode's generic interfaces for I/O access as provided by core, all Genode device drivers including drivers ported from Linux and gPXE can be executed as user-level components on all supported microkernels. However, so far, we have not enabled the use of these device drivers on Linux as base platform. The goal of this project is the systematic replacement of in-kernel Linux device drivers by Genode processes running in user space, effectively reducing the Linux kernel to a runtime for Genode's core process. But moving drivers to Genode processes is just the beginning. By employing further Genode functionality such as its native GUI, lwIP, and Noux, many protocol stacks can effectively be removed from the Linux kernel. The goal of this project is to evaluate how small the Linux kernel can get when used as a microkernel. Support for the Genode FPGA Graphics SoC platform ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ With Genode 11.02, we introduced the first version of native support for the MicroBlaze softcore CPU. With this foundation laid, we can proceed with bringing GUI-based interactive Genode applications to FPGA-based SoC platforms. As target SoC design, we aspire to use the open-source IP cores provided by the Genode FPGA Graphics Project: http://genode-labs.com/products/fpga-graphics Support for the HelenOS/Spark kernel ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [http://www.helenos.org - HelenOS] is a microkernel-based multi-server OS developed at the university of Prague. It is based on the Spark microkernel, which runs on a wide variety of CPU architectures including Sparc, MIPS, and PowerPC. This broad platform support makes Spark an interesting kernel to look at alone. But a further motivation is the fact that Spark does not follow the classical L4 road, providing a kernel API that comes with an own terminology and different kernel primitives. This makes the mapping of Spark's kernel API to Genode a challenging endeavour and would provide us with feedback regarding the universality of Genode's internal interfaces. Finally, this project has the potential to ignite a further collaboration between the HelenOS and Genode communities. Support for the seL4 kernel ~~~~~~~~~~~~~~~~~~~~~~~~~~~ The seL4 kernel developed by NICTA and OK-Labs is the first formally verified microkernel. It runs on the x86 and ARM architectures and supports the execution of a paravirtualized version of Linux on top. Even though seL4 is proprietary technology, a free binary release and the specification of the kernel API has been published early 2011. Being a capability-based kernel, seL4 is in the line of the current- generation L4 kernels alongside NOVA and Fiasco.OC. Genode already supports the latter two kernel, which hints at the feasibility to support seL4 as well. Currently, the seL4 kernel comes with a rather static user land, which is far from utilizing the full potential of the kernel with regard to dynamic resource management. By adapting Genode to seL4, a rich dynamic application workload would become available to this kernel, which could potentially spawn interest in extending the formal verification efforts at NICTA to the Genode system executing dynamic real-world applications. Support for the Barrelfish kernel ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [http://www.barrelfish.org - Barrelfish] is a so-called multi-kernel OS designed for heterogeneous multi-processor systems. At its heart, it is a microkernel-based multi-server OS. Its kernel provides different mechanisms than L4-based kernels. Instead of managing threads in the kernel, there is a mechanism for implementing preemptive multi-threading at user level. Consequently, inter-process communication does not address threads but protection domains. This makes the Barrelfish kernel a very interesting and challenging target for running Genode. Support for the XNU kernel (Darwin) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ XNU is the kernel used by Darwin and Mac OS X. It is derived from the MACH microkernel and extended with a UNIX-like syscall API. Because the kernel is used for Mac OS X, it could represent an industry- strength base platform for Genode supporting all CPU features as used by Mac OS X. Automated testing on the Codezero kernel ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Genode release 11.02 introduced an automated testing framework for all base platforms except for Codezero. Codezero was omitted because its build and configuration system requires user interaction. The goal of this project is to improve the Codezero configuration and build system to interface easier with Genode and to automate the build-and- integration procedure. This way, Codezero would become a base platform subject to many regular tests as performed with the other platforms. Optimizations ============= Low-latency audio streaming ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Genode comes with an audio streaming interface called 'Audio_out' session. It is based on a shared-memory packet stream accompanied with asynchronous data-flow signals. For real-time audio processing involving chains of Genode components, streams of audio data must be carried at low latency, imposing constraints to buffer sizes and the modes of operation of the audio mixer and audio drivers. The goal of this project is to create a holistic design of the whole chain of audio processing, taking thread-scheduling into account. A particular challenge is the mixed output of real-time (small buffer, low latency) and non-real-time (larger buffer to compensate jitter, higher latency) audio sources. -- Dr.-Ing. Norman Feske Genode Labs http://www.genode-labs.com · http://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

4 7

Thread context switch
by Amadeo Cuadrado 26 Mar '11

26 Mar '11

Hello, Is there any mechanism to switch contexts in Genode threads? What I want to do is, whenever some condition is satisfied, to save the current thread context, create a new context (new stack, update sp and ip) to substitute the thread's old context, and restore the old context when another condition is satisfied. I have looked into the implementation of the Thread class and, even though the thread context is public, the context allocation APIs seem to be private. Is there some other public API that I can use for this purpose? What would be the most reasonable way to tackle this? Thanks. Amadeo

3 4

LDSO Question
by Sam Kerr 23 Mar '11

23 Mar '11

Hi All, I have been trying to work with the LDSO library and have been having some more package. I am running Genode on top of Pistachio. I created a bootable image with the LDSO module, but when I start the disk, I get the following error message from LDSO: [init -> ldso] Starting ldso ... [init -> ldso] realloc - not yet implemented 04804002 pf @ fffffffc, ip=00042ecd --- "KD# user touches kernel area" --- --------------------------------- (eip=f010c342, esp=f01163c7) --- It's clear that realloc is not implemented, but is this provided in some other file? How do I work with the LDSO code? -Sam Kerr

4 14

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users