From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH 0/4] KVM: nVMX: prepare_vmcs02 optimizations Date: Mon, 1 Jan 2018 10:36:19 +0100 Message-ID: References: <1513860222-40944-1-git-send-email-pbonzini@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, kvm To: Wanpeng Li Return-path: Received: from mail-wm0-f48.google.com ([74.125.82.48]:44263 "EHLO mail-wm0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751169AbeAAJgZ (ORCPT ); Mon, 1 Jan 2018 04:36:25 -0500 In-Reply-To: Content-Language: en-US Sender: kvm-owner@vger.kernel.org List-ID: On 28/12/2017 09:39, Wanpeng Li wrote: > 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. :) Hmm, maybe you're using "-cpu host,+umip"? I'll check when I get back to work tomorrow. Paolo