users

users@lists.genode.org

2285 discussions

Checkpoint/restore of capabilities
by Denis Huber 24 Oct '16

24 Oct '16

Dear Genode community, as some of you already know, I want to create a checkpoint/restore mechanism for components on Genode 16.05 and Fiasco.OC. I want to create a component which monitors the PD and CPU sessions of its children (= targets for checkpoint/restore) to have access to their memory and thread states. For a complete checkpoint and restore of a child I also need to store the capabilities used by a child. How can I acquire and also restore all these capabilities? After a restore of a component the capability space shall be the "same" as before the checkpoint: 1) The capabilities after the restore shall point to corresponding object identities. 2) Also the capabilities after the restore shall be on the same slot (have the same address) in the capability space as before the checkpoint. The capability space resides in the kernel and Genode does not offer an API to manipulate it. Is there a way to accomplish my goal with Genode's API anyway? Kind regards, Denis

3 14

Linking genode processes at different address space
by Parfait Tokponnon 24 Oct '16

24 Oct '16

Dear Genode community, I would like to know if there is a way to link Genode process (or components) at different address spaces especially when building Heeselicht scenario. When playing with the kernel (Nova), I encounter some weird values from a userland process, but which component exactly it is, i don't really know since almost all of them are linked to the same virtual adress. According to me, one way to deal with it would be to name each PD (protection domain) in the kernel according to the Genode component they belong to, but I think this would be a bit tedious. So what I am projecting to do is to guess the component name from the adress space they are executing in (if they have different address space, right?). Any other idea is welcome. Thanks -- Parfait T.

3 4

Number of components per init
by Roman Iten 18 Oct '16

18 Oct '16

Hi, I wrote a simple run script 'manytimer', based on 'timer': https://github.com/rite/genode/tree/manytimer When the number of components exceeds 19, I get a "Quota exceeded!" warning. It seems that it doesn't matter if I use timer or other components. It also doesn't matter how much RAM quota I configure per timer. - Is this behaviour intended? - Whose quota exceeds (init, core, ...)? - Can I resolve the warning by increasing its quota? - In a scenario with 19 or more components (within one init), is it still possible to "assign all remaining resources to the last child by simply specifying an overly large quantum" as described in "Genode 16.05 Foundations" (see Chapter 6.2.2 "Resource quota saturation"). Or would there be no more slack memory available for init and core respectively? Thanks, Roman

3 9

Microkernels / Component-based OSes devroom - Call for Participation
by Josef Söntgen 17 Oct '16

17 Oct '16

FOSDEM 2017 - Microkernels / Component-based OSes devroom CALL FOR PARTICIPATION The developers of several free and open-source microkernel-based operating systems will meet at FOSDEM 2017 [1] in Brussels, Belgium and will share a developer room on Saturday of February 04, 2017 [2]. The devroom is currently looking for content in the form of talks and activities related to the area of microkernel-based operating systems. Possible topics include, but are not limited to: * Introduction of a specific OS or framework * Design of subsystems and the general architecture of an OS * Enabling support for hardware (architectures, device drivers) * Used languages and tools * Maintainance and testing * Security and robustness * Trends and challenges * Use cases, experiences, lessons learned and demos Please use the Pentabarf [3] system to submit your proposals and file it under the track “Microkernels and Component-based OS”. You do not need to create a new account if you already have one. When in doubt, please use the devroom mailing list [4]. If you do not want to give a talk yourself, you may still send suggestions for what else you would like to see, or do in the devroom. Please send your suggestions to the mailing list. The deadline for your proposal is on December the 4th. Make sure to include the following in your proposal: * Title of your talk (will be printed in the FOSDEM booklet) * Your full name (will be printed in the FOSDEM booklet) * A short abstract (one or two paragraphs) * Duration of your talk (please, at least 25 and no longer than 45 min) The official devroom schedule (along with the accepted talks) will be announced on December the 11th on the devroom's mailing list and the speakers will be notified via e-mail. The schedule will also be published on the FOSDEM website. About FOSDEM FOSDEM is a two-day event organised by volunteers to promote the widespread use of free and open source software. Taking place in the beautiful city of Brussels (Belgium), FOSDEM is widely recognised as the best such conference in Europe. FOSDEM covers a wide spectrum of free and open source software projects, and offers a platform for people to collaborate. To this end, FOSDEM has set up developer rooms (devrooms) with network/internet connectivity and projectors 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 discussions. Besides developer rooms, FOSDEM also offers main tracks, lightning talks, certification exams and project stands. Every year, FOSDEM hosts more than 5000 developers at the ULB Solbosch campus. Participation and attendance is totally free, though the organisers gratefully accept donations and sponsorship. No registration necessary. About the devroom Since the first Microkernel devroom in 2012 this devroom has been part of each following FOSDEM. By now it has become a somewhat institutionalized tradition for the micro kernel community to meet there; to this date over a dozen projects have participated in one way or another. Each of the projects face similar challenges but come up with partially differend solutions. Therefore, the goal of the Microkernel devroom is to bring the various projects together, let them exchange ideas, cross-pollinate and socialize. Social events It also has become a habit that the microkernel projects dine together somewhere in downtown Brussels after the devroom closes. The year 2017 will not be any different, so there is going to be a microkernel family dinner on Saturday night. The exact location and time will be specified later. Consult the FOSDEM web and other projects for additional social events such as the famous FOSDEM-organized Friday Beer Event and the FOSDEM-arranged free sightseeing tours for spouses. Important dates recap * 04.12.2016: Deadline for submissions * 11.12.2016: Schedule published and speakers notified of acceptance * 04.02.2017: The devroom takes places Links [1] http://fosdem.org/ [2] https://fosdem.org/2017/practical/transportation/ [3] https://fosdem.org/submit [4] https://lists.fosdem.org/listinfo/microkernel-devroom See you all at FOSDEM!

1 0

Heeselicht scenario
by Stefan Kalkowski 11 Oct '16

11 Oct '16

Hello Genode folks, hereby, I'd like to announce my recent activity to turn the Turmvilla scenario published by Norman after last year's Hack'n'Hike into an USB live setup. Instead of the original variation, this scenario enables you to boot Genode natively from an USB stick on top of your favorite Intel x86 hardware. In parallel, you can execute your previous installed OS on disk inside a VirtualBox VM without further modifications. This setup offered me the opportunity to switch to Genode without the need to alter my current Linux working environment. Thinking that I'm not the only one that might be interested in such a setup, I've spent some time during our recent Hack'n'Hike in a nice old house in "Heeselicht" to facilitate the steps to reproduce this setup. If you are undaunted, and like to give it a try, you can have a look at the corresponding issue: https://github.com/genodelabs/genode/issues/2018 There are detailed instructions in the issue. For further assistance, leave a comment at the issue tracker or reply to this email. Regards Stefan -- Stefan Kalkowski Genode Labs http://www.genode-labs.com/ · http://genode.org/

1 1

Enabling secure boot on the USB armory
by 오지수 05 Oct '16

05 Oct '16

Hello I'm currently trying to boot Genode 15.02 on the USB Armory. [1] provides tutorial of secure boot on USB Armory. But, [1] only handle linux zImage. Is this possible to generate signed U-boot for Genode image? [1] https://github.com/inversepath/usbarmory/wiki/Secure-boot

3 3

Intel wifi driver
by Martijn Verschoor 03 Oct '16

03 Oct '16

Hi everyone, I’m trying to setup the wifi driver in Turmvilla like scenario’s but with little success. The driver spits out a fair amount of warnings and errors which obfuscates my view of what could be the main issue; thus I would like to reach out for help. A log of the turmvilla scenario (https://github.com/nfeske/genode/tree/turmvilla-16.05) running on a Lenovo x201 is attached. I get very similar results on x250’s. Can anyone point out to me what might be the problem? Met vriendelijke groet / kind regards, Martijn Verschoor Cyber Security Labs B.V. | Gooimeer 6-31 | 1411 DD Naarden | The Netherlands +31 35 631 3253 (office) | +31 616 014 087 (mobile)

3 4

Netaidkit as an alternative wifi client
by Emery Hemingway 28 Sep '16

28 Sep '16

Hello list, I come not with a problem but a solution, My laptop shipped with a wireless card not supported by the Genode wifi driver, and replacing the card model raises an error from the BIOS (which raises some suspicions of firmware interaction). This is usually not a problem as I have plenty of ethernet endpoints in my house, but it is inconvenient when I want to move around. I discovered a few of the people I know in town have actually removed the wireless cards from their Linux laptops and instead use USB powered routers to connect to wifi. They recommended the NetAidKit to me, which I have been using without any problems. I connect to this small router through ethernet and the router acts as a wireless client. It is a solution with some physical bulk, but it pushes the complexity of wifi to the other side of my ethernet hardware. It costs 50 euro, a lot compared to simple client hardware, but it is a project I don't mind supporting. https://netaidkit.net/ Cheers, Emery

1 0

Page faults in managed dataspaces
by Denis Huber 27 Sep '16

27 Sep '16

Dear Genode Community, I want to implement a mechanism to monitor the access of a component to its address space. My idea is to implement a monitoring component which provides managed dataspaces to a target component. Each managed dataspace has several designated dataspaces (allocated, but not attached, and with a fixed location in the managed dataspace). I want to use several dataspaces to control the access range of the target component. Whenever the target component accesses an address in the managed dataspace, a page fault is triggered, because the managed dataspace has no dataspaces attached to it. The page fault is caught by a custom page fault handler. The page fault handler attaches the designated dataspace into the faulting managed dataspace and resolves the page fault. To test my concept I implemented a prototypical system with a monitoring component (called "ckpt") [1] and a target component [2]. [1] https://github.com/702nADOS/genode-CheckpointRestore-SharedMemory/blob/b502… [2] https://github.com/702nADOS/genode-CheckpointRestore-SharedMemory/blob/b502… The monitoring component provides a service [3] to receive a Thread capability to pause the target component before detaching the dataspace and resume after detaching and to provide a managed dataspace to the client. [3] https://github.com/702nADOS/genode-CheckpointRestore-SharedMemory/tree/b502… The monitoring component runs a main loop which pauses the client's main thread and detaches all attached dataspaces from the managed dataspace. The target component also runs a main loop which prints (reads) a number from the managed dataspace to the console and increments (writes) it in the managed dataspaces. The run script is found here [4]. [4] https://github.com/702nADOS/genode-CheckpointRestore-SharedMemory/blob/b502… The scenario works for the first 3 iterations of the monitoring component: Every 4 seconds it detaches the dataspaces from the managed dataspace and afterwards resolves the page faults by attaching the dataspaces back. After the 3. iteration, the target component accesses the theoretically empty managed dataspaces, but does not trigger a page fault. In fact, it reads and writes to the designated dataspaces as if it was attached. By running the run script I get the following output: [init -> target] Initialization started [init -> target] Requesting session to Resource service [init -> ckpt] Initialization started [init -> ckpt] Creating page fault handler thread [init -> ckpt] Announcing Resource service [init -> target] Sending main thread cap [init -> target] Requesting dataspace cap [init -> target] Attaching dataspace cap [init -> target] Initialization ended [init -> target] Starting main loop Genode::Pager_entrypoint::entry()::<lambda(Genode::Pager_object*)>:Could not resolve pf=6000 ip=10034bc [init -> ckpt] Initialization ended [init -> ckpt] Starting main loop [init -> ckpt] Waiting for page faults [init -> ckpt] Handling page fault: READ_FAULT pf_addr=0x00000000 [init -> ckpt] attached sub_ds0 at address 0x00000000 [init -> ckpt] Waiting for page faults [init -> target] 0 [init -> target] 1 [init -> target] 2 [init -> target] 3 [init -> ckpt] Iteration #0 [init -> ckpt] valid thread [init -> ckpt] detaching sub_ds_cap0 [init -> ckpt] sub_ds_cap1 already detached Genode::Pager_entrypoint::entry()::<lambda(Genode::Pager_object*)>:Could not resolve pf=6000 ip=10034bc [init -> ckpt] Handling page fault: READ_FAULT pf_addr=0x00000000 [init -> ckpt] attached sub_ds0 at address 0x00000000 [init -> ckpt] Waiting for page faults [init -> target] 4 [init -> target] 5 [init -> target] 6 [init -> target] 7 [init -> ckpt] Iteration #1 [init -> ckpt] valid thread [init -> ckpt] detaching sub_ds_cap0 [init -> ckpt] sub_ds_cap1 already detached [init -> target] 8 [init -> target] 9 [init -> target] 10 [init -> target] 11 [init -> ckpt] Iteration #2 [init -> ckpt] valid thread [init -> ckpt] sub_ds_cap0 already detached [init -> ckpt] sub_ds_cap1 already detached [init -> target] 12 [init -> target] 13 As you can see: After "iteration #1" ended, no page fault was caused, although the target component printed and incremented the integer stored in the managed dataspace. Could it be, that the detach method was not executed correctly? Kind regards Denis

3 8

tar archive and sd_card partition
by John David 27 Sep '16

27 Sep '16

Hello, I have a libc program called my_test, and I want this program to access files from both an archive (myarchive.tar) and an sd_card partition. For this, I have tried to write a run script and run it, but no luck so far. Part of the configuration is below. I would greatly appreciate if you could help me on the configuration. <start name="sd_card_drv"> <resource name="RAM" quantum="20M"/> <provides><service name="Block"/></provides> </start> <start name="part_blk"> <resource name="RAM" quantum="10M" /> <provides><service name="Block" /></provides> <route> <service name="Block"><child name="sd_card_drv" /></service> <any-service><parent/><any-child/></any-service> </route> <config> <policy label="my_test" partition="2"/> </config> </start> <start name="my_test"> <resource name="RAM" quantum="10M"/> <route> <any-service> <child name="part_blk" /> <parent/> <any-child/> </any-service> </route> <config> <libc stdout="/dev/log" stderr="/dev/log" > <vfs> <dir name="dev"> <log/></dir> <tar name="myarchive.tar"/> </vfs> </libc> </config> </start> Thanks and best regards, John

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users