Pierrick Bouvier <pierrick.bouv...@linaro.org> writes: > From: Daniel P. Berrangé <berra...@redhat.com> > > This gives some more context about the behaviour of the commands in > unsupported guest configuration or platform scenarios. > > Reviewed-by: Richard Henderson <richard.hender...@linaro.org> > Signed-off-by: Daniel P. Berrangé <berra...@redhat.com> > Signed-off-by: Pierrick Bouvier <pierrick.bouv...@linaro.org> > --- > qapi/misc-target.json | 43 ++++++++++++++++++++++++++++++++++++------- > 1 file changed, 36 insertions(+), 7 deletions(-) > > diff --git a/qapi/misc-target.json b/qapi/misc-target.json > index c5f9f6be7e1..6b857efc1cc 100644 > --- a/qapi/misc-target.json > +++ b/qapi/misc-target.json > @@ -110,7 +110,11 @@ > ## > # @query-sev: > # > -# Returns information about SEV > +# Returns information about SEV/SEV-ES/SEV-SNP. > +# > +# If unavailable due to an incompatible configuration the > +# returned @enabled field will be set to 'false' and the > +# state of all other fields is undefined.
"Undefined" makes my old C scars hurt. What about "unspecified"? > # > # Returns: @SevInfo > # [...]
