mm: show page state if isolation is failed
authorCho KyongHo <pullip.cho@samsung.com>
Fri, 9 Jun 2017 13:32:44 +0000 (22:32 +0900)
committerCosmin Tanislav <demonsingur@gmail.com>
Mon, 22 Apr 2024 17:23:00 +0000 (20:23 +0300)
commit562e6b5ac4f45bf01e1673bab4b5ac8b3e8d0622
tree5cc4dfddd73b3a56b1878ac349b0f2fa02eea801
parent4348777e112016edf164773ccd147f781410bf04
mm: show page state if isolation is failed

alloc_contig_range() shows the following message to the kernel log if
isolation of the given page ranges has been failed:
"__alloc_contig_range: [8fcd00, 900000) PFNs busy"

But the message provides no information but isolation of some pages in
that range is failed.
If isolation of specific pages is failed repeatedly, we should find
the reason. Identifying the state of pages that are not isolated is
very important to start solving the failure.

Change-Id: I83fa34f9c49989076e1ba20f5b92c570bdd180c0
Signed-off-by: Cho KyongHo <pullip.cho@samsung.com>
mm/page_isolation.c