Devel

devel@sel4.systems

1 participants
1384 discussions

Multikernel in RISCV
by David Martin 12 Apr '24

12 Apr '24

Hello, I'm currently working with seL4 & Polarfire (RISCV) and I'm working with a single core at the moment (doing some testing and understanding how seL4 works). Polarfire has 4 cores and I'd like to start using all of them in a multikernel configuration (every hart running its own sel4 kernel). I've found the following RFC: https://sel4.atlassian.net/browse/RFC-17 where Kent McLeod has done some work (https://github.com/kent-mcleod/camkes-manifest/blob/kent/multicore2/master.…) but only for ARM. Does someone know if the same approach will be taken for RISCV? or even better, if someone has already done it? Thanks, David.

2 1

Gpu passthrough
by Hugo V.C. 12 Apr '24

12 Apr '24

Hi all, here a simple question: is there any example/tutorial off gpu passthrough to a Linux guest? Best,

3 5

Release 0.4.0 of the seL4 Device Driver Framework
by Ivan Velickovic 09 Apr '24

09 Apr '24

Hello all This is a message to let people know that version 0.4.0 of the seL4 Device Driver Framework (sDDF) has been released. The sDDF aims to provide a collection of interfaces, libraries and tools for writing device drivers for seL4 that allow accessing devices securely and with low overhead. Some may be familiar with the sDDF from previous seL4 Summit talks. Since the pre-release at the 2023 Summit, we have made significant improvements to the networking sub-system, generally rationalising interfaces and further improving performance, the Ethernet device-class interfaces are now mature. We have also introduced preliminary specs and prototype implementations for serial, I2C, block, audio and graphics device classes. You can find information about the release and the accompanying documentation here: https://github.com/au-ts/sddf/releases/tag/0.4.0 Thanks, Ivan

1 0

Two weeks to go to submit a talk for seL4 summit 2024
by Birgit Brecknell 08 Apr '24

08 Apr '24

Two weeks to go to submit a talk [0] for seL4 summit 2024 [1]! If you’d like to submit a talk, please upload an abstract of one page or less to the submission portal [2]. The seL4 Summit 2024 will be held 15-17 October 2024 at the Holiday Inn Potts Point, Sydney, Australia. The summit will be an in-person event. Registration details to follow soon. We’re looking forward to many exciting proposals! [0] https://sel4.systems/Foundation/Summit/2024/cfp [1] https://sel4.systems/Foundation/Summit/2024/ [2] https://sel4.systems/Foundation/Summit/2024/submit -- Birgit Brecknell seL4 Foundation Project Coordinator birgit(a)sel4.systems bbrcknl(a)gmail.com

1 0

sel4test CACHEFLUSH0001 failed
by Leonid Meyerovich 29 Mar '24

29 Mar '24

Hello, I run sel4test on the aarch64 platform. My CACHEFLUSH0001 test in sel4test failed /* Clean makes data observable to non-cached page */ *ptr = 0xC0FFEE; *ptrc = 0xDEADBEEF; test_assert(*ptr == 0xC0FFEE); test_assert(*ptrc == 0xDEADBEEF); I have tried to make to 'improve' memory/cache coherence, but the last assertion still failed /* Clean makes data observable to non-cached page */ *ptr = 0xC0FFEE; *ptrc = 0xDEADBEEF; error = seL4_ARM_Page_Clean_Data(framec, 0, PAGE_SIZE_4K); error = seL4_ARM_Page_Invalidate_Data(framec, 0, PAGE_SIZE_4K); __asm volatile("dmb sy" ::: "memory"); test_assert(*ptr == 0xC0FFEE); test_assert(*ptrc == 0xDEADBEEF); Thank you, Leonid

2 2

Re: Only 512mb ram available on capdl-loader-image-arm-qemu-arm-virt image
by Peter Chubb 26 Mar '24

26 Mar '24

>>>>> "Daniele" == Daniele Feliciani <felicianidaniele(a)gmail.com> writes: Daniele> Hello Peter, I have the same Daniele> problem. i tried to change the guest ram value to Daniele> 0x40000000. I added set(QEMU_MEMORY "2048") in config.cmake Daniele> but I get the following errors while running : " Daniele> map_vm_memory_reservation@guest_memory.c:477 Failed to get Daniele> frame for reservation address 0x60000000" and " Daniele> vm_ram_touch@guest_ram.c:165 Failed to touch ram region: Not Daniele> registered RAM region 32 bit ARM insts not decoded" Check the size of the MMIO region. By default it uses 29 bits; for a 2G region you need 31 bits. In the devices.camkes file, in the untyped_mmios section. There's probably an entry, "0x40000000:29", try increasing this to "0x40000000:31" to get a 2^31 region. -- Dr Peter Chubb https://trustworthy.systems/ Trustworthy Systems Group CSE, UNSW Core hours: Mon 8am-3pm; Wed: 8am-5pm; Fri 8am-12pm.

3 3

Re: Only 512mb ram available on capdl-loader-image-arm-qemu-arm-virt image
by Daniele Feliciani 25 Mar '24

25 Mar '24

It doesn't seem to work. I'm attaching the device.camkes file and the error screenshots. Il giorno lun 25 mar 2024 alle ore 10:43 Peter Chubb < peter.chubb(a)unsw.edu.au> ha scritto: > >>>>> "Daniele" == Daniele Feliciani <felicianidaniele(a)gmail.com> writes: > > Daniele> I changed the value but now i > Daniele> have the following error: > > Danielle> ./simulate: QEMU command: qemu-system-aarch64 -machine > Danielle> virt,virtualization=on,highmem=off,secure=off -cpu cortex-a53 > -nographic > Danielle> -m size=2048 -kernel > images/capdl-loader-image-arm-qemu-arm-virt > Danielle> ELF-loader started on CPU: ARM Ltd. Cortex-A53 r0p4 > Danielle> paddr=[61b07000..62ee00b7] > Danielle> No DTB passed in from boot loader. > Danielle> Looking for DTB in CPIO archive...found at 61c07c68. > Danielle> Loaded DTB from 61c07c68. > Danielle> paddr=[60242000..60243fff] > Danielle> ELF-loading image 'kernel' to 60000000 > Danielle> paddr=[60000000..60241fff] > Danielle> vaddr=[8060000000..8060241fff] > Danielle> virt_entry=8060000000 > Danielle> ELF-loading image 'capdl-loader' to 60244000 > Danielle> paddr=[60244000..6170cfff] > Danielle> vaddr=[400000..18c8fff] > Danielle> virt_entry=408d88 > Danielle> Enabling hypervisor MMU and paging > Danielle> Jumping to kernel-image entry point... > Danielle> > Danielle> Bootstrapping kernel > Danielle> Warning: Could not infer GIC interrupt target ID, assuming 0. > Danielle> available phys memory regions: 1 > Danielle> [60000000..c0000000] > ^^^^^^^^^ this is the physical memory region you have to play > with. Make the region given to the VM start at 0x60000000 > instead of 040000000 > > -- > Dr Peter Chubb https://trustworthy.systems/ > Trustworthy Systems Group CSE, UNSW > Core hours: Mon 8am-3pm; Wed: 8am-5pm; Fri 8am-12pm. >

1 0

Reminder seL4 developer hangout
by Birgit Brecknell 25 Mar '24

25 Mar '24

Hi all A friendly reminder that the seL4 developer hangout is on next week: * Wed Apr 3, 7am UTC For your time zone, please see the calendar: https://sel4.systems/contact/ Zoom link: https://unsw.zoom.us/j/82640784431 cheers Birg --- Birgit Brecknell Project Coordinator, seL4 Foundation birgit(a)sel4.systems<mailto:birgit@sel4.systems> Mon 9am-5pm Wed 2pm-5pm Fri 9am-5pm

1 0

Only 512mb ram available on capdl-loader-image-arm-qemu-arm-virt image
by skydivebcn＠gmail.com 25 Mar '24

25 Mar '24

Hi! I'm running a an aarch64 Linux guest with qemu with "qemu-system-aarch64 -machine virt,virtualization=on,highmem=off,secure=off -cpu cortex-a53 -m size=2048 (...) -kernel capdl-loader-image-arm-qemu-arm-virt". I have noticed that no matter how I set the "-m size" parameter that only 512MB are available to the Linux guest. Removing the "highmem=off" crashes the system. Ok, what is the fastest, easiest way to get a workaround to this (if possible)? and have much more RAM available to Linux guest? Best,

2 1

next seL4 TSC meeting on Fri 22 Mar
by Gerwin Klein 20 Mar '24

20 Mar '24

The Technical Steering Committee (TSC) of the seL4 Foundation will hold its next public meting on: - Sydney: Fri, 22 Mar, 6pm - Central Europe: Fri, 22 Mar, 8am - US West Coast (LA/SF): Fri, 22 Mar, 0:00h See also the seL4 calendar feed available from here: https://sel4.systems/contact/home.pml The meeting is by Zoom, and you can join from here: https://unsw.zoom.us/j/83417411537 Anyone interested can join the meeting and listen to the discussion and request to speak, which will be granted if time permits. Only TSC members can vote. The seL4 code of conduct applies to the meeting [1]. The agenda for the meeting so far is: - action items from last meeting - RFC-17: IPI API - RFC-16: PMU (for discussion/feedback, not enough detail yet to vote) - RFC-15: Morello (for discussion/feedback, not enough detail yet to vote) - RFC-14: MCS budget limit thresholds — status? - should we remove deprecated sel4lib functions to enable verification? - steps for next seL4 release - discussion if there is time: - use GitHub discussions instead of discourse? (i.e. retire discourse?) - use GitHub for RFC process? (i.e. retire/archive JIRA?) If there are other items that I missed or you think should be on the agenda, please let me know. If we can't get to an item this time, we can still schedule another meeting. Cheers, Gerwin (TSC chair) [1]: https://docs.sel4.systems/processes/conduct.html _______________________________________________ Devel mailing list -- devel(a)sel4.systems To unsubscribe send an email to devel-leave(a)sel4.systems

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

Devel