users June 2020

users@lists.genode.org

6 participants
4 discussions

Re: Genode 20.05 : how to build kernel nova with debugging symbol ?
by Alexander Boettcher 19 Jun '20

19 Jun '20

On 19.06.20 13:11, Parfait Tok wrote: > Hi Alex, > > > Le ven. 19 juin 2020 à 10:55, Alexander Boettcher < > alexander.boettcher(a)genode-labs.com> a écrit : > >> >> look into build/x86_64/debug directory. There you find the hypervisor >> binary with debugging symbols. >> >> That used to be the case until now. > I've just made a fresh install from the git and there is nowhere I can find > the *kernel* debugging symbols, > although other binaries debugging symbols are right there in the > build/x86_64/debug directory. > This is the list of commands I issued. > git clone https://github.com/genodelabs/genode.git genode20.05 > cd genode20.05/ > ./tool/create_builddir x86_64 > xxx/genode20.05/prepare_port dde_linux nova x86emu dde_ipxe dde_zircon libc > seoul x86emu nova grub2 -j8 > xxx/genode20.05/tool/depot/create > genodelabs/pkg/x86_64/drivers_interactive-pc > genodelabs/bin/x86_64/base-nova genodelabs/bin/x86_64/demo > genodelabs/bin/x86_64/global_keys_handler genodelabs/bin/x86_64/init > genodelabs/bin/x86_64/nit_focus genodelabs/bin/x86_64/nitpicker > genodelabs/bin/x86_64/report_rom genodelabs/bin/x86_64/rom_filter > CROSS_DEV_PREFIX=/usr/local/genode/tool/19.05/bin/genode-x86- > cd build/x86_64/ > make run/demo KERNEL=nova > After build completed, > find -name *hypervisor* > ./var/run/demo/boot/hypervisor > What did I miss? If you invoke a script, using depot packages, you indeed get no binaries with symbols. The packages by default contain only stripped binaries. In this case you have to build the binary once, since you want to debug it, e.g. in your case: make -C build/x86_64 KERNEL=nova kernel to find in build/x86_64/debug the binaries with debugging symbols. Cheers, Alex. -- Alexander Boettcher Genode Labs https://www.genode-labs.com - https://www.genode.org Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

Genode 20.05 : how to build kernel nova with debugging symbol ?
by Parfait Tok 18 Jun '20

18 Jun '20

Hello, With the latest version, I don't know where to find the kernel binary (Nova) with its debugging symbols. Is there any option to pass to the building script in order to get this? Or how to modify the script to generate the kernel debugging symbols? I used to comment the line > exec [cross_dev_prefix]strip [run_dir]/boot/hypervisor > in file > tool/run/boot_dir/nova > but with the 20.05 version, it does not help. Thanks

1 0

Memory bandwidth degradation of Armv8 virtualization
by Chris Hofer 09 Jun '20

09 Jun '20

Hi everyone, I'm currently measuring the memory bandwidth of the Genode Armv8 Linux Virtualization by running tinymembench[1] and lmbench's memory bandwidth[2]. On the NXP I.mx8 the results of both benchmarks showed a degradation of roughly 25 to 35 percent (depending on the exact benchmark) compared to native Linux. I tried to ensure comparability with the native setup by disabling in native Linux all but one core and fixing this core's frequency to 1 GHz (which should be the frequency Genode uses). Both setups use the same Kernel version. To improve the performance I played with the register values controlling caching (clear HCR_EL2.CD - enable S2 Data cacheability; VTCR_EL2.Irgn0 and VTCR_EL2.Orgn0 respectively set to b11 - set Normal memory, Inner/Outer Write-Back Read-allocate No Write-Allocate Cachable). However, this had no significant effect. What's your opinion on that? Based on your experience with virtualization, do these values surprise you or is this an expected degradation? All the best, Chris [1] https://github.com/ssvb/tinymembench [2] http://lmbench.sourceforge.net/

2 1

Synchronous RPC and Session Types
by Sid Hussmann 03 Jun '20

03 Jun '20

Hi Genodians, in our current project, the question of synchronous communications between processes comes up quite often. For background, our scenario processes numerous parallel requests, which requires, among other operations, verifying a signature of a request and signing its response. The signature verification and signing operations are encapsulated in separate processes. That way they do not need to understand the complex message format of requests and responses, but only binary hashes and signatures. Therefore, the component processing the request must send the input data to the verify or sign component and wait for the response before continuing processing. In our current solution we use Genode's basic synchronous RPC mechanism. This approach has the effect of creating new session types when more different functionalities such as verifying or signing are added. This seems to be in conflict with the Genode philosophy of using only few selected session types. On the other hand, building the scenario using the asynchronous report/rom mechanism would lead to significantly more complex code to avoid mixing up the many requests being processed in parallel. Is there any better way to accomplish this? Cheers, Sid -- Sid Hussmann CTO & Founder gapfruit AG Baarerstrasse 135 6300 Zug - Switzerland sid.hussmann(a)gapfruit.com

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users June 2020