From: zhenwei pi <pizhenwei@bytedance.com>
To: pbonzini@redhat.com
Cc: qemu-devel@nongnu.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, libvir-list@redhat.com,
mprivozn@redhat.com, yelu@bytedance.com,
zhenwei pi <pizhenwei@bytedance.com>
Subject: [PATCH 0/2] implement crashloaded event for pvpanic
Date: Fri, 10 Jan 2020 18:06:32 +0800 [thread overview]
Message-ID: <20200110100634.491936-1-pizhenwei@bytedance.com> (raw)
Guest may handle panic by itself, then just reboot without pvpanic
notification. Then We can't separate the abnormal reboot from
normal operation.
Declear bit 1 for pvpanic as crashloaded event. It should work with
guest kernel side. Link: https://lkml.org/lkml/2019/12/14/265
Before running kexec, guest could wirte this bit to notify host side.
Host side handles crashloaded event, posts event to upper layer.
Then guest side continues to run kexec.
Test with libvirt, libvirt could recieve the new event. The patch of
libvirt will be sent soon.
Zhenwei Pi (2):
pvpanic: introduce crashloaded for pvpanic
pvpanic: implement crashloaded event handling
docs/specs/pvpanic.txt | 8 ++++++--
hw/misc/pvpanic.c | 11 +++++++++--
include/sysemu/runstate.h | 1 +
qapi/run-state.json | 22 +++++++++++++++++++++-
vl.c | 12 ++++++++++++
5 files changed, 49 insertions(+), 5 deletions(-)
--
2.11.0
next reply other threads:[~2020-01-10 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 10:06 zhenwei pi [this message]
2020-01-10 10:06 ` [PATCH 1/2] pvpanic: introduce crashloaded for pvpanic zhenwei pi
2020-01-21 8:22 ` Markus Armbruster
2020-01-21 10:50 ` Paolo Bonzini
2020-01-21 13:38 ` Markus Armbruster
2020-01-10 10:06 ` [PATCH 2/2] pvpanic: implement crashloaded event handling zhenwei pi
2020-01-21 8:37 ` Markus Armbruster
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=20200110100634.491936-1-pizhenwei@bytedance.com \
--to=pizhenwei@bytedance.com \
--cc=gregkh@linuxfoundation.org \
--cc=libvir-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mprivozn@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yelu@bytedance.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).