mirror/libbpf
1
0
Fork 0
mirror of https://github.com/netdata/libbpf.git synced 2026-03-30 05:09:06 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
42baefba714b2cce03fbfd68ecfff507a80adc1d
libbpf/travis-ci/vmtest/prepare_selftests.sh

21 lines
365 B
Bash
Raw Normal View History

vmtest: build and run bpf kernel selftests against various kernels Run kernel selftests in vmtest with the goal to test libbpf backward compatibility with older kernels. The list of kernels should be specified in .travis.yml config in `jobs` section, e.g. KERNEL=5.5.0. Enlisted kernel releases - 5.5.0 # built from main - 5.5.0-rc6 # built from bpf-next - LATEST The kernel specified as 'LATEST' in .travis.yml is built from bpf-next kernel tree, the rest of the kernels are downloaded from the specified in INDEX file. The kernel sources from bpf-next are manually patched with [1] from bpf tree to fix ranqslower build. This workaround should be removed after the patch is merged from bpf to bpf-next tree. Due to kernel sources being checked out the duration of the LATEST kernel test is ~30m. bpf selftests are built from tools/testing/selftests/bpf/ of bpf-next tree with HEAD revision set to CHECKPOINT-COMMIT specified in libbpf so selftests and libbpf are in sync. Currently only programs are tested with test_progs program, test_maps and test_verifier should follow. test_progs are run with blacklist required due to: - some features, e.g. fentry/fexit are not supported in older kernels - environment limitations, e.g an absence of the recent pahole in Debian - incomplete disk image The blacklist is passed to test_progs with -b option as specified in [2] patch set. Most of the preceeding tests are disabled due to incomplete disk image currenly lacking proper networking settings. For the LATEST kernel fome fentry/fexit tests are disabled due to pahole v1.16 is not abailible in Debian yet. Next steps are resolving issues with blacklisted tests, enabling maps and verifier testing, expanding the list of tested kernels. [1] https://lore.kernel.org/bpf/908498f794661c44dca54da9e09dc0c382df6fcb.1580425879.git.hex@fb.com/t.mbox.gz [2] https://www.spinics.net/lists/netdev/msg625192.html
2020-02-12 12:20:53 -08:00
#!/bin/bash
vmtests: add log folding Sprinkle log folds around, including timing. Signed-off-by: Andrii Nakryiko <andriin@fb.com>
2020-08-21 19:06:43 -07:00
set -eu
source $(cd $(dirname $0) && pwd)/helpers.sh
vmtest: #121 follow-ups. Loop increase bpf-next git fetch depth - The previously introduced git fetch depth of bpf-next tree is not sufficient when bpf-next tree is far ahead from libbpf checkpoint commit, so increase the depth up to 128 max. Since 128 may be an overkill for a general case, increase exponentially in a loop until max is reached. - Do not fetch bpf-next twice - Remove setup_example.sh
2020-02-18 18:04:26 -08:00
REPO_PATH=$1
${VMTEST_ROOT}/checkout_latest_kernel.sh ${REPO_PATH}
cd ${REPO_PATH}
if [[ "${KERNEL}" = 'LATEST' ]]; then
vmtests: add log folding Sprinkle log folds around, including timing. Signed-off-by: Andrii Nakryiko <andriin@fb.com>
2020-08-21 19:06:43 -07:00
travis_fold start build_kernel "Kernel build"
vmtest: #121 follow-ups. Loop increase bpf-next git fetch depth - The previously introduced git fetch depth of bpf-next tree is not sufficient when bpf-next tree is far ahead from libbpf checkpoint commit, so increase the depth up to 128 max. Since 128 may be an overkill for a general case, increase exponentially in a loop until max is reached. - Do not fetch bpf-next twice - Remove setup_example.sh
2020-02-18 18:04:26 -08:00
cp ${VMTEST_ROOT}/configs/latest.config .config
make -j $((4*$(nproc))) olddefconfig all
vmtests: add log folding Sprinkle log folds around, including timing. Signed-off-by: Andrii Nakryiko <andriin@fb.com>
2020-08-21 19:06:43 -07:00
travis_fold end build_kernel
vmtest: #121 follow-ups. Loop increase bpf-next git fetch depth - The previously introduced git fetch depth of bpf-next tree is not sufficient when bpf-next tree is far ahead from libbpf checkpoint commit, so increase the depth up to 128 max. Since 128 may be an overkill for a general case, increase exponentially in a loop until max is reached. - Do not fetch bpf-next twice - Remove setup_example.sh
2020-02-18 18:04:26 -08:00
fi
vmtest: build and run bpf kernel selftests against various kernels Run kernel selftests in vmtest with the goal to test libbpf backward compatibility with older kernels. The list of kernels should be specified in .travis.yml config in `jobs` section, e.g. KERNEL=5.5.0. Enlisted kernel releases - 5.5.0 # built from main - 5.5.0-rc6 # built from bpf-next - LATEST The kernel specified as 'LATEST' in .travis.yml is built from bpf-next kernel tree, the rest of the kernels are downloaded from the specified in INDEX file. The kernel sources from bpf-next are manually patched with [1] from bpf tree to fix ranqslower build. This workaround should be removed after the patch is merged from bpf to bpf-next tree. Due to kernel sources being checked out the duration of the LATEST kernel test is ~30m. bpf selftests are built from tools/testing/selftests/bpf/ of bpf-next tree with HEAD revision set to CHECKPOINT-COMMIT specified in libbpf so selftests and libbpf are in sync. Currently only programs are tested with test_progs program, test_maps and test_verifier should follow. test_progs are run with blacklist required due to: - some features, e.g. fentry/fexit are not supported in older kernels - environment limitations, e.g an absence of the recent pahole in Debian - incomplete disk image The blacklist is passed to test_progs with -b option as specified in [2] patch set. Most of the preceeding tests are disabled due to incomplete disk image currenly lacking proper networking settings. For the LATEST kernel fome fentry/fexit tests are disabled due to pahole v1.16 is not abailible in Debian yet. Next steps are resolving issues with blacklisted tests, enabling maps and verifier testing, expanding the list of tested kernels. [1] https://lore.kernel.org/bpf/908498f794661c44dca54da9e09dc0c382df6fcb.1580425879.git.hex@fb.com/t.mbox.gz [2] https://www.spinics.net/lists/netdev/msg625192.html
2020-02-12 12:20:53 -08:00
Reference in New Issue Copy Permalink