On 08/01/20 11:33, zhenwei pi wrote:
> In previous patch(https://lkml.org/lkml/2019/12/14/265), I defined a new bit
> (bit 1)
> PVPANIC_CRASH_LOADED for guest crash loaded event. And suggested by KH Greg,
> I moved
> the bit definition to an uapi header file.
> Then QEMU could include the header
On 1/8/20 6:05 PM, Paolo Bonzini wrote:
On 08/01/20 10:58, Michal Privoznik wrote:
the kernel-side patch certainly makes sense. I assume that you want the
event to propagate up from QEMU to Libvirt and so on? The QEMU patch
would need to declare a new event (qapi/misc.json) and send it in
han
On 08/01/20 10:58, Michal Privoznik wrote:
>> the kernel-side patch certainly makes sense. I assume that you want the
>> event to propagate up from QEMU to Libvirt and so on? The QEMU patch
>> would need to declare a new event (qapi/misc.json) and send it in
>> handle_event (hw/misc/pvpanic.c).
On 1/8/20 10:36 AM, Paolo Bonzini wrote:
On 08/01/20 09:25, zhenwei pi wrote:
Hey, Paolo
Currently, pvpapic only supports bit 0(PVPANIC_PANICKED).
We usually expect that guest writes ioport (typical 0x505) in
panic_notifier_list callback
during handling panic, then we can handle pvpapic event
On 08/01/20 09:25, zhenwei pi wrote:
> Hey, Paolo
>
> Currently, pvpapic only supports bit 0(PVPANIC_PANICKED).
> We usually expect that guest writes ioport (typical 0x505) in
> panic_notifier_list callback
> during handling panic, then we can handle pvpapic event PVPANIC_PANICKED in
> QEMU.
>