[Skiboot] [PATCH v4 13/18] fadump: Add OPAL API to register for fadump

[Stewart Smith]

Vasant Hegde <hegdevasant at linux.vnet.ibm.com> writes:
> This patch adds new API for fadump.
>   int64_t opal_fadump_manage(uint64_t cmd, void *data, uint64_t dsize)
>
>   cmd : 0x01 -> Register for fadump
>         0x02 -> Unregister fadump
> 	0x03 -> Invalidate existing dump
>
>   data : For cmd = 0x01, data contains payload section reservation details
>          (uses fadump structure format to send data).
>          For other cmd values, data will be NULL.
>   dsize: Size of data
>
> Return values:
>   OPAL_SUCCESS   : Operation success
>   OPAL_PARAMETER : Payload passed invalid data
>   OPAL_RESOURCE  : Ran out of MDST, MDDT table size
>   OPAL_PERMISSION: Already registered
>   OPAL_HARDWARE  : Fadump not supported

I'm thinking that the existing OPAL_(UN)REGISTER_DUMP_REGION calls could
be adequate here?

Even in the case where the kernel doesn't know anything about the new
dump infrastructure, if we passed something back via the OPAL_DUMP_READ
interface that we use on FSP systems today, we'd have a net gain in
functionality without any kernel (or userspace) changes. Or am I missing
something?

-- 
Stewart Smith
OPAL Architect, IBM.