Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751913AbdL0O2n (ORCPT ); Wed, 27 Dec 2017 09:28:43 -0500 Received: from mail-wm0-f43.google.com ([74.125.82.43]:38794 "EHLO mail-wm0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751043AbdL0O2l (ORCPT ); Wed, 27 Dec 2017 09:28:41 -0500 X-Google-Smtp-Source: ACJfBouc7vPsockugCwP14u+WmOShGBFp2QJDDdl6dHJVB05gMLejPMCgC6F3k0ncEZuxYXy+05usw== 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: Date: Wed, 27 Dec 2017 15:28:38 +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: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 307 Lines: 8 On 25/12/2017 11:08, Wanpeng Li wrote: >> I observe L1(latest kvm/queue) panic and L0(latest kvm/queue) >> calltrace, I'm not sure whether it is caused by this patchset. > It can be reproduced steadily by running kvm-unit-tests in L1. It works here, can you show the L0 call trace and/or bisect it? Paolo