public inbox for linux-mips@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivan Khoronzhuk <ivan.khoronzhuk@gmail.com>
To: Jinyang He <hejinyang@loongson.cn>
Cc: Ivan Khoronzhuk <ikhoronz@cisco.com>,
	linux-mips@vger.kernel.org, tsbogend@alpha.franken.de,
	linux-kernel@vger.kernel.org, yangtiezhu@loongson.cn,
	rppt@kernel.org
Subject: Re: [PATCH] mips: kernel: setup: fix crash kernel resource allocation
Date: Mon, 8 Feb 2021 15:17:15 +0200	[thread overview]
Message-ID: <20210208131714.GA4740@ikhorn> (raw)
In-Reply-To: <01729c08-c5e3-e9c0-2ddb-a5289e536153@loongson.cn>

On Sun, Feb 07, 2021 at 11:19:03AM +0800, Jinyang He wrote:
>On 02/06/2021 08:59 PM, Ivan Khoronzhuk wrote:
>
>>In order to avoid crash kernel corruption, its memory is reserved
>>early in memblock and as result, in time when resources are inited
>>it's not present in memblock.memory, so crash kernel memory is out
>>of ranges listed with for_each_mem_range(). To avoid it and still
>>keep memory reserved lets reseve it out of loop by inserting it in
>>iomem_resource.
>
>Hi, Ivan,
>
>I'm not familiar with memblock. If the following my ideas show my
>ignorance, please forgive me.
>
>First, not only the crash kernel is reserved early in memblock, but also
>code, data, and bss are also reserved in bootmem_init():
>
>    /* Reserve memory occupied by kernel. */
>    memblock_reserve(__pa_symbol(&_text),
>            __pa_symbol(&_end) - __pa_symbol(&_text));
>
>(CONFIG_NUMA is not enabled. NUMA platform reserved them is earlier.)
>
>If there is something unsuitable with the crash kernel, is there something
>unsuitable with the kernel memory?
>
>
>Then, for_each_mem_range() is normal memory. Although memblock_reserve()
>has used before that, it just adds memory to memblock.reserved. That means
>it will still appear in memblock.memory. Thus, here I have a question,
>do we need to use replace for_each_mem_range with for_each_mem_range_rev?

Reserve doesn't mean it's present in memblock.memory, if it memory was not
added before, like it's supposed. In my canse, seems like to local issue it
wasn't, that's why it was not present. So, traverse direction won't solve
this obviously.

>
>Finally, thank you for the patch, it makes me think a lot.
>
>Thanks,
>Jinyang
>
>>Fixes: a94e4f24ec83 ("MIPS: init: Drop boot_mem_map")
>>Signed-off-by: Ivan Khoronzhuk <ikhoronz@cisco.com>
>>---
>>Based on linux-next/master
>>
>>  arch/mips/kernel/setup.c | 8 +++++---
>>  1 file changed, 5 insertions(+), 3 deletions(-)
>>
>>diff --git a/arch/mips/kernel/setup.c b/arch/mips/kernel/setup.c
>>index 3785c72bc3bc..25e376ef2f2a 100644
>>--- a/arch/mips/kernel/setup.c
>>+++ b/arch/mips/kernel/setup.c
>>@@ -473,14 +473,15 @@ static void __init mips_parse_crashkernel(void)
>>  	crashk_res.end	 = crash_base + crash_size - 1;
>>  }
>>-static void __init request_crashkernel(struct resource *res)
>>+static void __init request_crashkernel(void)
>>  {
>>  	int ret;
>>  	if (crashk_res.start == crashk_res.end)
>>  		return;
>>-	ret = request_resource(res, &crashk_res);
>>+	/* The crashk resource shoud be located in normal mem */
>>+	ret = insert_resource(&iomem_resource, &crashk_res);
>>  	if (!ret)
>>  		pr_info("Reserving %ldMB of memory at %ldMB for crashkernel\n",
>>  			(unsigned long)(resource_size(&crashk_res) >> 20),
>>@@ -734,8 +735,9 @@ static void __init resource_init(void)
>>  		request_resource(res, &code_resource);
>>  		request_resource(res, &data_resource);
>>  		request_resource(res, &bss_resource);
>>-		request_crashkernel(res);
>>  	}
>>+
>>+	request_crashkernel();
>>  }
>>  #ifdef CONFIG_SMP
>

-- 
Regards,
Ivan Khoronzhuk

  reply	other threads:[~2021-02-08 13:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06 12:59 [PATCH] mips: kernel: setup: fix crash kernel resource allocation Ivan Khoronzhuk
2021-02-07  3:19 ` Jinyang He
2021-02-08 13:17   ` Ivan Khoronzhuk [this message]
2021-02-07  9:18 ` Mike Rapoport
2021-02-08 13:29   ` Ivan Khoronzhuk

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=20210208131714.GA4740@ikhorn \
    --to=ivan.khoronzhuk@gmail.com \
    --cc=hejinyang@loongson.cn \
    --cc=ikhoronz@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=rppt@kernel.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=yangtiezhu@loongson.cn \
    /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