-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Fix fast_page_fault_helper crashing instead of causing page faults #5054
Merged
+122
−123
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5054 +/- ##
=======================================
Coverage 83.19% 83.19%
=======================================
Files 247 247
Lines 26641 26641
=======================================
Hits 22163 22163
Misses 4478 4478
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
ShadowCurse
reviewed
Feb 27, 2025
Add spaces before parenthesis Suggested-by: Babis Chalios <[email protected]> Signed-off-by: Patrick Roy <[email protected]>
mmap should never fail, but having the check for failure after the memset is just wrong. Signed-off-by: Patrick Roy <[email protected]>
-1 wraps around to 255, which in case of commands executed over SSH clashes with SSH defined return codes. Signed-off-by: Patrick Roy <[email protected]>
Without calling sigprocmask, the SIGUSR1 that we're using will actually just kill the process instead of waking it up, as sigwait can only be used to wait for _pending_ signals, but signals are only marked as pending if they're blocked by a signal mask. If they're not blocked, they will instead call signal handlers, which will in this case just kill the process. This does mean that this program never worked the intended way, which also kinda proves it was not needed to show the different in page faults between huge pages and normal pages (test_ept_violation_count). Signed-off-by: Patrick Roy <[email protected]>
Currently, all tests that want to make use of UFFD import UFFD related functions from test_uffd.py. That's a bit awkward, so move them into their own utility module. Signed-off-by: Patrick Roy <[email protected]>
There's really no use in having this be a fixture, it's just a dictionary - it used to be a fixture because we were building the binaries inside of the test framework (and so each call to it as a function would trigger compilations), but now that we pre-compile everything that's no longer something to worry about. Signed-off-by: Patrick Roy <[email protected]>
4fb84a3
to
febb888
Compare
ShadowCurse
approved these changes
Feb 27, 2025
kalyazin
approved these changes
Feb 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Make page fault helper used in test_ept_violation_count actually cause page faults post restore. Currently, it is just crashing because the signal that is supposed to wake it up is actually killing it, due to no signal mask being installed.
Surrounded by a few refactors/fixes that came from me working on a page fault latency test before realizing that my approach was fundamentally flawed and I had to throw most of it away.
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 checkstyle
to verify that the PR passes theautomated style checks.
how they are solving the problem in a clear and encompassing way.
in the PR.
CHANGELOG.md
.Runbook for Firecracker API changes.
integration tests.
TODO
.rust-vmm
.