patches: Prefault page tables used in stacks allocated for threads #73
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.
We need to explicitly populate the page tables allocated for stacks (via mmap's
MAP_POPULATE
flag) in order to avoid infinite page fault loops during runtime. This measure is necessary since Unikraft on AArch64 does not switch stacks when handling CPU exceptions. A page fault occuring on the stack would cause the trap handler to save all the registers on the same stack, thus generating another page fault, ad infinitum.This PR is part of a larger series which provides support for Golang on ARM64 platforms: