All of lore.kernel.org
 help / color / mirror / Atom feed
From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Geoff Levand <geoff@infradead.org>
Cc: catalin.marinas@arm.com, will.deacon@arm.com,
	james.morse@arm.com, linux-arm-kernel@lists.infradead.org,
	kexec@lists.infradead.org
Subject: Re: [PATCH v21 4/8] arm64: kdump: add kdump support
Date: Thu, 7 Jul 2016 09:49:43 +0900	[thread overview]
Message-ID: <20160707004942.GV20774@linaro.org> (raw)
In-Reply-To: <1467826689.8880.39.camel@infradead.org>

On Wed, Jul 06, 2016 at 10:38:09AM -0700, Geoff Levand wrote:
> On Wed, 2016-07-06 at 16:52 +0900, AKASHI Takahiro wrote:
> > --- a/arch/arm64/mm/init.c
> > +++ b/arch/arm64/mm/init.c
> > @@ -136,6 +137,57 @@ static void __init reserve_crashkernel(void)
> >  }
> >  #endif /* CONFIG_KEXEC_CORE */
> >  
> > +#ifdef CONFIG_CRASH_DUMP
> > +static int __init early_init_dt_scan_elfcorehdr(unsigned long node,
> > +> 	> 	> const char *uname, int depth, void *data)
> > +{
> > +> 	> const __be32 *reg;
> > +> 	> int len;
> > +
> > +> 	> if (depth != 1 || strcmp(uname, "chosen") != 0)
> > +> 	> 	> return 0;
> > +
> > +> 	> reg = of_get_flat_dt_prop(node, "linux,elfcorehdr", &len);
> > +> 	> if (!reg || (len < (dt_root_addr_cells + dt_root_size_cells)))
> > +> 	> 	> return 1;
> > +
> > +> 	> elfcorehdr_addr = dt_mem_next_cell(dt_root_addr_cells, ??);
> > +> 	> elfcorehdr_size = dt_mem_next_cell(dt_root_size_cells, ??);
> > +
> > +> 	> return 1;
> > +}
> > +
> > +/*
> > + * reserve_elfcorehdr() - reserves memory for elf core header
> > + *
> > + * This function reserves elf core header given in "elfcorehdr=" kernel
> > + * command line parameter. This region contains all the information about
> > + * primary kernel's core image and is used by a dump capture kernel to
> > + * access the system memory on primary kernel.
> > + */
> > +static void __init reserve_elfcorehdr(void)
> > +{
> 
> It seems like you could get rid of all these conditionals by
> just putting this here:
> 
> 	if (!IS_ENABLED(CONFIG_CRASH_DUMP))
> 		return;

Add this to reserve_elfcorehdr()?
Unfortunately, it won't work because this function accesses
elfcorehdr_addr & elfcorehdr_size which are defined only
if CONFIG_CRASH_DUMP.

Thanks,
-Takahiro AKASHI

> 
> > +> 	> of_scan_flat_dt(early_init_dt_scan_elfcorehdr, NULL);
> > +
> > +> 	> if (!elfcorehdr_size)
> > +> 	> 	> return;
> > +
> > +> 	> if (memblock_is_region_reserved(elfcorehdr_addr, elfcorehdr_size)) {
> > +> 	> 	> pr_warn("elfcorehdr is overlapped\n");
> > +> 	> 	> return;
> > +> 	> }
> > +
> > +> 	> memblock_reserve(elfcorehdr_addr, elfcorehdr_size);
> > +
> > +> 	> pr_info("Reserving %lldKB of memory at 0x%llx for elfcorehdr\n",
> > +> 	> 	> elfcorehdr_size >> 10, elfcorehdr_addr);
> > +}
> > +#else
> > +static void __init reserve_elfcorehdr(void)
> > +{
> > +> 	> ;
> > +}
> > +#endif /* CONFIG_CRASH_DUMP */
> >  /*
> >   * Return the maximum physical address for ZONE_DMA (DMA_BIT_MASK(32)). It
> >   * currently assumes that for memory starting above 4G, 32-bit devices will
> > @@ -389,6 +441,8 @@ void __init arm64_memblock_init(void)
> >  
> >  > 	> reserve_crashkernel();
> >  
> > +> 	> reserve_elfcorehdr();
> > +
> >  > 	> early_init_fdt_scan_reserved_mem();
> >  
> >  > 	> /* 4GB maximum for 32-bit only capable devices */
> 

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: takahiro.akashi@linaro.org (AKASHI Takahiro)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v21 4/8] arm64: kdump: add kdump support
Date: Thu, 7 Jul 2016 09:49:43 +0900	[thread overview]
Message-ID: <20160707004942.GV20774@linaro.org> (raw)
In-Reply-To: <1467826689.8880.39.camel@infradead.org>

On Wed, Jul 06, 2016 at 10:38:09AM -0700, Geoff Levand wrote:
> On Wed, 2016-07-06 at 16:52 +0900, AKASHI Takahiro wrote:
> > --- a/arch/arm64/mm/init.c
> > +++ b/arch/arm64/mm/init.c
> > @@ -136,6 +137,57 @@ static void __init reserve_crashkernel(void)
> >  }
> >  #endif /* CONFIG_KEXEC_CORE */
> >  
> > +#ifdef CONFIG_CRASH_DUMP
> > +static int __init early_init_dt_scan_elfcorehdr(unsigned long node,
> > +> 	> 	> const char *uname, int depth, void *data)
> > +{
> > +> 	> const __be32 *reg;
> > +> 	> int len;
> > +
> > +> 	> if (depth != 1 || strcmp(uname, "chosen") != 0)
> > +> 	> 	> return 0;
> > +
> > +> 	> reg = of_get_flat_dt_prop(node, "linux,elfcorehdr", &len);
> > +> 	> if (!reg || (len < (dt_root_addr_cells + dt_root_size_cells)))
> > +> 	> 	> return 1;
> > +
> > +> 	> elfcorehdr_addr = dt_mem_next_cell(dt_root_addr_cells, ??);
> > +> 	> elfcorehdr_size = dt_mem_next_cell(dt_root_size_cells, ??);
> > +
> > +> 	> return 1;
> > +}
> > +
> > +/*
> > + * reserve_elfcorehdr() - reserves memory for elf core header
> > + *
> > + * This function reserves elf core header given in "elfcorehdr=" kernel
> > + * command line parameter. This region contains all the information about
> > + * primary kernel's core image and is used by a dump capture kernel to
> > + * access the system memory on primary kernel.
> > + */
> > +static void __init reserve_elfcorehdr(void)
> > +{
> 
> It seems like you could get rid of all these conditionals by
> just putting this here:
> 
> 	if (!IS_ENABLED(CONFIG_CRASH_DUMP))
> 		return;

Add this to reserve_elfcorehdr()?
Unfortunately, it won't work because this function accesses
elfcorehdr_addr & elfcorehdr_size which are defined only
if CONFIG_CRASH_DUMP.

Thanks,
-Takahiro AKASHI

> 
> > +> 	> of_scan_flat_dt(early_init_dt_scan_elfcorehdr, NULL);
> > +
> > +> 	> if (!elfcorehdr_size)
> > +> 	> 	> return;
> > +
> > +> 	> if (memblock_is_region_reserved(elfcorehdr_addr, elfcorehdr_size)) {
> > +> 	> 	> pr_warn("elfcorehdr is overlapped\n");
> > +> 	> 	> return;
> > +> 	> }
> > +
> > +> 	> memblock_reserve(elfcorehdr_addr, elfcorehdr_size);
> > +
> > +> 	> pr_info("Reserving %lldKB of memory at 0x%llx for elfcorehdr\n",
> > +> 	> 	> elfcorehdr_size >> 10, elfcorehdr_addr);
> > +}
> > +#else
> > +static void __init reserve_elfcorehdr(void)
> > +{
> > +> 	> ;
> > +}
> > +#endif /* CONFIG_CRASH_DUMP */
> >  /*
> >   * Return the maximum physical address for ZONE_DMA (DMA_BIT_MASK(32)). It
> >   * currently assumes that for memory starting above 4G, 32-bit devices will
> > @@ -389,6 +441,8 @@ void __init arm64_memblock_init(void)
> >  
> >  > 	> reserve_crashkernel();
> >  
> > +> 	> reserve_elfcorehdr();
> > +
> >  > 	> early_init_fdt_scan_reserved_mem();
> >  
> >  > 	> /* 4GB maximum for 32-bit only capable devices */
> 

  reply	other threads:[~2016-07-07  0:44 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06  7:52 [PATCH v21 0/8] arm64: kdump support AKASHI Takahiro
2016-07-06  7:52 ` AKASHI Takahiro
2016-07-06  7:52 ` [PATCH v21 1/8] arm64: kdump: reserve memory for crash dump kernel AKASHI Takahiro
2016-07-06  7:52   ` AKASHI Takahiro
2016-07-06 17:00   ` Geoff Levand
2016-07-06 17:00     ` Geoff Levand
2016-07-07  0:19     ` AKASHI Takahiro
2016-07-07  0:19       ` AKASHI Takahiro
2016-07-06 18:11   ` Thiago Jung Bauermann
2016-07-06 18:11     ` Thiago Jung Bauermann
2016-07-07  1:17     ` AKASHI Takahiro
2016-07-07  1:17       ` AKASHI Takahiro
2016-07-06  7:52 ` [PATCH v21 2/8] arm64: limit memory regions based on DT property, usable-memory AKASHI Takahiro
2016-07-06  7:52   ` AKASHI Takahiro
2016-07-06 17:48   ` Geoff Levand
2016-07-06 17:48     ` Geoff Levand
2016-07-06  7:52 ` [PATCH v21 3/8] arm64: kdump: implement machine_crash_shutdown() AKASHI Takahiro
2016-07-06  7:52   ` AKASHI Takahiro
2016-07-06 17:28   ` Geoff Levand
2016-07-06 17:28     ` Geoff Levand
2016-07-07  0:43     ` AKASHI Takahiro
2016-07-07  0:43       ` AKASHI Takahiro
2016-07-07 16:42       ` Geoff Levand
2016-07-07 16:42         ` Geoff Levand
2016-07-06  7:52 ` [PATCH v21 4/8] arm64: kdump: add kdump support AKASHI Takahiro
2016-07-06  7:52   ` AKASHI Takahiro
2016-07-06 17:38   ` Geoff Levand
2016-07-06 17:38     ` Geoff Levand
2016-07-07  0:49     ` AKASHI Takahiro [this message]
2016-07-07  0:49       ` AKASHI Takahiro
2016-07-06  7:52 ` [PATCH v21 5/8] arm64: kdump: add VMCOREINFO's for user-space coredump tools AKASHI Takahiro
2016-07-06  7:52   ` AKASHI Takahiro
2016-07-06  7:52 ` [PATCH v21 6/8] arm64: kdump: enable kdump in the arm64 defconfig AKASHI Takahiro
2016-07-06  7:52   ` AKASHI Takahiro
2016-07-06  7:52 ` [PATCH v21 7/8] arm64: kdump: update a kernel doc AKASHI Takahiro
2016-07-06  7:52   ` AKASHI Takahiro
2016-07-06 17:44   ` Geoff Levand
2016-07-06 17:44     ` Geoff Levand
2016-07-07  0:51     ` AKASHI Takahiro
2016-07-07  0:51       ` AKASHI Takahiro
2016-07-06  7:52 ` [PATCH v21 8/8] Documentation: dt: usable-memory and elfcorehdr nodes for arm64 kexec AKASHI Takahiro
2016-07-06  7:52   ` AKASHI Takahiro
2016-07-06 17:46   ` Geoff Levand
2016-07-06 17:46     ` Geoff Levand
2016-07-06 19:29   ` Thiago Jung Bauermann
2016-07-06 19:29     ` Thiago Jung Bauermann
2016-07-06 19:29     ` Thiago Jung Bauermann
2016-07-07  2:00     ` AKASHI Takahiro
2016-07-07  2:00       ` AKASHI Takahiro
2016-07-07  2:00       ` AKASHI Takahiro
2016-07-07 18:46       ` Thiago Jung Bauermann
2016-07-07 18:46         ` Thiago Jung Bauermann
2016-07-07 18:46         ` Thiago Jung Bauermann

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=20160707004942.GV20774@linaro.org \
    --to=takahiro.akashi@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=geoff@infradead.org \
    --cc=james.morse@arm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=will.deacon@arm.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 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.