From: Dave Young <dyoung@redhat.com>
To: Hari Bathini <hbathini@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, fenghua.yu@intel.com,
tony.luck@intel.com, linux-ia64@vger.kernel.org,
kexec@lists.infradead.org,
Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>,
ebiederm@xmission.com, Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org, vgoyal@redhat.com
Subject: Re: [PATCH v4 1/5] crash: move crashkernel parsing and vmcore related code under CONFIG_CRASH_CORE
Date: Fri, 6 Jan 2017 10:02:03 +0800 [thread overview]
Message-ID: <20170106020203.GA2863@dhcp-128-65.nay.redhat.com> (raw)
In-Reply-To: <148363734065.11570.16982557619253687714.stgit@hbathini.in.ibm.com>
Hi Hari
Thanks for the update.
On 01/05/17 at 10:59pm, Hari Bathini wrote:
> Traditionally, kdump is used to save vmcore in case of a crash. Some
> architectures like powerpc can save vmcore using architecture specific
> support instead of kexec/kdump mechanism. Such architecture specific
> support also needs to reserve memory, to be used by dump capture kernel.
> crashkernel parameter can be a reused, for memory reservation, by such
> architecture specific infrastructure.
>
> But currently, code related to vmcoreinfo and parsing of crashkernel
> parameter is built under CONFIG_KEXEC_CORE. This patch introduces
> CONFIG_CRASH_CORE and moves the above mentioned code under this config,
> allowing code reuse without dependency on CONFIG_KEXEC. There is no
> functional change with this patch.
>
> Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
> ---
>
> Changes from v3:
> * Renamed log_buf_kexec_setup()to log_buf_vmcoreinfo_setup() instead of
> log_buf_crash_setup().
>
> Changes from v2:
> * Used CONFIG_CRASH_CORE instead of CONFIG_KEXEC_CORE at
> appropriate places in printk and ksysfs.
>
>
> arch/Kconfig | 4
> include/linux/crash_core.h | 65 ++++++
> include/linux/kexec.h | 57 ------
> include/linux/printk.h | 4
> kernel/Makefile | 1
> kernel/crash_core.c | 445 ++++++++++++++++++++++++++++++++++++++++++++
> kernel/kexec_core.c | 404 ----------------------------------------
> kernel/ksysfs.c | 8 +
> kernel/printk/printk.c | 6 -
> 9 files changed, 531 insertions(+), 463 deletions(-)
> create mode 100644 include/linux/crash_core.h
> create mode 100644 kernel/crash_core.c
>
[snip]
Acked-by: Dave Young <dyoung@redhat.com>
Thanks
Dave
next prev parent reply other threads:[~2017-01-06 2:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 17:28 [PATCH v4 0/5] kexec/fadump: remove dependency with CONFIG_KEXEC and reuse crashkernel parameter for fadump Hari Bathini
2017-01-05 17:29 ` [PATCH v4 1/5] crash: move crashkernel parsing and vmcore related code under CONFIG_CRASH_CORE Hari Bathini
2017-01-06 2:02 ` Dave Young [this message]
2017-03-23 15:54 ` Hari Bathini
2017-01-05 17:31 ` [PATCH v4 2/5] ia64: reuse append_elf_note() and final_note() functions Hari Bathini
2017-01-06 2:03 ` Dave Young
2017-01-17 17:06 ` Hari Bathini
2017-01-24 18:11 ` Hari Bathini
2017-01-24 18:23 ` Tony Luck
2017-01-25 19:15 ` Hari Bathini
2017-01-31 22:21 ` Tony Luck
2017-02-01 1:11 ` Michael Ellerman
2017-01-20 5:47 ` Michael Ellerman
2017-01-24 18:08 ` Hari Bathini
2017-01-05 17:32 ` [PATCH v4 3/5] powerpc/fadump: remove dependency with CONFIG_KEXEC Hari Bathini
2017-01-13 11:27 ` Mahesh Jagannath Salgaonkar
2017-01-05 17:32 ` [PATCH v4 4/5] powerpc/fadump: reuse crashkernel parameter for fadump memory reservation Hari Bathini
2017-01-13 11:51 ` Mahesh Jagannath Salgaonkar
2017-01-05 17:32 ` [PATCH v4 5/5] powerpc/fadump: update documentation about crashkernel parameter reuse Hari Bathini
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=20170106020203.GA2863@dhcp-128-65.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=fenghua.yu@intel.com \
--cc=hbathini@linux.vnet.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=tony.luck@intel.com \
--cc=vgoyal@redhat.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).