/* * On some Power systems where RMO is 128MB, it still requires minimum of * 256MB for kernel to boot successfully. When kdump infrastructure is * configured to save vmcore over network, we run into OOM issue while * loading modules related to network setup. Hence we need additional 64M * of memory to avoid OOM issue.
*/ #define RTAS_FADUMP_MIN_BOOT_MEM ((0x1UL << 28) + (0x1UL << 26))
/* OS defined sections */ #define RTAS_FADUMP_PARAM_AREA 0x0100
/* Dump request flag */ #define RTAS_FADUMP_REQUEST_FLAG 0x00000001
/* Dump status flag */ #define RTAS_FADUMP_ERROR_FLAG 0x2000
/* * The Firmware Assisted Dump Memory structure supports a maximum of 10 sections * in the dump memory structure. Presently, three sections are used for * CPU state data, HPTE & Parameters area, while the remaining seven sections * can be used for boot memory regions.
*/ #define MAX_SECTIONS 10 #define RTAS_FADUMP_MAX_BOOT_MEM_REGS 7
/* Fields for disk dump option. */
__be32 dd_block_size;
__be64 dd_block_offset;
__be64 dd_num_blocks;
__be32 dd_offset_disk_path;
/* Maximum time allowed to prevent an automatic dump-reboot. */
__be32 max_time_auto;
};
/* * Firmware Assisted dump memory structure. This structure is required for * registering future kernel dump with power firmware through rtas call. * * In version 1, the platform permits one section header, dump-disk path * and ten sections. * * Note: No disk dump option. Hence disk dump path string section is not * included.
*/ struct rtas_fadump_mem_struct { struct rtas_fadump_section_header header; struct rtas_fadump_section rgn[MAX_SECTIONS];
};
/* * The firmware-assisted dump format. * * The register save area is an area in the partition's memory used to preserve * the register contents (CPU state data) for the active CPUs during a firmware * assisted dump. The dump format contains register save area header followed * by register entries. Each list of registers for a CPU starts with "CPUSTRT" * and ends with "CPUEND".
*/
/* Register save area header. */ struct rtas_fadump_reg_save_area_header {
__be64 magic_number;
__be32 version;
__be32 num_cpu_offset;
};
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.