Hypervisor memory range may be overlapped by runtime allocated resources #8738
Labels
status: new
The issue status: new for creation
Comments
jiaqingz-intel
added a commit
to jiaqingz-intel/acrn-hypervisor
that referenced
this issue
Sep 25, 2024
The hypervisor image size is determined at link time, but now it is calculated and stored in a global variable during mmu initialization, and the helper function reads from that variable. Change to calculate it inside helper function to avoid inconsistency. Tracked-On: projectacrn#8738 Signed-off-by: Jiaqing Zhao <[email protected]> Reviewed-by: Fei Li <[email protected]>
jiaqingz-intel
added a commit
to jiaqingz-intel/acrn-hypervisor
that referenced
this issue
Sep 25, 2024
Mark hypervisor memory region as unusable in its e820 table to avoid being overlapped by e820_alloc_memory(). As it is already filtered out in hypervisor e820 table, there is no longer need to filter it out in service VM e820. Tracked-On: projectacrn#8738 Signed-off-by: Jiaqing Zhao <[email protected]> Reviewed-by: Fei Li <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: