From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Jinyang He <hejinyang@loongson.cn>
Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>,
Serge Semin <fancer.lancer@gmail.com>,
Alexander Sverdlin <alexander.sverdlin@nokia.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, Paul Burton <paulburton@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] MIPS: reserve the memblock right after the kernel
Date: Fri, 13 Nov 2020 03:49:25 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.21.2011130339250.4064799@eddie.linux-mips.org> (raw)
In-Reply-To: <4a73a75f-a3b2-7ba1-d8a1-a46f5c20e734@loongson.cn>
On Fri, 13 Nov 2020, Jinyang He wrote:
> Commit: d3ff93380232 (mips: Make sure kernel memory is in iomem)
> As I thought, this check is related to kdump. More directly, it is
> related to the "mem=" parameter. Kexec-tools provide a "mem=" parameter
> to limit the kernel location in kdump. But sometimes the memory may be not
> enough and this check gives a way to ensure the capture kernel can
> start rightly. Although "mem=" is not in kexec-tools now, I thought
> it is also useful if someone use "mem=" to do other things.
I used to supply `mem=' by hand on many occasions across different MIPS
systems and for various reasons over the last 20 years; surely before
kexec was even thought of. The option itself has been there in the MIPS
port since I added it to Linux 2.4.0 back in Dec 2000.
Maciej
next prev parent reply other threads:[~2020-11-13 3:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 14:10 [PATCH] MIPS: reserve the memblock right after the kernel Alexander A Sverdlin
2020-11-07 9:40 ` Thomas Bogendoerfer
2020-11-09 10:34 ` Alexander Sverdlin
2020-11-09 11:08 ` Alexander Sverdlin
2020-11-10 9:55 ` Thomas Bogendoerfer
2020-11-10 10:29 ` Alexander Sverdlin
2020-11-11 14:52 ` Serge Semin
2020-11-13 2:30 ` Jiaxun Yang
2020-11-13 3:28 ` Jinyang He
2020-11-13 3:49 ` Maciej W. Rozycki [this message]
2020-11-13 12:29 ` Alexander Sverdlin
2020-11-13 12:56 ` Alexander Sverdlin
2020-11-13 9:17 ` Alexander Sverdlin
2020-11-13 13:09 ` Alexander Sverdlin
2020-11-16 22:31 ` Serge Semin
2020-11-17 9:41 ` Alexander Sverdlin
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=alpine.LFD.2.21.2011130339250.4064799@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=alexander.sverdlin@nokia.com \
--cc=fancer.lancer@gmail.com \
--cc=hejinyang@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.org \
--cc=stable@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).