From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH 00/12] KVM: x86: Fixes for debug registers, IA32_APIC_BASE, and nVMX Date: Thu, 16 Jan 2014 16:20:45 +0100 Message-ID: <52D7F8CD.8010203@redhat.com> References: <52D7F5D7.5070708@redhat.com> <52D7F6EB.30504@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Gleb Natapov , Marcelo Tosatti , kvm To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:64194 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752204AbaAPPU4 (ORCPT ); Thu, 16 Jan 2014 10:20:56 -0500 In-Reply-To: <52D7F6EB.30504@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: Il 16/01/2014 16:12, Jan Kiszka ha scritto: >> > I'm applying patches 1-10 (for now to kvm/queue). >> > >> > For the last two, I prefer to wait for 3.15. > Should we disable the broken features in 3.14? I was thinking about it---which would have meant applying patches 1-8 only. In the end I decided not to do it because the patch doesn't affect KVM-on-KVM emulation. If the patch already helped you in developing Jailhouse, so the feature must not be _completely_ broken. So the churn of reverting the feature now and reapplying it later is not warranted, IMO. Thanks, Paolo >> > >> > Also, for patch 11 I would really prefer to use check_nested_events for >> > both VMX and SVM. I will look at SVM next week. > OK, thanks. I will send an updated patch 11 and also a patch on top of 4 > to read the physical bit width from the guest cpuid.