-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Remove "ibpb_exit_to_user" from the host-only feature list if Amazon Linux #5473
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
Remove "ibpb_exit_to_user" from the host-only feature list if Amazon Linux #5473
Conversation
1c6127f
to
837abb2
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5473 +/- ##
=======================================
Coverage 82.79% 82.79%
=======================================
Files 263 263
Lines 27223 27223
=======================================
Hits 22538 22538
Misses 4685 4685
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
615948b
to
49eef77
Compare
Our test ubuntu host kernel hasn't backported the patch for VMScape [1]. Remove "ibpb_exit_to_user" from the host-minus-guest feature list only on Intel Cascade Lake that is the one where we run tests for Ubuntu. [1]: torvalds/linux@2f8f173 Signed-off-by: Takahiro Itazuri <[email protected]>
Now Ubuntu 24.04 AMI uses kernel v6.14. Signed-off-by: Takahiro Itazuri <[email protected]>
6cea787
to
1c2c839
Compare
@Manciukic Sorry, I removed a debug-print line. Could I have another look? |
Changes
Remove "ibpb_exit_to_user" from the host-only feature list if not Amazon Linux.
Reason
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
tools/devtool checkbuild --all
to verify that the PR passesbuild checks on all supported architectures.
tools/devtool checkstyle
to verify that the PR passes theautomated style checks.
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 inCHANGELOG.md
.[ ] If a specific issue led to this PR, this PR closes the issue.[ ] When making API changes, I have followed theRunbook for Firecracker API changes.
integration tests.
[ ] I have linked an issue to every newTODO
.rust-vmm
.