Devel January 2017

devel@sel4.systems

25 participants
32 discussions

CAmkES Templates
by Chris Guikema 19 Jan '17

19 Jan '17

Hello, I am working on a CAmkES application attempting to build a seL4 Network Stack. I am basing this on the CAmkES-VM and utilizing UDP Protocol with the lwIP library. During my build process, I get quite a few linking errors like this: undefined reference to `pbuf_alloc' This is odd, because in the templates, the proper header files are being linked in. There are also warnings like this: Warning: no template for ethdriver_1.to.source Even though the connection does exist: connection seL4Ethdriver eth_driver(from router.ethdriver, to ethdriver.client); Is there something obvious I am doing wrong? Thanks Chris

2 2

questions about SMMU on TK1 VMM
by PX 18 Jan '17

18 Jan '17

Hi, I have some questions about the SMMU on the new version of TK1 VMM as follows: 1. In the source code, smmu.c, the IO ASID 1 is assigned to hardware engine, AFI, which is supposed to connect with PCIE devices. However, when I add 1 to vm.smmu in vm.camkes, the VM can not access Ethernet and cause a SMMU translation error. But it works if I add 0 to vm.smmu as suggested by Kent. whats the reason to do so? 2. Each IO device is assigned with an IO space mapping. However, there is no IO ASID associated with these mappings. Does that means these mappings are associated with an IO ASID in the order given in vm.smmu? 3. Is it possible for the VMM to change the IO mapping for a specific device? say, invalidate old mapping and load a new mapping? what's the rough idea to do so? thanks Peng

2 1

questions about PCIE SMMU for tk1 vmm
by PX 16 Jan '17

16 Jan '17

Hi, I am confused by the SMMU management for PCIE device in the updated TK1 VMM. The IO ASID for PCIE device is 0. However, the start IO ASID is from 1 as defined in smmu.h. When initialized, the lookup table, smmu_ioasid_to_pd, has no entry for IO asid 0 at all. I don't understand how the page table for PCIE device is generated and used by SMMU? which part source code should I check ? thanks Peng

2 1

Re: [seL4] quesitons about TK1 VMM
by Kent.Mcleod＠data61.csiro.au 14 Jan '17

14 Jan '17

Hi Peng, Adding the ethernet card requires adding the 0 ASID in the vm.camkes file that I mentioned in the previous email. vm.smmu = [0, 10, 24]; This gives permission for PCIE devices to read and write to memory. I confirmed that on the TK1 Jetson the ethernet port works after this change. You may need to run "ifconfig eth0 up" to enable the device once the image boots. Regards, Kent. ? ________________________________ From: PX <seawolf.peng(a)gmail.com> Sent: Friday, January 13, 2017 12:13 PM To: Mcleod, Kent (Data61, Kensington NSW) Subject: Re: quesitons about TK1 VMM Kent, I am using NVIDIA Jetson TK1 board. The reason I want to use insecure config is to enable VM Linux to use Ethernet port. I do not care about the SD card. How can I just add Ethernet card? is there a way for me to avoid adding SD card to The VM linux as you just suggest in your email? Thanks Peng On Thursday,January 12, 2017, <Kent.Mcleod(a)data61.csiro.au<mailto:Kent.Mcleod@data61.csiro.au>> wrote: Hi Peng, Which hardware are you using to run the image? This project has only been tested on the TK1-SOM made by Colorado Engineering. The ethernet port doesn't work as the version of Linux that we use doesn't support it. As for your second question, we configure the IOMMU to only let Linux use the emmc device and USB device on the TK1-SOM. The error is caused because Linux is trying to access a SD card device that it isn't authorized to access. The TK1-SOM doesn't have any SD card hardware so camkes doesn't set up access. If you want to use the Insecure config then you will need to modify apps/vm/vm.camkes and add the right ID to vm.smmu on line 443. To find out which ID to add we take the ID:98 from your Address translation error and look it up in the TK1 technical reference manual. In the memory controller section of the manual there is a "Error Data Capture: Status" section that starts on page 716. Using the table there you can look up ID:98 to see that it belongs to the SWGROUP sdmmc3a. We can now take this and look in seL4 ("kernel/include/plat/tk1/plat/machine/smmu.h?") to find the relevant ASID. From the list of ASIDs we see that SMMU_SDMMC3A_ASID is defined as 23. This is the ID that needs to be added to the vm.smmu array in vm.camkes. Hope this helps, Regards, Kent. ________________________________ From: Devel <devel-bounces(a)sel4.systems> on behalf of PX <seawolf.peng(a)gmail.com> Sent: Friday, January 13, 2017 9:03 AM To: devel(a)sel4.systems Subject: [seL4] quesitons about TK1 VMM Hi, I built a TK1 ARM VMM image from the source code SEL4PROJ/camkes-vm-manifest in GitHub. I have some quesitons about the tk1_vmlinux. Question 1: If I use the original tk1_vm_defconfig, the eth0 does not work in vm. Is the tk1_vm_linux in default not supposed to access Ethernet card? Hpw do I access Ethernet card in this case? Question 2: If I change the VM conifg into insecure, CONFIG_TK1_INSECURE=y, the VM can not get booted, I get "SMMU address translation error". The error message is appended as follows: " [ 10.503932] mmc1: Invalid maximum block size, assuming 512 bytes [ 10.566465] mmc1: SDHCI controller on 700b0400.sdhci [700b0400.sdhci] using ADMA 64-bit SMMU Address translation error: ID: 98 address: 0xae609000 type: 6 direction: 0x0 IOPT permission: read 0x0 write 0x0 nonsecure 0x0 [ 10.617123] mmc1: ADMA error" Is this error caused by bugs in source code or my wrong config? if the later case, what's the correct config? thanks Peng

2 1

quesitons about TK1 VMM
by PX 13 Jan '17

13 Jan '17

Hi, I built a TK1 ARM VMM image from the source code SEL4PROJ/camkes-vm-manifest in GitHub. I have some quesitons about the tk1_vmlinux. Question 1: If I use the original tk1_vm_defconfig, the eth0 does not work in vm. Is the tk1_vm_linux in default not supposed to access Ethernet card? Hpw do I access Ethernet card in this case? Question 2: If I change the VM conifg into insecure, CONFIG_TK1_INSECURE=y, the VM can not get booted, I get "SMMU address translation error". The error message is appended as follows: " [ 10.503932] mmc1: Invalid maximum block size, assuming 512 bytes [ 10.566465] mmc1: SDHCI controller on 700b0400.sdhci [700b0400.sdhci] using ADMA 64-bit SMMU Address translation error: ID: 98 address: 0xae609000 type: 6 direction: 0x0 IOPT permission: read 0x0 write 0x0 nonsecure 0x0 [ 10.617123] mmc1: ADMA error" Is this error caused by bugs in source code or my wrong config? if the later case, what's the correct config? thanks Peng

1 0

question about SEL4PROJ /camkes-arm-vm-manifest
by PX 13 Jan '17

13 Jan '17

Hi, all I try to build a TK1 ARM VMM image from the source code SEL4PROJ/camkes-vm-manifest in GitHub. However, I can not compile it. I get errors when the compiler tries to build "camkes-accelerator" . I don't put any new code yet. I just: 1) repo init the url ; 2) repo sync; 3) make tk1_vm_defconfig; and 4) make. Did I do something wrong here? thanks Peng

2 5

Overly eager xsave size rejection
by Corey Richardson 12 Jan '17

12 Jan '17

in src/arch/x86/machine/fpu.c:140 on 4.0.0, there is > if (x86_cpuid_ebx(0x0d, 0x0) != CONFIG_XSAVE_SIZE) { > printf("XSAVE buffer set set to %d, but should be %d\n", CONFIG_XSAVE_SIZE, x86_cpuid_ebx(0x0d, 0x0)); > return false; > } I want to force a large(r than 576) xsave region so that TCBBits is always 11, to help my userspace be vaguely more kernel-config-independent. I don't think it's a problem if the xsave buffer in the TCB is larger than the hardware will actually use? I also think this is buggy. Shouldn't it be querying ecx, since things like AVX aren't enabled in the kernel? To be clear, this is my suggested change: > if (x86_cpuid_ecx(0x0d, 0x0) > CONFIG_XSAVE_SIZE) { > printf("XSAVE buffer set set to %d, but should be at least %d\n", CONFIG_XSAVE_SIZE, x86_cpuid_ecx(0x0d, 0x0)); > return false; > } -- cmr http://octayn.net/ +16038524272

2 5

question about SEL4PROJ /camkes-arm-vm-manifest
by PX 12 Jan '17

12 Jan '17

Hi, all I posted this question yesterday, and get no answer. Let me to be more specific this time. I try to build a TK1 ARM VMM image from the source code SEL4PROJ/camkes-vm-manifest in GitHub. However, I can not compile it. I get errors when the compiler tries to parse capDL. The errors are appended as follows: " make: Entering directory '/home/dev/Documents/new_vmm/projects/capd /capDL-tool' stack setup make: stack: Command not found Makefile:37: recipe for target 'sandbox' failed make: *** [sandbox] Error 127 make: Leaving directory '/home/dev/Documents/new_vmm/projects/capdl/capDL-tool' Makefile:51: recipe for target '/home/dev/Documents/new_vmm/stage/arm/tk1/parse-capDL/parse-capDL' failed " I checked that there is a file called stack.ymal in the directory: ~/capdl/capDL-tool. My system is also installed latest ghc and ghc-prof. Anybody can help me on this problem? Thanks Peng

3 3

Using the seL4 Benchmark Tool
by Chris Guikema 12 Jan '17

12 Jan '17

Hello, I am currently attempting to use the seL4 Benchmark tool. After going through the menuconfig (kernel -> build options -> Enable Benchmarks -> Track threads and kernel utilization time), I attempt to rebuild, and get a host of errors: In file included from /home/chrisguikema/gdbtest/kernel/include/compound_types.h:16:0, from /home/chrisguikema/gdbtest/kernel/include/types.h:15, from /home/chrisguikema/gdbtest/kernel/src/api/faults.c:14: /home/chrisguikema/gdbtest/kernel/include/object/structures.h:249:5: error: unknown type name 'benchmark_util_t' benchmark_util_t benchmark; And a lot more, but all along the "not a structure or union" line, which makes me think that either the header file isn't being linked properly, or the #ifdefs aren't working for everything. Did I do something improperly in my setup? Thanks, Chris Guikema

2 1

Workshop debrief?
by Jeff Waugh 10 Jan '17

10 Jan '17

Hey there, I might be hoping a little too much for video, but will there be slides and notes from the Workshop? (Particularly interested in the gaps discussion.) Would be handy content on the wiki. :-) Thanks, Jeff

3 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

Devel January 2017