From: Mukesh R <mrat...@linux.microsoft.com> Sent: Monday, September 15, 2025
6:15 PM
>
> On 9/15/25 10:54, Michael Kelley wrote:
> > From: Mukesh Rathor <mrat...@linux.microsoft.com> Sent: Tuesday, September
> > 9, 2025 5:10 PM
> >>
> >> Add data structures for hypervisor crash dump support to the hypervisor
> >> host ABI header file. Details of their usages are in subsequent commits.
> >>
> >> Signed-off-by: Mukesh Rathor <mrat...@linux.microsoft.com>
> >> ---
> >> include/hyperv/hvhdk_mini.h | 55 +++++++++++++++++++++++++++++++++++++
> >> 1 file changed, 55 insertions(+)
> >>
> >> diff --git a/include/hyperv/hvhdk_mini.h b/include/hyperv/hvhdk_mini.h
> >> index 858f6a3925b3..ad9a8048fb4e 100644
> >> --- a/include/hyperv/hvhdk_mini.h
> >> +++ b/include/hyperv/hvhdk_mini.h
> >>
[snip]
> >> +enum hv_crashdump_action {
> >> + HV_CRASHDUMP_NONE = 0,
> >> + HV_CRASHDUMP_SUSPEND_ALL_VPS,
> >> + HV_CRASHDUMP_PREPARE_FOR_STATE_SAVE,
> >> + HV_CRASHDUMP_STATE_SAVED,
> >> + HV_CRASHDUMP_ENTRY,
> >> +};
> >
> > Nit: Since these values are part of the ABI, it's probably better
> > to assign explicit values to each enum member in order to
> > ward off any mistaken reordering or additions in the middle
> > of the list.
>
> No, like I have mentioned in the past, we are mirroring hyp headers
> with the eventual goal of just consuming from there directly.
> Each change in ABI header is very carefully examined, we now have
> a process for it.
>
Acknowledged. I keep wanting to tighten up the ABI specification,
and sometimes forget that there are constraints on doing so.
Michael
