users

users@lists.genode.org

1 participants
2310 discussions

difference in genode memory allocation for NOVA and seL4
by Alexander Tormasov 19 Aug '20

19 Aug '20

Hello! I am trying to implement allocate_at() Libc:: function, which allocate memory region in given (desired) address. To implement I need to extend dataspace (as I understand, this is physical memory) at appropriate address, and later attach it to the local allocator. I found that memory allocation code from base/include/region_map/region_map.h /** * Shortcut for attaching a dataspace at a predefined local address */ Local_addr attach_at(Dataspace_capability ds, addr_t local_addr, size_t size = 0, off_t offset = 0) { return attach(ds, size, offset, true, local_addr); } does work for NOVA, but do not work for seL4 kernel for x86_64. This happens when I try to allocate 64k from pre-defined addresses like (try in order) 0xc000000000, 0x1c000000000, 0x2c000000000/etc… I create function int Libc::Mem_alloc_impl::Dataspace_pool::expand_at(size_t size, void * ptr, Range_allocator *alloc) and inside it, in my call to try { new_ds_cap = _ram->alloc(size); local_addr = _region_map->attach_at(new_ds_cap, addr_t(ptr), size); } in seL4 it catch exception catch (Region_map::Region_conflict) { while same calls in NOVA works ok. Problem happens in second call to attach_at(), new_ds_cap is ok. Are there significant difference in the memory allocation process (for particular addresses ranges) between NOVA and seL4? Thanks! Alexander

2 1

Re: Network issue
by Dima Sokolov 15 Aug '20

15 Aug '20

1 0

Genode's 12th anniversary
by Norman Feske 14 Aug '20

14 Aug '20

Dear Genode community, time flies by. We are now in the 12th year of Genode, following the very same vision we had when we founded the project. But in contrast to the early days, today Genode has long outgrown the status of an obscure research project and has gained a strong product focus. During the past year, this focus led us to embrace 64-bit ARM and NXP i.MX in particular, profound consolidation and optimization of the framework, the novel user interface of Sculpt OS, and the streamlining of work flows. Proud of these advances, we want to celebrate the Genode anniversary together with the community and friends around Genode by holding our traditional informal barbecue at the banks of the river Elbe: Eisenberger Straße, Dresden/Germany September 4, 2020 Google Maps: https://goo.gl/maps/C0luj If you are planning to attend, please let us know by writing a short note to: info(a)genode-labs.com 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

Re: Is Genode good for the Desktop?
by ttcoder＠netcourrier.com 11 Aug '20

11 Aug '20

Is Genode good for the Desktop and is it based on seL4? What does OS framework mean? Hi, Assuming you're looking for a personal take, rather than the official info available from genode.org (:-) : In my personal view, what makes Genode the "go-to" OS toolkit (or OS "framework" : a collection of modules that can work together or separately) is several things, but especially its modularity. A couple years back I used to be a happy camper as a user of a Be, Inc-derived OS, thinking if was "most" modular, "this is the place to be", rationalizing whatever problem I ran into as 'unavoidable with modern computing' and so on... Then I found out about Genode. It gives a new meaning to "lego like", assembling pieces together. In comparison, it makes my daily OS use look like child's play, a monolithic black box of crude, un-reusable, hard to maintain code. (talking of the internals, compared to the Genode internals, the APIs are another can of worms). The breakthrough for me was reading the PDF (Genode foundations.pdf). It takes some effort to comprehend it, it's not light reading... But if you really get "into" it, wow. As you read through it you'll keep thinking "why does so-and-so operating system not use the same mechanism as Genode-based OSes do ?". I believe seL4 is one of the micro-kernels that may be used by Genode, that info should be available on genode.org As to Desktop usage, if you ask around you'll probably get opinions over the whole spectrum, with many on the 'hopeful' scale, similar to that of the Genode Labs team : they reported a good while back that Sculpt-OS (their desktop OS based on Genode) has become their "daily driver" OS, which is a good milestone to have achieved. However, they still rely on VirtualBox for some things yet, so there are more milestones to reach. Some I remember being mentionned include self-hosting, i.e. ability for Sculpt OS to compile/build itself, having a native email client rather than relying on one embedded in VirtualBox, etc. Make yourself comfy and stay around a while, you'll see the people here are a quiet bunch, mainly reporting on their code once they have a deliverable. Cedric

1 0

Has Bhyve been ported to Genode?
by Lonnie Cumberland 11 Aug '20

11 Aug '20

Hello, I have been working with VMM's for a while now and it lately my understanding is that Bhyve is much better than VirtualBox. I was wondering if Bhyve has been ported to Genode yet as I would like to see it run with Bhyve+Sculpt+NOVA if that were possible? There is also a minimal port to OS-X called Xhyve ( https://github.com/machyve/xhyve) which is completely self-contained except for just a few calls to the hypervisor from what I read and might be easier to port than the base Bhyve. Cheers, Lonnie

2 2

Genode modified Bender sources?
by Lonnie Cumberland 11 Aug '20

11 Aug '20

Hello All, I am attempting to learn more about Bender (https://github.com/blitz/bender) and the way that it relocates modules so that I can get the NOVA x86_64 bit hypervisor using Bender to relocate the modules. I have been able to read a bit of the code from the bender github repo but in researching in the Genode repositories, I have come across some information that suggests Genode has a modified set of Bender sources: https://github.com/genodelabs/genode/tree/4450b37ff5b22e99133863a6f56d5b715… But, I could not locate the actual modified genode bender source code so that I can look things over. Can you please tell me where I can find these modified sources? Cheers, Lonnie

2 2

How to start my VM with the new Sculpt-CE preview (Problems)
by Lonnie Cumberland 11 Aug '20

11 Aug '20

Greetings All, I was trying to use these steps to get VBox started on Sculpt 20.02 https://genodians.org/m-stein/2019-03-07-vm-with-sculpt-ce-preview But Sculpt seems to error out and the Virtualbox console never starts. Is anyone able to get this to work? I also tried it using the Sculpt OVA imported into a Virtualbox on Ubuntu 20.04 and still the same results. Cheers, Lonnie

2 1

Libc Component Not Logging
by Daly, Connor G. 08 Aug '20

08 Aug '20

Hi all, Genode beginner here. Been working with the platform for a few weeks trying to port a standard Linux application I wrote to Genode. My program uses sockets, both for sending and receiving, and judging from the code in tcp_terminal, the only way to do sockets is with libc rather than native Genode. I've been trying to implement the first few phases of my program in Genode, but when I run them, no log messages seem to appear and I can't really tell if my program is doing anything. When I remove the libc relevant pieces of code and run my program through a base/Component, everything logs just fine. I created a small test program to find my mistake, so this piece of code does not log anything to qemu with a Linux target platform: #include <libc/component.h> #include <base/log.h> void Libc::Component::construct(Libc::Env &) { Genode::log("Hello world"); } For a run script, I'm using: build { core init widget } create_boot_directory install_config { <config verbose="yes"> <parent-provides> <service name="LOG"/> <service name="PD"/> <service name="CPU"/> <service name="ROM"/> <service name="IO_MEM"/> <service name="IO_PORT"/> <service name="RAM"/> </parent-provides> <default-route> <any-service> <parent/> <any-child/> </any-service> </default-route> <default caps="50"/> <start name="widget"> <resource name="RAM" quantum="1M"/> </start> </config>} build_boot_image { core ld.lib.so init widget libc.lib.so vfs.lib.so libm.lib.so } append qemu_args " -nographic " run_genode_until "Hello world" 10 Any help would be greatly appreciated. Thanks! -Connor

2 1

initial port of golang to genode
by Alexander Tormasov 04 Aug '20

04 Aug '20

I make some very rough port of golang runtime to genode (mostly for nova), https://github.com/tor-m6/genode.git This work is a side result of one of research project made in Innopolis University. It allow compilation and execution of simple go applications/packages (probably without unsupported os features). I use only gccgo version of golang compiler. Things like "go build" in cross mode not supported yet (while we make some techology to produce makefiles from "go build" to compilei go code, not attached yet). Other limitations see below. It build a set of libraries, in form of "libport" and "noux-pkg" each (because we need to run configure which is not supported in libport), as static ones. Also it build a set of standard golang packages (namely fmt, os, syscall, runtime/etc) as files for gccgo compilation. Note: Go runtinme support around 9 systems as backend. I use netbsd as simplest one for the base for new system - "inno". To implement context switching I have to develop it from the scratch; for stack port use alloc_secondary_stack() from Genode. I suspect that I need to use a low-level context switching from kernel (native thread switch), this is not implemented yet. Configuration after build ========================= Golang package (like fmt) is an object file (e.g. fmt.o) which appears in build/x86_64/noux-pkg/libgo/ directory and subdirectories. This path should be included during golang/gccgo compilation (not only linking). Built libraries for Go will be in ${LIB_CACHE_DIR}/libgo/libgobegin.a ${LIB_CACHE_DIR}/libgo/libgolibbegin.a ${LIB_CACHE_DIR}/libgo/libgo.a Current limitations =================== - RAM quota in .run file should be >= 1300M: genode do not support MAP_ANON flag, so, we cant reserve memory (544Gb) for arena, and, therefore, go to Windows-like model with "small" immediate allocation; it force 2GB limitation in code and make direct allocation of ~1.1Gb - can run in VM with 1 CPU only: in general it support checking of CPU number (by backporting patch from current genode code) and trying to run everything, but it hangs somewhere in the middle due to recursive locking (error "deadlock ahead" in acquire() in mutex.cc) May be this is small mistake - don't have time to find and fix (in this place due to slot_jump() gdb do not give normal info related to stack). I found that problem during stack unwind in ... runtime.startm -> runtime.newm -> runtime.newm -> runtime.mcommoninit -> runtime.callers -> runtime_callers() -> backtrace_full() ... here it try to call -> strlcpy() -> _jmp_slot() and make again guard inside this function - it works only on x86_64, tested on nova kernel genode do not support makecontex/setcontext/gencontext family; but it is crucial to support go because of goroutine model; I have to implement it by myself. It is machine-dependent; moreover, context swiching do not work after direct port from libc/etc - I have to make 1 step stack unwind procedure to jump using stack frame to the next function. So, I add everywhere compilation option -fno-omit-frame-pointer to be sure that this approach works. Probably it need only for implementation of the file mycontext.cc - it can work on seL4 as well, while I did not submit additional dirty changes for go runtime (I swithed to nova/gdb) - any go application need to add 3 files into it (may be it worth to place them in another library or libgo.a) - dummy.cc with Genode initialization and some empty functions which are not supported on genode, mycontext.cc and myacontext.s with implementation of x86 [sg]etcontext - during port I make a set of dirty fixes for absent on the platform (genode/nova), in particular "empty" C implementaion of sendfile(), getpgid(), lchown(), mount(), settimeofday(), mlock(), munlock(), mlockall(), munlockall(), sigaltstack(); in go part of runtime port I also "damage" some functions, in particualr route.sysctl(), broke poll.ReadDirent(), partially broke logic in runtime.sysMap/sysReserve because of unsupported mem range reservation, do not use ptrace, broke routing in netbsd version of syscall.toRoutingMessage and some others, see patches for libgo in repos/libports/src/lib/libgo/. so, anything in Golang which use them will fail. Potentially new genode releases will contain something which can replace or fix these and other patched functions - once I compile all code with -O3 option, and it hangs. I did not check why... Questions? tor(a)innopolis.ru, origin in https://github.com/tor-m6/genode.git

1 1

sel4 build broken in 20.05?
by Alexander Tormasov 04 Aug '20

04 Aug '20

I am trying to compile sel4 demo for x86, and hit an error: during compilation of [CC] kernel_final.s in the process which give /usr/local/genode/tool/current/bin/genode-x86-gcc -S -o kernel_final.s kernel_final.c it generates asm error error: impossible constraint in ‘asm’! Any suggestions? Log below [CC] kernel_final.s In file included from /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/assert.h:15, from /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/arch/x86/arch/types.h:15, from /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/basic_types.h:15, from /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/types.h:14, from /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/src/api/faults.c:14: /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/util.h:89:7: warning: conflicting types for built-in function ‘memset’ [-Wbuiltin-declaration-mismatch] void *memset(void *s, unsigned long c, unsigned long n) VISIBLE; ^~~~~~ /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/util.h:91:31: warning: conflicting types for built-in function ‘strncmp’ [-Wbuiltin-declaration-mismatch] int PURE strncmp(const char *s1, const char *s2, int n); ^~~~~~~ In file included from /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/api/types.h:23, from /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/compound_types.h:15, from /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/types.h:15, from /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/src/api/faults.c:14: /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/machine/io.h:35:6: warning: conflicting types for built-in function ‘putchar’ [-Wbuiltin-declaration-mismatch] void putchar(char c); ^~~~~~~ /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/machine/io.h:38:8: warning: conflicting types for built-in function ‘puts’ [-Wbuiltin-declaration-mismatch] word_t puts(const char *s) VISIBLE; ^~~~ /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/src/machine/io.c:154:1: warning: conflicting types for built-in function ‘isdigit’ [-Wbuiltin-declaration-mismatch] isdigit(char c) ^~~~~~~ In file included from /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/arch/x86/arch/kernel/x2apic.h:17, from /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/arch/x86/arch/kernel/apic.h:18, from /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/plat/pc99/plat/machine/interrupt.h:20, from /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/plat/pc99/plat/machine/hardware.h:14, from /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/machine.h:18, from /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/api/syscall.h:15, from /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/src/api/faults.c:16: /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/arch/x86/arch/machine.h: In function ‘x86_flush_rsb’: /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/arch/x86/arch/machine.h:348:5: warning: asm operand 1 probably doesn’t match constraints asm volatile( ^~~~~~~ /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/include/arch/x86/arch/machine.h:348:5: error: impossible constraint in ‘asm’ /home/tor/gen/20.05-tor/contrib/sel4-7935487f91a31c0cd8aaf09278f6312af56bb935/src/kernel/sel4/Makefile:653: recipe for target 'kernel_final.s' failed make[4]: *** [kernel_final.s] Error 1

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users