sel4bench icon indicating copy to clipboard operation
sel4bench copied to clipboard

sel4 benchmarking applications and support library.

Results 14 sel4bench issues
Sort by recently updated
recently updated
newest added

This addresses parts of https://github.com/seL4/sel4bench/issues/21 and adds a build with clang. The resulting archive gets the suffix `-clang`. For `gcc` builds no suffix is used to avoid breaking any existing...

hw-test

Test with: axel-h/seL4#165

hw-test

The `IRQ` benchmark at `sel4bench/apps/irq` can be removed. It is disabled at the moment as it out of date and does not build. The purpose of this benchmark is to...

Chapter 6 of the seL4 white paper states that the overhead of a round-trip IPC is approximately 720 cycles. Up-to-date performance results listed on the [seL4 Benchmarks page] (https://sel4.systems/About/Performance/) look...

The existing page mapping benchmarks only appear to be implemented for x86 platforms. In this PR, I have extended the benchmarks to work on AARCH64 and fixed a bug with...

New benchmarks for testing VM fault performance - converted some of the tests from seL4test to benchmarks (can later be extended for other types of benchmarks) as well as added...

hw-test

I currently use the seL4bench to test some benchmarks. I use a for loop to evaluate the performance of my benchmark, and the results show that the performance of the...

Hi, Is there any way to print log message in a process created by benchmark_spawn_process? I tried ZF_LOG, benchmark_write, print but none of them worked.

I thought I had seen this building successfully before, but it seems that was not the case. Error message is: ``` In file included from /github/workspace/projects/seL4_libs/libsel4bench/arch_include/arm/armv/armv8-a/sel4bench/armv/private.h:9, from /github/workspace/projects/seL4_libs/libsel4bench/arch_include/arm/armv/armv8-a/sel4bench/armv/sel4bench.h:10, from /github/workspace/projects/seL4_libs/libsel4bench/arch_include/arm/sel4bench/arch/sel4bench.h:12,...

Fault benchmark `apps/fault` fails to build for RISC-V (undefined reference)