From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Geoff Levand <geoff@infradead.org>
Cc: Pratyush Anand <panand@redhat.com>,
catalin.marinas@arm.com, will.deacon@arm.com,
james.morse@arm.com, Mark Salter <msalter@redhat.com>,
kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v21 1/8] arm64: kdump: reserve memory for crash dump kernel
Date: Thu, 7 Jul 2016 09:19:56 +0900 [thread overview]
Message-ID: <20160707001955.GT20774@linaro.org> (raw)
In-Reply-To: <1467824418.8880.21.camel@infradead.org>
Geoff,
Thank you for your reviewing.
On Wed, Jul 06, 2016 at 10:00:18AM -0700, Geoff Levand wrote:
> On Wed, 2016-07-06 at 16:52 +0900, AKASHI Takahiro wrote:
> >
> > +#ifdef CONFIG_KEXEC_CORE
> > +/*
> > + * reserve_crashkernel() - reserves memory for crash kernel
> > + *
> > + * This function reserves memory area given in "crashkernel=" kernel command
> > + * line parameter. The memory reserved is used by dump capture kernel when
> > + * primary kernel is crashing.
> > + */
> > +static void __init reserve_crashkernel(void)
> > +{
> > +> > unsigned long long crash_size = 0, crash_base = 0;
> > +> > int ret;
> > +
> > +> > ret = parse_crashkernel(boot_command_line, memblock_phys_mem_size(),
> > +> > > > > &crash_size, &crash_base);
> > +> > /* no crashkernel= or invalid value specified */
> > +> > if (ret || !crash_size)
> > +> > > return;
> > +
> > +> > if (crash_base == 0) {
> > +> > > /* Current arm64 boot protocol requires 2MB alignment */
> > +> > > crash_base = memblock_find_in_range(0,
> > +> > > > > MEMBLOCK_ALLOC_ACCESSIBLE, crash_size, SZ_2M);
> > +> > > if (crash_base == 0) {
> > +> > > > pr_warn("Unable to allocate crashkernel (size:%llx)\n",
> > +> > > > > crash_size);
> > +> > > > return;
> > +> > > }
> > +> > > memblock_reserve(crash_base, crash_size);
> > +
> > +> > } else {
> > +> > > /* User specifies base address explicitly. */
> > +> > > if (!memblock_is_region_memory(crash_base, crash_size) ||
> > +> > > > memblock_is_region_reserved(crash_base, crash_size)) {
> > +> > > > pr_warn("crashkernel has wrong address or size\n");
> > +> > > > return;
> > +> > > }
> > +
> > +> > > if (!IS_ALIGNED(crash_base, SZ_2M)) {
> > +> > > > pr_warn("crashkernel base address is not 2MB aligned\n");
> > +> > > > return;
> > +> > > }
> > +
> > +> > > memblock_reserve(crash_base, crash_size);
> > +> > }
> > +
> > +> > pr_info("Reserving %lldMB of memory at %lldMB for crashkernel\n",
> > +> > > crash_size >> 20, crash_base >> 20);
> > +
> > +> > crashk_res.start = crash_base;
> > +> > crashk_res.end = crash_base + crash_size - 1;
> > +}
> > +#else
> > +static void __init reserve_crashkernel(void)
> > +{
> > +> > ;
> > +}
> > +#endif /* CONFIG_KEXEC_CORE */
> > +
I know that this is just a matter of preference, but
I can see more use cases of the above than the below
that you mentioned under arm64 directory.
So I want to keep the current style unchanged unless
the maintainers don't like it.
Thanks,
-Takahiro AKASHI
> I think it is a bit cleaner if you move this conditional
> into the function and have something like:
>
> static void __init reserve_crashkernel(void)
> {
> #ifdef CONFIG_KEXEC_CORE
> #else
> #endif
> }
>
> -Geoff
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2016-07-07 0:14 UTC|newest]
Thread overview: 25+ 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 ` [PATCH v21 1/8] arm64: kdump: reserve memory for crash dump kernel AKASHI Takahiro
2016-07-06 17:00 ` Geoff Levand
2016-07-07 0:19 ` AKASHI Takahiro [this message]
2016-07-06 18:11 ` Thiago Jung Bauermann
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 17:48 ` Geoff Levand
2016-07-06 7:52 ` [PATCH v21 3/8] arm64: kdump: implement machine_crash_shutdown() AKASHI Takahiro
2016-07-06 17:28 ` Geoff Levand
2016-07-07 0:43 ` AKASHI Takahiro
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 17:38 ` Geoff Levand
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 ` [PATCH v21 6/8] arm64: kdump: enable kdump in the arm64 defconfig AKASHI Takahiro
2016-07-06 7:52 ` [PATCH v21 7/8] arm64: kdump: update a kernel doc AKASHI Takahiro
2016-07-06 17:44 ` Geoff Levand
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 17:46 ` Geoff Levand
2016-07-06 19:29 ` Thiago Jung Bauermann
2016-07-07 2:00 ` AKASHI Takahiro
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=20160707001955.GT20774@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=msalter@redhat.com \
--cc=panand@redhat.com \
--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 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).