Demand paging and fallible memory copy for LVBS#654
Merged
Conversation
d31c159 to
e07d604
Compare
e07d604 to
4eecc49
Compare
sangho2
commented
Feb 11, 2026
added 2 commits
February 11, 2026 17:34
7067977 to
10fb2ee
Compare
10fb2ee to
a17e6d4
Compare
|
🤖 SemverChecks 🤖 Click for details |
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
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 demand paging support for user-space addresses on the LVBS platform, handling user-space page faults from both user-mode and kernel-mode contexts (e.g., syscall handler copying not-yet mapped or invalid user pages using
memcpy_fallible). This PR resolves #637.Changes
memcpy_fallible+ RAIIVtl0MappedGuard;copy_from_vtl0_physuseszerocopy::FromBytesfor memory safetykernel_modefield onExceptionInfoandResumeKernelPlatform/ExceptionFixupvariants onContinueOperation