From: Dave Young <dyoung@redhat.com> To: linux-kernel@vger.kernel.org, kexec@lists.infradead.org Cc: Cong Wang <xiyou.wangcong@gmail.com>, Neil Horman <nhorman@redhat.com>, Ingo Molnar <mingo@kernel.org>, "Eric W. Biederman" <ebiederm@xmission.com>, Vivek Goyal <vgoyal@redhat.com>, Tony Luck <tony.luck@intel.com>, Anton Vorontsov <avorontsov@ru.mvista.com>, Michael Ellerman <mpe@ellerman.id.au>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Martin Schwidefsky <schwidefsky@de.ibm.com>, Hari Bathini <hbathini@linux.vnet.ibm.com>, dzickus@redhat.com, bhe@redhat.com, akpm@linux-foundation.org Subject: [PATCH] kdump: add default crashkernel reserve kernel config options Date: Mon, 21 May 2018 10:53:37 +0800 [thread overview] Message-ID: <20180521025337.GA4627@dhcp-128-65.nay.redhat.com> (raw) This is a rework of the crashkernel=auto patches back to 2009 although I'm not sure if below is the last version of the old effort: https://lkml.org/lkml/2009/8/12/61 https://lwn.net/Articles/345344/ I changed the original design, instead of adding the auto reserve logic in code, in this patch just introduce two kernel config options for the default crashkernel value in MB and the threshold of system memory in MB so that only reserve default when system memory is equal or above the threshold. With the kernel configs distributions can easily change the default values so that people do not need to manually set kernel cmdline for common use cases and one can still overwrite the default value with manual setup or disable it by using crashkernel=0 Signed-off-by: Dave Young <dyoung@redhat.com> --- Another difference is with original design the crashkernel size scales with system memory, according to test, large machine may need more memory in kdump kernel because of several factors: 1. cpu numbers, because of the percpu memory allocated for cpus. (kdump can use nr_cpus=1 to workaround this, but some arches do not support nr_cpus=X for example powerpc) 2. IO devices, large system can have a lot of io devices, although we can try to only add those device drivers we needed, it is still a problem because of some built-in drivers, some stacked logical devices eg. device mapper devices, acpi etc. Even if only considering the meta data for driver model it will still be a big number eg. sysfs files etc. 3. The minimum memory requirement for some device drivers are big, even if some of them have implemented low meory profile. It is usual to see 10M memory use for a storage driver. 4. user space initramfs size growing. Busybox is not usable if we need to add udev support and some complicate storage support. Use dracut with systemd, especially networking stuff need more memory. So probably add another kernel config option to scale the memory size eg. CRASHKERNEL_DEFAULT_SCALE_RATIO is also good to have, in RHEL we use base_value + system_mem >> (2^14) for x86. I'm still hesatating how to describe and add this option. Any suggestions will be appreciated. arch/Kconfig | 16 ++++++++++++++++ kernel/crash_core.c | 23 ++++++++++++++++++++++- 2 files changed, 38 insertions(+), 1 deletion(-) --- linux-x86.orig/arch/Kconfig +++ linux-x86/arch/Kconfig @@ -10,6 +10,22 @@ config KEXEC_CORE select CRASH_CORE bool +config CRASHKERNEL_DEFAULT_THRESHOLD_MB + int "System memory size threshold for kdump memory default reserving" + depends on CRASH_CORE + default 0 + help + CRASHKERNEL_DEFAULT_MB is used as default crashkernel value if + the system memory size is equal or bigger than the threshold. + +config CRASHKERNEL_DEFAULT_MB + int "Default crashkernel memory size reserved for kdump" + depends on CRASH_CORE + default 0 + help + This is used as the default kdump reserved memory size in MB. + crashkernel=X kernel cmdline can overwrite this value. + config HAVE_IMA_KEXEC bool --- linux-x86.orig/kernel/crash_core.c +++ linux-x86/kernel/crash_core.c @@ -9,6 +9,7 @@ #include <linux/crash_core.h> #include <linux/utsname.h> #include <linux/vmalloc.h> +#include <linux/sizes.h> #include <asm/page.h> #include <asm/sections.h> @@ -143,6 +144,24 @@ static int __init parse_crashkernel_simp return 0; } +static int __init get_crashkernel_default(unsigned long long system_ram, + unsigned long long *size) +{ + unsigned long long sz = CONFIG_CRASHKERNEL_DEFAULT_MB; + unsigned long long thres = CONFIG_CRASHKERNEL_DEFAULT_THRESHOLD_MB; + + thres *= SZ_1M; + sz *= SZ_1M; + + if (sz >= system_ram || system_ram < thres) { + pr_debug("crashkernel default size can not be used.\n"); + return -EINVAL; + } + *size = sz; + + return 0; +} + #define SUFFIX_HIGH 0 #define SUFFIX_LOW 1 #define SUFFIX_NULL 2 @@ -240,8 +259,10 @@ static int __init __parse_crashkernel(ch *crash_size = 0; *crash_base = 0; - ck_cmdline = get_last_crashkernel(cmdline, name, suffix); + if (!strstr(cmdline, "crashkernel=")) + return get_crashkernel_default(system_ram, crash_size); + ck_cmdline = get_last_crashkernel(cmdline, name, suffix); if (!ck_cmdline) return -EINVAL;
WARNING: multiple messages have this Message-ID (diff)
From: Dave Young <dyoung@redhat.com> To: linux-kernel@vger.kernel.org, kexec@lists.infradead.org Cc: dzickus@redhat.com, Neil Horman <nhorman@redhat.com>, Tony Luck <tony.luck@intel.com>, bhe@redhat.com, Michael Ellerman <mpe@ellerman.id.au>, Hari Bathini <hbathini@linux.vnet.ibm.com>, "Eric W. Biederman" <ebiederm@xmission.com>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Martin Schwidefsky <schwidefsky@de.ibm.com>, Cong Wang <xiyou.wangcong@gmail.com>, akpm@linux-foundation.org, Anton Vorontsov <avorontsov@ru.mvista.com>, Ingo Molnar <mingo@kernel.org>, Vivek Goyal <vgoyal@redhat.com> Subject: [PATCH] kdump: add default crashkernel reserve kernel config options Date: Mon, 21 May 2018 10:53:37 +0800 [thread overview] Message-ID: <20180521025337.GA4627@dhcp-128-65.nay.redhat.com> (raw) This is a rework of the crashkernel=auto patches back to 2009 although I'm not sure if below is the last version of the old effort: https://lkml.org/lkml/2009/8/12/61 https://lwn.net/Articles/345344/ I changed the original design, instead of adding the auto reserve logic in code, in this patch just introduce two kernel config options for the default crashkernel value in MB and the threshold of system memory in MB so that only reserve default when system memory is equal or above the threshold. With the kernel configs distributions can easily change the default values so that people do not need to manually set kernel cmdline for common use cases and one can still overwrite the default value with manual setup or disable it by using crashkernel=0 Signed-off-by: Dave Young <dyoung@redhat.com> --- Another difference is with original design the crashkernel size scales with system memory, according to test, large machine may need more memory in kdump kernel because of several factors: 1. cpu numbers, because of the percpu memory allocated for cpus. (kdump can use nr_cpus=1 to workaround this, but some arches do not support nr_cpus=X for example powerpc) 2. IO devices, large system can have a lot of io devices, although we can try to only add those device drivers we needed, it is still a problem because of some built-in drivers, some stacked logical devices eg. device mapper devices, acpi etc. Even if only considering the meta data for driver model it will still be a big number eg. sysfs files etc. 3. The minimum memory requirement for some device drivers are big, even if some of them have implemented low meory profile. It is usual to see 10M memory use for a storage driver. 4. user space initramfs size growing. Busybox is not usable if we need to add udev support and some complicate storage support. Use dracut with systemd, especially networking stuff need more memory. So probably add another kernel config option to scale the memory size eg. CRASHKERNEL_DEFAULT_SCALE_RATIO is also good to have, in RHEL we use base_value + system_mem >> (2^14) for x86. I'm still hesatating how to describe and add this option. Any suggestions will be appreciated. arch/Kconfig | 16 ++++++++++++++++ kernel/crash_core.c | 23 ++++++++++++++++++++++- 2 files changed, 38 insertions(+), 1 deletion(-) --- linux-x86.orig/arch/Kconfig +++ linux-x86/arch/Kconfig @@ -10,6 +10,22 @@ config KEXEC_CORE select CRASH_CORE bool +config CRASHKERNEL_DEFAULT_THRESHOLD_MB + int "System memory size threshold for kdump memory default reserving" + depends on CRASH_CORE + default 0 + help + CRASHKERNEL_DEFAULT_MB is used as default crashkernel value if + the system memory size is equal or bigger than the threshold. + +config CRASHKERNEL_DEFAULT_MB + int "Default crashkernel memory size reserved for kdump" + depends on CRASH_CORE + default 0 + help + This is used as the default kdump reserved memory size in MB. + crashkernel=X kernel cmdline can overwrite this value. + config HAVE_IMA_KEXEC bool --- linux-x86.orig/kernel/crash_core.c +++ linux-x86/kernel/crash_core.c @@ -9,6 +9,7 @@ #include <linux/crash_core.h> #include <linux/utsname.h> #include <linux/vmalloc.h> +#include <linux/sizes.h> #include <asm/page.h> #include <asm/sections.h> @@ -143,6 +144,24 @@ static int __init parse_crashkernel_simp return 0; } +static int __init get_crashkernel_default(unsigned long long system_ram, + unsigned long long *size) +{ + unsigned long long sz = CONFIG_CRASHKERNEL_DEFAULT_MB; + unsigned long long thres = CONFIG_CRASHKERNEL_DEFAULT_THRESHOLD_MB; + + thres *= SZ_1M; + sz *= SZ_1M; + + if (sz >= system_ram || system_ram < thres) { + pr_debug("crashkernel default size can not be used.\n"); + return -EINVAL; + } + *size = sz; + + return 0; +} + #define SUFFIX_HIGH 0 #define SUFFIX_LOW 1 #define SUFFIX_NULL 2 @@ -240,8 +259,10 @@ static int __init __parse_crashkernel(ch *crash_size = 0; *crash_base = 0; - ck_cmdline = get_last_crashkernel(cmdline, name, suffix); + if (!strstr(cmdline, "crashkernel=")) + return get_crashkernel_default(system_ram, crash_size); + ck_cmdline = get_last_crashkernel(cmdline, name, suffix); if (!ck_cmdline) return -EINVAL; _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2018-05-21 2:53 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-21 2:53 Dave Young [this message] 2018-05-21 2:53 ` [PATCH] kdump: add default crashkernel reserve kernel config options Dave Young 2018-05-21 19:02 ` Andrew Morton 2018-05-21 19:02 ` Andrew Morton 2018-05-22 1:43 ` Dave Young 2018-05-22 1:43 ` Dave Young 2018-05-22 1:48 ` Dave Young 2018-05-22 1:48 ` Dave Young 2018-05-23 7:06 ` Dave Young 2018-05-23 7:06 ` Dave Young 2018-05-23 15:53 ` Eric W. Biederman 2018-05-23 15:53 ` Eric W. Biederman 2018-05-23 20:22 ` Petr Tesarik 2018-05-23 20:22 ` Petr Tesarik 2018-05-24 1:49 ` Dave Young 2018-05-24 1:49 ` Dave Young 2018-05-24 6:57 ` Petr Tesarik 2018-05-24 6:57 ` Petr Tesarik 2018-05-24 7:26 ` Dave Young 2018-05-24 7:26 ` Dave Young 2018-05-24 7:39 ` Dave Young 2018-05-24 7:39 ` Dave Young 2018-05-24 7:56 ` Dave Young 2018-05-24 7:56 ` Dave Young 2018-05-24 8:29 ` Baoquan He 2018-05-24 8:29 ` Baoquan He 2018-05-24 9:02 ` Petr Tesarik 2018-05-24 9:02 ` Petr Tesarik 2018-05-24 7:31 ` Baoquan He 2018-05-24 7:31 ` Baoquan He 2018-05-24 16:34 ` Eric W. Biederman 2018-05-24 16:34 ` Eric W. Biederman 2018-05-25 4:59 ` Petr Tesarik 2018-05-25 4:59 ` Petr Tesarik 2018-05-25 20:00 ` Eric W. Biederman 2018-05-25 20:00 ` Eric W. Biederman 2018-05-28 12:34 ` Petr Tesarik 2018-05-28 12:34 ` Petr Tesarik 2018-05-29 12:19 ` Eric W. Biederman 2018-05-29 12:19 ` Eric W. Biederman 2018-05-24 1:42 ` Dave Young 2018-05-24 1:42 ` Dave Young 2018-05-24 16:41 ` Eric W. Biederman 2018-05-24 16:41 ` Eric W. Biederman 2018-05-25 2:43 ` Dave Young 2018-05-25 2:43 ` Dave Young
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20180521025337.GA4627@dhcp-128-65.nay.redhat.com \ --to=dyoung@redhat.com \ --cc=akpm@linux-foundation.org \ --cc=avorontsov@ru.mvista.com \ --cc=benh@kernel.crashing.org \ --cc=bhe@redhat.com \ --cc=dzickus@redhat.com \ --cc=ebiederm@xmission.com \ --cc=hbathini@linux.vnet.ibm.com \ --cc=kexec@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=mpe@ellerman.id.au \ --cc=nhorman@redhat.com \ --cc=schwidefsky@de.ibm.com \ --cc=tony.luck@intel.com \ --cc=vgoyal@redhat.com \ --cc=xiyou.wangcong@gmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.