On 08/03/2016 07:20 AM, Balbir Singh wrote:
On Tue, 2016-08-02 at 18:49 +0530, Srikar Dronamraju wrote:
Fadump kernel reserves significant number of memory blocks. On a multi-node
machine, with CONFIG_DEFFERRED_STRUCT_PAGE support, fadump kernel fails to
boot. Fix this by disabling deferred page struct initialisation.
How much memory does a fadump kernel need? Can we bump up the limits depending
on the config. I presume when you say fadump kernel you mean kernel with
FADUMP in the config?
BTW, I would much rather prefer a config based solution that does not select
DEFERRED_INIT if FADUMP is enabled.
IIRC the kdump/fadump kernel is typically the same vmlinux as the main
kernel, just with special initrd and boot params. So if you want
deferred init for the main kernel, this would be impractical.
Balbir
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>