users January 2017

users@lists.genode.org

22 participants
18 discussions

foc_odroid_x2 with tftp boot via uboot on odroid u3
by Bernhard Blieninger 22 Nov '17

22 Nov '17

Hi guys, we are trying to get genode running on an odroid u3 which should be quite similar to the foc_odroid_x2. I followed the instructions from here: http://odroid.com/dokuwiki/doku.php?id=en:u3_building_u-boot and here: http://forum.odroid.com/viewtopic.php?f=82&t=9128 And i used the newest version of u-boot from hardkernel here: https://github.com/hardkernel/u-boot/tree/odroid-v2015.10 I wanted to use tftp boot so and did not really know how to start at first place, so i picked up the ubuntu image from here: http://odroid.com/dokuwiki/doku.php?id=en:u3_release_linux_ubuntu and copied it via dd to the sd card. Then I just let the sd_fuse script from the first link overwrite the bootcode on the sdcard. And wrote into the boot.txt at the first partition the bootcode which it should execute, in my case something like this: |setenv ethact sms0| |setenv ethaddr 00:10:75:2A:AE:E0| |setenv gatewayip 192.168.4.1| |setenv netmask 255.255.255.0| |setenv serverip 192.168.4.2| |setenv usbethaddr 00:10:75:2A:AE:E0| |setenv ipaddr 192.168.4.43| || |usb start| |tftp 0x70000000 odroid/uImage| |bootm| | |Where uImage is the uImage created from the foc_odroid build. Then I used ||| | ||mkimage -A arm -C none -T script -n 'Custom Boot Script' -d boot.txt boot.scr|| |||| || ||to build the boot.scr and booted the odroid u3.|| || Problem now is that is says something like: || *ERROR: booting os 'Unknown OS' (3) is not supported* Where 3 means something like Checksum OK as the uboot manual states. Now I took the zImage from the ubuntu on the sd card and converted it to a uImage with the mkimage program. Put both on the tftp server and changed the boot.txt accordingly. If i select zImage the ubuntu kernel boots up and gets a kernel panic, if i select uImage(now from Ubuntu) i get the same unknown OS error. Does someone have similar issues and can tell me how to fix it? Is it even possible to use the foc_odroid_x2 on u3, they share the same hardware so it should be? Thanks in advance. Best regards, Bernhard.| | -- Bernhard Blieninger, B.Sc. Technische Universität München Fakultät für Informatik Lehrstuhl für Betriebssysteme Boltzmannstraße 3 85748 Garching Tel. +49 89 289 18795 Fax +49 89 289 18557 bliening@...389... www.os.in.tum.de

6 14

Restoring child with checkpointed state
by Denis Huber 15 Nov '17

15 Nov '17

Dear Genode community, thanks to you [1], I could implement my Checkpoint/Restore mechanism on Genode/Fiasco.OC. I also added the incremental checkpoint optimization, to stored only changed memory regions compared to the last checkpoint (although this is not working reliably due to a Fiasco.OC bug, which Stefan Kalkowski found for me [2]). I also managed to checkpoint the capability map and restore it with new badges and insert missing capabilities into the capability space of Fiasco.OC. [1] https://sourceforge.net/p/genode/mailman/message/35322604/ [2] https://sourceforge.net/p/genode/mailman/message/35377269/ My problem is, although I restore all RPC objects, especially the instruction and stack pointer of the main thread, and the capability map and space, the target component just starts its execution from the beginning of its Component::construct function. My approach: For the restore phase, I use Genode's native bootstrap mechanism (i.e. I create a Genode::Child object) until it requests a LOG session from my Checkpoint/Restore component. I force a LOG session request in ::Constructor_component::construct() just before "Genode::call_component_construct(env);" in https://github.com/genodelabs/genode/blob/16.08/repos/base/src/lib/base/ent… Until the session request several RAM dataspaces are created, among other RPC objects, and attached to the address space. In my restore mechanism I identify the RPC objects, which were created by the bootstrap/startup mechanism, and only restore their state. After that point, I recreate and restore the state of all other RPC objects which are known by the child component. At last, I restore the capability map and space. During that process the mandatory CPU threads are identified (three of them: "ep", "signal_handler", and "childs_rom_name") and restored to their checkpointed state, especially the ip and sp registers. I did that through the use of Cpu_thread::state(Thread_state), but without luck. Also, although I know that the CPU threads were already started, I tried to call Cpu_thread::start(ip, sp), but without success. After the restoration which happens entirely during the LOG session request of the child, my component returns with a valid session object to the child. Now the child should continue the work from the point where it was checkpointed, but it continues its execution right after the LOG session request, ignoring the setting of the instruction pointer. The source code of the restore CPU thread state is found in [3]. I used run script [4] for the tests. [3] https://github.com/702nADOS/genode-CheckpointRestore-SharedMemory/blob/660a… [4] https://github.com/702nADOS/genode-CheckpointRestore-SharedMemory/blob/660a… Curiously, the child runs just as nothing happened, although its stack area was also manipulated. Perhaps my approach by reusing the bootstrap/startup mechanism is not destined to work, or maybe I have missed some important points in this mechanism. If so, please point me to the problem. I would also consider other restoration approaches, for example, by recreating all RPC objects manually and insert them into the capability map/space. What are your thoughts on my approach? Can it work? Does something else work better? Kind regards, Denis

4 19

[Genode] Suggestion about mailing list subject
by Martin Iturbide 27 Mar '17

27 Mar '17

Hello to all. I was wondering if it can be useful to configure the mailing list to include on the subject (before the text) something like [Genode] or [Genode-Main] . I know that it is easy to set a rule and folder for the mailing list messages on the mail client, but in some other cases I like to identify visually and fast the messages that are from this mailing list in a group of mails. This is just a thought, I don't know how hard or easy will be to configure this on the sourceforge mailing lists. Regards -- Martín Itúrbide http://www.os2world.com martin@...476... martiniturbide@...9... Quito - Ecuador

5 5

Reading thread registers
by Denis Huber 07 Mar '17

07 Mar '17

Hello Genode community, in my checkpoint component I intercepted the Cpu session of a child, through which I get all Thread_capabilities created for and by the child. To store the state of a component I need to store the registers of the threads used by the child. I tried reading the registers through the "Thread_state Cpu_thread::state()" method, but it did not contain any information about (just zeros). I'm using Genode 16.05, kernel Fiasco.OC (pbax9 build). By inspecting the kernel API of foc, I found out that the function l4_thread_ex_regs_ret can read the sp and ip register. By changing the state method in platform_thread.cc (in base-foc) I could get the registers: Thread_state Platform_thread::state() { Thread_state s; if (_pager_obj) s = _pager_obj->state; _pager_obj->state.ip = ~0UL; _pager_obj->state.sp = ~0UL; l4_umword_t flags = 0; l4_thread_ex_regs_ret(_thread.local.dst(), &_pager_obj->state.ip, &_pager_obj->state.sp, &flags); s.sp = _pager_obj->state.sp; s.ip = _pager_obj->state.ip; s.kcap = _gate.remote; s.id = _gate.local.local_name(); s.utcb = _utcb; return s; } But other registers like r0 - r12 are missing. Is there a simple way in Genode to get them? Can I utilize the utcb memory location to find the missing registers? Kind regards Denis

2 6

Re: USB storage detachment / reattachment
by Boris Mulder 13 Feb '17

13 Feb '17

Dear Genode developers, Following Martijn's mail at the end of last year, which stated: >> As a way to support detachment / reattachment of USB storage I’m >> thinking about placing the rump_fs and part_blk components in a child >> subtree of the CLI component that is spawned on demand and cleaned-up >> after use. But this seems a bit like overkill. > That's exactly the right solution. I don't think that it's overkill > either. Spawning up rump_fs and part_blk dynamically is certainly quick > enough. Memory-wise, it does not take more resources that a static > scenario either. By letting your CLI component implement the protocol > outlined above, you have full control over chain of events. Also the > aborting rump_fs is nothing fatal anymore but can be gracefully handled > by the CLI component. As another benefit, the solution does not need us > to supplement the notion of hot-plugging to the file-system and block > session interfaces, which would otherwise inflate the complexity of > these interfaces (and thereby all the clients that rely on them). Martijn and I have been thinking of a way to implement this, and came to the conclusion that instead of spawning the stack as children of the CLI component, it might be better to use a new management component in-between. As Josef said earlier: > A custom runtime/management component could monitor the > usb_drv device report and spawn the whole stack if it detects a USB > storage device. The usb_drv's device report does not contain the device > class so far though but adding that to the report is easy. This is exactly what we're trying to do now. We want to create a custom component called "media" that monitors usb devices by reading the report. It provides a service to other components through which they can request a filesystem session in order to read-write from/to the usb-stick. For this, it spawns the part_blk and rump_fs components as children if the usb is plugged in, and kills them once the usb is plugged out. It roughly looks like this: rump_fs part_blk | | CLI media USB_drv | | | init But this raises a few questions. First, the filesystem interface needs to be presented to the client somehow. To avoid adding another layer of indirection into media, essentially duplicating rump_fs's entire API, we would like the client (in this case CLI) to be directly connected to rump_fs. The client can then ask media if the USB is connected before calling a function from rump_fs. However, this means that rump_fs provides a service, announces it to its parent (media), and media has to decide what to do with that announce. It can implement rump_fs as a slave, but that way the entire API needs to be copied into media so media can present it as its own service to the client. So we would like media to announce the filesystem service to its parent (in this case init), so any client can use this service. In the same way, any session request will be passed from CLI to its parent (init), init has to pass it to media, and media passes it to rump_fs. However, the current implementation and specification of genode does not allow services of any server to exist in any level above the server's parent. Services can only be provided to direct parents, and to other components in the parent's subtree. Therefore, copying the API from the child to the parent seems unavoidable. Another problem that pops up is that media has to spawn all these subcomponents as children. In order to route block session requests from rump-fs to part-blk, media needs to implement some routing policy and effectively serves the same role for these two components as init serves for the system. So we could: 1. Copy all necessary code for routing from init to media (which is almost all code if we want to be generic). 2. Let media spawn another init child component (let's call it sub-init for now) which in turn spawns rump-fs and part-blk and does the routing. To us, the second option seems much more clean as it involves no code-copying. However, services announced by rump-fs can not be used by other components that are not children of the new init, and are kind of useless. Their announcements can not be passed on to the parents, leaving us with the same problem as we had with rump_fs but with the additional problem that even if there would be a custom way to forward service announces and requests to the parent/child respectively, sub-init has no such policy, and this functionality has to be included in sub-init's code as well, adding a lot of complexity. Eventually both cases bottle down to the same problem: service announcements to a parent cannot automatically be forwarded to that parent's parent, and likewise, service requests need to be able to be delegated to children of children without a lot of hassle. The only option if I'm correct is implementing this functionality manually, but this does not work if the parent is an existing component that does not support it. Is there a reason this is never done? For init it is clear that it would never pass an announce to its parent (usually core) or receive session requests from it. But how about the general case? And how should we solve cases such as the above scenario? kind regards, Boris Mulder Cyber Security Labs B.V. | Gooimeer 6-31 | 1411 DD Naarden | The Netherlands +31 35 631 3253 (office)

4 10

Why DDE BSD for audio?
by Alexander Senier 01 Feb '17

01 Feb '17

Hi all, when looking into Genodes driver support, I was wondering about DDE BSD. The audio_* ports seems to be its only use case. Is there any (technical) justification for not porting audio drivers from Linux using DDE Linux? With USB, WiFi and GMA there were much more complex driver ported using DDE Linux after all... Thanks! Cheers, Alex

3 3

performance benchmark
by Parfait Tokponnon 30 Jan '17

30 Jan '17

Hello all, Is there any benchmark (performance) tool ready to run in Genode? I am trying to introduce some redundant execution scheme into the Nova kernel and I would like to have a hint of the performance impact (on Genode components). Since it is an unfinished work, the demo is the only scenario I can run now. I have read about the trace session in 13.08 release which may help but I failed to build the trace example scenario (to get some insight of the feature) *Here are the outputs* In the master branch: make run/trace ... cp: cannot stat ‘bin/rpc_name’: No such file or directory while executing "exec cp bin/$binary [run_dir]/genode" (procedure "copy_and_strip_genode_binaries_to_run_dir" line 4) invoked from within ... In the 13.08 release make run/trace Makefile:91: /mk/global.mk: No such file or directory make: *** No rule to make target `/mk/global.mk'. Stop. I also read about the* TCP/IP Automated benchmarking* in 13.05 release. In the master branch: make run/network_test_nic_raw Error: No run script for network_test_nic_raw In the 13.05 release Makefile:91: /mk/global.mk: No such file or directory make: *** No rule to make target `/mk/global.mk'. Stop. Any suggestion is welcom. -- Parfait T.

2 1

Genode on Odroid-XU4
by Yevgeny Lavrov 24 Jan '17

24 Jan '17

Greetings I would like to try Genode on Odroid-XU4. I aware that there's no support available for this ARM device yet. However, I want to give it a try, but I don't know where to start. Can you please point me in the right direction so I can find the information that I'll need to get started this task? Thanks

2 8

Recipes not working
by Chris Rothrock 20 Jan '17

20 Jan '17

There are two recipes that I was able to successfully compile and run in Genode 16.08 that are no longer working with Genode 16.11 and was wondering if I could get assistance to make them work in this version. The default make run/demo works fine for me but if I try using the make run/demo with the Nova kernel I get an error "Error: target 'drivers/usb' does not exist". Also, I am trying to run the recipe for virtualbox (using Nova hypervisor) and this worked with Genode v16.08 but now I can't make this recipe. The port libiconv is required but I get an error trying to prepare_port on this one (Error: Hash sum check for libiconv failed). I also tried to update the hash (./tool/port/update_hash libiconv) but this didn't work. Any assistance on these two issues would be appreciated. Thanks, Chris -- Thank You, Chris Rothrock Senior System Administrator (315) 308-1637

2 1

Native Android Application Execution in Genode (Dalvik VM / ART)
by Alexy Gallardo Segura 17 Jan '17

17 Jan '17

Hello, I am writing to consult everyone on a topic in the genode section Challenges, in particular on the "Dalvik VM of Android natively in Genode". Norman Feske told me that currently Android also uses ART (Android runtime). Especially I have no preference, I'm only interested in running Android applications in GenodeOS. I am interested in working on this topic, but I have some questions to ask. Is anyone working on this topic? I reviewed the current issues but I did not find Anything related. Which would be better to incorporate to Genode Dalvik or ART, or any other variant? Finally, if you have any suggestions on where to start the review first? regards Alexy Gallardo Segura

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users January 2017