From: Chen Zhou <chenzhou10@huawei.com>
To: <tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
<ebiederm@xmission.com>, <rppt@linux.ibm.com>,
<catalin.marinas@arm.com>, <will.deacon@arm.com>,
<akpm@linux-foundation.org>, <ard.biesheuvel@linaro.org>
Cc: <horms@verge.net.au>, <takahiro.akashi@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <kexec@lists.infradead.org>,
<linux-mm@kvack.org>, <wangkefeng.wang@huawei.com>,
Chen Zhou <chenzhou10@huawei.com>
Subject: [PATCH v5 4/4] kdump: update Documentation about crashkernel on arm64
Date: Tue, 16 Apr 2019 15:43:29 +0800 [thread overview]
Message-ID: <20190416074329.44928-5-chenzhou10@huawei.com> (raw)
In-Reply-To: <20190416074329.44928-1-chenzhou10@huawei.com>
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 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index 308af3b..a055983 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -715,14 +715,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
--
2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Chen Zhou <chenzhou10@huawei.com>
To: <tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
<ebiederm@xmission.com>, <rppt@linux.ibm.com>,
<catalin.marinas@arm.com>, <will.deacon@arm.com>,
<akpm@linux-foundation.org>, <ard.biesheuvel@linaro.org>
Cc: wangkefeng.wang@huawei.com, linux-mm@kvack.org,
Chen Zhou <chenzhou10@huawei.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
takahiro.akashi@linaro.org, horms@verge.net.au,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 4/4] kdump: update Documentation about crashkernel on arm64
Date: Tue, 16 Apr 2019 15:43:29 +0800 [thread overview]
Message-ID: <20190416074329.44928-5-chenzhou10@huawei.com> (raw)
In-Reply-To: <20190416074329.44928-1-chenzhou10@huawei.com>
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 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index 308af3b..a055983 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -715,14 +715,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
--
2.7.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Chen Zhou <chenzhou10@huawei.com>
To: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
ebiederm@xmission.com, rppt@linux.ibm.com,
catalin.marinas@arm.com, will.deacon@arm.com,
akpm@linux-foundation.org, ard.biesheuvel@linaro.org
Cc: wangkefeng.wang@huawei.com, linux-mm@kvack.org,
Chen Zhou <chenzhou10@huawei.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
takahiro.akashi@linaro.org, horms@verge.net.au,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 4/4] kdump: update Documentation about crashkernel on arm64
Date: Tue, 16 Apr 2019 15:43:29 +0800 [thread overview]
Message-ID: <20190416074329.44928-5-chenzhou10@huawei.com> (raw)
In-Reply-To: <20190416074329.44928-1-chenzhou10@huawei.com>
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 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index 308af3b..a055983 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -715,14 +715,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
--
2.7.4
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2019-04-16 7:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 7:43 [PATCH v5 0/4] support reserving crashkernel above 4G on arm64 kdump Chen Zhou
2019-04-16 7:43 ` Chen Zhou
2019-04-16 7:43 ` Chen Zhou
2019-04-16 7:43 ` [PATCH v5 1/4] x86: kdump: move reserve_crashkernel_low() into kexec_core.c Chen Zhou
2019-04-16 7:43 ` Chen Zhou
2019-04-16 7:43 ` Chen Zhou
2019-04-16 7:43 ` [PATCH v5 2/4] arm64: kdump: support reserving crashkernel above 4G Chen Zhou
2019-04-16 7:43 ` Chen Zhou
2019-04-16 7:43 ` Chen Zhou
2019-04-16 7:43 ` [PATCH v5 3/4] memblock: extend memblock_cap_memory_range to multiple ranges Chen Zhou
2019-04-16 7:43 ` Chen Zhou
2019-04-16 7:43 ` Chen Zhou
2019-04-16 7:43 ` Chen Zhou [this message]
2019-04-16 7:43 ` [PATCH v5 4/4] kdump: update Documentation about crashkernel on arm64 Chen Zhou
2019-04-16 7:43 ` Chen Zhou
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=20190416074329.44928-5-chenzhou10@huawei.com \
--to=chenzhou10@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.