users

users@lists.genode.org

2285 discussions

Bare bones child process creation.
by Daniel Waddington 31 Mar '16

31 Mar '16

Hi, I'm trying to do bare bones process creation without using the Child or Process helper classes (I'm toying around with serialization ideas). I tried to construct something similar to http://genode.org/documentation/architecture/process but I can't seem to get it to work (error = exception base not specified on nova32). Does anyone have a small code sample in the vain of http://genode.org/documentation/architecture/process ? Daniel

3 3

Memory protection clarification.
by Daniel Waddington 29 Mar '16

29 Mar '16

Hi, If an application allocates memory from its parent (e.g., from init) - is this memory capability granted or mapped? Assuming a secure kernel and IOMMU, how secure is this memory from access by other processes or the root process? How is memory clean up after application exit/death? (Sorry for the newbie questions, I have some catching up to do). Daniel

2 4

RAM Quota Forwarding
by Nobody III 29 Mar '16

29 Mar '16

I made a service router that subclasses Genode::Root, and I've gotten it to work, but I'm unsure of how to properly implement RAM quota forwarding. How do I implement this?

2 1

Genode in distributed scenarios and ROM proxy implementation
by Johannes Schlatow 23 Mar '16

23 Mar '16

Hi, as I'm beginning to use Genode in a distributed scenario, I had some thoughts about the use of proxy components in order to transmit particular session interfaces over an arbitrary communication medium. The general concept here is that a client component can connect to a server component running on a different Genode system by using a proxy component on each side. For starters, I implemented this for the ROM session. I call this implementation "remote ROM": The remote ROM server is instantiated on the server side and connects to a local ROM service. It relays the content of a particular ROM module the remote ROM client, which is instantiated on another Genode system. The remote ROM client receives the updated ROM content from the remote ROM server and provides a local ROM service. In order to generalise the implementation, I separated the network-specific part in a backend library so that the backend can be tailored for the particular communication medium, protocol and policy. I think this renders the implementation highly flexible. I added a backend implementation (nic_ip) as a proof of concept, which uses a Nic service to transmit network packets with a static IPv4 header. In my opinion, the remote ROM implementation is already the enabler for quite a lot of distributed scenarios as it allows full publisher-subscriber communication of arbitrary data without adding too much interdependencies between the systems. The implementation can be found here: https://github.com/ValiValpas/genode-world/tree/remoterom *Please feel free to adapt/contribute/improve this concept and its implementation.*

3 4

Article about Genode's RISC-V support
by Sebastian Sumpf 22 Mar '16

22 Mar '16

Hello everyone, Genode's 16.02 release added support for the RISC-V CPU architecture. As a follow-up, we just published an experience report where we examine the RISC-V design in more detail. Also, we take an in depth look at the steps that were necessary and the challenges we met in order to enable our base-hw kernel and Genode for this platform. The article can be found at: http://genode.org/documentation/articles/riscv Cheers, Sebastian

1 0

Idea on system-level debugging solution
by Johannes Schlatow 21 Mar '16

21 Mar '16

Hi, as I'm recently developing more sophisticated applications with Genode, I had an idea about how to augment the framework with some system-level debugging functionality that I'd like to share and discuss here: First of all, the idea is motivated by the observation that most Genode components are of rather low complexity by themselves. Hence, debugging not only involves the code of a single component, but the operation of the component in context of its interaction with other components. I have therefore been thinking about a generic mechanism to instrument multiple Genode components in a way that allows halting the operation of a component on an incoming/outgoing signal or RPC, and printing the status of certain objects of that component. The major concept I imagine is a hook-based approach that can be used to halt a particular component on demand. The demand would be indicated by a debug ROM that is provided for each component. Once the component is halted, it can react to changes of the debug ROM and be instructed to print debug information or continue the operation for instance. In addition, we would have a debug component as a central controller and user interface. Based on the user input, the debug controller populates the debug ROMs that are evaluated by the debug logic of the component(s) under test. With this mechanism, we could eventually set "breakpoints" at the hooks of the debugged components and interactively (or automatically) print the debug information of the components. The debug logic can probably be implemented as a debug library that implements the hooks. A component is being instrumented by adding calls to the library functions and registering callback functions that print the debug information. Debugging is disabled by linking against a dummy library. Maybe this could also be implemented as a trace policy. Disclaimer: I currently do not have the resources to implement such a feature, hence anyone keen on this idea is kindly invited to do so ;-)

3 2

GDB monitor
by Joscha Benz 18 Mar '16

18 Mar '16

Hi, im currently working with Genode on Zynq-7000 based HW and i was trying to port GDB Monitor to that platform. So far i implemented * ports/src/lib/gdbserver_platform/spec/hw_zynq/low.cc * ports/lib/mk/spec/hw_zynq/gdbserver_platform.mk I then tried running a modified version "make run/gdb_monitor_interactive". I'm using tcp_terminal as terminal session. My first problem is that running the above command times out while the run-script is waiting for GDB monitor to start. I guess when using tcp_terminal "/dev/terminal" is only created after making a connection to it? I am able to connect to GDB monitormanually and i can read/set registers, print backtrace and set breakpoints. But actually running specific parts of the code being debugged does not work. Jumping to function func1 after setting a breakpoint at func2 for example yields the following: Assertion failed: _state == AWAITS_RESUME || _state == ACTIVE File: repos/base-hw/src/core/kernel/thread.cc:134 Function: void Kernel::Thread::_pause() Typing "run" the gdb complains: The "remote" target does not support "run". Try "help target" or "continue". I dont really know what the problem is at this point. Do i have to implement additional files to get a full working port of GDB monitor for hw_zynq? Or am i just doing something wrong? I also tried using GDB monitor with foc_x86_32 and nova_x86_32. I ran "make run/gdb_monitor" but i get the following result for both platforms: GDB monitor is up, starting GDB spawn /usr/local/genode-gcc/bin/genode-x86-gdb bin/test-gdb_monitor -n -batch -ex target remote localhost:5555 -ex set interactive-mode off -ex symbol-file bin/ld.lib.so -ex b Linker::Binary::call_entry_point -ex c -ex delete 1 -ex symbol-file bin/test-gdb_monitor -ex b main -ex set solib-search-path bin -ex sharedlibrary -ex c -ex delete 2 -ex b puts -ex c -ex bt -ex print test_var -ex set var test_var=2 -ex print test_var -ex b Test_thread::entry() -ex c -ex info threads -ex step -ex c -ex thread 1 -ex bt -ex q 2&>1 [init -> gdb_monitor] fcntl(): command 4 args 66 not supported - terminal [init -> gdb_monitor] fcntl(): command 6 args -1 not supported - terminal int main(): --- init created, waiting for exit condition --- Don't know how to attach. Try "help target". GDB can't read core files on this machine. Ignoring packet error, continuing... warning: unrecognized item "timeout" in "qSupported" response Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Remote communication error. Target disconnected.: Die Verbindung wurde vom Kommunikationspartner zurückgesetzt. Breakpoint 1 at 0xaab20: file repos/base/src/lib/ldso/main.cc, line 364. The program is not being run. Breakpoint 2 at 0x1000a05: file repos/base/include/base/thread.h, line 583. The program is not being run. Breakpoint 3 at 0x1007720 The program is not being run. No stack. $1 = 1 Cannot access memory at address 0x1008cac $2 = 1 Breakpoint 4 at 0x1005ae0: file repos/ports/src/test/gdb_monitor/main.cc, line 44. The program is not being run. No threads. The program is not being run. The program is not being run. Thread ID 1 not known. No stack. Error: Breakpoint in main() did not trigger Makefile:246: die Regel für Ziel „run/gdb_monitor“ scheiterte make: *** [run/gdb_monitor] Fehler 255 I can see that the problem seems to be related to the terminal session. Is this supposed to work out of the box? Any hint/advice would be much appreciated. All changes i made may be found here: https://github.com/ValiValpas/genode/tree/zynq_gdb_monitor Regards, Joscha

2 4

service router
by Nobody III 18 Mar '16

18 Mar '16

I've been trying to implement my own service router, to make dynamic configuration easier. However, I'm struggling to find a way to request services with only a label and a service name and provide them when a service is requested. I've looked at the init code, but I'm trying to allow the server to provide services to siblings, which complicates things. Could somebody please give me some pointers? I suspect that I may need to extend Genode::Root to provide different services/capabilities according the the router's policy. Am I correct? I haven't quite been able to piece together how capability/session requests are resolved.

2 3

Custom implementation of core services
by David Werner 14 Mar '16

14 Mar '16

Hi Genode-mailing-list, i have a little problem with my ram and rm custom implementations. When i try to create a child component which uses my custom sessions/services by running the following code: int main(void) { PDBG("--- start proxy_server ---\n"); PDBG("--- announcing proxy services --- "); Cap_connection cap; static Sliced_heap sliced_heap(env()->ram_session(), env()->rm_session()); enum { STACK_SIZE = 8*1024 }; static Rpc_entrypoint ep(&cap, STACK_SIZE, "proxy_ep"); static Proxy::Prm_root prm_root(&ep, &ep, &sliced_heap); PDBG("PRM_root created and back in server-main!"); static Proxy::Pram_root pram_root(&ep, &ep, &sliced_heap); PDBG("PRAM_root created and back in server-main!"); env()->parent()->announce(ep.manage(&prm_root)); PDBG("PRM service announced!"); env()->parent()->announce(ep.manage(&pram_root)); PDBG("PRAM service announced!"); PDBG("--- starting test child ---"); /* Creating session for child environment */ static Rom_connection rom("proxy_test_client"); static Pd_connection pd; static Proxy::Pram_connection pram; <---------------- custom service, execution fails here. static Cpu_connection cpu; static Proxy::Prm_connection prm; <---------------- custom service static Cap_connection child_cap; /* declaring ref account for child's ram session and transferring quota */ enum { CHILD_QUOTA = 1*1024*1024 }; pram.ref_account(env()->ram_session_cap()); env()->ram_session()->transfer_quota(pram.ram_cap(), CHILD_QUOTA); /* creating test child */ Test_child proxy_test_child(rom.dataspace(), pd.cap(), pram.cap(), cpu.cap(), prm.cap(), &child_cap); PDBG("--- proxy_server is going to sleep ---"); sleep_forever(); PDBG("Server still awake - This output should not be reached!"); return 0; } I get this output: Genode 15.11-71-g2e0e767 int main(): --- create local services --- int main(): --- start init --- int main(): transferred 112 MB to init int main(): --- init created, waiting for exit condition --- [init] Could not open ROM session for module "ld.lib.so" [init -> proxy_server] int main(): --- start proxy_server --- [init -> proxy_server] int main(): --- announcing proxy services --- [init -> proxy_server] Proxy::Prm_root::Prm_root(Genode::Rpc_entrypoint*, Genode::Rpc_entrypoint*, Genode::Allocator*): Creating Prm_root_component... [init -> proxy_server] int main(): PRM_root created and back in server-main! [init -> proxy_server] Proxy::Pram_root::Pram_root(Genode::Rpc_entrypoint*, Genode::Rpc_entrypoint*, Genode::Allocator*): Creating Pram_root_component... [init -> proxy_server] int main(): PRAM_root created and back in server-main! [init -> proxy_server] int main(): PRM service announced! [init -> proxy_server] int main(): PRAM service announced! [init -> proxy_server] int main(): --- starting test child --- [init -> proxy_server] virtual Proxy::Pram_session_component* Proxy::Pram_root::_create_session(const char*): Creating Pram_session_component... KERNEL: Warning: nothing mapped: (Obj_space) from [0xfffffffffccfe5d8/38]: 0000000000000237 size: 0000000000000001 to [0xfffffffffccfe5d8/38] Error: Test execution timed out make: *** [run/proxy] Fehler 254 I have no idea why this may happen. When running a component which is started by init and which is no child of my server component opening a connection to my custom service works perfectly fine. I'd be very grateful for a little bit of help here. Best regards, David

2 3

Re: Mouse pointer speed
by Bent Bracke 13 Mar '16

13 Mar '16

Hi I ran it without qemu like you suggested and it worked :-) Thank you! Kind regards Bent Bracke > On 9. mar. 2016, at 08.40, Stefan Kalkowski <stefan.kalkowski@...1...> wrote: > > Hello Bent, > >> On 03/09/2016 07:15 AM, Bent Bracke wrote: >> Hi >> >> Sorry about the lack of details. >> >> It is possible that it's just too fast. I'm simply having difficulties clicking on anything because the mouse pointer moves around so quickly. >> >> I'm running genode with qemu on Ubuntu on macbookpro via parallels. >> >> It is a usb trackball which works fine on Ubuntu and OS X. > > so you run Genode inside a virtual machine (Qemu) inside a virtual > machine (parallels)? Then of course the actual hardware, your usb > trackball, does not play a role anymore. Using this kind of nested > virtualization lead to different various problems for different people > in the past. > > A possible solution to circumvent the nesting of virtualization > techniques would be to use your Ubuntu VM for building the Genode > scenario, but instead of executing it within Qemu, you could boot the > resulting ISO image again via parallels natively on your Mac OS in a > second VM. > > Regards > Stefan > >> Kind regards >> Bent Bracke >> >>> On 7. mar. 2016, at 17.14, Norman Feske <norman.feske@...1...> wrote: >>> >>> >>> Hello Bent, >>> >>>> In all the examples that come with Genode, the mouse pointer moves at >>>> what seems like an erratic speed. >>>> Is this a driver issue or something else? >>> >>> I am afraid that your question is too unspecific to give you a good >>> answer. Do you observe the erratic behavior on different machines and >>> with different mouses? Are you referring to a PS/2 mouse (with the PS/2 >>> driver) or a USB HID mouse (with the USB driver)? Or are you using a USB >>> mouse with the PS/2 driver? In the latter case, the BIOS provides some >>> rudimentary PS/2 emulation. It is really hard to diagnose the problem >>> remotely. >>> >>> That said, our PS/2 driver is indeed rather simple. It resets the mouse >>> but does not attempt to set any specific parameters with respect to >>> mouse speed or acceleration. You can have a look at >>> repos/os/src/drivers/input/ps2/ to investigate. >>> >>> If you observe the problem with the USB HID driver, this would surprise >>> me because we are actually using the Linux USB driver on Genode. So the >>> mouse should work just as well as on Linux. >>> >>> 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 >>> >>> ------------------------------------------------------------------------------ >>> Transform Data into Opportunity. >>> Accelerate data analysis in your applications with >>> Intel Data Analytics Acceleration Library. >>> Click to learn more. >>> http://makebettercode.com/inteldaal-eval >>> _______________________________________________ >>> genode-main mailing list >>> genode-main(a)lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/genode-main >> ------------------------------------------------------------------------------ >> Transform Data into Opportunity. >> Accelerate data analysis in your applications with >> Intel Data Analytics Acceleration Library. >> Click to learn more. >> http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140 >> _______________________________________________ >> genode-main mailing list >> genode-main(a)lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/genode-main > > -- > Stefan Kalkowski > Genode Labs > > http://www.genode-labs.com/ · http://genode.org/ > > ------------------------------------------------------------------------------ > Transform Data into Opportunity. > Accelerate data analysis in your applications with > Intel Data Analytics Acceleration Library. > Click to learn more. > http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140 > _______________________________________________ > genode-main mailing list > genode-main(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/genode-main

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users