users

users@lists.genode.org

2320 discussions

Compiling Kernel Modules for Genode on iMX53 with TrustZone
by Mauricio Gutierrez Barnett 07 Nov '17

07 Nov '17

Hello, I have a question about adding kernel modules to the Genode OS. So I have built and boot the tz_vmm scenario for platform hw_imx53_qsb_tz on the i.MX53 development board using another thread on this mailing list as a guide. I was able to get it up and running on the board with no problems. However, I need to install a kernel module into the normal world linux. In order to do this I need to be able to cross compile the module for the target kernel running in normal world from my desktop. However, while I have access to the target compiler I do not have a target kernel directory. That is, only the final image of linux is provided, not the source code used to compile it. I know the version is provided as Linux version 2.6.35.3-01270-g9533414. However, if I try to use the 2.6.35.3-generic version as a target I get a symbol version error when I try to insmod: "disagrees about version of symbol kmalloc_caches Unknown symbol kmalloc_caches (err -22)" I believe this is because the kernel running in the normal world has been modified. I am wondering if there is another way for me to compile kernel modules for Genode. If not, would it be possible for you to release the source code of your modified kernel which you used to create the Linux Image that runs in the normal world? Thank you for your time, Mauricio Gutierrez

2 3

test
by Martin Stein 02 Nov '17

02 Nov '17

test

1 0

binary naming
by Johannes Kliemann 02 Nov '17

02 Nov '17

Hi, while booting Genode directly on Linux I encountered the problem that Linux requires to call `/init` in the initramfs. Unfortunately Genode requires to call `core` which loads `init` so renaming core to init isn't enough. I renamed init to init2 core to init and called it with "label=init2" which works at first (core finds all ROM sessions) but then segfaults with "init2[45]: segfault at 7f11c473b128 ip 00007f11c4645f40 sp 00007ffc1c8c15f8 error 4 in ld.lib.so[7f11c45c5000+95000]" and the warning "Warning: blocking canceled in entrypoint constructor". This warning was addressed on Linux before in [0] and fixed in ad2859b6b9dae96c48329eebc0a73527ba4deb9b. I have already included this patch. To boot Genode on Linux with this behaviour, checkout [1] and change "KERNEL_RUN_OPT(linux) := --include power_on/linux --include log/linux" to "KERNEL_RUN_OPT(linux) := $(QEMU_RUN_OPT)" in your etc/build.conf (with linux as kernel ofc). Beside renaming I also tried to make the ROM session chdir into a sub directory or to prepend this directory to the binary name. Neither of made Genode correctly find the binaries. I have to say that Linux is not booting into a real fs but is using a initramfs which consists of a cpio archive. What would be the way to go to either rename the binaries to a Linux compatible scheme or to change the library search to find its binaries in a cpio archive (both options should be changeable at build time to still use the current linux)? Regards, Johannes [0]: https://github.com/genodelabs/genode/issues/2521 [1]: https://github.com/jklmnn/genode/commit/ef4becffcfc4bfc4079ff411872023b0362…

4 8

Wifi_drv: wpa_supplicant functionality
by Boris Mulder 30 Oct '17

30 Oct '17

Hi, On linux, the wpa_supplicant.config has some options, including remembering multiple wifi networks and the selection of the 'best' one based on policy and signal strength. On genode, this file is generated by the genode code inside wifi_drv containing only one entry depending on the "selected_accesspoint" config node. So if I may ask, is it possible to write the file yourself and use all features of wpa_supplicant on genode, or has it been stripped of all (or parts of) the functionality and should I use selected_accesspoint instead? -- Met vriendelijke groet / kind regards, Boris Mulder Cyber Security Labs B.V. | Gooimeer 6-31 | 1411 DD Naarden | The Netherlands +31 35 631 3253 (office)

2 3

Sd_card Driver Sabrelite : Command Timed out
by George Joseph 28 Oct '17

28 Oct '17

I was trying genode 17.05 on sabrelite board. The sd_card bench application gave these errors. [init -> sd_card_bench] Error: command timed out [init -> sd_card_bench] Error: prefix command timed out [init -> sd_card_bench] Error: Sd_send_op_cond command failed [init -> sd_card_bench] Error: Uncaught exception of type 'Sd_card::Host_controller::Detection_failed' [init -> sd_card_bench] Warning: abort called - thread: ep [init] child "sd_card_bench" exited with exit value 1 But go_idle command is the successfully send. The card is working fine from the uboot mmc commands. I cant find any reason. I have checked the registers in the usdhc controller the register values seems fine. What can be the possible reasons?.

2 2

compile port into noux-pkg and native library
by Nobody III 27 Oct '17

27 Oct '17

I have successfully compiled liblzma as a native Genode library, and I've compiled xz-utils as a noux package, but given that the two are in the same source tree, how do I compile xz-utils for noux using the native liblzma library? I'm not seeing any configure options that would allow building xz-utils for a precompiled liblzma rather than building the two together. Is there a good way to do this? I recognize that what I'm trying to do isn't really necessary, but it still would be nice to get this to work. Aside from reducing compile time, if I understand correctly, this should allow for multithreading, as that's all handled in the liblzma library, rather than in the command-line xz utility itself. Am I correct here?

1 0

Qt5: Signals and QApplications inside Threads
by Boris Mulder 26 Oct '17

26 Oct '17

Dear Genode folks, I have built an application with Qt5. I want it to also be able to read ROM modules from a report_rom server and to be able to handle updates to that ROM using signals. When I run QApplication::exec() however, it does not return and the entrypoint cannot listen to signals, causing them to be ignored. So I created another QThread and run my QApplication in there. Now I get the following error: WARNING: QApplication was not created in the main() thread. And the application does not do anything and does not react to events. What can I do to be able to run both the qt event loop and the genode event loop? regards, Boris -- Met vriendelijke groet / kind regards, Boris Mulder Cyber Security Labs B.V. | Gooimeer 6-31 | 1411 DD Naarden | The Netherlands +31 35 631 3253 (office)

2 3

Base-hw kernel GIC issue with a Cortex--A7 processor.
by Bob Stewart 19 Oct '17

19 Oct '17

Hi, I'm bringing up the 17.08 base-hw kernel/core on an NXP IMX6ULL SoC, which uses a Cortex A7 single core processor, and am having issues creating the singleton instance of the GIC after kernel initialization. In short the attempt to create the singleton causing the processor to die! The PIC code is all existing ARM code, I supply the addresses of the GIC-400 interrupt distributor and its cpu interface from the NXP documentation. Using the u-boot command line I see that the GIC register addresses in memory agree with the documentation. The physical addresses are 0x00A01000 and 0x00A02000 which are translated to virtual addresses 0xF0001000 and 0xF002000. The core initialization code in ../base-hw/src/core/kernel/init.cc first creates a cpu pool object then creates a cpu object in the pool passing to it the address of the unmanaged singleton object for the PIC.The cpu initialization code would use this object to unmask an interrupt for a timer, if it ever got that far! It appears to die in the execution of the placement new operator in ../base/src/include/base/internal/unmanaged_singleton.h: template <typename T, typename... ARGS> static void call(char * const dst, ARGS &&... args) { new (dst) T(args...); } (Where T would be Kernel::Pic) The Pic constructor is never called when the new executes. I was testing using the log run script which does not need a timer to execute the test, so I removed the creation of the Pic object and its use in the cpu object initialization. The test ran successfully to completion and provided the memory allocator outputs and the print test output: Bytes transferred = 686398 (a793e hex) ## Booting kernel from Legacy Image at 82000000 ... Image Name: Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 686334 Bytes = 670.2 KiB Load Address: 81000000 Entry Point: 81000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK Starting kernel ... kernel initialized In cpu timer irq is 87 :virt_alloc: Allocator 0x910cc2bc dump: Block: [00001000,80000000) size=2097148K avail=2097148K max_avail=2097148K Block: [80105000,81000000) size=15340K avail=15340K max_avail=2097148K Block: [811a0000,91000000) size=260480K avail=260480K max_avail=2097148K Block: [912a2000,912a3000) size=4K avail=0 max_avail=0 Block: [912a3000,d0000000) size=1029492K avail=1029492K max_avail=1029492K Block: [e0000000,e0001000) size=4K avail=0 max_avail=0 Block: [e0001000,f0000000) size=262140K avail=262140K max_avail=1029492K Block: [f0002000,f0003000) size=4K avail=0 max_avail=0 Block: [f0007000,f0008000) size=4K avail=0 max_avail=262028K Block: [f000c000,fffef000) size=262028K avail=262028K max_avail=262028K => mem_size=4020883456 (3834 MB) / mem_avail=4020867072 (3834 MB) :phys_alloc: Allocator 0x910cb250 dump: Block: [80106000,80107000) size=4K avail=0 max_avail=0 Block: [80107000,80108000) size=4K avail=0 max_avail=32K Block: [80108000,80110000) size=32K avail=32K max_avail=32K Block: [8025b000,8025c000) size=4K avail=0 max_avail=506240K Block: [8025c000,8025d000) size=4K avail=0 max_avail=0 Block: [8025d000,81000000) size=13964K avail=13964K max_avail=506240K Block: [811a0000,a0000000) size=506240K avail=506240K max_avail=506240K => mem_size=532738048 (508 MB) / mem_avail=532721664 (508 MB) :io_mem_alloc: Allocator 0x910cd334 dump: Block: [00000000,80106000) size=2098200K avail=2098200K max_avail=2098200K Block: [80110000,8025b000) size=1324K avail=1324K max_avail=2098200K Block: [81000000,811a0000) size=1664K avail=1664K max_avail=1610612735 Block: [a0000000,ffffffff) size=1610612735 avail=1610612735 max_avail=161061273 5 => mem_size=3762229247 (3587 MB) / mem_avail=3762229247 (3587 MB) :io_port_alloc: Allocator 0x910ce3a0 dump: => mem_size=0 (0 MB) / mem_avail=0 (0 MB) :irq_alloc: Allocator 0x910cf40c dump: Block: [00000000,00000001) size=1 avail=1 max_avail=1 Block: [00000002,00000057) size=85 avail=85 max_avail=936 Block: [00000058,00000400) size=936 avail=936 max_avail=936 => mem_size=1022 (0 MB) / mem_avail=1022 (0 MB) :rom_fs: ROM modules: ROM: [810e2000,810e2156) config ROM: [810e3000,811133c4) init ROM: [81114000,8119b470) ld.lib.so<http://ld.lib.so> ROM: [8119c000,8119f58c) test-log Genode 17.08 <local changes> 507 MiB RAM and 64535 caps assigned to init [init -> test-log] hex range: [0e00,1680) [init -> test-log] empty hex range: [0abc0000,0abc0000) (empty!) [init -> test-log] hex range to limit: [f8,ff] [init -> test-log] invalid hex range: [f8,08) (overflow!) [init -> test-log] negative hex char: 0xfe [init -> test-log] positive hex char: 0x02 [init -> test-log] multiarg string: "parent -> child.7" [init -> test-log] String(Hex(3)): 0x3 [init -> test-log] Test done. I guess I don't understand the allocator outputs as I would have expected the two pages at address 0xA01000 for the GIC-400 to show up in the io_mem_alloc allocator output with zero availability. I hope that has something to do with this problem as don't see a good way of debugging the placement new operation. As an aside, I noticed a lurking bug in the Pic cpu interface register definitions in ...base-hw/src/lib/hw/arm/pic.h: The struct Irq_id inside both struct Iar and struct Eoir are sized as struct Irq_id : Bitfield<0:10> { }; . They both should be { struct Irq_id : Bitfield<0:9> { }; struct Cpu_id : Bitfield<10:12> { }; }; Thanks in advance for any help. Bob Stewart Get Outlook for Android<https://aka.ms/ghei36>

3 8

thread cancel_blocking usage, kernels
by Steven Harp 18 Oct '17

18 Oct '17

The Genode book suggests that an RPC caller can protect itself from blocking in a stalled server by creating a watchdog thread to monitor the process of the call, and cancel it if it takes too long. Is there a robust/canonical example of using cancel_blocking in this way? My experiment with this (Genode 17.08, x86_32) seems to work as expected--but, only with the OKL4 kernel!? With nova, hw, and seL4, the cancel_blocking() method executes but seemingly to no effect: the thread continues to wait on the (contrived) very slow RPC call, which eventually completes. Suggestions? // Steve Harp

2 3

additional base linux core
by Johannes Kliemann 18 Oct '17

18 Oct '17

Hi, I want to create a base-linux core that is able to run on a bare linux kernel to use it such as any other microkernel in Genode. Since base-linux already implements some of the required interfaces I'd like to reuse the already existing components as much as possible. Yet I'm not sure what the way to go is: - Copying the contents of base-linux into a new repository would probably make an easy start but lead to code duplication (and I would probably have to port all updates of base-linux). - I already tried to reinclude the contents of base-linux (my repository currently only consists of Makefile fragments). Even though it builds it's often quite hacky to relocate some of the $(REP_DIR) entries to base-linux without breaking $(REP_DIR) itself. Also external libs sometimes don't seem to find the correct headers. - Directly extending base-linux would avoid these problems but this would require either a switch to choose between the original and the new functionality of this core or even better a "hybrid" core that is able to run in both environments. Also this change would probably need to get upstream (I don't know if this kind of change would be a problem generally). What is the recommended way to do this? Regards, Johannes

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users