[Skiboot] [RFC PATCH 05/16] hdata: Setup memory for MDRT table

Vasant Hegde hegdevasant at linux.vnet.ibm.com
Tue Apr 3 22:04:36 AEST 2018

Hostboot fills MDRT table after moving memory content from source to destination
memory. And OPAL relies on this table to extract the dump. We have to make sure
this table is intact. Hence define memory relative to SKIBOOT_BASE so that our
relocation doesn't overwrite this memory.

Signed-off-by: Vasant Hegde <hegdevasant at linux.vnet.ibm.com>
 include/mem-map.h | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/include/mem-map.h b/include/mem-map.h
index 12b0a71b3..50c70c7d3 100644
--- a/include/mem-map.h
+++ b/include/mem-map.h
@@ -103,11 +103,17 @@
 #define PSI_TCE_TABLE_SIZE_P7	0x00020000UL
 #define PSI_TCE_TABLE_SIZE_P8	0x00200000UL
+/* This is our dump result table after MPIPL. Hostboot will write to this
+ * memory after moving dump content from source to destination memory.
+ */
+#define MDRT_TABLE_BASE		(SKIBOOT_BASE + 0x01c00000)
+#define MDRT_TABLE_SIZE		0x00010000
 /* Total size of the above area
  * (Ensure this has at least a 64k alignment)
-#define SKIBOOT_SIZE		0x01c00000
+#define SKIBOOT_SIZE		0x01c10000
 /* We start laying out the CPU stacks from here, indexed by PIR
  * each stack is STACK_SIZE in size (naturally aligned power of

More information about the Skiboot mailing list