From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/3] Nested TSC handling Date: Wed, 10 Aug 2011 18:40:34 +0300 Message-ID: <4E42A672.5060005@redhat.com> References: <1312289591-nyh@il.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, "Roedel, Joerg" , Zachary Amsden , Bandan Das , Marcelo Tosatti To: "Nadav Har'El" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:37596 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750826Ab1HJPkp (ORCPT ); Wed, 10 Aug 2011 11:40:45 -0400 In-Reply-To: <1312289591-nyh@il.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: On 08/02/2011 03:53 PM, Nadav Har'El wrote: > The following are patches I propose for fixing the bug discovered by Bandan > Das and discussed in the "Nested VMX - L1 hangs on running L2" thread. > > The first patch should fix the originally-reported bug, as explained in the > aforementioned thread: A new x86_op read_l1_tsc() is called L1's TSC is > needed, instead of assuming that calling kvm_read_msr() will do that > (because this has to return L2's TSC when a nested guest is running). > > The second and third patches fix relatively-unimportant corner cases in > nested VMX and nested SVM TSC handling. > > I'd appreciate it if the people who noticed this bug can verify that these > patches indeed solve it for them. > Thanks, applied. -- error compiling committee.c: too many arguments to function