Add bpfcompat to Testing in Virtual Environments#155
Merged
Conversation
qmonnet
approved these changes
Jun 30, 2026
qmonnet
left a comment
qmonnet
left a comment
Owner
There was a problem hiding this comment.
Hi, and thanks! Looks useful.
You might want to review the README for bpfcompat - this section in particular should probably be removed: https://github.com/Kernel-Guard/bpfcompat#repository-hygiene
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds bpfcompat under eBPF Workflow: Tools and Utilities → Testing in Virtual Environments.
bpfcompat boots real Linux kernels in disposable QEMU/KVM VMs and load/attach-validates a compiled
.bpf.oinside each, across a multi-distro, multi-arch (5.x–6.x, x86_64 + ARM64) kernel matrix. On failure it classifies the reason (missing BTF, unsupported map/program type, CO-RE relocation) and emits a JSON/Markdown compatibility matrix; it ships as a CI gate and a GitHub Action. Apache-2.0.bcc in a Docker container),- [name](url) - Description.format.npm run ci-lintpasses locally.