Aarch64 physical ID heap: fix setting of memory end address #2038
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
In instances where the physical memory start address is fixed to a hardcoded value (such as when instantiating a Qemu "virt" machine type), the memory end address should be calculated from the hardcoded start value instead of from the start of usable memory. This change fixes a "frame 0x00ff800042200800 already full" fatal error caused by a "data abort in el1 write" exception that is triggered when the kernel allocates memory at an address range past the end of physical memory (e.g. when the user process tries to use more memory than available).
eyberg
approved these changes
Jul 7, 2024
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.
In instances where the physical memory start address is fixed to a hard-coded value (such as when instantiating a Qemu "virt" machine type), the memory end address should be calculated from the hard-coded start value instead of from the start of usable memory.
This change fixes a "frame 0x00ff800042200800 already full" fatal error caused by a "data abort in el1 write" exception that is triggered when the kernel allocates memory at an address range past the end of physical memory (e.g. when the user process tries to use more memory than available).