From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 4/5] KVM: SVM: Allow EFER.LMSLE to be set with nested svm Date: Thu, 06 May 2010 14:42:35 +0300 Message-ID: <4BE2AB2B.5040107@redhat.com> References: <1273068285-3105-1-git-send-email-joerg.roedel@amd.com> <1273068285-3105-5-git-send-email-joerg.roedel@amd.com> <4BE184E3.1010508@redhat.com> <4BE1DB9C.7000405@amd.com> <20100506093842.GE7515@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Przywara, Andre" , Marcelo Tosatti , "kvm@vger.kernel.org" , "linux-kernel@vger.kernel.org" To: "Roedel, Joerg" Return-path: In-Reply-To: <20100506093842.GE7515@amd.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 05/06/2010 12:38 PM, Roedel, Joerg wrote: > Subject: [PATCH] KVM: X86: Inject #GP with the right rip on efer writes > This patch fixes a bug in the KVM efer-msr write path. If a > guest writes to a reserved efer bit the set_efer function > injects the #GP directly. The architecture dependent wrmsr > function does not see this, assumes success and advances the > rip. This results in a #GP in the guest with the wrong rip. > This patch fixes this by reporting efer write errors back to > the architectural wrmsr function. > Applied, thanks. -- error compiling committee.c: too many arguments to function