From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: KVM_HYPERCALL
Date: Mon, 18 May 2009 14:33:24 +0300
Message-ID: <4A114784.6050201@redhat.com>
References: <3D9CB4061D1EB3408D4A0B910433453C030BCA8A1B@inbmail01.lsi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
To: "Kumar, Venkat" <Venkat.Kumar@lsi.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx2.redhat.com ([66.187.237.31]:38590 "EHLO mx2.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752461AbZERLd1 (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 18 May 2009 07:33:27 -0400
In-Reply-To: <3D9CB4061D1EB3408D4A0B910433453C030BCA8A1B@inbmail01.lsi.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Kumar, Venkat wrote:
> Hi Avi - Yes the control is not coming to neither " kvm_handle_exit " nor "handle_vmcall" after the hypercall is made from the guest.
> If I am not wrong, the "KVM_HYPERCALL" instruction is expected to work, isn't it?
>   

Yes, it should.  Are you sure the guest is executing this instruction?

-- 
error compiling committee.c: too many arguments to function