Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752696AbeABNC3 (ORCPT + 1 other); Tue, 2 Jan 2018 08:02:29 -0500 Received: from mail-wm0-f41.google.com ([74.125.82.41]:36250 "EHLO mail-wm0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751514AbeABNC1 (ORCPT ); Tue, 2 Jan 2018 08:02:27 -0500 X-Google-Smtp-Source: ACJfBov2uQ5QhAEtqkLOeADtDuBwsEZcmIhn+dk6OkTn5HB+eVOmpFasWxuecn/KtVaXwcbi3WfE3w== Subject: Re: [PATCH 0/4] KVM: nVMX: prepare_vmcs02 optimizations To: Wanpeng Li Cc: linux-kernel@vger.kernel.org, kvm References: <1513860222-40944-1-git-send-email-pbonzini@redhat.com> From: Paolo Bonzini Message-ID: <8a500669-8529-de09-343c-fd54172a588f@redhat.com> Date: Tue, 2 Jan 2018 14:02:23 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On 02/01/2018 02:05, Wanpeng Li wrote: > The issue is still there after applying this to both L0 and L1, > actually, I can observe a vmentry fail just before the splatting in L0 > w/ and w/o the above code. In addition, I comment out the other > testcases in unittests.cfg except vmx_controls, then run > ./run_tests.sh. Ok, I didn't understand that you're running vmx.flat inside L1 (thus creating an L3 guest). The patch I sent is wrong, because SECONDARY_EXEC_DESC should always be clear in vmx->secondary_exec_control. Note that even with "-cpu host,+vmx,-umip" I get a hang at PASS: Use TPR shadow enabled: TPR threshold 0x10: vmlaunch fails So that might not be entirely related. However, the failures with descriptor exiting are new. Paolo