From: Paolo Bonzini <pbonzini@redhat.com>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: linux-kernel@vger.kernel.org, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH 0/4] KVM: nVMX: prepare_vmcs02 optimizations
Date: Wed, 27 Dec 2017 15:28:38 +0100 [thread overview]
Message-ID: <d4122b14-710f-5b50-c4f2-095901756e19@redhat.com> (raw)
In-Reply-To: <CANRm+CxN8F_Wvb3w6e0rxXz6AwsnhE_Ugf5coJAMvqrGz0H+-A@mail.gmail.com>
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
next prev parent reply other threads:[~2017-12-27 14:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 12:43 Paolo Bonzini
2017-12-21 12:43 ` [PATCH 1/4] KVM: VMX: split list of shadowed VMCS field to a separate file Paolo Bonzini
2017-12-21 22:51 ` Jim Mattson
2017-12-21 12:43 ` [PATCH 2/4] KVM: nVMX: track dirty state of non-shadowed VMCS fields Paolo Bonzini
2017-12-21 22:57 ` Jim Mattson
2017-12-25 3:03 ` Wanpeng Li
2017-12-31 8:08 ` Paolo Bonzini
2017-12-31 22:48 ` Wanpeng Li
2017-12-21 12:43 ` [PATCH 3/4] KVM: nVMX: initialize descriptor cache fields in prepare_vmcs02_full Paolo Bonzini
2017-12-21 12:43 ` [PATCH 4/4] KVM: nVMX: initialize more non-shadowed " Paolo Bonzini
2017-12-25 3:09 ` Wanpeng Li
2017-12-27 9:54 ` Paolo Bonzini
2017-12-28 2:07 ` Wanpeng Li
2017-12-25 10:07 ` [PATCH 0/4] KVM: nVMX: prepare_vmcs02 optimizations Wanpeng Li
2017-12-25 10:08 ` Wanpeng Li
2017-12-27 14:28 ` Paolo Bonzini [this message]
2017-12-28 8:39 ` Wanpeng Li
2018-01-01 9:36 ` Paolo Bonzini
2018-01-01 23:01 ` Paolo Bonzini
2018-01-02 1:05 ` Wanpeng Li
2018-01-02 13:02 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d4122b14-710f-5b50-c4f2-095901756e19@redhat.com \
--to=pbonzini@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®