Skip to content

Commit

Permalink
mem-map: Setup memory for MDRT table
Browse files Browse the repository at this point in the history
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@linux.vnet.ibm.com>
[oliver: rebased]
Signed-off-by: Oliver O'Halloran <oohall@gmail.com>
  • Loading branch information
Vasant Hegde authored and oohal committed Aug 15, 2019
1 parent f10e629 commit bbe6e96
Showing 1 changed file with 7 additions and 1 deletion.
8 changes: 7 additions & 1 deletion include/mem-map.h
Expand Up @@ -89,11 +89,17 @@
#define PSI_TCE_TABLE_BASE (SKIBOOT_BASE + 0x01a00000)
#define PSI_TCE_TABLE_SIZE_P8 0x00200000UL

/* This is our dump result table after MPIPL. Hostboot will write to this
* memory after moving memory 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
Expand Down

0 comments on commit bbe6e96

Please sign in to comment.