All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Zhou <chenzhou10@huawei.com>
To: <tglx@linutronix.de>, <mingo@redhat.com>,
	<catalin.marinas@arm.com>, <will@kernel.org>, <dyoung@redhat.com>,
	<bhe@redhat.com>, <robh+dt@kernel.org>
Cc: <arnd@arndb.de>, <John.p.donnelly@oracle.com>,
	<pkushwaha@marvell.com>, <horms@verge.net.au>,
	<guohanjun@huawei.com>, <chenzhou10@huawei.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <kexec@lists.infradead.org>
Subject: [PATCH v8 5/5] dt-bindings: chosen: Document linux,low-memory-range for arm64 kdump
Date: Thu, 21 May 2020 17:38:05 +0800	[thread overview]
Message-ID: <20200521093805.64398-6-chenzhou10@huawei.com> (raw)
In-Reply-To: <20200521093805.64398-1-chenzhou10@huawei.com>

Add documentation for DT property used by arm64 kdump:
linux,low-memory-range.
"linux,low-memory-range" is an another memory region used for crash
dump kernel devices.

Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
---
 Documentation/devicetree/bindings/chosen.txt | 25 ++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/Documentation/devicetree/bindings/chosen.txt b/Documentation/devicetree/bindings/chosen.txt
index 45e79172a646..bfe6fb6976e6 100644
--- a/Documentation/devicetree/bindings/chosen.txt
+++ b/Documentation/devicetree/bindings/chosen.txt
@@ -103,6 +103,31 @@ While this property does not represent a real hardware, the address
 and the size are expressed in #address-cells and #size-cells,
 respectively, of the root node.
 
+linux,low-memory-range
+----------------------
+This property (arm64 only) holds a base address and size, describing a
+limited region below 4G. Similar to "linux,usable-memory-range", it is
+an another memory range which may be considered available for use by the
+kernel.
+
+e.g.
+
+/ {
+	chosen {
+		linux,low-memory-range = <0x0 0x70000000 0x0 0x10000000>;
+		linux,usable-memory-range = <0x202f 0xc0000000 0x0 0x40000000>;
+	};
+};
+
+The main usage is for crash dump kernel devices when reserving crashkernel
+above 4G. When reserving crashkernel above 4G, there may be two crash kernel
+regions, one is below 4G, the other is above 4G. In order to distinct from
+the high region, use this property to pass the low region.
+
+While this property does not represent a real hardware, the address
+and the size are expressed in #address-cells and #size-cells,
+respectively, of the root node.
+
 linux,elfcorehdr
 ----------------
 
-- 
2.20.1


WARNING: multiple messages have this Message-ID (diff)
From: Chen Zhou <chenzhou10@huawei.com>
To: <tglx@linutronix.de>, <mingo@redhat.com>,
	<catalin.marinas@arm.com>, <will@kernel.org>, <dyoung@redhat.com>,
	<bhe@redhat.com>, <robh+dt@kernel.org>
Cc: John.p.donnelly@oracle.com, arnd@arndb.de,
	devicetree@vger.kernel.org, chenzhou10@huawei.com,
	linux-doc@vger.kernel.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org, horms@verge.net.au,
	guohanjun@huawei.com, pkushwaha@marvell.com,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 5/5] dt-bindings: chosen: Document linux, low-memory-range for arm64 kdump
Date: Thu, 21 May 2020 17:38:05 +0800	[thread overview]
Message-ID: <20200521093805.64398-6-chenzhou10@huawei.com> (raw)
In-Reply-To: <20200521093805.64398-1-chenzhou10@huawei.com>

Add documentation for DT property used by arm64 kdump:
linux,low-memory-range.
"linux,low-memory-range" is an another memory region used for crash
dump kernel devices.

Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
---
 Documentation/devicetree/bindings/chosen.txt | 25 ++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/Documentation/devicetree/bindings/chosen.txt b/Documentation/devicetree/bindings/chosen.txt
index 45e79172a646..bfe6fb6976e6 100644
--- a/Documentation/devicetree/bindings/chosen.txt
+++ b/Documentation/devicetree/bindings/chosen.txt
@@ -103,6 +103,31 @@ While this property does not represent a real hardware, the address
 and the size are expressed in #address-cells and #size-cells,
 respectively, of the root node.
 
+linux,low-memory-range
+----------------------
+This property (arm64 only) holds a base address and size, describing a
+limited region below 4G. Similar to "linux,usable-memory-range", it is
+an another memory range which may be considered available for use by the
+kernel.
+
+e.g.
+
+/ {
+	chosen {
+		linux,low-memory-range = <0x0 0x70000000 0x0 0x10000000>;
+		linux,usable-memory-range = <0x202f 0xc0000000 0x0 0x40000000>;
+	};
+};
+
+The main usage is for crash dump kernel devices when reserving crashkernel
+above 4G. When reserving crashkernel above 4G, there may be two crash kernel
+regions, one is below 4G, the other is above 4G. In order to distinct from
+the high region, use this property to pass the low region.
+
+While this property does not represent a real hardware, the address
+and the size are expressed in #address-cells and #size-cells,
+respectively, of the root node.
+
 linux,elfcorehdr
 ----------------
 
-- 
2.20.1


_______________________________________________
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, catalin.marinas@arm.com,
	will@kernel.org, dyoung@redhat.com, bhe@redhat.com,
	robh+dt@kernel.org
Cc: John.p.donnelly@oracle.com, arnd@arndb.de,
	devicetree@vger.kernel.org, chenzhou10@huawei.com,
	linux-doc@vger.kernel.org, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org, horms@verge.net.au,
	guohanjun@huawei.com, pkushwaha@marvell.com,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 5/5] dt-bindings: chosen: Document linux, low-memory-range for arm64 kdump
Date: Thu, 21 May 2020 17:38:05 +0800	[thread overview]
Message-ID: <20200521093805.64398-6-chenzhou10@huawei.com> (raw)
In-Reply-To: <20200521093805.64398-1-chenzhou10@huawei.com>

Add documentation for DT property used by arm64 kdump:
linux,low-memory-range.
"linux,low-memory-range" is an another memory region used for crash
dump kernel devices.

Signed-off-by: Chen Zhou <chenzhou10@huawei.com>
---
 Documentation/devicetree/bindings/chosen.txt | 25 ++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/Documentation/devicetree/bindings/chosen.txt b/Documentation/devicetree/bindings/chosen.txt
index 45e79172a646..bfe6fb6976e6 100644
--- a/Documentation/devicetree/bindings/chosen.txt
+++ b/Documentation/devicetree/bindings/chosen.txt
@@ -103,6 +103,31 @@ While this property does not represent a real hardware, the address
 and the size are expressed in #address-cells and #size-cells,
 respectively, of the root node.
 
+linux,low-memory-range
+----------------------
+This property (arm64 only) holds a base address and size, describing a
+limited region below 4G. Similar to "linux,usable-memory-range", it is
+an another memory range which may be considered available for use by the
+kernel.
+
+e.g.
+
+/ {
+	chosen {
+		linux,low-memory-range = <0x0 0x70000000 0x0 0x10000000>;
+		linux,usable-memory-range = <0x202f 0xc0000000 0x0 0x40000000>;
+	};
+};
+
+The main usage is for crash dump kernel devices when reserving crashkernel
+above 4G. When reserving crashkernel above 4G, there may be two crash kernel
+regions, one is below 4G, the other is above 4G. In order to distinct from
+the high region, use this property to pass the low region.
+
+While this property does not represent a real hardware, the address
+and the size are expressed in #address-cells and #size-cells,
+respectively, of the root node.
+
 linux,elfcorehdr
 ----------------
 
-- 
2.20.1


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  parent reply	other threads:[~2020-05-21  9:35 UTC|newest]

Thread overview: 102+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21  9:38 [PATCH v8 0/5] support reserving crashkernel above 4G on arm64 kdump Chen Zhou
2020-05-21  9:38 ` Chen Zhou
2020-05-21  9:38 ` Chen Zhou
2020-05-21  9:38 ` [PATCH v8 1/5] x86: kdump: move reserve_crashkernel_low() into crash_core.c Chen Zhou
2020-05-21  9:38   ` Chen Zhou
2020-05-21  9:38   ` Chen Zhou
2020-05-26  0:56   ` Baoquan He
2020-05-26  0:56     ` Baoquan He
2020-05-26  0:56     ` Baoquan He
2020-05-21  9:38 ` [PATCH v8 2/5] arm64: kdump: reserve crashkenel above 4G for crash dump kernel Chen Zhou
2020-05-21  9:38   ` Chen Zhou
2020-05-21  9:38   ` Chen Zhou
2020-05-26  0:59   ` Baoquan He
2020-05-26  0:59     ` Baoquan He
2020-05-26  0:59     ` Baoquan He
2020-05-21  9:38 ` [PATCH v8 3/5] arm64: kdump: add memory for devices by DT property, low-memory-range Chen Zhou
2020-05-21  9:38   ` Chen Zhou
2020-05-21  9:38   ` Chen Zhou
2020-05-21  9:38 ` [PATCH v8 4/5] kdump: update Documentation about crashkernel on arm64 Chen Zhou
2020-05-21  9:38   ` Chen Zhou
2020-05-21  9:38   ` Chen Zhou
2020-05-21  9:38 ` Chen Zhou [this message]
2020-05-21  9:38   ` [PATCH v8 5/5] dt-bindings: chosen: Document linux, low-memory-range for arm64 kdump Chen Zhou
2020-05-21  9:38   ` Chen Zhou
2020-05-21 13:29   ` [PATCH v8 5/5] dt-bindings: chosen: Document linux,low-memory-range " Rob Herring
2020-05-21 13:29     ` [PATCH v8 5/5] dt-bindings: chosen: Document linux, low-memory-range " Rob Herring
2020-05-21 13:29     ` Rob Herring
2020-05-22  3:24     ` [PATCH v8 5/5] dt-bindings: chosen: Document linux,low-memory-range " chenzhou
2020-05-22  3:24       ` chenzhou
2020-05-22  3:24       ` chenzhou
2020-05-26 21:18       ` Rob Herring
2020-05-26 21:18         ` Rob Herring
2020-05-26 21:18         ` Rob Herring
2020-05-29 16:11         ` James Morse
2020-05-29 16:11           ` James Morse
2020-05-29 16:11           ` James Morse
2020-06-20  3:54           ` chenzhou
2020-06-20  3:54             ` chenzhou
2020-06-20  3:54             ` chenzhou
2020-05-26  1:42 ` [PATCH v8 0/5] support reserving crashkernel above 4G on " Baoquan He
2020-05-26  1:42   ` Baoquan He
2020-05-26  1:42   ` Baoquan He
2020-05-26  2:28   ` chenzhou
2020-05-26  2:28     ` chenzhou
2020-05-26  2:28     ` chenzhou
2020-05-28 22:20   ` John Donnelly
2020-05-28 22:20     ` John Donnelly
2020-05-28 22:20     ` John Donnelly
2020-05-29  8:05     ` Will Deacon
2020-05-29  8:05       ` Will Deacon
2020-05-29  8:05       ` Will Deacon
2020-06-01 12:02 ` Prabhakar Kushwaha
2020-06-01 12:02   ` Prabhakar Kushwaha
2020-06-01 12:02   ` Prabhakar Kushwaha
2020-06-01 19:30   ` John Donnelly
2020-06-01 19:30     ` John Donnelly
2020-06-01 19:30     ` John Donnelly
2020-06-01 21:02     ` Bhupesh Sharma
2020-06-01 21:02       ` Bhupesh Sharma
2020-06-01 21:02       ` Bhupesh Sharma
2020-06-01 21:59       ` John Donnelly
2020-06-01 21:59         ` John Donnelly
2020-06-01 21:59         ` John Donnelly
2020-06-02  5:38         ` Prabhakar Kushwaha
2020-06-02  5:38           ` Prabhakar Kushwaha
2020-06-02  5:38           ` Prabhakar Kushwaha
2020-06-02 14:41           ` John Donnelly
2020-06-02 14:41             ` John Donnelly
2020-06-02 14:41             ` John Donnelly
2020-06-03 11:47             ` Prabhakar Kushwaha
2020-06-03 11:47               ` Prabhakar Kushwaha
2020-06-03 11:47               ` Prabhakar Kushwaha
2020-06-03 13:20               ` chenzhou
2020-06-03 13:20                 ` chenzhou
2020-06-03 13:20                 ` chenzhou
2020-06-03 15:30                 ` John Donnelly
2020-06-03 15:30                   ` John Donnelly
2020-06-03 15:30                   ` John Donnelly
2020-06-03 19:47                   ` Bhupesh Sharma
2020-06-03 19:47                     ` Bhupesh Sharma
2020-06-03 19:47                     ` Bhupesh Sharma
2020-06-04  7:14                     ` Will Deacon
2020-06-04  7:14                       ` Will Deacon
2020-06-04  7:14                       ` Will Deacon
2020-06-04 17:01                     ` Nicolas Saenz Julienne
2020-06-04 17:01                       ` Nicolas Saenz Julienne
2020-06-04 17:01                       ` Nicolas Saenz Julienne
2020-06-05  2:26                       ` John Donnelly
2020-06-05  2:26                         ` John Donnelly
2020-06-05  2:26                         ` John Donnelly
2020-06-05  8:21                         ` Nicolas Saenz Julienne
2020-06-05  8:21                           ` Nicolas Saenz Julienne
2020-06-05  8:21                           ` Nicolas Saenz Julienne
2020-06-19  2:32                       ` John Donnelly
2020-06-19  2:32                         ` John Donnelly
2020-06-19  2:32                         ` John Donnelly
2020-06-19  8:21                         ` chenzhou
2020-06-19  8:21                           ` chenzhou
2020-06-19  8:21                           ` chenzhou
2020-06-20  0:01                           ` John Donnelly
2020-06-20  0:01                             ` John Donnelly
2020-06-20  0:01                             ` John Donnelly

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=20200521093805.64398-6-chenzhou10@huawei.com \
    --to=chenzhou10@huawei.com \
    --cc=John.p.donnelly@oracle.com \
    --cc=arnd@arndb.de \
    --cc=bhe@redhat.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dyoung@redhat.com \
    --cc=guohanjun@huawei.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pkushwaha@marvell.com \
    --cc=robh+dt@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=will@kernel.org \
    /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.