From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Baoquan He <bhe@redhat.com>
Cc: Huacai Chen <chenhc@lemote.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Eric Biederman <ebiederm@xmission.com>,
Dave Young <dyoung@redhat.com>, Vivek Goyal <vgoyal@redhat.com>,
"open list:MIPS" <linux-mips@vger.kernel.org>,
kexec@lists.infradead.org, Fuxin Zhang <zhangfx@lemote.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH 1/3] MIPS: Crash kernel should be able to see old memories
Date: Mon, 5 Oct 2020 01:40:47 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.21.2010050133330.333514@eddie.linux-mips.org> (raw)
In-Reply-To: <alpine.LFD.2.21.2010032200470.333514@eddie.linux-mips.org>
On Sat, 3 Oct 2020, Maciej W. Rozycki wrote:
> > Interesting. Seems MIPS does support mem=X@Y, even though the document
> > of 'mem=' says it's used to specify amount of memory, but not memory
> > region. Anyway, leave this to mips reviewers, thanks for replying.
> >
> > ~~~~~~~~~~~~~~~~~~~
> > mem=nn[KMG] [KNL,BOOT] Force usage of a specific amount of memory
> > Amount of memory to be used in cases as follows:
>
> Yep, I implemented it for the DECstation back in 2000:
>
> commit 97b7ae4257ef7ba8ed9b7944a4f56a49af3e8abb
> Author: Ralf Baechle <ralf@linux-mips.org>
> Date: Mon Dec 11 16:41:05 2000 +0000
>
> Memmap fixes from Maciej.
>
> (from the LMO repo) in line with the x86 syntax. I don't know why it
> hasn't ever been documented in "Kernel Parameters" (for any port), but I'm
> fairly sure it has been somewhere.
Self-correction: documentation used to be there, but was removed around
Linux 2.5.65:
commit 041a679cb20e4fcb841665b09cf7c6d24ab4ad39
Author: Ralf Baechle <ralf@linux-mips.org>
Date: Thu Jun 5 00:04:28 2003 +0000
Merge with Linux 2.5.65.
(same repo) as the parameter was renamed to `memmap=' in the x86 port.
Obviously whoever did that did not bother to check other ports, even
though the parameter was marked (and `memmap=' still is) generic.
Maciej
next prev parent reply other threads:[~2020-10-05 0:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 2:30 [PATCH 1/3] MIPS: Crash kernel should be able to see old memories Huacai Chen
2020-09-23 2:30 ` [PATCH 2/3] MIPS: Reserve extra memory for crash dump Huacai Chen
2020-09-23 2:30 ` [PATCH 3/3] MIPS: Loongson64: Add kexec/kdump support Huacai Chen
2020-09-23 3:35 ` Jinyang He
2020-09-24 0:31 ` Huacai Chen
2020-09-23 13:35 ` Jiaxun Yang
2020-09-24 1:19 ` Huacai Chen
2020-09-24 1:48 ` Jiaxun Yang
2020-09-24 2:15 ` Jinyang He
2020-09-23 2:45 ` [PATCH 1/3] MIPS: Crash kernel should be able to see old memories Baoquan He
2020-09-23 2:58 ` Huacai Chen
2020-09-23 3:08 ` Baoquan He
2020-10-03 21:07 ` Maciej W. Rozycki
2020-10-05 0:40 ` Maciej W. Rozycki [this message]
2020-09-23 3:02 ` Jinyang He
2020-09-23 3:13 ` Huacai Chen
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.2010050133330.333514@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=bhe@redhat.com \
--cc=chenhc@lemote.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=jiaxun.yang@flygoat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=vgoyal@redhat.com \
--cc=zhangfx@lemote.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).