[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C21C136.9070708@redhat.com>
Date: Wed, 23 Jun 2010 11:09:26 +0300
From: Avi Kivity <avi@...hat.com>
To: "Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>
CC: Gleb Natapov <gleb@...hat.com>,
LKML <linux-kernel@...r.kernel.org>, kvm@...r.kernel.org,
Ingo Molnar <mingo@...e.hu>,
Fr??d??ric Weisbecker <fweisbec@...il.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Cyrill Gorcunov <gorcunov@...il.com>,
Lin Ming <ming.m.lin@...el.com>,
Sheng Yang <sheng@...ux.intel.com>,
Marcelo Tosatti <mtosatti@...hat.com>,
oerg Roedel <joro@...tes.org>,
Jes Sorensen <Jes.Sorensen@...hat.com>,
Zachary Amsden <zamsden@...hat.com>, zhiteng.huang@...el.com,
tim.c.chen@...el.com, Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH V2 3/5] ara virt interface of perf to support kvm guest
os statistics collection in guest os
On 06/23/2010 04:43 AM, Zhang, Yanmin wrote:
>
>> A reset does not involve destroying a vm; you have to clean up as part
>> of the rest process.
>>
> What does 'reset' here mean? Is it a reboot or halt? If it's a halt, it involves
> destroying a vm. If a host user just kills the qemu process, is it a reset involving
> destroying a vm?
>
'reset' is either a complete reset ('system_reset' on the qemu monitor,
cycles through the bios etc.) or just an INIT signal to one vcpu.
Neither involves destroying a vm.
>> You aren't guaranteed a reboot notifier will be called. On the other
>> hand, we need a kexec handler.
>>
> ordinary kexec calls all reboot notifiers. Only crash kexec doesn't call them.
> I will implement a machine_ops.crash_shutdown callback.
>
Thanks.
--
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