users

users@lists.genode.org

2285 discussions

Component communication over ethernet using VDE switches
by Kevin Burton 22 Oct '21

22 Oct '21

Hello, I am currently writing a program which boils down to a few components communicating over Ethernet using sockets. This works well utilizing the nic_router functionality, but I would like to emulate a more realistic scenario with the components being started from their own respective run scripts. I know for a fact that this was possible using the VDE switch functionality of QEMU in late 2015, but can't get it to work now the same way it used to, which simply consisted of starting the switch in a terminal and appending -net vde,sock=<switch location> to the QEMU args. No errors or warnings are thrown. Does anybody have recent experience with VDE switches or knows anything similar that could be used to achieve a more lifelike scenario? If possible, examples of such run scripts would be very helpful. Thanks in advance for your assistance. Kind regards, Kevin Burton

2 1

sleep and/or keyboard listen
by Kevin Burton 17 Oct '21

17 Oct '21

Hello Genodians, is it possible to have the main thread either sleep for a specific amount of time or have it wait for a keyboard input? If yes, how would I go about implementing it? I have read online that the Timer service is in charge of sleeps, but I haven't found a way to use it at all. Thanks in advance for your help. Kind regards, Kevin Burton

3 2

gdb_monitor for NOVA hit Error: __cxa_pure_virtual called
by Alexander Tormasov 15 Oct '21

15 Oct '21

I am trying gdb debugging for 21.08 (gcc 10.3) for nova x86_64 I compile everything from the scratch using make -C build/x86_64/ KERNEL=nova BOARD=pc CFLAGS="-g -O0" VERBOSE= run/go_app_dbg while attempt to run it inside qemu with 2 GB I see a problem in dbg_monitor itself, see below SeaBIOS (version rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org) iPXE (http://ipxe.org) 00:02.0 CA00 PCI2.10 PnP PMM+7FF90660+7FEF0660 CA00 Booting from Hard Disk... Boot failed: could not read the boot disk Booting from DVD/CD... Bender: Hello World. NOVA' hwp config: eeo=na irq=na hwp=na epp=na epb=na NOVA Microhypervisor v8-5c64bba (x86_64): Oct 12 2021 01:47:36 [gcc 10.3.0] [MBI2] [ 0] TSC:2014786 kHz BUS:1009035 kHz (measured) [ 0] CORE:0:0:0 6:f:b:0 [0] Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz Hypervisor NOVA (API v8) core image [0000000000100000,00000000011bd000) binaries region [0000000000351000,00000000011bd000) free for reuse detected physical memory: 0x0000000000000000 - size: 0x000000000009fc00 use physical memory: 0x0000000000000000 - size: 0x000000000009f000 detected physical memory: 0x0000000000100000 - size: 0x000000007fedf000 use physical memory: 0x0000000000100000 - size: 0x000000007fedf000 reserved memory: 0x7ef20000 - size: 0x10be2f0 type=-2 reserved memory: 0x9fc00 - size: 0x400 type=2 reserved memory: 0xf0000 - size: 0x10000 type=2 reserved memory: 0x7ffdf000 - size: 0x21000 type=2 reserved memory: 0xb0000000 - size: 0x10000000 type=2 reserved memory: 0xfed1c000 - size: 0x4000 type=2 reserved memory: 0xfffc0000 - size: 0x40000 type=2 reserved memory: 0xfd000000 - size: 0x300000 type=-5 reserved memory: 0x1000000 - size: 0x800000 type=-1 reserved memory: 0x1800000 - size: 0x1c00000 type=-1 reserved memory: 0x7ffe20f8 - size: 0x0 type=-3 Hypervisor reports 1x1 CPU Warning: CPU has no invariant TSC. mapping: affinity space -> kernel cpu id - package:core:thread remap (0x0) -> 0 - 0:0:0) boot cpu ROM modules: ROM: [000000007f172000,000000007f172701) config ROM: [000000000000e000,0000000000012000) core_log ROM: [000000007fe32000,000000007ff968e8) gdb_monitor ROM: [000000007ff97000,000000007ffdd870) gdbserver_platform.lib.so ROM: [000000007f173000,000000007f2084a8) init ROM: [000000007f235000,000000007f398c78) ld.lib.so ROM: [000000007f399000,000000007f631cb0) libc.lib.so ROM: [000000007f632000,000000007f68fb20) libm.lib.so ROM: [000000007fdf9000,000000007fe31d58) pc_uart_drv ROM: [000000000000c000,000000000000d000) platform_info ROM: [000000007f690000,000000007f69ca70) posix.lib.so ROM: [000000007f69d000,000000007f8bce58) stdcxx.lib.so ROM: [000000007f9f5000,000000007fdf8418) test-go ROM: [000000007f209000,000000007f2342d0) timer ROM: [000000007f8bd000,000000007f9f4938) vfs.lib.so 36M kernel memory Genode 21.05-180-geb2f7074f <local changes> 1994 MiB RAM and 63254 caps assigned to init [init -> gdb_monitor] 0x1000000 .. 0x10ffffff: linker area [init -> pc_uart_drv] --- UART driver started — [init -> gdb_monitor] Error: __cxa_pure_virtual called, return addr is 0x12c849 I printed stack trace here: 0x000000000012c849: Linker::Root_object::~Root_object()::{lambda(Linker::Dependency&)#1}::operator()(Linker::Dependency&) const at linker.h:361 0x0000000000136eb9: void Genode::Fifo<Linker::Dependency>::dequeue<Linker::Root_object::~Root_object()::{lambda(Linker::Dependency&)#1}>(Linker::Root_object::~Root_object()::{lambda(Linker::Dependency&)#1} const&) at fifo.h:170 0x0000000000134261: void Genode::Fifo<Linker::Dependency>::dequeue_all<Linker::Root_object::~Root_object()::{lambda(Linker::Dependency&)#1}>(Linker::Root_object::~Root_object()::{lambda(Linker::Dependency&)#1} const&) at fifo.h:182 (discriminator 1) 0x000000000012c8cc: Linker::Root_object::~Root_object() at linker.h:363 0x00000000001305ea: Linker::Binary::Binary(Genode::Env&, Genode::Allocator&, Linker::Config const&, char const*) at main.cc:368 (discriminator 1) 0x0000000000137e5e: void Unmanaged_singleton_constructor::call<Linker::Binary, Genode::Env&, Genode::Heap&, Linker::Config const&, char const*&>(char*, Genode::Env&, Genode::Heap&, Linker::Config const&, char const*&) at unmanaged_singleton.h:58 0x00000000001362d0: Linker::Binary* unmanaged_singleton<Linker::Binary, 8, Genode::Env&, Genode::Heap&, Linker::Config const&, char const*>(Genode::Env&, Genode::Heap&, Linker::Config const&, char const*&&) at unmanaged_singleton.h:87 0x0000000000133245: Component::construct(Genode::Env&) at main.cc:812 (discriminator 4) 0x00000000000a61e6: (anonymous namespace)::Constructor_component::construct() at entrypoint.cc:320 0x00000000000ab265: Genode::Meta::Empty Genode::Meta::call_member<Genode::Meta::Empty, (anonymous namespace)::Constructor_component, Genode::Meta::Empty>((anonymous namespace)::Constructor_component&, Genode::Meta::Empty&, void ((anonymous namespace)::Constructor_component::*)()) at meta.h:464 (discriminator 4) 0x00000000000ab180: Genode::Meta::Empty (anonymous namespace)::Constructor::Rpc_construct::serve<(anonymous namespace)::Constructor_component, Genode::Meta::Empty>((anonymous namespace)::Constructor_component&, Genode::Meta::Empty&) at entrypoint.cc:293 0x00000000000aaf2d: (anonymous namespace)::Constructor::Rpc_construct::Ret_type Genode::Rpc_dispatcher<(anonymous namespace)::Constructor, (anonymous namespace)::Constructor_component>::_do_serve<(anonymous namespace)::Constructor::Rpc_construct>((anonymous namespace)::Constructor::Rpc_construct::Server_args&, Genode::Meta::Overload_selector<(anonymous namespace)::Constructor::Rpc_construct, Genode::Meta::Empty>) at rpc_server.h:146 0x00000000000aaabd: Genode::Rpc_exception_code Genode::Rpc_dispatcher<(anonymous namespace)::Constructor, (anonymous namespace)::Constructor_component>::_do_dispatch<Genode::Meta::Type_list<(anonymous namespace)::Constructor::Rpc_construct> >(Genode::Rpc_opcode, Genode::Ipc_unmarshaller&, Genode::Msgbuf_base&, Genode::Meta::Overload_selector<Genode::Meta::Type_list<(anonymous namespace)::Constructor::Rpc_construct>, Genode::Meta::Type_list<(anonymous namespace)::Constructor::Rpc_construct> >) at rpc_server.h:182 0x00000000000aa92d: Genode::Rpc_dispatcher<(anonymous namespace)::Constructor, (anonymous namespace)::Constructor_component>::dispatch(Genode::Rpc_opcode, Genode::Ipc_unmarshaller&, Genode::Msgbuf_base&) at rpc_server.h:236 0x00000000000aa868: Genode::Rpc_object<(anonymous namespace)::Constructor, (anonymous namespace)::Constructor_component>::dispatch(Genode::Rpc_opcode, Genode::Ipc_unmarshaller&, Genode::Msgbuf_base&) at rpc_server.h:273 0x00000000000c9d4e: Genode::Rpc_entrypoint::_activation_entry()::{lambda(Genode::Rpc_object_base*)#1}::operator()(Genode::Rpc_object_base*) const at rpc_entrypoint.cc:168 0x00000000000cbda4: Genode::Trait::Functor<decltype (&Genode::Rpc_entrypoint::_activation_entry()::{lambda(Genode::Rpc_object_base*)#1}::operator())>::Return_type Genode::Object_pool<Genode::Rpc_object_base>::apply<Genode::Rpc_entrypoint::_activation_entry()::{lambda(Genode::Rpc_object_base*)#1}>(unsigned long, Genode::Trait::Functor) at object_pool.h:147 0x00000000000ca08e: Genode::Rpc_entrypoint::_activation_entry() at rpc_entrypoint.cc:171 run file #debug go application via gdb # set build_components { core init timer lib/ld drivers/uart app/gdb_monitor test/go_app } lappend build_components "lib/gdbserver_platform-$::env(KERNEL)" build $build_components create_boot_directory install_config { <config> <parent-provides> <service name="ROM" /> <service name="LOG" /> <service name="RM" /> <service name="CPU" /> <service name="PD" /> <service name="IRQ" /> <service name="IO_MEM" /> <service name="IO_PORT" /> </parent-provides> <default-route> <any-service> <parent/> <any-child/> </any-service> </default-route> <default caps="250" /> <start name="timer" caps="200"> <resource name="RAM" quantum="2M"/> <provides> <service name="Timer"/> </provides> </start> <start name="pc_uart_drv" caps="200"> <resource name="RAM" quantum="2M" /> <provides> <service name="Uart"/> <service name="Terminal"/> </provides> <config> <policy label_prefix="gdb_monitor" uart="1" /> </config> </start> <start name="gdb_monitor" caps="3500"> <resource name="RAM" quantum="550M" /> <provides> <service name="test-go" /> </provides> <config verbose="yes" ld_verbose="yes"> <target name="test-go" > <config verbose="yes" ld_verbose="yes"> <vfs> <dir name="dev"> <log/> </dir> <rom name="ld.lib.so" label="ld.lib.so"/> <rom name="libc.lib.so" label="libc.lib.so"/> <rom name="vfs.lib.so" label="vfs.lib.so"/> <rom name="libm.lib.so" label="libm.lib.so"/> <rom name="stdcxx.lib.so" label="stdcxx.lib.so"/> <rom name="binary" label="test-go"/> <dir name="proc"> <dir name="self"> <rom name="exe" label="test-go"/> </dir> </dir> </vfs> <libc stdout="/dev/log" stderr="/dev/log" /> </config> </target> <preserve name="RAM" quantum="180M" /> <vfs> <dir name="dev"> <log/> <terminal/> </dir> </vfs> <libc stdout="/dev/log" stderr="/dev/log"> <mmap local_area_default_size="1610612736" /> </libc> </config> </start> </config> } # evaluated by the run tool proc binary_name_gdbserver_platform_lib_so { } { return "gdbserver_platform-$::env(KERNEL).lib.so" } build_boot_image { core init timer ld.lib.so libc.lib.so libm.lib.so posix.lib.so stdcxx.lib.so vfs.lib.so test-go pc_uart_drv gdb_monitor gdbserver_platform.lib.so } any ideas how to fix?

1 1

Troubleshooting interrupt delivery
by Tomasz Gajewski 15 Oct '21

15 Oct '21

Hi, after some time of inactivity I decided to get back to my work on porting Genode to different Raspberry Pi devices. As in the meantime major blocker (problem with usb host) seem to by resolved and much improvements in multiple aspects related to introducing new boards (platform driver, unified naming of depot packages, etc.) I'm optimistic about results. However I run into a problem that stopped me for quite some time now and I'm getting out of ideas. I started with an attempt to make run/ping work on Raspberry Pi 2. I thought that it will be a straightforward work as: * it already works on Raspberry Pi 1 * Raspberry Pi 2 is has the same usb and network device * interrupt controller is similar and I already have implementation for it working on some earlier Genode release With addition of some logs I've verified that on both variants (Pi 1 and Pi 2): * 'rpi_usb_host_drv' asked for a device from 'rpi_new_platform_drv' * 'Irq_session_component::sigh(...) was called for IRQ 9 (usb device interrupt) - I believe that it was due to rpc from 'rpi_usb_host_drv' * 'Irq::Context' constructor was called in 'rpi_usb_host_drv' and after that 'Irq_session_component::sigh()' and 'Irq_session_component::ack_irq()' were called for interrupt 9 * after some device driver initialization and discovery 'rpi_usb_host_drv' prints log 'dev_dbg: Calling enable_global_interrupts' and after that IRQ 9 is detected in `bcm2835_pic.cc` and 'Kernel::User_irq::occured()' for that interrupt is called. After that there is a difference. On a Raspberry Pi 1 'Lx_kit::Irq::Context::handle_irq()' in 'rpi_usb_host_drv' is executed but it doesn't on version 2. As I verified that interrupt is detected and processed AFAIU properly on base-hw level I don't see other device specific things that can cause this behavior. Is it possible that new platform driver somehow 'blocks' this interrupt delivery? I don't see how would that be as calls to 'sigh()' and 'ack_irq()' worked. Can someone share some ideas what can be wrong or how should I try to debug such problem? Maybe that is something obvious and only I can't find it. Currently my branch is based on master from the middel of August and if that can help I can publish it after some minor cleanup. Tomasz Gajewski

2 4

Announcement: Sculpt OS 21.10 released
by Norman Feske 15 Oct '21

15 Oct '21

Hello everyone, today we have released the version 21.10 of the Sculpt operating system, which incorporates many of Genode's recent developments. https://genode.org/news/sculpt-os-release-21.10 To highlight the most prominent additions: - GPU-accelerated graphics for Intel GPUs of generations 8 and newer - Media playback in the Chromium-based web browser - USB webcam support - VirtualBox 6 in addition to VirtualBox 5 - Encrypted file store based on our custom CBE block encrypter It goes without saying that the new release is accompanied with an updated manual: https://genode.org/documentation/articles/sculpt-21-10 https://genode.org/documentation/sculpt-21-10.pdf A ready-to-use disk image is provided at the Sculpt download page: https://genode.org/download/sculpt We plan to cover individual features by dedicated articles at the https://genodians.org website. Updating from Sculpt 21.03 -------------------------- Users of Sculpt 21.03 will feel just at home with the new version. When updating to the new version, please nevertheless pay attention to the following changes. - Should you use a manually managed NIC-router configuration, note that the attribute 'dns_server_from' has been renamed to 'dns_config_from'. - For using VirtualBox 6 instead of VirtualBox 5, note that the machine configuration file is not 100% compatible. For this reason, version 6 requests a file named 'machine.vbox6'. So you can maintain the machine configurations for both versions side by side. A working template for a 'machine.vbox6' file comes installed along with the vbox6 package. You can find it at depot/genodelabs/raw/vbox6/2021-10-05/machine.vbox6 Note that version 6 is not time-tested yet. Please use it with caution. - The RTC driver is no longer part of the base system but is now provided as an optional component called "system clock-pc". It is available in the tools menu of the genodelabs depot. - The recall_fs launcher has been replaced by the recall_fs package, which eases the use of multiple instances of the component, e.g., one in front of the file vault and one behind the file vault. - Depot index files are now annotated with the CPU architectures supported by the author. Should you provide an index file, please see https://github.com/genodelabs/genode/issues/4295 for more information. Have fun with the new version of Sculpt OS! Norman -- Dr.-Ing. Norman Feske Genode Labs https://www.genode-labs.com · https://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 1

CBE crypt interface
by Stefan Thöni 15 Oct '21

15 Oct '21

Hello Genodians We are implementing hardware accelerated encryption for the CBE and have a question pertaining to this: How should the Cbe_crypto::Interface be implemented when the underlying hardware is asynchronous, e.g. driven by interrupts? I think I understand the semantics of submit_encryption_request and encryption_request_complete but this mechanism doesn't seem to help with asynchronous completion. As far as I can tell, no signals are used with the Cbe_crypto::Interface. What am I missing? Best regards Stefan -- Freundliche Grüsse Stefan Thöni Chairman of the Board Senior Security Architect +41 79 610 64 95 gapfruit AG Baarerstrasse 135 6300 Zug https://gapfruit.com

4 8

running CBE on RAM vfs
by Stefan Thöni 08 Oct '21

08 Oct '21

Hello Genodians As a precursor of running CBE on our i.MX8 IoT device, I'm trying to run CBE entirely from RAM based in a vfs and testing it using the block_tester. To achieve this I merged the vfs_cbe_init and vfs_cbe runscript using a sequence to run cbe_init before vfs_cbe. My problem is that the cbe/current/data device seems to be only 4 KiB or 1 block in size, regardless of how I parameterize cbe_init. Any ideas on why this happens or how to fix it? For reference, my runscript repos/gems/run/vfs_cbe_ram.run is available on the following branch: https://github.com/throwException/genode/tree/cbe_ram Best regards Stefan

2 1

Libc Socket in Thread
by Kevin Burton 04 Oct '21

04 Oct '21

Hello, I am new to Genode and currently writing a program in which two components communicate with each other over virtual ethernet. The communication using a NIC router works completely fine if started from the main component, but fails whenever initiated from a thread. Hereby Error: pthread_self() called from alien thread named 'Broker Thread' no RM attachment (READ pf_addr=0x4b8 pf_ip=0x10f62dfc from pager_object: pd='init -> manager' thread='Broker Thread') is thrown when the 'connect' function is called. I have tried resolving this by simply allocating some RAM and also by initializing a sliced heap, both to no avail. Unfortunately it is imperative for the component to initialize a connection from within a thread. Therefore I would be very grateful for any help regarding this issue. I have attached the thread's code to this mail. Kind regards, Kevin Burton

2 1

Re: users Digest, Vol 41, Issue 17
by Sid Agrawal 30 Sep '21

30 Sep '21

Hi Norman, 1. Use plain text, not HTML. > > 2. When replying, quote sensibly selected parts of the original posting. > Avoid quoting the original posting in full. Keep in mind that top > postings are generally frowned upon. > > Sorry about this. Will follow the guidelines going forward. Best, Sid

1 1

Re: users Digest, Vol 41, Issue 8
by Sid Agrawal 30 Sep '21

30 Sep '21

Hi Uwe, Some comment inline about clone() in Linux. On Wed, Sep 22, 2021 at 11:39 PM <users-request(a)lists.genode.org> wrote: > [CAUTION: Non-UBC Email] > > Send users mailing list submissions to > users(a)lists.genode.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.genode.org/listinfo/users > or, via email, send a message with subject or body 'help' to > users-request(a)lists.genode.org > > You can reach the person managing the list at > users-owner(a)lists.genode.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of users digest..." > > > Today's Topics: > > 1. Getting Started with Genode (Sid Agrawal) > 2. Aw: Getting Started with Genode (Uwe) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 22 Sep 2021 16:04:28 -0700 > From: Sid Agrawal <siagraw(a)cs.ubc.ca> > To: users(a)lists.genode.org > Subject: Getting Started with Genode > Message-ID: > <CA+F2VKa1+d-217PQ+BwjYb= > ssj+eTatXjL2nt8E-LR-7tkMuTQ(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi Genodians, > I am a graduate student at the University of British Columbia with > their Systopia > Lab <http://systopia.cs.ubc.ca/>. My research area is operating systems, > and I would like to use Genode(with seL4) as the OS platform for > demonstrating my research ideas. As with starting with a new platform I > have run into some hurdles. At the end I have given a summary of my > research project, which is still in a nascent stage. > > > - *Running the hello_tutorial*: the hello_tutorial job on qemu does not > finish to completing and times out. Below are my steps on ubuntu > 20.04.1. I > am using the Genode development container > <https://genodians.org/skalk/2020-09-29-docker-devel>, so the tools > should not an issue. I also tried it outside the container. > > git clone git://github.com/genodelabs/genode.git > cd genode > tool/ports/prepare_port sel4 > tool/ports/prepare_port grub2 > tool/create_builddir x86_64 > > cd x86_64/build/ > # Change build/x86_64/etc/build.conf. > # Change kernel to sel4 and add hello_tutorial > diff etc/build.conf.old etc/build.conf > > 20c20 > > < #KERNEL ?= nova > > --- > > > KERNEL ?= sel4 > > 85a86 > > > REPOSITORIES += $(GENODE_DIR)/repos/hello_tutorial > > make > make hello > make run/hello # This times out as shown below. > > [init -> hello_server] creating root component [0m [0m > [init -> hello_client] upgrading quota donation for PD session (0 > bytes, 4 caps) > [0m [0m > [init] child "hello_server" requests resources: cap_quota=3 [0m [0m > [init] child "hello_client" requests resources: ram_quota=0, cap_quota=4 > [0m [0m > Error: Test execution timed out > > > > Any comments on what I am doing wrong would be very helpful. Secondly, what > would be the best way to go about debugging an issue like this. > > > - Summary of my research project > <https://sid-agrawal.ca/index.html#research-projects> on building > "General > Purpose Isolation Mechanisms". > > After sixty years of operating system evolution, we continue to find new > and different isolation mechanisms: threads, processes, containers, virtual > machines, lightweight contexts. Even applications provide isolation > mechanisms: a JVM is a user-level process that provides isolation units > whose API is Java bytecodes; some browsers offer units of isolation between > each browser tab. > > We ask whether we really need to have N different isolation mechanisms or, > instead, we could develop a framework in which all these different > mechanisms represent points on a continuum. If we could do that, then > perhaps A) we could implement such a unified framework, and B) the > framework might allow us to discover new and useful isolation mechanisms > (that could be created seamlessly rather than requiring an entirely new > implementation). > > The project has three main goals: > > > - Develop a theoretical model or framework to unify existing isolation > mechanisms. > - Identify novel points in the model that are useful. > - Implement the model in seL4. > > The Fig below shows how different access and isolation levels of memory can > be used to construct different types of PD. The points along the Y-axis are > building blocks of memory isolation. The points on the X-axis are different > types of PD. A given PD can be constructed using different building > blocks, which > are represented as circles that intersect one or more blocks. Mapping these > concepts to Genode, > > This is an evolving model, as we are still investigating: > > > - If the "Security and Performance Guarantees" across any two types of > PD can be compared. > - Should there be more building blocks on the Y-axis > - What novel types of PD can we come up by combining the different > building blocks > > [image: image] > > > I am excited about building my project with Genode, the composability in > its architecture make it well suited as platform to show unconventional OS > ideas. > > Best, > Sid > sid-agrawal.ca >

3 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users