Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752803AbdL1Ijv (ORCPT ); Thu, 28 Dec 2017 03:39:51 -0500 Received: from mail-oi0-f67.google.com ([209.85.218.67]:46662 "EHLO mail-oi0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751633AbdL1Ijt (ORCPT ); Thu, 28 Dec 2017 03:39:49 -0500 X-Google-Smtp-Source: ACJfBotj2AYvVI3qn1TBuED0+FIUdv3W1GJt/MD/aN1QMfzotDM5xnbTUfANFUcDAAV2YTiPISROeAvbcGh6fdEWpbk= MIME-Version: 1.0 In-Reply-To: References: <1513860222-40944-1-git-send-email-pbonzini@redhat.com> From: Wanpeng Li Date: Thu, 28 Dec 2017 16:39:48 +0800 Message-ID: Subject: Re: [PATCH 0/4] KVM: nVMX: prepare_vmcs02 optimizations To: Paolo Bonzini Cc: linux-kernel@vger.kernel.org, kvm Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 623 Lines: 15 2017-12-27 22:28 GMT+08:00 Paolo Bonzini : > 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? L0 call trace has already been posted here. https://lkml.org/lkml/2017/12/25/53 In addition, the splatting is still there after I revert the last 9 nVMX optimization patches in kvm/queue. So it is not caused by this patchset. :) Regards, Wanpeng Li