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 v8] s390x/cpu: expose the guest crash information
Date: Tue, 13 Feb 2018 09:54:16 +0100 [thread overview]
Message-ID: <20180213095416.6d35c22c.cohuck@redhat.com> (raw)
In-Reply-To: <20180209122543.25755-1-borntraeger@de.ibm.com>
On Fri, 9 Feb 2018 12:25:43 +0000
Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> This patch is the s390 implementation of guest crash information,
> similar to commit d187e08dc4 ("i386/cpu: add crash-information QOM
> property") and the related commits. We will detect several crash
> reasons, with the "disabled wait" being the most important one, since
> this is used by all s390 guests as a "panic like" notification.
(...)
> Co-authored-by: Jing Liu <liujbjl@linux.vnet.ibm.com>
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> ---
> qapi/run-state.json | 55 +++++++++++++++++++++++++++++++++++++++++++++++++--
> target/s390x/cpu.c | 45 +++++++++++++++++++++++++++++++++++++++++
> target/s390x/cpu.h | 2 ++
> target/s390x/helper.c | 5 ++++-
> target/s390x/kvm.c | 15 +++++++-------
> vl.c | 11 +++++++++--
> 6 files changed, 120 insertions(+), 13 deletions(-)
Thanks, applied.
prev parent reply other threads:[~2018-02-13 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 12:25 [Qemu-devel] [PATCH v8] s390x/cpu: expose the guest crash information Christian Borntraeger
2018-02-12 17:39 ` Cornelia Huck
2018-02-12 17:51 ` Eric Blake
2018-02-12 18:16 ` Cornelia Huck
2018-02-13 8:54 ` Cornelia Huck [this message]
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=20180213095416.6d35c22c.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).