users March 2018

users@lists.genode.org

27 participants
31 discussions

SMC Calls in Trustzone VMM Scenario
by Mauricio Gutierrez 23 Apr '18

23 Apr '18

Hello, I have been doing some work with the Genode Trustzone VMM scenario on my i.MX53 development board and I am having a bit of trouble understanding how the SMC calls work between the normal and secure world. Online you talk about how you implemented 6 calls in the modified normal world linux kernel but in the main for the tz_vmm I only found 4 different cases in the _handle_smc() function. In any case, I wanted to add my own call and was able to add it and check that the required arguments are passed correctly and everything so that part I think I understand. However, I need to do some of the handling in Monitor Mode and my understanding was that an SMC would throw your into monitor mode but it seems the handler operates in user mode? Since it is not privileged then I am not able to call a "cps #22" to switch to monitor mode. In an earlier thread I know you refer to the section "World switch between non-secure world and secure > world" in http://genode.org/documentation/articles/trustzone. But I am still uncertain as to how I could get my case in _handle_smc() to enter monitor mode so that I can play around with the NS bit without leaving secure world. I have been studying what happens when I call an smc, say "smc #4" from normal world. But I have not been able to exactly pin point, where is the entry point for such an exception in the Genode secure world call? What exactly happens once I make that call to secure world and where I can I find/follow the code? Is this covered somewhere in your book? I know about the mode_transitions.s file as well as the exception_vector.s and vm.cc files in repos/base-hw/src/core/spec/arm_v7/trustzone, it seems this is the entry point? But where does it go after we call the nonsecure_to_secure transition? Most importantly, I need to understand where is the code operating in monitor mode? Where does it end and where does it start? How can I tell? If I needed to write at least some part of my smc handler in monitor mode before it switches out, what is the best approach to doing that? I apologize for all the questions and would appreciate any help and guidance you can provide. Thank you, Mauricio

2 5

usb issues on AMD 9xx chipset
by Nobody III 03 Apr '18

03 Apr '18

I've been testing Genode's current compatibility with my desktop computer, which has an AMD 9xx chipset. While the framebuffer driver works fine, usb_drv does not. Here's the full output: Genode 18.02-2-g6888094f6 <local changes> 16299 MiB RAM and 63253 caps assigned to init [init -> acpi_drv] Found MADT [init -> acpi_drv] MADT IRQ 0 -> GSI 2 flags: 0 [init -> acpi_drv] MADT IRQ 9 -> GSI 9 flags: 15 [init -> acpi_drv] Found MCFG [init -> acpi_drv] MCFG BASE 0xe0000000 seg 0x0 bus 0x0-0xff [init -> platform_drv] 0:2.0 - bridge 1:0.0 [init -> platform_drv] 0:9.0 - bridge 2:0.0 [init -> platform_drv] 0:14.4 - bridge 3:0.0 [init -> platform_drv] 0:15.0 - bridge 4:0.0 [init -> platform_drv] 0:15.3 - bridge 5:0.0 [init -> usb_drv] Could not read screen resolution in config node [init -> usb_drv] Configured HID screen with 0x0 (multitouch=false) [init -> usb_drv] No <storage> config node found - not starting the USB Storage (Block) service [init -> usb_drv] No <nic> config node found - not starting the USB Nic (Network) service [init -> usb_drv] No <raw> config node found - not starting external USB service [init -> usb_drv] Enabled UHCI (USB 1.0/1.1) support [init -> usb_drv] Enabled OHCI (USB 1.0/1.1) support [init -> usb_drv] Enabled EHCI (USB 2.0) support [init -> usb_drv] Enabled XHCI (USB 3.0) support *[init -> platform_drv] Warning: Out_of_caps during Device_component construction* *[init -> platform_drv] Warning: Out_of_caps during Device_component construction* *[ 0] sys_assign_pci: Invalid Hint (0x200)* [init -> platform_drv] Error: usb_drv -> : assignment of PCI device 2:0.0 failed phys=0xe0200000 virt=0x80400000 [init -> usb_drv] ioremap: mapped phys 0xfe100000 (size 32768) to virt 0x20000 [init -> usb_drv] dev_info: xHCI Host Controller [init -> usb_drv] dev_info: new USB bus registered, assigned bus number 1 [init -> usb_drv] dev_info: hcc params 0x040040a5 hci version 0x100 quirks 0x00000010 [init -> platform_drv] 2:0.0 adjust IRQ as reported by ACPI: 10 -> 48 [init -> platform_drv] 2:0.0 uses MSI 64bit, vector 0x9f, address 0xfee10000, maskable [init -> usb_drv] dev_info: USB hub found [init -> usb_drv] dev_info: 4 ports detected [init -> usb_drv] dev_info: xHCI Host Controller [init -> usb_drv] dev_info: new USB bus registered, assigned bus number 2 [init -> usb_drv] dev_info: We don't know the algorithms for LPM for this host, disabling LPM. [init -> usb_drv] dev_info: USB hub found [init -> usb_drv] dev_info: 4 ports detected [ 0] sys_assign_pci: Invalid Hint (0xb2) [init -> platform_drv] Error: usb_drv -> : assignment of PCI device 0:16.2 failed phys=0xe00b2000 virt=0x1000 [init -> usb_drv] ioremap: mapped phys 0xfe204000 (size 256) to virt 0x17000 [init -> usb_drv] dev_info: EHCI Host Controller [init -> usb_drv] dev_info: new USB bus registered, assigned bus number 3 [init -> usb_drv] dev_info: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround [init -> platform_drv] 0:16.2 adjust IRQ as reported by ACPI: 11 -> 17 [init -> platform_drv] 0:16.2 uses IRQ, vector 0x11, non-maskable [init -> usb_drv] dev_info: irq 130, io mem 0xfe204000 [init -> usb_drv] dev_info: USB 2.0 started, EHCI 1.00 [init -> usb_drv] dev_info: USB hub found [init -> usb_drv] dev_info: 4 ports detected [ 0] sys_assign_pci: Invalid Hint (0x9a) [init -> platform_drv] Error: usb_drv -> : assignment of PCI device 0:13.2 failed phys=0xe009a000 virt=0x1000 [init -> usb_drv] ioremap: mapped phys 0xfe207000 (size 256) to virt 0x28000 [init -> usb_drv] dev_info: EHCI Host Controller [init -> usb_drv] dev_info: new USB bus registered, assigned bus number 4 [init -> usb_drv] dev_info: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround [init -> platform_drv] 0:13.2 adjust IRQ as reported by ACPI: 11 -> 17 [init -> platform_drv] 0:13.2 uses IRQ, vector 0x11, non-maskable [init -> usb_drv] dev_info: irq 131, io mem 0xfe207000 [init -> usb_drv] dev_info: USB 2.0 started, EHCI 1.00 [init -> usb_drv] dev_info: USB hub found [init -> usb_drv] dev_info: 5 ports detected [ 0] sys_assign_pci: Invalid Hint (0x92) [init -> platform_drv] Error: usb_drv -> : assignment of PCI device 0:12.2 failed phys=0xe0092000 virt=0x1000 [init -> usb_drv] ioremap: mapped phys 0xfe209000 (size 256) to virt 0x29000 [init -> usb_drv] dev_info: EHCI Host Controller [init -> usb_drv] dev_info: new USB bus registered, assigned bus number 5 [init -> usb_drv] dev_info: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround [init -> platform_drv] 0:12.2 adjust IRQ as reported by ACPI: 11 -> 17 [init -> platform_drv] 0:12.2 uses IRQ, vector 0x11, non-maskable [init -> usb_drv] dev_info: irq 132, io mem 0xfe209000 Also, I get the following message in dmesg on linux (from drivers/usb/host/pci-quirks.c), but not from usb_drv: QUIRK: Enable AMD PLL fix What might be going on? Why would usb_drv cause platform_drv to run out of CAPs, even when I assign it 2000 CAPs (instead of 800)?

4 7

Question about long IPC implementation in Genode implementation
by yu000013 03 Apr '18

03 Apr '18

Hi there, I'm currently doing tests of IPC on different microkernels using Genode framework. I'm wondering whether there're any long IPC implementation inside the framework that I can make use of. Thank you very much! Yelly

2 2

base-linux ram dataspace file descriptor usage
by Johannes Kliemann 29 Mar '18

29 Mar '18

Hi all, I'm struggling with modifying the Ram_dataspace in base-linux. I have replaced the file descriptor opened in > void Ram_dataspace_factory::_export_ram_ds(Dataspace_component *ds) in base-linux/src/core/ram_daraspace_support.cc by opening a special device file that provides mappable ram. I have attached the exact diff that causes the segfault. The kernel module that provides the device file and the ioctl is available at [1]. I have tested it on a Linux system and mapping memory and reading/writing it worked flawlessly. With this change each component creates a segmentation fault. I was not able to trace it, I couldn't even find out in which file it occurs. The instruction pointer randomly appeared in repos/base/src/lib/base/lock.cc or in repos/base/src/lib/base/heap.cc. I have touched neither of these files. Is there any information about where this is used exactly? I was unable to trace the usage of the mapped memory beyond Region_map_mmap::attach. I have also traced the calls inside the kernel module and it looks as it only uses open, mmap and close so there shouldn't a problem. I'd like to give you further information about this but I have absolutely no idea by myself. Regards, Johannes [1]: https://github.com/jklmnn/hwiodev/blob/0f5d367162812ee015434e5b97fdf208ef36…

2 3

access to tsc calibration info
by Steven Harp 27 Mar '18

27 Mar '18

x86-specific question: Is there a generic way to get access to the TSC frequency calibration information, as provided by modern x86 CPUs in MSRs? (User mode components cannot directly read these.) The information is readily available in Nova's hypervisor information page (Hip), conveniently exported as a ROM. But I am not spotting a similar export for (e.g.) seL4. The data is present in the sel4 boot info structure (in core)--maybe this is accessible to components in some manner? Suggests a possible platform API, if not already present... Suggestions? // Steve Harp

2 1

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users March 2018