From: James Hogan <james.hogan@mips.com>
To: David Daney <david.daney@cavium.com>
Cc: <linux-mips@linux-mips.org>, <ralf@linux-mips.org>,
<linux-kernel@vger.kernel.org>,
"Steven J. Hill" <steven.hill@cavium.com>
Subject: Re: [PATCH] MIPS: Add iomem resource for kernel bss section.
Date: Mon, 13 Nov 2017 18:21:34 +0000 [thread overview]
Message-ID: <20171113182134.GD31917@jhogan-linux.mipstec.com> (raw)
In-Reply-To: <20171012195034.5758-1-david.daney@cavium.com>
On Thu, Oct 12, 2017 at 12:50:34PM -0700, David Daney wrote:
> The kexec/kdump tools need to know where the .bss is so it can be
> included in the core dump. This allows vmcore-dmesg to have access to
> the dmesg buffers of the crashed kernel as well as allowing the
> debugger to examine variables in the bss section.
>
> Add a request for the bss resource in addition to the already
> requested code and data sections.
>
> Signed-off-by: David Daney <david.daney@cavium.com>
Thanks, applied.
Cheers
James
> ---
> arch/mips/kernel/setup.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/mips/kernel/setup.c b/arch/mips/kernel/setup.c
> index fe39397..702c678 100644
> --- a/arch/mips/kernel/setup.c
> +++ b/arch/mips/kernel/setup.c
> @@ -80,6 +80,7 @@ EXPORT_SYMBOL(mips_io_port_base);
>
> static struct resource code_resource = { .name = "Kernel code", };
> static struct resource data_resource = { .name = "Kernel data", };
> +static struct resource bss_resource = { .name = "Kernel bss", };
>
> static void *detect_magic __initdata = detect_memory_region;
>
> @@ -927,6 +928,8 @@ static void __init resource_init(void)
> code_resource.end = __pa_symbol(&_etext) - 1;
> data_resource.start = __pa_symbol(&_etext);
> data_resource.end = __pa_symbol(&_edata) - 1;
> + bss_resource.start = __pa_symbol(&__bss_start);
> + bss_resource.end = __pa_symbol(&__bss_stop) - 1;
>
> for (i = 0; i < boot_mem_map.nr_map; i++) {
> struct resource *res;
> @@ -966,6 +969,7 @@ static void __init resource_init(void)
> */
> request_resource(res, &code_resource);
> request_resource(res, &data_resource);
> + request_resource(res, &bss_resource);
> request_crashkernel(res);
> }
> }
> --
> 2.9.5
>
prev parent reply other threads:[~2017-11-13 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 19:50 David Daney
2017-11-13 18:21 ` James Hogan [this message]
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=20171113182134.GD31917@jhogan-linux.mipstec.com \
--to=james.hogan@mips.com \
--cc=david.daney@cavium.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=steven.hill@cavium.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
Powered by JetHome