From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:45054)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <wency@cn.fujitsu.com>) id 1S8S8D-00042t-6j
	for qemu-devel@nongnu.org; Fri, 16 Mar 2012 04:03:49 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <wency@cn.fujitsu.com>) id 1S8S86-000280-An
	for qemu-devel@nongnu.org; Fri, 16 Mar 2012 04:03:24 -0400
Received: from [222.73.24.84] (port=28253 helo=song.cn.fujitsu.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <wency@cn.fujitsu.com>) id 1S8S86-00027Q-0Y
	for qemu-devel@nongnu.org; Fri, 16 Mar 2012 04:03:18 -0400
Message-ID: <4F62F430.7030103@cn.fujitsu.com>
Date: Fri, 16 Mar 2012 16:05:04 +0800
From: Wen Congyang <wency@cn.fujitsu.com>
MIME-Version: 1.0
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>
	<CAG7+5M0gEpoJ_jnC8_4Ae-xe2rr7+CJLZh3JjAhh=p=-2bEAcA@mail.gmail.com>
	<20120315103923.GL2304@redhat.com>
	<4F61D1AF.4040603@siemens.com> <4F61D688.5040406@redhat.com>
In-Reply-To: <4F61D688.5040406@redhat.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [Qemu-devel] [PATCH 0/2 v3] kvm: notify host when guest panicked
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Avi Kivity <avi@redhat.com>
Cc: kvm list <kvm@vger.kernel.org>, Gleb Natapov <gleb@redhat.com>, Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel <qemu-devel@nongnu.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, Eric Northup <digitaleric@google.com>, Amit Shah <amit.shah@redhat.com>, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>

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