users

users@lists.genode.org

7 participants
2332 discussions

ARMv8 Development Board
by David Loosli 26 Mar '18

26 Mar '18

Signatur HSR Hi all, I am currently trying to find an ARMv8 development board to port the Muen separation kernel to the ARM architecture as my bachelor thesis. In the mailing list archive I found a post about porting Genode to ARMv8 64-bit processors. Is there still someone working on this topic? And if yes, which development boards are used? I am actually looking for a board with 64-bit ARM processor, virtualization support, generic interrupt controller GICv2, SMMU and JTAG interface. So far my favourite is the Hardkernel Odroid C2 board (even though it doesn't completely meet the requirements). I would appreciate your opinion and recommendations. Thanks and regards, David David Loosli Informatik BSc /HSR Rapperswil/

2 2

Genode demo with seL4 Kernel no longer working
by Chris Rothrock 23 Mar '18

23 Mar '18

Previously, the demo build of Genode with seL4 worked perfectly fine but it seems with the newer port of seL4, this is no longer working. If I use KERNEL=nova, the build runs fine, both through QEMU and booting the hardware with the build but with KERNEL=sel4, here is the output m(via hardware boot). Is this a known issue? Chris Boot config: parsing cmdline 'sel4 disable_iommu' Boot config: console_port = 0x3f8 Boot config: debug_port = 0x3f8 Boot config: disable_iommu = true Detected 1 boot module(s): module #0: start=0xa98000 end=0x125e330 size=0x7c6330 name='image.elf' Parsing GRUB physical memory map Physical Memory Region from 0 size 9dc00 type 1 Physical Memory Region from 9dc00 size 2400 type 2 Physical Memory Region from e0000 size 20000 type 2 Physical Memory Region from 100000 size b2bfb000 type 1 Adding physical memory region 0x100000-0xb2cfb000 Physical Memory Region from b2cfb000 size b84000 type 2 Physical Memory Region from b387f000 size 200000 type 4 Physical Memory Region from b3a7f000 size 80000 type 3 Physical Memory Region from b3aff000 size 1000 type 1 Adding physical memory region 0xb3aff000-0xb3b00000 Physical Memory Region from b3b00000 size ad00000 type 2 Physical Memory Region from e0000000 size 10000000 type 2 Physical Memory Region from fd000000 size 1800000 type 2 Physical Memory Region from fec00000 size 1000 type 2 Physical Memory Region from fed00000 size 1000 type 2 Physical Memory Region from fed10000 size a000 type 2 Physical Memory Region from fed20000 size 60000 type 2 Physical Memory Region from fed84000 size 1000 type 2 Physical Memory Region from fedb0000 size 10000 type 2 Physical Memory Region from fee00000 size 1000 type 2 Physical Memory Region from ff700000 size 900000 type 2 Physical Memory Region from 100000000 size 13f800000 type 1 Adding physical memory region 0x100000000-0x23f800000 Got VBE info in multiboot. Current video mode is 16767 ACPI: RSDP paddr=0xfbe30 ACPI: RSDP vaddr=0xfbe30 ACPI: RSDT paddr=0xb3afd074 ACPI: RSDT vaddr=0xb3afd074 Kernel loaded to: start=0x200000 end=0xa98000 size=0x898000 entry=0x201209 ACPI: RSDT paddr=0xb3afd074 ACPI: RSDT vaddr=0xb3afd074 ACPI: FADT paddr=0xb3aef000 ACPI: FADT vaddr=0xb3aef000 ACPI: FADT flags=0x384a5 ACPI: MADT paddr=0xb3aed000 ACPI: MADT vaddr=0xb3aed000 ACPI: MADT apic_addr=0xfee00000 ACPI: MADT flags=0x1 ACPI: MADT_APIC apic_id=0x0 ACPI: MADT_APIC apic_id=0x2 ACPI: MADT_APIC apic_id=0x4 ACPI: MADT_APIC apic_id=0x6 ACPI: MADT_IOAPIC ioapic_id=2 ioapic_addr=0xfec00000 gsib=0 ACPI: MADT_ISO bus=0 source=0 gsi=2 flags=0x0 ACPI: MADT_ISO bus=0 source=9 gsi=9 flags=0xd ACPI: 4 CPU(s) detected ELF-loading userland images from boot modules: size=0x162e000 v_entry=0x2000018 v_start=0x2000000 v_end=0x362e000 p_start=0x125f000 p_end=0x288d000 Moving loaded userland images to final location: from=0x125f000 to=0xa98000 size=0x162e000 Starting node #0 with APIC ID 0 Mapping kernel window is done Starting node #1 with APIC ID 2 Starting node #2 with APIC ID 4 Starting node #3 with APIC ID 6 Booting all finished, dropped to user space Warning: memory in range [0000000100000000,0000000200000000) is unavailable (due to limited untyped cnode range) Warning: memory in range [0000000200000000,0000000220000000) is unavailable (due to limited untyped cnode range) Warning: memory in range [0000000220000000,0000000230000000) is unavailable (due to limited untyped cnode range) Warning: memory in range [0000000230000000,0000000238000000) is unavailable (due to limited untyped cnode range) Warning: memory in range [0000000238000000,000000023c000000) is unavailable (due to limited untyped cnode range) Warning: memory in range [000000023e000000,000000023f000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [000000023f800000,0000000240000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000000240000000,0000000280000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000000280000000,0000000300000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000000300000000,0000000400000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000000400000000,0000000800000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000000800000000,0000001000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000001000000000,0000002000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000002000000000,0000004000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000004000000000,0000008000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000008000000000,0000408000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000408000000000,0000608000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000608000000000,0000708000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000708000000000,0000788000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [0000788000000000,00007c8000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [00007c8000000000,00007e8000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [00007e8000000000,00007f8000000000) is unavailable (due to limited untyped cnode range) Warning: device memory in range [00007f8000000000,0000800000000000) is unavailable (due to limited untyped cnode range) virtual address layout of core: overall [0000000000002000,00000000c0000000) core image [0000000002000000,000000000362e000) ipc buffer [000000000362e000,000000000362f000) boot_info [000000000362f000,0000000003631000) stack area [0000000040000000,0000000050000000) Warning: need physical memory, but Platform object not constructed yet Warning: need physical memory, but Platform object not constructed yet Warning: need physical memory, but Platform object not constructed yet Warning: need physical memory, but Platform object not constructed yet Warning: need physical memory, but Platform object not constructed yet Warning: need physical memory, but Platform object not constructed yet boot module 'nit_focus' (89200 bytes) boot module 'nitlog' (143312 bytes) boot module 'ps2_drv' (184584 bytes) boot module 'report_rom' (127384 bytes) boot module 'acpi_drv' (127504 bytes) boot module 'pointer' (161504 bytes) boot module 'scout' (1776120 bytes) boot module 'testnit' (105128 bytes) boot module 'ld.lib.so' (906600 bytes) boot module 'launchpad.config' (594 bytes) boot module 'nitpicker' (369920 bytes) boot module 'timer' (110832 bytes) boot module 'platform_drv' (370128 bytes) boot module 'config' (7521 bytes) boot module 'fb_drv' (384720 bytes) boot module 'liquid_fb' (329272 bytes) boot module 'status_bar' (139744 bytes) boot module 'global_keys_handler' (172968 bytes) boot module 'launchpad' (811456 bytes) boot module 'init' (344960 bytes) boot module 'rom_filter' (120536 bytes) Warning: need physical memory, but Platform object not constructed yet Genode 17.11-221-g8d09d02 <local changes> 2793 MiB RAM and 261141 caps assigned to init Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x1 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x2 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x4 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x8 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x10 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x20 [init -> nitpicker_config] resource_request: ram_quota=5239 [init] child "nitpicker_config" requests resources: ram_quota=5239 [init -> acpi_drv] Found MADT [init -> acpi_drv] MADT IRQ 0 -> GSI 2 flags: 0 [init -> acpi_drv] MADT IRQ 9 -> GSI 9 flags: 13 [init -> acpi_drv] Found MCFG [init -> acpi_drv] MCFG BASE 0xe0000000 seg 0x0 bus 0x0-0xff [init -> acpi_drv] Found DMAR [init -> acpi_drv] 39 bit DMA physical addressable , IRQ remapping supported [init -> acpi_drv] DMA remapping structure type=0 [init -> acpi_drv] DMA remapping structure type=0 [init -> acpi_drv] DMA remapping structure type=1 [init -> acpi_drv] DMA remapping structure type=1 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x40 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x80 Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x100 [init -> ps2_drv] Using keyboard with scan code set 1 (xlate) [init -> fb_drv] Found PCI VGA at 00:02.0 [init -> fb_drv] fb mapped to 0x4000 [init -> ps2_drv] Error: failed to read from port [init -> platform_drv] PS2 uses IRQ, vector 0x1 [init -> platform_drv] PS2 uses IRQ, vector 0xc [init -> ps2_drv] resource_request: ram_quota=20480 [init] child "ps2_drv" requests resources: ram_quota=20480 -- Thank You, Chris Rothrock Senior System Administrator (315) 308-1637

2 2

Genode::Pd_connection::address_space returns invalid capability
by Johannes Kliemann 21 Mar '18

21 Mar '18

Hi all, on base-linux when Genode::Pd_connection::address_space is called it returns an invalid capability. In the platform_drv [1] this causes the Region_map to fail to attach the DMA memory. On NOVA for example this capability is valid. I went through the code but I still have no idea what causes this capability to be invalid. Regards, Johannes [1]: https://github.com/genodelabs/genode/blob/1f7b5e75bfeb9ec35b975b4db66fc9b9b…

1 0

problem building depot for fb_sdl
by Duss Pirmin 20 Mar '18

20 Mar '18

Hello all I have two clones of Genode (18.02-20-g1f7b5e75b) on two different machines. On my Ubuntu Artful fb_sdl can't be built due to a missing header file (SDL/SDL.h). I then tested it on my ARCH Linux, where the build works flawless. Does the recipe for fb_sdl by accident use some header files from the build system? Can this cause any problems or should I just install the missing header files on my Ubunt? Best regards, Pirmin

2 1

Individual file access
by Nobody III 16 Mar '18

16 Mar '18

To start off, I'm planning on building a component that handles file open/save requests for other components, primarily graphical applications. My plan is to use a qt5 QFileDialog for the user to select one or more files, then modify the vfs server's configuration to attach the selected file(s) to the component's filesystem. To attach individual files to a component's filesystem, it seems like I should write a server-side link vfs plugin. The plugin would be like a symlink, but would transparently resolve the link within the vfs server, providing access to otherwise inaccessible files. Is this possible? If so, can you give me some tips on how to implement it?

2 7

Library Isolation
by Nobody III 16 Mar '18

16 Mar '18

In Genode, it would be very useful to be able to isolate libraries into their own child processes, greatly reducing the scope of possible security holes. I want to write a generic method for doing this simply, efficiently, and transparently. Can you assess my ideas and/or give me other ideas? For method calls, one option would be to generate an RPC interface for each library. This seems doable, but methods involving pointers to large amounts of data may be an issue. I could wrap pointers in buffers, but dynamic argument sizes and limits on RPC argument sizes could be an issue. I could maybe use a packet stream. This would fix some issues, and would remove the need for an individual RPC interface for each library, however the packet stream might need to be fairly large. I might be able to use the RPC idea above, but wrap each pointer in a dataspace. Is this possible? And is it efficient?

3 13

VFS FIFO plugin
by Nobody III 16 Mar '18

16 Mar '18

I've started writing a (single-file) FIFO VFS plugin. I have gotten it to compile, but I still need a little help. How should I test my plugin? I'm not aware of a good run script to base a test on. How should I register signal handlers? I can use a list of List_element<Signal_context_capability>, but that requires extra dynamic memory allocations. How should I handle this to properly account for memory?

1 0

how to use genode on riscv
by Dd Nirvana 16 Mar '18

16 Mar '18

Hi guys, I am so glad to know that genode has supported RISCV from v16.02. I have already read the article(http://genode.org/documentation/articles/riscv) which introduce how genode port the RISCV. However, I am still a little confused about how to build a runnable genode image and how to run it on riscv platform like spike. Could you give me any advices to do it? Thanks a lot! Dong Du

2 2

Genode affinity, multi-core separation and service encapsulation (core inferences)
by Daniel Krefft 15 Mar '18

15 Mar '18

Hello, after an exhaustive evaluation of different scenarios for testing the coherent execution of components on distinct cores, the following question arises: Is it basically possible to separate a component running on core 1 completely (e.g. pd, ram, rom, log) from the remaining system running on core 0? Our results so far demonstrate that, in any case, a component running on core 1 utilizes at least the rom and log services provided by init which is running on core 0. Also the usage of a second level init component (which is suggested by the genode book) didn't change the resulting behavior. Of course, genode is not meant to be a separation kernel by design, but would it still be possible to map/assign resources/partitions to corresponding cores? Or do all components running on different cores still have to contact the genode CORE component which is running on core 0? Best regards Daniel -- Daniel Krefft MSc. Wissenschaftlicher Mitarbeiter Technische Universitaet Muenchen Fakultaet fuer Informatik Lehrstuhl fuer Betriebssysteme Arcisstrasse 21 80333 Muenchen Tel. +49 89 289 18791 daniel.krefft@...256... www.os.in.tum.de/personen/krefft

4 6

base-linux IRQ session
by Johannes Kliemann 14 Mar '18

14 Mar '18

Hi all, I'm currently implementing the IRQ session on base-linux. If I understood the Foundations book correctly interrupts are waiting in a separate thread that locks when it is waiting and continues (and calls the handler) once an interrupt is triggered. According to this I have implemented a kernel module [1] that triggers interrupts via reads on a device file. The interrupt can be registered via ioctl on the file descriptor and the a blocking read is called that returns once the registered interrupts has been triggered. I have looked into the implementations of base-nova and base-hw but didn't completely understand it. As far as I understood the session component implements the session and only requires the interrupt number and a signal handler. The Irq_object implements the waiting thread but I didn't see where it is waiting for the interrupt. Also as far as I could see it the actual interrupt capability stays inside the session in core and only the signal handler capability is passed to the component. Is my understanding of this correct? And is there any further documentation on this? Regards, Johannes [1]: https://github.com/jklmnn/hwiodev/blob/c445eb58daa6d29e9f779bf6ad4b00818fba…

3 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users