powerpc/fadump: Do not allow hot-remove memory from fadump reserved area.
authorMahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Mon, 20 Aug 2018 08:17:32 +0000 (13:47 +0530)
committerMichael Ellerman <mpe@ellerman.id.au>
Fri, 21 Dec 2018 00:32:49 +0000 (11:32 +1100)
commit0db6896ff6332ba694f1e61b93ae3b2640317633
tree90958ad084f82e8e72757071fd6387ab22fdd471
parentf86593be1e7f5405b980bb4b11640250ac81d7cb
powerpc/fadump: Do not allow hot-remove memory from fadump reserved area.

For fadump to work successfully there should not be any holes in reserved
memory ranges where kernel has asked firmware to move the content of old
kernel memory in event of crash. Now that fadump uses CMA for reserved
area, this memory area is now not protected from hot-remove operations
unless it is cma allocated. Hence, fadump service can fail to re-register
after the hot-remove operation, if hot-removed memory belongs to fadump
reserved region. To avoid this make sure that memory from fadump reserved
area is not hot-removable if fadump is registered.

However, if user still wants to remove that memory, he can do so by
manually stopping fadump service before hot-remove operation.

Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
arch/powerpc/include/asm/fadump.h
arch/powerpc/kernel/fadump.c
arch/powerpc/platforms/pseries/hotplug-memory.c