Skip to content

vmm: warn instead of bailing out on unexpected subleaf for leaf 0xB. #5231

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jun 2, 2025

Conversation

zulinx86
Copy link
Contributor

Changes

Prints a warning message instead of erroring out on unexpected subleaf detected for CPUID leaf 0xB.

Reason

Fixes #5213

License Acceptance

By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following Developer
Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md.

PR Checklist

  • I have read and understand CONTRIBUTING.md.
  • I have run tools/devtool checkstyle to verify that the PR passes the
    automated style checks.
  • I have described what is done in these changes, why they are needed, and
    how they are solving the problem in a clear and encompassing way.
  • [ ] I have updated any relevant documentation (both in code and in the docs)
    in the PR.
  • [ ] I have mentioned all user-facing changes in CHANGELOG.md.
  • If a specific issue led to this PR, this PR closes the issue.
  • [ ] When making API changes, I have followed the
    Runbook for Firecracker API changes.
  • I have tested all new and changed functionalities in unit tests and/or
    integration tests.
  • [ ] I have linked an issue to every new TODO.

  • This functionality cannot be added in rust-vmm.

@zulinx86 zulinx86 added the Status: Awaiting review Indicates that a pull request is ready to be reviewed label May 29, 2025
@zulinx86 zulinx86 enabled auto-merge (rebase) May 29, 2025 08:11
Copy link

codecov bot commented May 29, 2025

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 82.94%. Comparing base (fbf24fe) to head (4a58521).
Report is 2 commits behind head on main.

Files with missing lines Patch % Lines
src/vmm/src/cpu_config/x86_64/cpuid/normalize.rs 0.00% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5231      +/-   ##
==========================================
+ Coverage   82.89%   82.94%   +0.04%     
==========================================
  Files         250      250              
  Lines       26965    26966       +1     
==========================================
+ Hits        22353    22367      +14     
+ Misses       4612     4599      -13     
Flag Coverage Δ
5.10-c5n.metal 83.38% <0.00%> (-0.01%) ⬇️
5.10-m5n.metal 83.38% <0.00%> (+<0.01%) ⬆️
5.10-m6a.metal 82.60% <0.00%> (-0.01%) ⬇️
5.10-m6g.metal 79.22% <ø> (ø)
5.10-m6i.metal 83.38% <0.00%> (+<0.01%) ⬆️
5.10-m7a.metal-48xl 82.58% <0.00%> (?)
5.10-m7g.metal 79.22% <ø> (ø)
5.10-m7i.metal-24xl 83.34% <0.00%> (?)
5.10-m7i.metal-48xl 83.33% <0.00%> (?)
5.10-m8g.metal-24xl 79.21% <ø> (?)
5.10-m8g.metal-48xl 79.22% <ø> (?)
6.1-c5n.metal 83.43% <0.00%> (+<0.01%) ⬆️
6.1-m5n.metal 83.43% <0.00%> (+<0.01%) ⬆️
6.1-m6a.metal 82.64% <0.00%> (-0.01%) ⬇️
6.1-m6g.metal 79.22% <ø> (ø)
6.1-m6i.metal 83.42% <0.00%> (-0.01%) ⬇️
6.1-m7a.metal-48xl 82.63% <0.00%> (?)
6.1-m7g.metal 79.22% <ø> (ø)
6.1-m7i.metal-24xl 83.44% <0.00%> (?)
6.1-m7i.metal-48xl 83.44% <0.00%> (?)
6.1-m8g.metal-24xl 79.21% <ø> (?)
6.1-m8g.metal-48xl 79.21% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

KVM no longer returns any subleaves greater than 0. The patch was merged
in v6.2 and backported to v5.10. So for all our supported kernels,
subleaves >= 2 should not be included [1].

However, we intentionally leave Firecracker not fail for unsupported
kernels to keep working. Note that we can detect KVM regression thanks
to the test that compares a fingerprint with its baseline.

So prints a warning message without bailing out.

[1]: torvalds/linux@45e966f

Signed-off-by: Takahiro Itazuri <[email protected]>
@zulinx86 zulinx86 merged commit 455cf98 into firecracker-microvm:main Jun 2, 2025
5 of 7 checks passed
@zulinx86 zulinx86 deleted the ext_topo_leaf branch June 2, 2025 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Awaiting review Indicates that a pull request is ready to be reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] Unexpected subleaf error in unsupported kernels
3 participants