linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Jinyang He <hejinyang@loongson.cn>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Use common way to parse elfcorehdr
Date: Wed, 3 Feb 2021 19:28:42 -0800	[thread overview]
Message-ID: <57e74a56-abc1-dbc0-1277-5effb0e4e4c6@infradead.org> (raw)
In-Reply-To: <1612408033-5446-1-git-send-email-hejinyang@loongson.cn>

On 2/3/21 7:07 PM, Jinyang He wrote:
> "elfcorehdr" can be parsed at kernel/crash_dump.c
> 
> Signed-off-by: Jinyang He <hejinyang@loongson.cn>

Hm, looks like that would require CONFIG_CRASH_DUMP?


> ---
>  arch/mips/kernel/setup.c | 49 +++++++++++++++++++++---------------------------
>  1 file changed, 21 insertions(+), 28 deletions(-)
> 
> diff --git a/arch/mips/kernel/setup.c b/arch/mips/kernel/setup.c
> index 7e1f8e2..4d2f915 100644
> --- a/arch/mips/kernel/setup.c
> +++ b/arch/mips/kernel/setup.c
> @@ -29,6 +29,7 @@
>  #include <linux/of_fdt.h>
>  #include <linux/of_reserved_mem.h>
>  #include <linux/dmi.h>
> +#include <linux/crash_dump.h>
>  
>  #include <asm/addrspace.h>
>  #include <asm/bootinfo.h>
> @@ -404,34 +405,32 @@ static int __init early_parse_memmap(char *p)
>  }
>  early_param("memmap", early_parse_memmap);
>  
> -#ifdef CONFIG_PROC_VMCORE
> -static unsigned long setup_elfcorehdr, setup_elfcorehdr_size;
> -static int __init early_parse_elfcorehdr(char *p)
> +static void __init mips_reserve_vmcore(void)
>  {
> +#ifdef CONFIG_PROC_VMCORE
>  	phys_addr_t start, end;
>  	u64 i;
>  
> -	setup_elfcorehdr = memparse(p, &p);
> -
> -	for_each_mem_range(i, &start, &end) {
> -		if (setup_elfcorehdr >= start && setup_elfcorehdr < end) {
> -			/*
> -			 * Reserve from the elf core header to the end of
> -			 * the memory segment, that should all be kdump
> -			 * reserved memory.
> -			 */
> -			setup_elfcorehdr_size = end - setup_elfcorehdr;
> -			break;
> +	if (!elfcorehdr_size) {
> +		for_each_mem_range(i, &start, &end) {
> +			if (elfcorehdr_addr >= start && elfcorehdr_addr < end) {
> +				/*
> +				 * Reserve from the elf core header to the end of
> +				 * the memory segment, that should all be kdump
> +				 * reserved memory.
> +				 */
> +				elfcorehdr_size = end - elfcorehdr_addr;
> +				break;
> +			}
>  		}
>  	}
> -	/*
> -	 * If we don't find it in the memory map, then we shouldn't
> -	 * have to worry about it, as the new kernel won't use it.
> -	 */
> -	return 0;
> -}
> -early_param("elfcorehdr", early_parse_elfcorehdr);
> +
> +	pr_info("Reserving %ldKB of memory at %ldKB for kdump\n",
> +		(unsigned long)elfcorehdr_size >> 10, (unsigned long)elfcorehdr_addr >> 10);
> +
> +	memblock_reserve(elfcorehdr_addr, elfcorehdr_size);
>  #endif
> +}
>  
>  #ifdef CONFIG_KEXEC
>  
> @@ -653,13 +652,7 @@ static void __init arch_mem_init(char **cmdline_p)
>  	 */
>  	memblock_set_current_limit(PFN_PHYS(max_low_pfn));
>  
> -#ifdef CONFIG_PROC_VMCORE
> -	if (setup_elfcorehdr && setup_elfcorehdr_size) {
> -		printk(KERN_INFO "kdump reserved memory at %lx-%lx\n",
> -		       setup_elfcorehdr, setup_elfcorehdr_size);
> -		memblock_reserve(setup_elfcorehdr, setup_elfcorehdr_size);
> -	}
> -#endif
> +	mips_reserve_vmcore();
>  
>  	mips_parse_crashkernel();
>  #ifdef CONFIG_KEXEC
> 


-- 
~Randy


  reply	other threads:[~2021-02-04  3:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04  3:07 [PATCH] MIPS: Use common way to parse elfcorehdr Jinyang He
2021-02-04  3:28 ` Randy Dunlap [this message]
2021-02-04  3:57   ` Jinyang He
2021-02-04  4:01     ` Randy Dunlap
     [not found]       ` <0c36f7e5-ce5d-e2ed-55a0-2f9113ac06bb@loongson.cn>
2021-02-04  4:21         ` Randy Dunlap

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=57e74a56-abc1-dbc0-1277-5effb0e4e4c6@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=hejinyang@loongson.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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).