All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: qemu-s390x <qemu-s390x@nongnu.org>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Cornelia Huck <cohuck@redhat.com>, Thomas Huth <thuth@redhat.com>,
	David Hildenbrand <david@redhat.com>,
	Halil Pasic <pasic@linux.vnet.ibm.com>,
	Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4] s390x/cpu: expose the guest crash information
Date: Mon, 5 Feb 2018 15:43:55 +0100	[thread overview]
Message-ID: <f90354e5-663a-b996-e031-3c2ca12732e5@de.ibm.com> (raw)
In-Reply-To: <20180205141215.50207-1-borntraeger@de.ibm.com>



On 02/05/2018 03:12 PM, Christian Borntraeger wrote:

[...]

> diff --git a/target/s390x/cpu.h b/target/s390x/cpu.h
> index a1123ad621..71414cc324 100644
> --- a/target/s390x/cpu.h
> +++ b/target/s390x/cpu.h
> @@ -77,6 +77,14 @@ typedef struct MchkQueue {
>      uint16_t type;
>  } MchkQueue;
> 
> +/* Crash cases. */
> +enum crash_reasons {
I should add a CRASH_REASON_UNKNOWN,


> +    CRASH_REASON_PGM,
> +    CRASH_REASON_EXT,
> +    CRASH_REASON_WAITPSW,
> +    CRASH_REASON_OPEREXC,
> +};


> +
>  struct CPUS390XState {
>      uint64_t regs[16];     /* GP registers */
>      /*
> @@ -102,6 +110,8 @@ struct CPUS390XState {
> 
>      PSW psw;
> 
> +    enum crash_reasons crash_reason;
> +

as this gets zeroed on reset.
If we ever get called from other code that does not set a crash reason we better
say "unknown"

  reply	other threads:[~2018-02-05 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 14:12 [Qemu-devel] [PATCH v4] s390x/cpu: expose the guest crash information Christian Borntraeger
2018-02-05 14:43 ` Christian Borntraeger [this message]
2018-02-05 15:11   ` Cornelia Huck

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=f90354e5-663a-b996-e031-3c2ca12732e5@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=eblake@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.