mm/memory hotplug/unplug: Fix zone going non-contiguous after new memory is plugged #1
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.
when new memory is plugged, set_zone_contiguous will never set the zone as contiguous, because the memory section of the newly plugged memory is still offline during the zone contiguity check.
if the memory section of the pfn is offline, __pageblock_pfn_to_page cannot return a page for that pfn, causing set_zone_contiguous to skip setting zone->contiguous.
The fix is to move set_zone_contiguous after online_mem_sections, ensuring that the newly plugged memory is already onlined before the set_zone_contiguous.
Reviewed-by: Tianyou Li tianyou.li@intel.com
Reviewed-by: Nanhai Zou nanhai.zou@intel.com
Signed-off-by: Liu, Yuan1 yuan1.liu@intel.com