From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] KVM: x86: Fix re-execution of patched vmmcall
Date: Fri, 13 Mar 2015 13:28:04 -0300
Message-ID: <20150313162804.GA16394@amt.cnet>
References: <54FDF42F.5000607@siemens.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: kvm <kvm@vger.kernel.org>, Paolo Bonzini <pbonzini@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:50929 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752730AbbCMSsM (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 13 Mar 2015 14:48:12 -0400
Content-Disposition: inline
In-Reply-To: <54FDF42F.5000607@siemens.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Mon, Mar 09, 2015 at 08:27:43PM +0100, Jan Kiszka wrote:
> For a very long time (since 2b3d2a20), the path handling a vmmcall
> instruction of the guest on an Intel host only applied the patch but no
> longer handled the hypercall. The reverse case, vmcall on AMD hosts, is
> fine. As both em_vmcall and em_vmmcall actually have to do the same, we
> can fix the issue by consolidating both into the same handler.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Applied, thanks.