4 pvpanic device is a simulated device, through which a guest panic
5 event is sent to qemu, and a QMP event is generated. This allows
6 management apps (e.g. libvirt) to be notified and respond to the event.
8 The management app has the option of waiting for GUEST_PANICKED events,
9 and/or polling for guest-panicked RunState, to learn when the pvpanic
10 device has fired a panic event.
12 The pvpanic device can be implemented as an ISA device (using IOPORT) or as a
18 pvpanic exposes a single I/O port, by default 0x505. On read, the bits
19 recognized by the device are set. Software should ignore bits it doesn't
20 recognize. On write, the bits not recognized by the device are ignored.
21 Software should set only bits both itself and the device recognize.
27 a guest panic has happened and should be processed by the host
29 a guest panic has happened and will be handled by the guest;
30 the host should record it or report it, but should not affect
31 the execution of the guest.
36 The PCI interface is similar to the ISA interface except that it uses an MMIO
37 address space provided by its BAR0, 1 byte long. Any machine with a PCI bus
38 can enable a pvpanic device by adding ``-device pvpanic-pci`` to the command
44 pvpanic device is defined with ACPI ID "QEMU0001". Custom methods:
49 To determine whether guest panic notification is supported.
54 Returns a byte, with the same semantics as the I/O port interface.
59 To send a guest panic event.
62 Arg0 is a byte to be written, with the same semantics as the I/O interface.
66 The ACPI device will automatically refer to the right port in case it