From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wen Congyang Subject: Re: [PATCH 0/2 v3] kvm: notify host when guest panicked Date: Fri, 09 Mar 2012 09:21:53 +0800 Message-ID: <4F595B31.9090301@cn.fujitsu.com> References: <4F58664D.1070800@cn.fujitsu.com> <4F58943E.1050402@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Gleb Natapov , kvm list , Jan Kiszka , qemu-devel , "linux-kernel@vger.kernel.org" , KAMEZAWA Hiroyuki To: Avi Kivity Return-path: In-Reply-To: <4F58943E.1050402@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org At 03/08/2012 07:13 PM, Avi Kivity Wrote: > On 03/08/2012 09:57 AM, Wen Congyang wrote: >> We can know the guest is paniced when the guest runs on xen. >> But we do not have such feature on kvm. >> >> Another purpose of this feature is: management app(for example: >> libvirt) can do auto dump when the guest is crashed. If management >> app does not do auto dump, the guest's user can do dump by hand if >> he sees the guest is paniced. >> >> I touch the hypervisor instead of using virtio-serial, because >> 1. it is simple >> 2. the virtio-serial is an optional device, and the guest may >> not have such device. >> >> Changes from v2 to v3: >> 1. correct spelling >> >> Changes from v1 to v2: >> 1. split up host and guest-side changes >> 2. introduce new request flag to avoid changing return values. > > I see no Documentation/ changes. What shoude be writen into Documentation/? I read the documents under Documentation/virtual/kvm, not all KVM_EXIT_* are writen in api.txt. In this patch set, I introduce a new exit_reason: KVM_EXIT_GUEST_PANICKED, but I donot know where I should write. Thanks Wen Congyang