From: zhenwei pi <pizhenwei@bytedance.com>
To: pbonzini@redhat.com
Cc: gregkh@linuxfoundation.org, yelu@bytedance.com,
qemu-devel@nongnu.org, zhenwei pi <pizhenwei@bytedance.com>,
mprivozn@redhat.com
Subject: [PATCH 1/2] pvpanic: introduce crashloaded for pvpanic
Date: Tue, 14 Jan 2020 10:31:01 +0800 [thread overview]
Message-ID: <20200114023102.612548-2-pizhenwei@bytedance.com> (raw)
In-Reply-To: <20200114023102.612548-1-pizhenwei@bytedance.com>
Add bit 1 for pvpanic. This bit means that guest hits a panic, but
guest wants to handle error by itself. Typical case: Linux guest runs
kdump in panic. It will help us to separate the abnormal reboot from
normal operation.
Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
---
docs/specs/pvpanic.txt | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/docs/specs/pvpanic.txt b/docs/specs/pvpanic.txt
index c7bbacc778..bdea68a430 100644
--- a/docs/specs/pvpanic.txt
+++ b/docs/specs/pvpanic.txt
@@ -16,8 +16,12 @@ pvpanic exposes a single I/O port, by default 0x505. On read, the bits
recognized by the device are set. Software should ignore bits it doesn't
recognize. On write, the bits not recognized by the device are ignored.
Software should set only bits both itself and the device recognize.
-Currently, only bit 0 is recognized, setting it indicates a guest panic
-has happened.
+
+Bit Definition
+--------------
+bit 0: setting it indicates a guest panic has happened.
+bit 1: named crashloaded. setting it indicates a guest panic and run
+ kexec to handle error by guest itself.
ACPI Interface
--------------
--
2.11.0
next prev parent reply other threads:[~2020-01-14 2:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 2:31 [PATCH 0/2] pvpanic: implement crashloaded event for pvpanic zhenwei pi
2020-01-14 2:31 ` zhenwei pi [this message]
2020-01-18 20:50 ` [PATCH 1/2] pvpanic: introduce crashloaded " Paolo Bonzini
2020-01-14 2:31 ` [PATCH 2/2] pvpanic: implement crashloaded event handling zhenwei pi
2020-01-18 20:52 ` Paolo Bonzini
2020-01-20 19:12 ` Eric Blake
2020-01-21 10:49 ` Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2020-01-10 10:06 [PATCH 0/2] implement crashloaded event for pvpanic zhenwei pi
2020-01-10 10:06 ` [PATCH 1/2] pvpanic: introduce crashloaded " zhenwei pi
2020-01-21 8:22 ` Markus Armbruster
2020-01-21 10:50 ` Paolo Bonzini
2020-01-21 13:38 ` 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=20200114023102.612548-2-pizhenwei@bytedance.com \
--to=pizhenwei@bytedance.com \
--cc=gregkh@linuxfoundation.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).