[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200110100634.491936-1-pizhenwei@bytedance.com>
Date: Fri, 10 Jan 2020 18:06:32 +0800
From: zhenwei pi <pizhenwei@...edance.com>
To: pbonzini@...hat.com
Cc: qemu-devel@...gnu.org, linux-kernel@...r.kernel.org,
gregkh@...uxfoundation.org, libvir-list@...hat.com,
mprivozn@...hat.com, yelu@...edance.com,
zhenwei pi <pizhenwei@...edance.com>
Subject: [PATCH 0/2] implement crashloaded event for pvpanic
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
Powered by blists - more mailing lists