users September 2020

users@lists.genode.org

6 participants
6 discussions

Start a nNew thread

Network issue
by Dima Sokolov 01 Feb '21

01 Feb '21

3 3

mmap implementation for ANON mapping with desired address
by Alexander Tormasov 21 Dec '20

21 Dec '20

I am trying to implement not-yet supported (as mentioned by nfeske@ in mailing list) option for mmap() related to anonymous mapping with pre-defined (desired) address. Like libc function with desired address out_addr. void *Libc::Mem_alloc_impl::alloc_at(void *out_addr, size_t size) I use a couple of useful function in avl allocator. Anyway, I found that straight - forward implementation do not work because of allocation gaps filled together with main allocation. In particular, if we want to allocate e.g. 0x10000 from address 0x500000 then we typically allocate 0x13000 bytes, including ones for avl metadata/etc stored in the same space, and receive virtual address range used, e.g. 0x500000 - 0x513000: /* * Calculate block size of needed backing store. The block must hold the * requested 'size' with the requested alignment, a new Dataspace structure * and space for AVL-node slab blocks if the allocation above failed. * Finally, we align the size to a 4K page. */ size_t request_size = size + max((1 << align_log2), 1024) + Allocator_avl::slab_block_size() + sizeof(Dataspace); Software I used (golang runtime) sometimes try to expand previous allocation, e.g. it can request allocation of 0x8000 bytes before previous range, like 0x4f8000 - 0x500000. In that case I can’t perform the operation - because it will try to allocate 0xa000 bytes from desired address 0x4f8000 - and it obviously fail due to Range_conflict. So, I split allocation to 2 parts - one for this gap by standard alloc() and random placement and second one by my own alloc_at() with size exactly correspond to the requested one. Implementation available as a patch to 20.05 at https://github.com/tor-m6/genode/commit/78fc751bea8acc2b515e04bec9f3a883461… Problem I see here is a free operation: it just free the block with requested address, and do not touch others, gap-related blocks. For me it is not obvious that they need to be free, because in the code (e.g. by unmap()) I do not see explicit free of other allocated structures, in particular, dataspace extension or related block metadata. Question: should I make additional efforts to trace and delete something else - except what standard free does here: /* forward request to our local allocator */ _alloc.free(addr); Like for dataspace structure or address ranges for second «auxiliary» allocation? PS Another potential problem is a probability to overlap of first «random address» allocation with desired address. This happens with first attempt to implement allocator - it allocates address from desired range, and immediately put here 0x18 bytes of Dataspace structure, and then fail because requested address is already busy by this structure! Anyway, I consider such a probability relatively small with proposed approach and ignore it (may be I am wrong)

4 23

The Falkon browser / Chromium engine running natively on Genode is absolutely beautiful
by baconicsynergy＠protonmail.ch 29 Sep '20

29 Sep '20

I can't access my Gmail or Protonmail yet (it says the engine isn't up to date), but I don't care - this is a huge step forward for Genode's web capabilities! I can't tell you how excited this makes me. Considering that Firefox usage is much lower lately (unfortunately :/) investing in a Chromium based web browser is wise. It's also going to be very nice not needing to spin up a virtual machine to use a feature-filled web browser Looking forward to future updates!

1 0

Announcement: Sculpt OS 20.08 released
by Norman Feske 17 Sep '20

17 Sep '20

Hello everyone, I'm pleased to announce the release of Sculpt OS 20.08, along with a ready-to-use system image and OVA appliance: https://genode.org/download/sculpt Please refer to the updated documentation when using this version: https://genode.org/documentation/articles/sculpt-20-08 https://genode.org/documentation/sculpt-20-08.pdf (PDF) You can find a short summary of the changes in the following article: https://genodians.org/nfeske/2020-09-17-sculpt-os Have fun sculpting! 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

fs_rom "follows" files
by Roman Iten 10 Sep '20

10 Sep '20

Hello Genodians I use `run/bash` and added a simple component that logs the content of a ROM module: ```xml <start name="test-update"> <resource name="RAM" quantum="2M"/> <route> <service name="ROM" label="test.config"> <child name="vfs_rom" label="tmp/test.config"/> </service> <any-service> <parent/> <any-child/> </any-service> </route> </start> ``` Then, I execute the following commands on the interactive shell: ```bash > echo "1st-cfg" > /tmp/test.config` # "1st-cfg" is logged > mv /tmp/test.config /tmp/test.backup` # nothing is logged > echo "2nd-cfg" > /tmp/test.config` # nothing is logged > echo "3rd-cfg" > /tmp/test.backup` # "3rd-cfg" is logged ``` Is it the intended behavior that `fs_rom` "follows" the file or should it always provide the ROM content of the file with the specified name instead? The background of this question is that in fact, `test-update` for example could be a component that consumes the `test.config` and is supposed to react on configuration updates. Cheers, Roman

2 2

Attached_mmio with platform_drv
by Pirmin Duss 03 Sep '20

03 Sep '20

Hello Genodians I'm currenty working on a I2C driver for the iMX8 processor. I actually started this before the 20.08 release. But when I read that the new platform driver for the iMX8 SoC can automatically enable/disable clocks for subsystems, I decided to use this new feature, as I had problems enabling the clocks before. If my assumptions are correct (by reading the code of the usb_host_drv), one is able to get a capability to the IOMEM that the platform driver has mapped via `acquire_device().io_mem_dataspace()`. What is currently not clear to me, is how to map the `Attached_mmio` of the driver use the mapped IOMEM, to be able to use the register definitions? Or does a driver that uses the `platform_drv` component require an other way to access the registers? My current work in progress code (with lots debug stuff in it) can be found at [1]. Best regards, Pirmin [1] https://github.com/trimpim/genode/tree/i2c_dirver_imx8q_evk_20.08

3 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users September 2020