Devel October 2014

devel@sel4.systems

20 participants
15 discussions

x86 Bootable USB install
by Matthew Scaperoth 14 Oct '14

14 Oct '14

Hello, I am at the George Washington University working on benchmarking the seL4 system. I am new to systems, and I am having a hard time building a bootable USB image On Ubuntu 14.04 x86. I understand that there is a Grub2 stanza on the Downloads page <https://sel4.systems/Download/> on the SeL4 website, but I cannot find the sel4kernel and sel4rootserver files in the system to build into a boot image. I would like to build an image using a process similar to the one in Pistachio (see https://www.l4ka.org/120.php) except for using Grub2 of course. Are there instructions for booting on full hardware such as a PC? Regards, Matthew Scaperoth Jr. Programmer Analyst The George Washington University Academic Technologies Tel: 202-994-6907

5 7

How is the sel4test-driver process created?
by Yuxin Ren 14 Oct '14

14 Oct '14

Hi All, Now I am working on sel4test project. I know there is a process for sel4test-driver, and it will spawn new process which does the actual testing. But I want to know how the sel4test-driver process is created, especially how its memory and capability is set up. Could anyone show me the code for those stuff and it is great if give me some explanation or comments about it? Thank you very much Yuxin

4 3

Console Output for Test Files in seL4test-manifest?
by Matthew Scaperoth 12 Oct '14

12 Oct '14

Hey All, First, thank you for your responses so far. This message board has been helpful with learning seL4. While we have been working to benchmark the seL4 system on bare metal we have run into some trouble trying to figure out how to get output to the console instead of serial. For our tests we are using the existing seL4test-manifest files and defining custom tests within the apps/sel4test-tests/src/tests/ipc.c file. We noticed that the test output will only go to serial. We have tested with and without the debug configuration. We would like to see all output go to console. We have tried to remove debug defines on the system call path for __arch_putchar() which seems to only affect the serial output. These system calls don't seem to affect the direction of the output, but only what is being output to serial. Is there a driver missing from the test libraries that defines the console output? Is there a specific way to output to console when working with tests. To test these settings we are working with a 32-bit build and are using syslinux to create a bootable USB to test on bare metal. Regards, Matthew Scaperoth Jr. Programmer Analyst The George Washington University Academic Technologies Tel: 202-994-6907

2 1

Is this path wrong?
by Harry Butterworth 05 Oct '14

05 Oct '14

diff --git a/lib/WPTutorial.thy b/lib/WPTutorial.thy index f6ecd0a..cd0d992 100644 --- a/lib/WPTutorial.thy +++ b/lib/WPTutorial.thy @@ -9,7 +9,7 @@ *) theory WPTutorial -imports Bits_R +imports "../proof/refine/Bits_R" begin text {*

1 0

Error in comment in abstract spec Syscall_A.thy
by Harry Butterworth 05 Oct '14

05 Oct '14

diff --git a/spec/abstract/Syscall_A.thy b/spec/abstract/Syscall_A.thy index e308501..6576f78 100644 --- a/spec/abstract/Syscall_A.thy +++ b/spec/abstract/Syscall_A.thy @@ -72,7 +72,7 @@ occured in the first operation); this second operation may result in an error; \item the error handler @{text h_error} to execute if the second operation resulted in an error; -\item the third and last operation @{text h_error} to execute (if +\item the third and last operation @{text m_finalise} to execute (if no error occured in the second operation); this operation may be interrupted. \end{itemize}

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

Devel October 2014