ARM physical heap: exclude all identity-mapped memory #2087
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.
The memory range that is identity-mapped during boot is used, among other things, as temporary stack for both the boot processor and the secondary processors; therefore, it should not be included in the physical memory ranges, otherwise a secondary processor can corrupt memory that has been allocated for other kernel uses. This fixes unhandled exceptions that cause boot failures when running the kernel on Azure Standard_D2ps_v5 instances.
In addition, the Azure cloud_init code is being amended to avoid printing a potentially misleading error message if an unsuccessful attempt to connect to the Azure Wire Server is made before the network interface acquires a DHCP address.