[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221026144208.373504-3-xianting.tian@linux.alibaba.com>
Date: Wed, 26 Oct 2022 22:42:08 +0800
From: Xianting Tian <xianting.tian@...ux.alibaba.com>
To: paul.walmsley@...ive.com, palmer@...belt.com,
aou@...s.berkeley.edu, anup@...infault.org, heiko@...ech.de,
guoren@...nel.org, mick@....forth.gr,
alexandre.ghiti@...onical.com, bhe@...hat.com, vgoyal@...hat.com,
dyoung@...hat.com, corbet@....net, Conor.Dooley@...rochip.com,
bagasdotme@...il.com
Cc: kexec@...ts.infradead.org, linux-doc@...r.kernel.org,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
crash-utility@...hat.com, heinrich.schuchardt@...onical.com,
k-hagio-ab@....com, hschauhan@...ltrace.org, yixun.lan@...il.com,
Xianting Tian <xianting.tian@...ux.alibaba.com>
Subject: [PATCH V5 2/2] Documentation: kdump: describe VMCOREINFO export for RISCV64
The following interrelated definitions and ranges are needed by the kdump
crash tool, which are exported by "arch/riscv/kernel/crash_core.c":
VA_BITS,
PAGE_OFFSET,
phys_ram_base,
KERNEL_LINK_ADDR,
MODULES_VADDR ~ MODULES_END,
VMALLOC_START ~ VMALLOC_END,
VMEMMAP_START ~ VMEMMAP_END,
Document these RISCV64 exports above.
Reviewed-by: Bagas Sanjaya <bagasdotme@...il.com>
Signed-off-by: Xianting Tian <xianting.tian@...ux.alibaba.com>
---
.../admin-guide/kdump/vmcoreinfo.rst | 29 +++++++++++++++++++
1 file changed, 29 insertions(+)
diff --git a/Documentation/admin-guide/kdump/vmcoreinfo.rst b/Documentation/admin-guide/kdump/vmcoreinfo.rst
index 6726f439958c..86fd88492870 100644
--- a/Documentation/admin-guide/kdump/vmcoreinfo.rst
+++ b/Documentation/admin-guide/kdump/vmcoreinfo.rst
@@ -595,3 +595,32 @@ X2TLB
-----
Indicates whether the crashed kernel enabled SH extended mode.
+
+RISCV64
+=======
+
+VA_BITS
+-------
+
+The maximum number of bits for virtual addresses. Used to compute the
+virtual memory ranges.
+
+PAGE_OFFSET
+-----------
+
+Indicates the virtual kernel start address of the direct-mapped RAM region.
+
+phys_ram_base
+-------------
+
+Indicates the start physical RAM address.
+
+MODULES_VADDR|MODULES_END|VMALLOC_START|VMALLOC_END|VMEMMAP_START|VMEMMAP_END|KERNEL_LINK_ADDR
+----------------------------------------------------------------------------------------------
+
+Used to get the correct ranges:
+
+ * MODULES_VADDR ~ MODULES_END : Kernel module space.
+ * VMALLOC_START ~ VMALLOC_END : vmalloc() / ioremap() space.
+ * VMEMMAP_START ~ VMEMMAP_END : vmemmap space, used for struct page array.
+ * KERNEL_LINK_ADDR : start address of Kernel link and BPF
--
2.17.1
Powered by blists - more mailing lists