Madhavan Srinivasan <maddy@xxxxxxxxxxxxxxxxxx> writes:Hi stewart,
(I'll comment on the skiboot one too), but I think that if the class* in patch 9 should opal_imc_counters_init return something otherSo, init call will return OPAL_PARAMETER for the unsupported
than OPAL_SUCCESS in the case on invalid arguments? Maybe
OPAL_PARAMETER? (I think you fix this in a later patch anyway?)
domains (core and nest are supported). And if the init operation
fails for any reason, it would return OPAL_HARDWARE. And this is
documented.
exists but init is a no-op, then OPAL_IMC_COUNTERS_INIT should return
OPAL_SUCCESS and just do nothing. This future proofs everything, and the
API is that one *must* call _INIT before start.