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, 16 Mar 2012 16:05:04 +0800 Message-ID: <4F62F430.7030103@cn.fujitsu.com> References: <4F60726E.3090807@cn.fujitsu.com> <4F607325.6050607@redhat.com> <20120314104608.GU2304@redhat.com> <4F607789.4010109@redhat.com> <4F607CE4.2060809@cn.fujitsu.com> <4F609822.7050502@redhat.com> <20120314131415.GB2304@redhat.com> <4F609A15.5020902@redhat.com> <20120314132552.GC2304@redhat.com> <20120315103923.GL2304@redhat.com> <4F61D1AF.4040603@siemens.com> <4F61D688.5040406@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , Gleb Natapov , Eric Northup , "Daniel P. Berrange" , kvm list , qemu-devel , "linux-kernel@vger.kernel.org" , KAMEZAWA Hiroyuki , Amit Shah To: Avi Kivity Return-path: In-Reply-To: <4F61D688.5040406@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org At 03/15/2012 07:46 PM, Avi Kivity Wrote: > On 03/15/2012 01:25 PM, Jan Kiszka wrote: >>>> >>> There was such vm exit (KVM_EXIT_HYPERCALL), but it was deemed to be a >>> bad idea. >> >> BTW, this would help a lot in emulating hypercalls of other hypervisors >> (or of KVM's VAPIC in the absence of in-kernel irqchip - I had to jump >> through hoops therefore) in user space. Not all those hypercall handlers >> actually have to reside in the KVM module. >> > > That is true. On the other hand the hypercall ABI might go to pieces if > there was no central implementation. > I prefer this: host <-> guest kernel: use hypercall host <-> guest userspace: use virtio-serial(or other way that not modify kernel) Thanks Wen Congyang