diff options
| author | Madhavan Srinivasan <maddy@linux.vnet.ibm.com> | 2017-10-11 23:20:04 +0530 |
|---|---|---|
| committer | Stewart Smith <stewart@linux.vnet.ibm.com> | 2017-10-15 20:08:14 -0500 |
| commit | 9750eee802f8d6396147ee4e046e1859949a0e55 (patch) | |
| tree | ef1a85f126817d091ea35b960e468ed1eb4f1c17 /doc/xscom-node-bindings.rst | |
| parent | a9cf7c586871bdd8187760862c2df8bb2fbb2d6f (diff) | |
| download | skiboot-9750eee802f8d6396147ee4e046e1859949a0e55.zip skiboot-9750eee802f8d6396147ee4e046e1859949a0e55.tar.gz skiboot-9750eee802f8d6396147ee4e046e1859949a0e55.tar.bz2 | |
hw/imc: pause microcode at boot
IMC nest counters has both in-band (ucode access) and out of
band access to it. Since not all nest counter configurations
are supported by ucode, out of band tools are used to characterize
other configuration.
So it is prefer to pause the nest microcode at boot to aid the
nest out of band tools. If the ucode not paused and OS does not
have IMC driver support, then out to band tools will race with
ucode and end up getting undesirable values. Patch to check and
pause the ucode at boot.
OPAL provides APIs to control IMC counters. OPAL_IMC_COUNTERS_INIT
is used to initialize these counters at boot. OPAL_IMC_COUNTERS_START
and OPAL_IMC_COUNTERS_STOP API calls should be used to start and pause
these IMC engines. `doc/opal-api/opal-imc-counters.rst` details the
OPAL APIs and their usage.
Signed-off-by: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Diffstat (limited to 'doc/xscom-node-bindings.rst')
0 files changed, 0 insertions, 0 deletions