users

users@lists.genode.org

3 participants
2349 discussions

gdb_monitor not working on nova_x86_64
by Nobody III 01 Jul '16

01 Jul '16

I am planning on using gdb_monitor to debug components I write, but it doesn't seem to work. I have tried all the run scripts, and none of them succeed at attaching the debugger. I looked for any recent applicable commits in genodelabs/master, but none of them are more recent than the 16.05 release which my personal repo is currently based on. Here is the output from gdb_monitor.run: int main(): --- create local services --- int main(): --- start init --- int main(): transferred 86 MB to init [init] parent provides [init] service "ROM" [init] service "RAM" [init] service "IRQ" [init] service "IO_MEM" [init] service "IO_PORT" [init] service "PD" [init] service "RM" [init] service "CPU" [init] service "LOG" [init] child "timer" [init] RAM quota: 1863680 [init] ELF binary: timer [init] priority: 0 [init] provides service Timer [init] child "uart_drv" [init] RAM quota: 1863680 [init] ELF binary: uart_drv [init] priority: 0 [init] provides service Terminal [init] provides service Uart [init] child "gdb_monitor" [init] RAM quota: 3960832 [init] ELF binary: gdb_monitor [init] priority: 0 [init] child "timer" announces service "Timer" [init -> uart_drv] --- i8250 UART driver started --- [init] child "uart_drv" announces service "Uart" [init] child "uart_drv" announces service "Terminal" [init -> gdb_monitor] usinGDB monitor is up, starting GDB spawn /usr/local/genode-gcc/bin/genode-x86-gdb bin/ld.lib.so -n -ex target remote localhost:5555 -ex set interactive-mode off -ex b binary_ready_hook_for_gdb -ex c -ex delete 1 -ex file bin/test-gdb_monitor -ex b main -ex set solib-search-path bin -ex sharedlibrary -ex c -ex delete 2 2&>1 ----- test: breakpoint in 'main()' ----- g the pipe libc plugin [init -> gdb_monitor] int sigaction(int, const sigaction*, sigaction*): sigaction not implemented [init -> gdb_monitor] Process target created; pid = 1 [init -> gdb_monitor] unsupported ioctl (request=0x40047477) [init -> gdb_monitor] unsupported ioctl (request=0x80047476) [init -> uart_drv] Baudrate is not defined. Use default 115200 GNU gdb (GDB) 7.3.1 Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html > This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=x86_64-unknown-linux-gnu --target=x86_64-pc-elf". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /home/kingtux/genode/build/nova_x86_64/bin/ld.lib.so...[init -> gdb_monitor] Remote debugging using /dev/terminal [init -> gdb_monitor] fcntl(): command 4 args 66 not supported - terminal [init -> gdb_monitor] fcntl(): command 6 args 4294967295 not supported - terminal int main(): --- init created, waiting for exit condition --- done. Don't know how to attach. Try "help target". GDB can't read core files on this machine. localhost:5555: Connection timed out. Breakpoint 1 at 0xafd10: file /home/kingtux/genode/repos/base/src/lib/ldso/debug.cc, line 21. The program is not being run. Load new symbol table from "/home/kingtux/genode/build/nova_x86_64/bin/test-gdb_monitor"? (y or n) [answered Y; input not from terminal] Reading symbols from /home/kingtux/genode/build/nova_x86_64/bin/test-gdb_monitor...done. Breakpoint 2 at 0x1001678: file /home/kingtux/genode/repos/ports/src/test/gdb_monitor/main.cc, line 93. The program is not being run. (gdb) *** Error: Breakpoint in main() did not trigger Makefile:261: recipe for target 'run/gdb_monitor' failed make: *** [run/gdb_monitor] Error 255

2 2

TRACE API: trace identification
by Joscha Benz 30 Jun '16

30 Jun '16

Hi, im currently using genode's TRACE API to trace communication paths between multiple threads. For that to work properly I need to be able to map all corresponding trace events to each other. For example a RPC_CALL event to the corresponding RPC_DISPATCH event. The problem is as follows. Since a trace event is logged _before_ the related action is executed, it is possible that a thread is preempted between those two actions. In that case I'm unable to do the mapping just using the information provided by the TRACE API or am I missing something? Best regards, Joscha

1 0

multiboot l4linux and ubuntu
by john stokes 30 Jun '16

30 Jun '16

after building the l4linux using make run/l4linux i got the iso file of l4linux now i want to create a grub2 entry for l4linux along with ubuntu how should i do it? i have followed methods given on other places they all are distro specific i have also seen nova hypervisor multiboot mailing list doubt it is of not much help is there any way to use create_grub2 tool? my l4linux file is at <build-dir>/foc_x86_32/var/run/l4linux/boot <build-dir>/foc_x86_32/var/run/l4linux/genode <build-dir>/foc_x86_32/var/run/l4linux/fiasco <build-dir>/foc_x86_32/var/run/l4linux/boot/grub <build-dir>/foc_x86_32/var/run/l4linux/boot/isolinux <build-dir>/foc_x86_32/var/run/l4linux/boot/bender <build-dir>/foc_x86_32/var/run/l4linux/boot/grub/menu.lst contains following things timeout 0 default 0 title Genode on Fiasco.OC kernel /boot/bender module /fiasco/bootstrap module /fiasco/fiasco -serial_esc module /fiasco/sigma0 module /genode/core module /genode/config module /genode/init module /genode/timer module /genode/kdb_uart_drv module /genode/l4linux module /genode/initrd.gz module /genode/ps2_drv module /genode/fb_drv module /genode/nic_drv module /genode/platform_drv module /genode/acpi_drv module /genode/report_rom vbeset 0x117 506070

2 2

allocator out of memory error during creation of File_system::Connection
by Nobody III 30 Jun '16

30 Jun '16

I have been working on my fs_filter (vfs-like) component, and it compiles, but fails to successfully create a File_system::Connection. Even with a ram quota of 1G, I get the following error: Uncaught exception of type 'Genode::Allocator::Out_of_memory' What am I doing wrong? I have tried multiple different allocator configurations (e.g. Allocator_avl(sliced_heap), Allocator_avl(Genode::env()->heap()), Allocator_avl(0)), but nothing fixes or changes the error.

1 0

File_system signals
by Nobody III 30 Jun '16

30 Jun '16

In my fs_filter component (much like the vfs server), I am trying to allow multiple clients fast, non-blocking access to multiple filesystems. To do this without several threads, my component needs to know when each filesystem server unblocks so it can send more packets. Unfortunately, the File_system::Client interface (which File_system::Connection inherits) doesn't provide a way to receive signals when the server acknowledges packets or is ready for more packets, given that it only provides a Session:Tx::Source object for accessing the packet stream. The Session::Tx::Source interface provide the methods sigh_ack_avail() and sigh_ready_to_submit(), which allow a cilent to get the signal handlers currently in use, but doesn't allow registering new signal handlers. I added a workaround that exposes the Packet_stream_tx::Client object to the client, but it would be good to have a better way to register these signal handlers. Is there currently a way to do this, or does this require a modification to the API, like what I did?

2 2

error related to block device while running make run/l4linux
by john stokes 29 Jun '16

29 Jun '16

after doing make menuconfig and selecting block device support for l4linux so that when i boot it on real hardware the root file system can be mounted easily.but i am getting this infinite loop is there any solution for bloc device support ? [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64 [init -> l4linux] Invalid IO-Port access at pc = 005a9650 port=0x64

2 2

16.05 custom kernel call fails to get session capability.
by Bob Stewart 28 Jun '16

28 Jun '16

Hi, I'm moving from release 15.11 to 16.05 on base-hw and am having a "service denied" issue when trying to get a connection to a custom service I created to handle pin muxing on TI Sitara processors. In this family of processors, access to a "Control Module" is need to enable subsystems, set up clock frequencies, and set the mode for gpio pins which have multiple functions dependent upon the mode they are set to. Write access to the Control Module is only allowed in a privileged mode so I had to create custom kernel calls to access the appropriate SoC registers. I did this in release 14.05 by adding the code for unrestricted kernel calls to base-hw and it has been working without issue through various releases until I stared to move to 16.05. The log output I'm getting is: Starting kernel ... kernel initialized Genode 16.05 <local changes> int main(): --- create local services --- int main(): --- start init --- int main(): transferred 503 MB to init int main(): --- init created, waiting for exit condition --- [init] Could not open ROM session for module "ld.lib.so" [init -> ctrl_module] ---437x Control Module Server : Setting Pin Muxes--- [init -> ctrl_module] pin mux capability [init -> timer] Maximum timeout 1717986000 us [init -> timer] --- am437x timer driver --- [init -> 437x_platform_client] --- 437x platform being configured -- [init -> ctrl_module] Uncaught exception of type 'Genode::Parent::Service_denied' [init -> ctrl_module] Warning: abort called - thread: ep [init] virtual void Genode::Child_policy::exit(int): child "ctrl_module" exited w ith exit value 1 [init -> 437x_platform_client] Enabled dmtimer 3 freq = 1 [init -> 437x_platform_client] Enabled dmtimer 4 freq = 1 ....(other messages unrelated to the issue follow) The uncaught exception is being generated in my "pinmux_session" connection code when a capability for a session is requested, as shown the following in the following code snippet from pinmux_connection.h namespace Genode { struct Pinmux_connection; } struct Genode::Pinmux_connection : Connection<Pinmux_session>, Pinmux_session_client { /** * Issue session request * * \noapi */ Capability<Pinmux_session> _session(Parent &parent, char const *label, long priority, unsigned long affinity) { Genode::printf("pin mux capability\n"); return***/session(parent,/**/ /**/ "priority=0x%lx, affinity=0x%lx, ram_quota=16K, label=\"%s\"",/**/ /**/ priority, affinity, label); (exception occurs here)/* } /** * Constructor * * \param label initial session label * \param priority designated priority of the Pinmux * \param affinity which physical CPU the VM should run on top of */ Pinmux_connection(Genode::Env &env, const char *label = "", long priority = Cpu_session::DEFAULT_PRIORITY, unsigned long affinity = 0) : Connection<Pinmux_session>( env, _session(env.parent(), label, priority, affinity)), Pinmux_session_client(cap()) { } /** * Constructor * * \noapi * \deprecated Use the constructor with 'Env &' as first * argument instead */ Pinmux_connection(const char *label = "", long priority = Cpu_session::DEFAULT_PRIORITY, unsigned long affinity = 0) : Connection<Pinmux_session>(_session(*env()->parent(), label, priority, affinity)), Pinmux_session_client(cap()) { Genode::printf("ctrl mod connection\n");} }; This code differs from the 15.11 code in that the request for a session now requires a "parent" argument in 16.05. Looking at similar kernel call codes like the vm calls, my changes to my custom calls for 16.05 appear to be correct. I can see in the kernel code (parent.h) where the exception is occurring but I have no clue as to why it occurs. Any hints would be greatly appreciated. Thanks, Bob Stewart

3 3

Recursive Nitpicker
by Michael Ullrich 28 Jun '16

28 Jun '16

Hallo, I'm currently trying to modularize a Qt-based ChatClient. The basic idea is to isolate the parts of some guy-components from each other. I want to use Nitpicker for this. In generally the Client itself should run in a trusted nitpicker session. Now I want to start another nitpicker-sessions inside the quote-client. Meaning by that, I want for example a trusted input-field or a trusted label, isolated from the remaining qt-app. So isolate several graphical components from each other. Is it in generally a good idea, to use nitpicker in that way? Has someone tried something similar, or is there an reference implementation for that? With kind regards, Michael Ullrich

3 2

Benchmarking Genode TrustZone
by Tiago Brito 28 Jun '16

28 Jun '16

Hi, I want to benchmark the execution of a function running in the secure world of the TZ_VMM scenario in the i.MX53 QSB. I have added a syscall to Linux which allows me to trigger a world switch from a user program running in Linux. In this program I have a function which allocates a buffer and processes it (each buffer position is changed in some way). This same function is coded inside TZ_VMM. This is what I'm testing: 1. Inside my user program in Linux I use gettimeofday before and after the execution of the function in order to get the amount of milliseconds in between. This is my NW test. 2. Inside my user program in Linux I use gettimeofday to get the start time, then I execute the syscall which in turn does a world switch. Then the function is executed inside the SW and it returns to the user program inside Linux. After this I call another gettimeofday in order to get the amount of milliseconds of execution. The problem is that test 1 is giving me about 90 ms of real time execution, but test 2 gives me about 40 ms. I suspect it might be a problem with Linux virtualization in the TZ_VMM example, which may be causing a drift in Linux's clock once it loses control to the SW. What I mean is, when there isn't a syscall triggering the SMC, Linux can count time just fine, but once the control is lost to the secure world the clock inside Linux becomes inconsistent and doesn't count time while the secure world is executing. Is this right? Since I really need to benchmark a scenario similar to this I think that the best alternative is to offload the time functionality to Genode (SW). I create another syscall which is responsible for starting a timer inside Genode, then I call the SMC syscall which processes the buffer in the SW, then I call the time syscall again and check the difference. When I want to benchmark the NW function I follow the same steps as before. Will this work as intended? I'm thinking that this alternative may suffer from the same problem as before if Genode's time clock becomes inconsistent whenever Linux is being executed in NW. Do you know any other way to benchmark a world switch + processing + world switch scenario? Is there any timer I can execute inside TZ_VMM? Thanks in advance, Tiago

4 9

l4linux fails on fiasco.oc 64bit
by john stokes 27 Jun '16

27 Jun '16

i tried to run l4linux over foc_x86_32 platefrom it ran well. now after building the build directory for foc_x86_64 i am agian trying to run the run script of l4linux from the build directory then i am getting this error I have changed the <spec>.conf and of the ports-foc and other tarhget.mk for my foc_x86_64 but it is not working the error is : the same thing works fine for foc_x86_32 Program drivers/nic/nic_drv Program drivers/platform/spec/x86/platform_drv Library alarm Library timer Program drivers/timer/timer Program drivers/uart/kdb/spec/foc/kdb_uart_drv Program drivers/uart/spec/i8250/uart_drv Program init/init Library l4lx COMPILE l4_util_util.o In file included from /home/rishabh/genode-16.05/repos/ports-foc/src/lib/l4lx/l4_util_util.cc:18:0: /home/rishabh/genode-16.05/repos/ports-foc/include/l4/util/util.h: In function ‘void Fiasco::l4_touch_ro(const void*, unsigned int)’: /home/rishabh/genode-16.05/repos/ports-foc/include/l4/util/util.h:31:34: error: cast from ‘const void*’ to ‘unsigned int’ loses precision [-fpermissive] bptr = (const char*)(((unsigned)addr) & L4_PAGEMASK); ^ /home/rishabh/genode-16.05/repos/ports-foc/include/l4/util/util.h:32:34: error: cast from ‘const void*’ to ‘unsigned int’ loses precision [-fpermissive] eptr = (const char*)(((unsigned)addr+size-1) & L4_PAGEMASK); ^ /home/rishabh/genode-16.05/repos/ports-foc/include/l4/util/util.h: In function ‘void Fiasco::l4_touch_rw(const void*, unsigned int)’: /home/rishabh/genode-16.05/repos/ports-foc/include/l4/util/util.h:45:28: error: cast from ‘const void*’ to ‘unsigned int’ loses precision [-fpermissive] bptr = (char*)(((unsigned)addr) & L4_PAGEMASK); ^ /home/rishabh/genode-16.05/repos/ports-foc/include/l4/util/util.h:46:34: error: cast from ‘const void*’ to ‘unsigned int’ loses precision [-fpermissive] eptr = (const char*)(((unsigned)addr+size-1) & L4_PAGEMASK); ^ make[3]: *** [l4_util_util.o] Error 1 make[2]: *** [l4lx.lib] Error 2 make[1]: *** [gen_deps_and_build_targets] Error 2 make[1]: Leaving directory `/home/rishabh/genode-16.05/build/foc_x86_64' Error: Genode build failed make: *** [run/l4linux] Error 252

3 6

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users