aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorzhenwei pi <pizhenwei@bytedance.com>2020-01-14 10:31:01 +0800
committerPaolo Bonzini <pbonzini@redhat.com>2020-01-24 20:59:07 +0100
commit600d7b47e8f5085919fd1d1157f25950ea8dbc11 (patch)
tree803b2f724a4583417a95a55a14dbdec8147f5c53 /docs
parentbc9888f759baa64ab6084e4dd8e24ba80b0c3143 (diff)
pvpanic: introduce crashloaded for pvpanic
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> Message-Id: <20200114023102.612548-2-pizhenwei@bytedance.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/specs/pvpanic.txt8
1 files 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
--------------