0001 What: /sys/firmware/opal/dump
0002 Date: Feb 2014
0003 Contact: Stewart Smith <stewart@linux.vnet.ibm.com>
0004 Description:
0005 This directory exposes interfaces for interacting with
0006 the FSP and platform dumps through OPAL firmware interface.
0007
0008 This is only for the powerpc/powernv platform.
0009
0010 =============== ===============================================
0011 initiate_dump: When '1' is written to it,
0012 we will initiate a dump.
0013 Read this file for supported commands.
0014
0015 0xXX-0xYYYY: A directory for dump of type 0xXX and
0016 id 0xYYYY (in hex). The name of this
0017 directory should not be relied upon to
0018 be in this format, only that it's unique
0019 among all dumps. For determining the type
0020 and ID of the dump, use the id and type files.
0021 Do not rely on any particular size of dump
0022 type or dump id.
0023 =============== ===============================================
0024
0025 Each dump has the following files:
0026
0027 =============== ===============================================
0028 id: An ASCII representation of the dump ID
0029 in hex (e.g. '0x01')
0030 type: An ASCII representation of the type of
0031 dump in the format "0x%x %s" with the ID
0032 in hex and a description of the dump type
0033 (or 'unknown').
0034 Type '0xffffffff unknown' is used when
0035 we could not get the type from firmware.
0036 e.g. '0x02 System/Platform Dump'
0037 dump: A binary file containing the dump.
0038 The size of the dump is the size of this file.
0039 acknowledge: When 'ack' is written to this, we will
0040 acknowledge that we've retrieved the
0041 dump to the service processor. It will
0042 then remove it, making the dump
0043 inaccessible.
0044 Reading this file will get a list of
0045 supported actions.
0046 =============== ===============================================
