From: Chen Zhou <chenzhou10@huawei.com>
To: Bhupesh Sharma <bhsharma@redhat.com>, <catalin.marinas@arm.com>,
<will.deacon@arm.com>, <akpm@linux-foundation.org>,
<ard.biesheuvel@linaro.org>, <rppt@linux.ibm.com>,
<tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
<ebiederm@xmission.com>
Cc: <wangkefeng.wang@huawei.com>, <linux-mm@kvack.org>,
<kexec@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<takahiro.akashi@linaro.org>, <horms@verge.net.au>,
<linux-arm-kernel@lists.infradead.org>,
Bhupesh SHARMA <bhupesh.linux@gmail.com>
Subject: Re: [PATCH 4/4] kdump: update Documentation about crashkernel on arm64
Date: Thu, 16 May 2019 11:23:58 +0800 [thread overview]
Message-ID: <168b5c80-9a8b-ee94-9cfb-56e4955958c1@huawei.com> (raw)
In-Reply-To: <de5b827f-5db2-2280-b848-c5c887b9bb58@redhat.com>
On 2019/5/15 13:16, Bhupesh Sharma wrote:
> On 05/07/2019 09:20 AM, Chen Zhou wrote:
>> Now we support crashkernel=X,[high,low] on arm64, update the
>> Documentation.
>>
>> Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
>> ---
>> Documentation/admin-guide/kernel-parameters.txt | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
>> index 268b10a..03a08aa 100644
>> --- a/Documentation/admin-guide/kernel-parameters.txt
>> +++ b/Documentation/admin-guide/kernel-parameters.txt
>> @@ -705,7 +705,7 @@
>> memory region [offset, offset + size] for that kernel
>> image. If '@offset' is omitted, then a suitable offset
>> is selected automatically.
>> - [KNL, x86_64] select a region under 4G first, and
>> + [KNL, x86_64, arm64] select a region under 4G first, and
>> fall back to reserve region above 4G when '@offset'
>> hasn't been specified.
>> See Documentation/kdump/kdump.txt for further details.
>> @@ -718,14 +718,14 @@
>> Documentation/kdump/kdump.txt for an example.
>> crashkernel=size[KMG],high
>> - [KNL, x86_64] range could be above 4G. Allow kernel
>> + [KNL, x86_64, arm64] range could be above 4G. Allow kernel
>> to allocate physical memory region from top, so could
>> be above 4G if system have more than 4G ram installed.
>> Otherwise memory region will be allocated below 4G, if
>> available.
>> It will be ignored if crashkernel=X is specified.
>> crashkernel=size[KMG],low
>> - [KNL, x86_64] range under 4G. When crashkernel=X,high
>> + [KNL, x86_64, arm64] range under 4G. When crashkernel=X,high
>> is passed, kernel could allocate physical memory region
>> above 4G, that cause second kernel crash on system
>> that require some amount of low memory, e.g. swiotlb
>>
>
> IMO, it is a good time to update 'Documentation/kdump/kdump.txt' with this patchset itself for both x86_64 and arm64, where we still specify only the old format for 'crashkernel' boot-argument:
>
> Section: Boot into System Kernel
> =======================
>
> On arm64, use "crashkernel=Y[@X]". Note that the start address of
> the kernel, X if explicitly specified, must be aligned to 2MiB (0x200000).
> ...
>
> We can update this to add the new crashkernel=size[KMG],low or crashkernel=size[KMG],high format as well.
>
> Thanks,
> Bhupesh
>
> .
Sure, we can also update here.
Thanks,
Chen Zhou
next prev parent reply other threads:[~2019-05-16 3:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 3:50 [PATCH 0/4] support reserving crashkernel above 4G on arm64 kdump Chen Zhou
2019-05-07 3:50 ` [PATCH 1/4] x86: kdump: move reserve_crashkernel_low() into kexec_core.c Chen Zhou
2019-06-05 16:29 ` James Morse
2019-06-13 11:26 ` Chen Zhou
2019-06-12 8:45 ` Dave Young
2019-06-13 11:27 ` Chen Zhou
2019-05-07 3:50 ` [PATCH 2/4] arm64: kdump: support reserving crashkernel above 4G Chen Zhou
2019-06-05 16:29 ` James Morse
2019-06-13 11:27 ` Chen Zhou
2019-06-13 12:44 ` James Morse
2019-05-07 3:50 ` [PATCH 3/4] memblock: extend memblock_cap_memory_range to multiple ranges Chen Zhou
2019-05-07 3:50 ` [PATCH 4/4] kdump: update Documentation about crashkernel on arm64 Chen Zhou
2019-05-15 5:16 ` Bhupesh Sharma
2019-05-16 3:23 ` Chen Zhou [this message]
2019-05-15 5:06 ` [PATCH 0/4] support reserving crashkernel above 4G on arm64 kdump Bhupesh Sharma
2019-05-16 3:19 ` Chen Zhou
2019-06-03 2:24 ` Chen Zhou
2019-06-05 16:32 ` James Morse
2019-06-13 11:27 ` Chen Zhou
2019-06-13 12:43 ` James Morse
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=168b5c80-9a8b-ee94-9cfb-56e4955958c1@huawei.com \
--to=chenzhou10@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bhsharma@redhat.com \
--cc=bhupesh.linux@gmail.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=rppt@linux.ibm.com \
--cc=takahiro.akashi@linaro.org \
--cc=tglx@linutronix.de \
--cc=wangkefeng.wang@huawei.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