[Skiboot] [PATCH v3 2/2] doc/opal-api: Add OPAL_CEC_REBOOT2 OPAL call description
Mahesh J Salgaonkar
mahesh at linux.vnet.ibm.com
Wed Jul 29 04:06:03 AEST 2015
From: Vipin K Parashar <vipin at linux.vnet.ibm.com>
This patch adds doc/opal-api/opal-cec-reboot-6-116.txt file
to add description for OPAL_CEC_REBOOT* OPAL call.
Signed-off-by: Vipin K Parashar <vipin at linux.vnet.ibm.com>
Signed-off-by: Mahesh Salgaonkar <mahesh at linux.vnet.ibm.com>
---
doc/opal-api/opal-cec-reboot-6-116.txt | 55 ++++++++++++++++++++++++++++++++
1 file changed, 55 insertions(+)
create mode 100644 doc/opal-api/opal-cec-reboot-6-116.txt
diff --git a/doc/opal-api/opal-cec-reboot-6-116.txt b/doc/opal-api/opal-cec-reboot-6-116.txt
new file mode 100644
index 0000000..6f6be11
--- /dev/null
+++ b/doc/opal-api/opal-cec-reboot-6-116.txt
@@ -0,0 +1,55 @@
+OPAL_CEC_REBOOT and OPAL_CEC_REBOOT2
+------------------------------------
+
+#define OPAL_CEC_REBOOT 6
+#define OPAL_CEC_REBOOT2 116
+
+There are two opal calls to invoke system reboot.
+OPAL_CEC_REBOOT: Used for normal reboot by linux host.
+
+OPAL_CEC_REBOOT2: Newly introduced to handle abnormal system reboots.
+The Linux kernel will make this OPAL call when it has to terminate
+abruptly due to an anomalous condition. The kernel will push some system
+state context to OPAL, which will in turn push it down to the BMC for
+further analysis.
+
+OPAL_CEC_REBOOT
+---------------
+Syntax:
+int64_t opal_cec_reboot(void)
+
+Input parameters:
+None.
+
+System reboots normally.
+
+OPAL_CEC_REBOOT2
+----------------
+Syntax:
+int64_t opal_cec_reboot2(uint32_t reboot_type, uint64_t diag, uint64_t size)
+
+Input parameters:
+ @reboot_type Type of reboot. (see below)
+ @diag Pointer to buffer containing debug information.
+ @size Size of the diag buffer.
+
+Depending on reboot type the this call will carry out additional steps
+before triggering reboot.
+
+Supported reboot types:
+----------------------
+OPAL_REBOOT_NORMAL = 0
+ Behavior is as similar to that of opal_cec_reboot()
+
+OPAL_REBOOT_PLATFORM_ERROR = 1
+ Log an error to the BMC and then trigger a system checkstop, using
+ the information provided by 'ibm,sw-checkstop-fir' property in the
+ device-tree. Post the checkstop trigger, OCC/BMC will collect
+ relevant data for error analysis and trigger a reboot.
+
+ In absence of 'ibm,sw-checkstop-fir' device property, this function
+ will return with OPAL_UNSUPPORTED and no reboot will be triggered.
+
+Unsupported Reboot type
+ For unsupported reboot type, this function will return with
+ OPAL_UNSUPPORTED and no reboot will be triggered.
More information about the Skiboot
mailing list