From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/5] Important fixes for KVM-AMD Date: Thu, 06 May 2010 11:51:16 +0300 Message-ID: <4BE28304.9090005@redhat.com> References: <1273068285-3105-1-git-send-email-joerg.roedel@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , kvm@vger.kernel.org, linux-kernel@vger.kernel.org To: Joerg Roedel Return-path: In-Reply-To: <1273068285-3105-1-git-send-email-joerg.roedel@amd.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 05/05/2010 05:04 PM, Joerg Roedel wrote: > Hi Avi, Marcelo, > > here is a set of patches which fix problems in kvm-amd. Patch 1 fixes a > stupid problem with the event-reinjection introduced by me in my > previous patchset. Patch 2 was a helper to find the bug patch 3 fixes. > I kept it in the patchset because it may be helpful in the future to > debug other problems too. Patch 3 is the most important fix because it > makes kvm-amd on 32 bit hosts work again. Without this patch the first > vmrum fails with exit-reason VMEXIT_INVALID. Patch 4 fixes the Xen 4.0 > shipped with SLES11 in nested svm. The last patch in this series fixes a > potential l2-guest breakout scenario because it may be possible for the > l2-guest to issue hypercalls directly to the host if the l1-hypervisor > does not intercept VMMCALL. > All applied, thanks. -- error compiling committee.c: too many arguments to function