From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: qemu-s390x <qemu-s390x@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>,
Thomas Huth <thuth@redhat.com>,
David Hildenbrand <david@redhat.com>,
Halil Pasic <pasic@linux.vnet.ibm.com>,
Eric Blake <eblake@redhat.com>,
Bjoern Walk <bwalk@linux.vnet.ibm.com>,
Boris Fiuczynski <fiuczy@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v6] s390x/cpu: expose the guest crash information
Date: Thu, 8 Feb 2018 09:09:56 +0100 [thread overview]
Message-ID: <20180208090956.63db5456.cohuck@redhat.com> (raw)
In-Reply-To: <238dde55-387e-7f99-b557-67759d182ce3@de.ibm.com>
On Wed, 7 Feb 2018 19:15:22 +0100
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> 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
>
> ?
Looks good to me.
next prev parent reply other threads:[~2018-02-08 8:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 12:38 [Qemu-devel] [PATCH v6] s390x/cpu: expose the guest crash information Christian Borntraeger
2018-02-07 13:07 ` no-reply
2018-02-07 13:15 ` Christian Borntraeger
2018-02-07 13:21 ` David Hildenbrand
2018-02-07 13:29 ` Christian Borntraeger
2018-02-07 14:04 ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2018-02-07 14:32 ` David Hildenbrand
2018-02-07 14:12 ` [Qemu-devel] " no-reply
2018-02-07 16:58 ` Cornelia Huck
2018-02-07 17:56 ` Eric Blake
2018-02-07 18:15 ` Christian Borntraeger
2018-02-08 8:09 ` Cornelia Huck [this message]
2018-02-07 18:44 ` Christian Borntraeger
2018-02-07 19:11 ` Eric Blake
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180208090956.63db5456.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=bwalk@linux.vnet.ibm.com \
--cc=david@redhat.com \
--cc=eblake@redhat.com \
--cc=fiuczy@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).