qemu-s390x
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [qemu-s390x] [PATCH v6] s390x/cpu: expose the guest crash informatio


From: Christian Borntraeger
Subject: Re: [qemu-s390x] [PATCH v6] s390x/cpu: expose the guest crash information
Date: Wed, 7 Feb 2018 19:15:22 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2


On 02/07/2018 05:58 PM, Cornelia Huck wrote:

> 
>> +##
>> +# @S390CrashReason:
>> +#
>> +# Reason why the CPU is in a crashed state.
>> +#
>> +# @unknown: no crash reason was set
>> +#
>> +# @disabledwait: the CPU has entered a disabled wait state
>> +#
>> +# @extintloop: timer interrupt with new PSW enabled for timer
>> +#
>> +# @pgmintloop: program interrupt with BAD new PSW
>> +#
>> +# @opintloop: operation exception interrupt with invalid code at the program
>> +#             interrupt new PSW
>> +#
>> +# Since: 2.12
>> +##
>> +{ 'enum': 'S390CrashReason',
>> +  'data': [ 'unknown',
>> +            'disabledwait',
>> +            'extintloop',
>> +            'pgmintloop',
>> +            'opintloop' ] }
> 
> Would some hyphens or underscores make this a bit more readable? FWICS,
> QAPI would create something like S390_CRASH_REASON_DISABLED_WAIT for
> 'disabled-wait', which looks reasonable to me.


disabled-wait
extint-loop
pgmint-loop
opint-loop 

?
> 
> With the build fix and the description change for extintloop, this
> looks fine to me (with or without a changed enum).
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]