riscv64/pmap: fix not currently mapped memory being accessed #619
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.
Description
When executing (v)fork, first the memory map is copied and then the new process switches to that map. On risc-v, when mapping new page, cache is invalidated. However, the invalidation may cause page fault when the virtual address is not mapped in the context of currently used memory map. This PR fixes this by switching to the memory map in which the address is mapped, executing the flush/inval and returning to original memory map.
Motivation and Context
Types of changes
How Has This Been Tested?
riscv64-noelv-fpga
Checklist:
Special treatment