[Skiboot] [PATCH v5 6/8] skiboot: Add documentation for nest IMC opal call
Hemant Kumar
hemant at linux.vnet.ibm.com
Wed Feb 8 08:11:51 AEDT 2017
This patch adds documentation for the the opal call
opal_nest_imc_counters_control().
Signed-off-by: Hemant Kumar <hemant at linux.vnet.ibm.com>
---
Changelog:
v2 -> v3:
- Changed references from IMA to IMC.
v1 -> v2:
- Changed references for "pore_slw" to "IMA Microcode".
doc/opal-api/opal-nest-imc-counters.rst | 49 +++++++++++++++++++++++++++++++++
1 file changed, 49 insertions(+)
create mode 100644 doc/opal-api/opal-nest-imc-counters.rst
diff --git a/doc/opal-api/opal-nest-imc-counters.rst b/doc/opal-api/opal-nest-imc-counters.rst
new file mode 100644
index 0000000..74c96d8
--- /dev/null
+++ b/doc/opal-api/opal-nest-imc-counters.rst
@@ -0,0 +1,49 @@
+OPAL_NEST_IMC_COUNTERS_CONTROL
+==============================
+
+OPAL call interface for per-chip nest instrumentation support.
+Currently, the interface supports starting and stopping the In Memory
+Collection Microcode running in the OCC complex for Nest
+Instrumentation from Host OS.
+
+The interface can be extended to include more modes and operations to use
+the multiple debug modes for nest IMC instrumentation.
+
+Parameters
+----------
+``uint64_t mode``
+ Currently, only production mode is supported.
+ The "NEST_IMC_PRODUCTION_MODE" macro defined in "include/imc.h"
+ is used for this.
+
+``uint64_t operation``
+ For "NEST_IMC_PRODUCTION_MODE" mode, this parameter is used
+ to start and stop the IMC microcode. (include/opal-api.h)
+
+ - OPAL_NEST_IMC_STOP -- Stop
+ - OPAL_NEST_IMC_START -- Start
+
+ For other modes, this parameter is undefined for now.
+
+``uint64_t value_1``
+ - For "NEST_IMC_PRODUCTION_MODE" mode, this parameter should be
+ zero.
+ - For other modes, this parameter is undefined for now.
+
+``uint64_t value_3``
+ - For "NEST_IMC_PRODUCTION_MODE" mode, this parameter should be
+ zero.
+ - For other modes, this parameter is undefined for now.
+
+Returns
+-------
+OPAL_PARAMETER
+ In any one/some/all of the following cases :
+
+ - Unsupported ``mode``
+ - Unsupported ``operation``
+ - Non-zero ``value_1`` or ``value_2``
+OPAL_HARDWARE
+ If xscom_write fails.
+OPAL_SUCCESS
+ On successful execution of the ``operation`` in the given ``mode``.
--
2.7.4
More information about the Skiboot
mailing list