Add libbpf-tool profile tests

[mayankfz]

Description

Add libbpf-tool profile tests

Related Issue

Add libbpf-tool profile tests

Type of Change

• Bug fix
• New feature
• Breaking change
• Refactoring
• Documentation update

Checklist

• Description is filled in above
• No credentials, secrets, or internal details are included
• Peer review requested (if not, add required peer reviewers after raising PR)
• Tests executed and results posted below

Test Validation

Key Test Cases:

• verify_bpf_profile_captures_stacks -> profiles dd workload 3s, asserts >2 stack lines
• verify_bpf_profile_stack_filtering ->validates -K (kernel) and -U (user) flags
• verify_bpf_profile_no_resource_leak -> 5 rapid runs, asserts BPF prog count stable
• verify_bpf_profile_handles_edge_cases -> bad PID + target exit mid-profile, no segfault

Impacted LISA Features:

• Adds 4 bpf-profile test cases to LibbpfToolsSuite in lisa/microsoft/testsuites/bpf/libbpf_tools.py

Tested Azure Marketplace Images:

• MicrosoftCBLMariner:azure-linux-3:azure-linux-3:latest

Test Results

Image	VM Size	Result
azure-linux-3:latest (3.20260706.01)	Standard_D2ads_v5	4/4 SKIPPED
azure-linux-3 + sideloaded v0.29.1-5 RPM	Standard_D2ads_v5	4/4 PASSED

[Copilot]

Pull request overview

This PR extends the existing LibbpfToolsSuite with new test coverage for the bpf-profile tool (profiling, stack filtering, resource cleanup, and edge-case handling) to validate libbpf-tools functionality beyond basic install/binary execution checks.

Changes:

• Added helper methods to locate bpf-profile, start a CPU workload, and clean it up.
• Added multiple new bpf-profile test cases covering stack capture, -K/-U filtering, leak checks via bpftool, and edge cases.
• (PR hygiene) The PR description is still the default template placeholders and should be filled in before approval.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 6 comments.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 4 comments.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 11 comments.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 5 comments.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 6 comments.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 9 comments.

Comments suppressed due to low confidence (1)

lisa/microsoft/testsuites/bpf/libbpf_tools.py:411

• 139 and -11 are magic numbers here. Add an inline comment (or use a named constant) to clarify that these exit codes commonly map to SIGSEGV so the intent of this assertion stays clear.

        ).is_not_in(139, -11)
        log.info("Target exit mid-profile handled gracefully")

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 4 comments.

[LiliDeng]

@mayankfz
Is it expected? test image: microsoftcblmariner azure-linux-3 azure-linux-3-gen2 3.20260501.01

[mayankfz]

@mayankfz Is it expected? test image: microsoftcblmariner azure-linux-3 azure-linux-3-gen2 3.20260501.01

Yes @LiliDeng , the update package still needs to be released the changes are under review. So, that is why tested with the copying the package rpm locally as well. For now, it will get skipped if the tool is not present. Have mentioned the same in the description as well. Thanks.

[LiliDeng]

@mayankfz Is it expected? test image: microsoftcblmariner azure-linux-3 azure-linux-3-gen2 3.20260501.01

Yes @LiliDeng , the update package still needs to be released the changes are under review. So, that is why tested with the copying the package rpm locally as well. For now, it will get skipped if the tool is not present. Have mentioned the same in the description as well. Thanks.

Thanks for the explanation.
From the log, I saw package has been installed, but later the command was still not found, do you mean the package is not ready yet, for the future version of the package will work? Then how we know that it is a real package issue?

[mayankfz]

@mayankfz Is it expected? test image: microsoftcblmariner azure-linux-3 azure-linux-3-gen2 3.20260501.01

Yes @LiliDeng , the update package still needs to be released the changes are under review. So, that is why tested with the copying the package rpm locally as well. For now, it will get skipped if the tool is not present. Have mentioned the same in the description as well. Thanks.

Thanks for the explanation. From the log, I saw package has been installed, but later the command was still not found, do you mean the package is not ready yet, for the future version of the package will work? Then how we know that it is a real package issue?

The current libbpf-tools package in the Azure Linux 3 repo (0.29.1-4) does not include the bpf-profile binary, it is being added in version 0.29.1-5, which is still under review. That is why the package installs successfully but the command is not found.

The test handles this gracefully, it checks if bpf-profile is available and skips with a clear message if not. Once the updated package (0.29.1-5) is published to the repo, the test will pick it up automatically without any code changes.
To validate the test logic itself, I sideloaded the locally built RPM on a test VM and confirmed all 4 test cases pass. Thanks.