mirror of
https://github.com/sched-ext/scx.git
synced 2024-11-25 12:10:24 +00:00
05f5c69747
Use virtme-ng to run the schedulers after they're built; virtme-ng allows to pick an arbitrary sched-ext enabled kernel and run it virtualizing the entire user-space root filesystem, so we can basically exceute the recompiled schedulers inside such kernel. This should allow to catch potential run-time issue in advance (both in the kernel and the schedulers). The sched-ext kernel is taken from the Ubuntu ppa (ppa:arighi/sched-ext) at the moment, since it is the easiest / fastest way to get a precompiled sched-ext kernel to run inside the Ubuntu 22.04 testing environment. The schedulers are tested using the new meson target "test_sched", the specific actions are defined in meson-scripts/test_sched. By default each test has a timeout of 30 sec, after the virtme-ng completes the boot (that should be enough to initialize the scheduler and run the scheduler for some seconds), while the total lifetime of the virtme-ng guest is set to 60 sec, after this time the guest will be killed (this allows to catch potential kernel crashes / hangs). If a single scheduler fails the test, the entire "test_sched" action will be interrupted and the overall test result will be considered a failure. At the moment scx_layered is excluded from the tests, because it requires a special configuration (we should probably pre-generate a default config in the workflow actions and change the scheduler to use the default config if it's executed without any argument). Moreover, scx_flatcg is also temporarily excluded from the tests, because of these known issues: - https://github.com/sched-ext/scx/issues/49 - https://github.com/sched-ext/sched_ext/pull/101 Signed-off-by: Andrea Righi <andrea.righi@canonical.com>
19 lines
983 B
Plaintext
19 lines
983 B
Plaintext
option('bpf_clang', type: 'string', value: 'clang',
|
|
description: 'clang to use when compiling .bpf.c')
|
|
option('bpftool', type: 'string', value: 'bpftool',
|
|
description: 'bpftool to use when generating .bpf.skel.h')
|
|
option('libbpf_a', type: 'string',
|
|
description: 'Static libbpf.a to use')
|
|
option('libbpf_h', type: 'array',
|
|
description: 'libbpf header directories, only meaningful with libbpf_a option')
|
|
option('cargo', type: 'string', value: 'cargo',
|
|
description: 'cargo to use when building rust sub-projects')
|
|
option('cargo_home', type: 'string',
|
|
description: 'CARGO_HOME env to use when invoking cargo')
|
|
option('offline', type: 'boolean', value: 'false',
|
|
description: 'Compilation step should not access the internet')
|
|
option('enable_rust', type: 'boolean', value: 'true',
|
|
description: 'Enable rust sub-projects')
|
|
option('kernel', type: 'string', value: 'vmlinuz',
|
|
description: 'kernel image used to test schedulers')
|