users

users@lists.genode.org

2357 discussions

make -C build.nova-x86_64 run/demo results in -no-kvm option
by J T 18 Jan '13

18 Jan '13

While trying out different parts of the genode build tree I tried doing a make -C build.nova-x86_64 run/demo which resulted in something like this: ... genode build completed using NOVA kernel at /home/xx/src/genode/build.nova-x86_64/kernel/hypervisor creating ISO image... spawn qemu-system-x86_64 -no-kvm -cpu core2duo -m 256 -serial mon:stdio -cdrom var/run/demo.iso qemu-system-x86_64: -no-kvm: invalid option ... I'm currently running centos 6 as a remote server and doing the builds there and initially I didn't have qemu-system available on it. It took me a while to locate an rpm (in rpmforge-extras) that had qemu-system_x86_64 - however it does not recognise the -no-kvm command line option. In fact I'm having trouble locating any documentation for QEMU that mentions that command line option so I'm wondering whether the option is bogus or I need to be looking elsewhere to get a qemu install that has the command with that argument.

2 1

RFR: Ubuntu Server Dev Environment Possible/Preferred for Genode ?
by J T 18 Jan '13

18 Jan '13

Hi, Currently I've been trying to use a Centos VM I have running remotely on a Xen host as a Genode build environment. Is it really better for me to switch to using Ubuntu ? If so, since I really dislike using Linux in its desktop GUI flavours and would prefer not to run it locally as a VM either .. I'm wondering if anyone has had any luck running a server version of Ubuntu that can be accessed remotely using a local X11 server (on my Mac for example). Thanks, Kt.

1 0

make run/demo on a linux base on a 64 bit centos distro - SYS_waitpid not declared
by J T 18 Jan '13

18 Jan '13

$ make run/demo ... Program core/core COMPILE cpu_session_extension.o In file included from /home/xx/source/genode/base-linux/src/core/cpu_session_extension.cc:11:0: /home/xx/source/genode/base-linux/src/core/include/core_linux_syscalls.h: In function ‘int lx_pollpid()’: /home/xx/source/genode/base-linux/src/core/include/core_linux_syscalls.h:115:20: error: ‘SYS_waitpid’ was not declared in this scope make[2]: *** [cpu_session_extension.o] Error 1 make[1]: *** [core.prg] Error 2 make: *** [gen_deps_and_build_targets] Error 2 Prior to this I had to run tool/toolchain since the other method for using genode's custom precompiled toolchain didnt work for me.

2 1

Re: HelenOS kernel (Spartan) as a Genode platform
by Tobias Börtitz 16 Jan '13

16 Jan '13

Hi Paul, thank you for the comments. I will have a look at the issue trackers during the next days after talking to the corresponding people. Even updating the documentation an helenos's wiki may be a good idea at some point. John, you may be misslead by the term "platform". The Genode framework is a userland implementation of a capabilty based OS, which is capable of running on top of different microkernels. The term "platform" in this case refers to the used microkernel the framework is running on. In my case I strip HelenOS of its userland and only use their microkernel (which is called SPARTAN). So I port the Genode famwork to be able to run on top of the new platform HelenOS/SPARTAN. I do hope this clarifies things for you. If not, please let me know. Regards, Tobias

1 0

HelenOS kernel (Spartan) as a Genode platform
by Paul Dufresne 16 Jan '13

16 Jan '13

I believed that an HelenOS GoogleSummerOfCode (GSOC) project for 2012 was: https://www.google-melange.com/gsoc/project/google/gsoc2012/kurbel/20001 http://trac.helenos.org/ticket/419 Basically no GSOC 2012 projects was accepted for Genode, but it was for the HelenOS. So Tobias Börtitz did work on that during summer of 2012. Now, after reading his last report ( http://comments.gmane.org/gmane.os.helenos.devel/740 ) I understand his work was incomplete. (Seen a bit other comments by searching "HelenOS as a Genode platform" on Google ) I suppose he did not continue the project after the GSOC 2012. Does his branch (work) is publicly available and if so where? I took a look to: https://github.com/genodelabs/genode/network but I don't seems to find it there. I don't really expect to continue his work, but before discovering Genode, I was reading quite a bit about HelenOS and I'd like to be able to peek at this work.

4 5

Genode 12.11 on Ubuntu 64 bits: Could not open file "ld.lib.so" seems to cause black window
by Paul Dufresne 16 Jan '13

16 Jan '13

First, I did not search yet for issues showing this. It is just a ... "hey, that's seems wrong, anyone knows about this?". After my "make run/demo" on Linux Ubuntu 64 bits, I got a big black window, that was empty so I closed it. The log after compilation shows: Program app/launchpad/launchpad COMPILE launcher.o COMPILE launchpad_window.o COMPILE main.o LINK launchpad make[1]: Leaving directory `/home/paul/Bureau/Genode/genode-12.11/build.lx' genode build completed spawn ./core int main(): --- create local services --- int main(): --- start init --- int main(): transferred 79 MB to init int main(): --- init created, waiting for exit condition --- [init] Could not open file "ld.lib.so" [init -> launchpad] Could not open file "ld.lib.so" [init -> launchpad] Could not open file "config" [init -> launchpad] Could not obtain config file ^Cint main(): --- destroying init --- virtual void Genode::Core_parent::close(Genode::Session_capability): implement me, please destroy_server_socket_pair called for IPC server which should never happen context area detach from 0x2fe000 - not implemented int main(): --- core main says good bye --- virtual void Genode::Core_parent::close(Genode::Session_capability): implement me, please virtual void Genode::Core_parent::close(Genode::Session_capability): implement me, please expect: spawn id exp6 not open while executing "expect { -re $wait_for_re { } timeout { puts stderr "Error: Test execution timed out"; exit -2 } }" (procedure "run_genode_until" line 8) invoked from within "run_genode_until forever" (file "/home/paul/Bureau/Genode/genode-12.11/os/run/demo.run" line 129) invoked from within "source $include_name" ("foreach" body line 3) invoked from within "foreach include_name [get_cmd_arg --include ""] { puts "using run script $include_name" source $include_name }" (file "/home/paul/Bureau/Genode/genode-12.11/tool/run" line 508) make: *** [run/demo] Error 1 paul@...162...:~/Bureau/Genode/genode-12.11/build.lx$ paul@...162...:~/Bureau/Genode/genode-12.11/build.lx$ locate ld.lib paul@...162...:~/Bureau/Genode/genode-12.11/build.lx$

3 5

Re: OM: A real-world, tangible, desktop implementation of Genode
by unknown＠example.com 15 Jan '13

15 Jan '13

I'm looking to implement an 'auii' on the genode platform. I'll be putting out the 'auii' spec along with (within really) an xml based model/prototype, hopefully this first quarter 2013 (this year) at iintera.org. It addresses rather completely the 'user interaction thng', including various use levels. If anyone's interested in participating let me know. I might accelerate the spec/proto/model release accordingly. > ----- Original Message ----- > From: John Bessa > Sent: 01/14/13 03:07 PM > To: Genode OS Framework Mailing List > Subject: Re: OM: A real-world, tangible, desktop implementation of Genode > > Hello Norman, > > My break-down of your writing is that the biggest challenge for the > user-model is to structure a > > 1) user-relationship via the > 2) desktop to a > 3) chain of interacting components with regard to data > 4) persistence and > 5) access > > I describe this "chain of interaction" as "complexity," but complex data is > usually described as "dictionaries" --showing low comprehension of it. > Shell, in particular "comprehended" complexity so effectively with its > file-objects that I think we fell into a homeostasis while we should have > been extending it to create its own objects. Thus, we would have > currently-valid interaction with the OS. An OO shell extension might > include the "arrow" operator to define, or link, interaction between > desktop objects. > > I am attempting to create a summary of L4/Genode material including Drops > and its OS kit components, the driver synthesis concept, and your > alternative microkernels (such as Xen) to create SVG charting material. I > have seen Lua used in L4 boot, so that should go in the summary as well. > > Preserving the GNU/Unix gcc structure makes sense through "eating your own > dog food" it provides an easy entry point for younger free/software > programmers. Because these young programmers probably > have limited resources, the computer running Genode (such as a flashed > Android device) might be their only one, so allowing them to use this > device for development reinforces "eating your own," well, vegetables. As > an early administrator, I recall that Shell's and GNU's simplicity as its > asset allowing for easy inquiry into efficiency, practicality (usability), > and security. It was easy to make a good living when Shell was king from > 1990-2000. > > Regards, John >

1 0

Road map 2013
by Norman Feske 15 Jan '13

15 Jan '13

Hello and happy New Year everybody, the advent of 2013 is a good opportunity to make up our minds about Genode's road map for this year. But before I will start with explaining my preferences, I'd like to outline my thoughts about the last year's road map. In 2012, we labeled our activities as "Eating our own dog food". Our goal was to bring Genode into a shape that makes it usable as working environment for conducting Genode development. On our road-map website (http://genode.org/about/road-map) we listed a long list of desirable goals. Looking through the list makes me proud of our achievements. Just to name a few highlights, there is the ability to build Genode on Genode, SSH, lighttpd, the new file-system infrastructure, the new DDE linux and DDE OSS. But even though the list is impressive and the pieces nicely come together, we are not quite there yet to realistically make the switch to Genode as development environment. Two major missing points are a solid UI concept that leverages Genode's unique architecture and a "real" file system. You will find those points in my suggestions for this year's road map below. Even though we missed our ambitious main goal for 2012, there is no cause for despair. There are indeed many achievements in addition to our road-map items to be proud of. The most visible addition is the thorough support for ARM-based platforms reaching from versatile express, over freescale i.MX, to OMAP4. Another amazing development is the added base-hw platform that enables Genode to be executed without a 3rd-party kernel. Furthermore, the largely revised support for the Linux base platform makes Genode fit to be used as component framework on Linux, which is a quite unexpected turn of events. So what is coming next? >From my point of view, I see four major construction sites that we should address this year: framework infrastructure, self-hosting, tooling and optimizations, and hardware support. Framework infrastructure ======================== The primary group of people Genode tries to cater well are developers and integrators of systems. Genode is meant as a tool box to empower those people to build real-world component-based system solutions. From this audience, we receive requests for improvements in the following areas: * Multi-processor support: On some base platforms, SMP support is available but the framework still misses a holistic concept to manage and configure the use of multiple CPUs. * Storage: Block-device access is a general concern. Even though we laid the foundations for Genode's storage infrastructure, several pieces are still missing, in particular a "real" (non-FAT) file system, block/file/directory caching, and I/O scheduling. Without those pieces, there is no way to achieve the application performance that we desire. * Networking: The current TCP/IP performance using lwIP has room for improvement. So I'd like to find a solution to bring TCP/IP performance on Genode on par with Linux. Maybe this means to find the bottlenecks in our lwIP port, or even going for another TCP/IP stack? * Qt5: Now that Qt5 is officially released, we should consider to switch from Qt4 to Qt5. * Low-latency audio: The current audio_out-session interface was our first shot into the direction of audio processing. To enable use cases where streaming audio and sporadic sounds must be accommodated at the same time, we need to revise our approach. There is already work in progress on this topic. * Cryptography * Random numbers * Block-device encryption Self-hosting ============ The second major topic is redeeming the promise stated for the past year - using Genode as a real-world OS. The following pieces are missing. Compared to the list on the old road map, this one is rather small. So I am very positive! * UI concept for pleasant working environment * Tiled window manager * Terminal improvements (e.g., scroll buffer) * Noux improvements (e.g., signals) * Tools * Git (work is already in progress) * Mail user agent * Instant-messaging software * Support for 'make prepare' (e.g., SVN, wget, mawk) * Support for run tool: expect, Qemu Tooling and optimization ======================== Now that Genode's work loads get ever more complex, we feel the drastically increased need to understand its inner behavior and detect possible black holes where the performance goes. When the system scenarios were rather small, printf-debugging was quite feasible. But now, with multiple instances of Noux running concurrently with several drivers, we need better tools for understanding, debugging, and tracing the system. In a component-based system like Genode, the creation of such tooling support of especially challenging because we need to walk on new grounds. In my opinion, good tooling is key to direct our efforts spent with performance optimizations. The goal should be to ultimately debunk the slow performance of microkernel-based systems as a myth. Hardware support ================ The attractiveness of our framework corresponds to the degree of hardware support. Since we want to make Genode more attractive, we need to continue our efforts with creating custom drivers, porting drivers, and enabling platforms. The following points are the most interesting ones from my point of view: * Intel architecture * IOMMU support * Improved virtualization support (Vancouver on NOVA) * Intel wireless * ARM architecture * Extending support for SoC platforms * TrustZone Of course, Genode's road map for 2013 is not meant to be dictated by me. Please chime in, discuss the topics above and propose additional items. I hope that we will reach consent for the goals of this year by mid January. Then I will update the official road map on the website. Cheers Norman -- 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 6

small questions regarding JDB ipc call trace
by jaeyong yoo 15 Jan '13

15 Jan '13

Hello! Here goes an example line of jdb IPC call trace output: ipc: 04df repl->[C:INV] DID=ffffffff L=0 [00000000] (00000000,00000000) TO=0/0 ipc: 045f call ipc->[C:205003] DID=40d L=0 [0000000b] (00000fb0,00000003) TO=INF/INF I have looked through the fiasco source code that generates this output and figured out that L=0 is the label of message [00000000] is the tag of the message (00000fb0,00000003) is the first two words of the message My questions are: 1) I observe most labels are zero in the output. I think genode defines label 0 as invalid capability, then this value looks like not correct? 2) What is the tag of the message? 3) By any chance, the second word of the message is the opcode? (Since I would like to know the opcode in IPC, that is my wish) Best regards Jaeyong

2 1

Manually set MSI in Genode under base-foc failed
by Jilong Kuang 15 Jan '13

15 Jan '13

Hi all, I was trying to manually (hack) set MSI in Genode under base-foc but failed. I'd like to describe my approach here and see if anyone can spot any mistakes or missing parts? First, I added the Msi_flag (0x80000000) to the IRQ number in the l4_icu_bind() and setup_irq_mode() functions in genode/base-foc/src/core/irq_session_component.cc. So the kernel will know this is a MSI-type IRQ. In addition, I added a l4_icu_msi_info() function to return msg info for driver msi configuration (In my case it returns the first available vector in IDT, which is 0x21) Second, in my driver code, I do the following: Genode::Irq_connection _irq(80); //random MSI number Dev->config_msi(0x21); //configure the dev (e1000 card in my case) to use MSI mode while (1) { _irq.wait_for_irq(); Dev->interrupt_handler(); } However, I never saw any MSI-type interrupt triggered by Fiasco kernel. After instrumenting kernel, I did see kernel created an MSI-type irq object and the corresponding Irq_sender object and attached itself to the right receiving thread (Interrupt_handler::handler_cap()). But I don't know why Irq_sender::kinvoke was not triggered in the kernel. Thank you very much for your help! Best regards, Jilong

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users