From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:58899)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1SAQxv-0002V0-TA
	for qemu-devel@nongnu.org; Wed, 21 Mar 2012 15:13:01 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1SAQxr-0005BV-6u
	for qemu-devel@nongnu.org; Wed, 21 Mar 2012 15:12:59 -0400
Received: from mail-ob0-f173.google.com ([209.85.214.173]:60228)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1SAQxr-0005BN-2T
	for qemu-devel@nongnu.org; Wed, 21 Mar 2012 15:12:55 -0400
Received: by obbwd20 with SMTP id wd20so1003681obb.4
	for <qemu-devel@nongnu.org>; Wed, 21 Mar 2012 12:12:53 -0700 (PDT)
Message-ID: <4F6A2832.9080306@codemonkey.ws>
Date: Wed, 21 Mar 2012 14:12:50 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
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-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Gleb Natapov <gleb@redhat.com>, kvm list <kvm@vger.kernel.org>, 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>

On 03/15/2012 06:46 AM, 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.

Just declare that outl 0x505 is a megaultracall and s/vmcall/outb/g and call it 
a day.

The performance difference between vmcall and outl is so tiny compared to the 
cost of dropping to userspace that it really doesn't matter which instruction is 
used.

Regards,

Anthony Liguori

>