[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120612093504.1f7e24f1@doriath.home>
Date: Tue, 12 Jun 2012 09:35:04 -0300
From: Luiz Capitulino <lcapitulino@...hat.com>
To: Wen Congyang <wency@...fujitsu.com>
Cc: kvm list <kvm@...r.kernel.org>, qemu-devel <qemu-devel@...gnu.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Avi Kivity <avi@...hat.com>,
"Daniel P. Berrange" <berrange@...hat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Jan Kiszka <jan.kiszka@...mens.com>,
Gleb Natapov <gleb@...hat.com>
Subject: Re: [Qemu-devel] [PATCH 3/3] deal with guest panicked event
On Tue, 12 Jun 2012 14:55:37 +0800
Wen Congyang <wency@...fujitsu.com> wrote:
> >> +static void panicked_perform_action(void)
> >> +{
> >> + switch(panicked_action) {
> >> + case PANICKED_REPORT:
> >> + panicked_mon_event("report");
> >> + break;
> >> +
> >> + case PANICKED_PAUSE:
> >> + panicked_mon_event("pause");
> >> + vm_stop(RUN_STATE_GUEST_PANICKED);
> >> + break;
> >> +
> >> + case PANICKED_QUIT:
> >> + panicked_mon_event("quit");
> >> + exit(0);
> >> + break;
> >> + }
> >
> > Having the data argument is not needed/wanted. The mngt app can guess it if it
> > needs to know it, but I think it doesn't want to.
>
> Libvirt will do something when the kernel is panicked, so it should know the action
> in qemu side.
But the action will be set by libvirt itself, no?
--
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