users

users@lists.genode.org

3 participants
2319 discussions

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

DMA memory data race?
by Stefan Thöni 27 Sep '21

27 Sep '21

Hello Genodians While implementing our driver for the i.MX8 CAAM device, I experience some problems with DMA using the following steps: a) Allocate DMA memory using alloc_dma_buffer from the platform session. b) Fill the DMA memory with some data. c) Tell the hardware to work with the data by register write. d) Look at the result code provided by the hardware. I observe an error result code from the hardware indicating the DMA read failed or returned the wrong data, unless I insert some time-consuming code (like a call to Genode::log or just a burning cycles) between b) and c). I think the problem could be a data race between the CPU filling the RAM and the device reading it by DMA. On the other hand, I provide the UNCACHED argument to alloc_dma_buffer which should, if my understanding is correct, be reflected in the page table disabling the cache thus avoiding this problem. What am I missing? Kind regards Stefan

3 2

Re: Getting Started with Genode
by Sid Agrawal 24 Sep '21

24 Sep '21

On Thu, Sep 23, 2021 at 3:00 AM <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. Re: Getting Started with Genode (Christian Helmuth) > 2. Re: CBE crypt interface (Norman Feske) > 3. Re: CBE crypt interface (Stefan Thöni) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 23 Sep 2021 10:02:00 +0200 > From: Christian Helmuth <christian.helmuth(a)genode-labs.com> > To: users(a)lists.genode.org > Subject: Re: Getting Started with Genode > Message-ID: <20210923080200.GB2343(a)genode-labs.com> > Content-Type: text/plain; charset=utf-8 > > Hello Sid, welcome to the list! > > On Thu, Sep 23, 2021 at 01:04:28 CEST, Sid Agrawal wrote: > > - *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. > > I suppose you succeded in running the scenario on Linux and NOVA like > follows. > > make run/hello KERNEL=linux BOARD=linux > make run/hello KERNEL=nova > > For seL4 I can reproduce what you pasted above, so the issue is > related to the used platform. As the log output states "hello_server" > is requesting more resources and requires cap_quota (capability quota) > increased during an operation that requires 3 caps. A look into the > init configuration (see hello.run) reveals the following. > >  > <default caps="50"/> > > Now you may grant the component some more caps to make it run > successully by changing > > <start name="hello_server" caps="54"> > > to the hello_server start node and running > > make run/hello KERNEL=sel4 > > This results in additional resource requests > > [init] child "hello_server" requests resources: ram_quota=0, cap_quota=4 > > The reason is that the seL4 platforms works quite different from NOVA > and expectedly Linux, which results in a higher capability consumption > of the used software stack. > > The following start nodes render the scenario working again. > > <start name="hello_server" caps="58"> > ... > <start name="hello_client" caps="51"> > > Thank you, Christian, for the resolution as well as the explanation. > Please see Chapters "Resource trading" [1] and "Resource assignment" > [2] in the Genode Foundations book for a thorough explanation. > > [1] > https://genode.org/documentation/genode-foundations/21.05/architecture/Reso… > [2] > https://genode.org/documentation/genode-foundations/21.05/system_configurat… > > Regards > -- > Christian Helmuth > Genode Labs > > https://www.genode-labs.com/ · https://genode.org/ > https://twitter.com/GenodeLabs · https://www.genodians.org/ > > Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden > Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth > > > > ------------------------------ > > Message: 2 > Date: Thu, 23 Sep 2021 10:19:03 +0200 > From: Norman Feske <norman.feske(a)genode-labs.com> > To: users(a)lists.genode.org > Subject: Re: CBE crypt interface > Message-ID: <7c847df2-79db-2075-9a77-8bf0cd94fde8(a)genode-labs.com> > Content-Type: text/plain; charset="utf-8" > > Hello Stefan, > > > We are implementing hardware accelerated encryption for the CBE and have > > a question pertaining to this: > > I wonder, is performance your primary motivation? If so, there might be > other opportunities for optimization that are worth implementing first, > before resorting to hardware acceleration. Should your primary > motivation be the hiding of the keys from software, that's really cool! > > > 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 > I cannot speak for the 'Cbe_crypto::Interface' specifically. But in > general, a VFS plugin with outstanding requests is polled for the > completion (request_complete) each time after I/O happened, i.e., after > an I/O signal occurred. > > You may take a look at how the implementation of the VFS terminal plugin > responds to incoming data for reading ('_read_avail_handler') [1]. The > 'read_avail_sigh' corresponds to your interrupt. > > [2] > > https://github.com/genodelabs/genode/blob/master/repos/os/src/lib/vfs/termi… > > To support batches of outstanding requests at the VFS (for hiding the > latency of the crypto device), one may consider maintaining multiple > file handles (at the client of the VFS plugin) where each file handle > can have one request in flight. So the degree of parallelism can be > tuned by the number of open file handles. Right now, I think that the > CBE does not schedule more than one crypto request at a time though. > > Cheers > 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 0

Porting cmake: undefined references to "pthread_barrier" functions
by Joel Valenciano 24 Sep '21

24 Sep '21

I was trying to build cmake, as I figured it would be useful for self-hosting, but in the link phase, it fails with an undefined reference to pthread_barrier_destroy(), along with a few other BSD incompatibilities. The "pthread_barrier" functions are used by libuv, not cmake directly, so I made port files for each, as well as a custom target.mk, but I'm not sure what to do about these BSD features. Specifically, here's what I've seen is missing: -pthread_barrier init(), wait(), and destroy() -some BSD sysctl() items related to resource usage info -a sysctl() to access the program's executable binary from itself Most of the calls are in "src/unix/freebsd.c" and "src/unix/kqueue.c". I wrote an implementation of the pthread_barrier functions that uses Genode::Blockade as a barrier, and I think the resource sysctl()'s can be implemented with Pd_session's ram quota functions, but I figured I should ask.

1 0

app/seoul: build fails with several "duplicate case value" errors
by Joel Valenciano 24 Sep '21

24 Sep '21

When trying to build seoul, I run into several "duplicate case value" errors in executor/instructions.inc. This error seems to occur with the upstream version as well, but I don't know what is causing it. Log contents are attached.

2 4

Getting Started with Genode
by Sid Agrawal 23 Sep '21

23 Sep '21

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 2

Update intel wifi_drv
by Pirmin Duss 13 Sep '21

13 Sep '21

Hello Genodians We have an ARM platform with a Intel AX200NGW WIFI module. This isn't supported by the current `wifi_drv`. Support for this module type was recently added to the Linux kernel. If no one has already started upgrading `wifi_drv` I would volunteer to update the driver to the new Linux-device-driver environment. I would at first create the version for x86_64 which can be tested more easily. If this works I would then create the version for ARM64. Best regards, Pirmin

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users