[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F606E06.8070302@redhat.com>
Date: Wed, 14 Mar 2012 12:08:06 +0200
From: Avi Kivity <avi@...hat.com>
To: Wen Congyang <wency@...fujitsu.com>
CC: Amit Shah <amit.shah@...hat.com>,
"Daniel P. Berrange" <berrange@...hat.com>,
kvm list <kvm@...r.kernel.org>,
qemu-devel <qemu-devel@...gnu.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Jan Kiszka <jan.kiszka@...mens.com>,
Gleb Natapov <gleb@...hat.com>
Subject: Re: [PATCH 0/2 v3] kvm: notify host when guest panicked
On 03/14/2012 12:04 PM, Wen Congyang wrote:
> >
> > This is sufficient. On the host, you can open /tmp/foo using a custom
> > program or nc (nc -U /tmp/foo). On the guest, you can just open
> > /dev/virtio-ports/port1 and read/write into it.
>
> I have two questions:
> 1. does it OK to open this device when the guest is panicked?
>
On panic, I think it's best to reset the device and drive it directly
from the panic handler.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists