pmm: fix initial physical memory frames processing #46
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
It is important to assign initial 4K and 2M frames to the front of available frames list. Initial virtual memory mapping is small and the first frames are being used by pagetables initialization. Always consume entire region of physical memory by adding tailing 4K frames till the end of the region. Detect properly incorrectly processed regions and panic with some details for debugging. Signed-off-by: Pawel Wieczorkiewicz <[email protected]>
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.
It is important to assign initial 4K and 2M frames to the front of
available frames list. Initial virtual memory mapping is small and
the first frames are being used by pagetables initialization.
Always consume entire region of physical memory by adding tailing 4K
frames till the end of the region.
Detect properly incorrectly processed regions and panic with some
details for debugging.
Signed-off-by: Pawel Wieczorkiewicz [email protected]
*Issue #35
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.