From: "Longpeng (Mike)" <longpeng2@huawei.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Alex Williamson" <alex.williamson@redhat.com>,
kvm <kvm@vger.kernel.org>, "Radim Krčmář" <rkrcmar@redhat.com>,
"Huangweidong (C)" <weidong.huang@huawei.com>,
Gonglei <arei.gonglei@huawei.com>,
"wangxin (U)" <wangxinxin.wang@huawei.com>
Subject: Re: [help] host kernel panic in kvm's wakeup_handler()
Date: Fri, 26 May 2017 18:53:06 +0800 [thread overview]
Message-ID: <59280912.2000303@huawei.com> (raw)
In-Reply-To: <11b3f9a3-7c89-639e-84e0-219c9e376a66@redhat.com>
On 2017/5/26 18:40, Paolo Bonzini wrote:
>
>
> On 24/05/2017 07:04, Longpeng (Mike) wrote:
>>>> it crashed at *1ec1* and %rax get a wrong value(0xdead000000100100) at *1e92*,
>>>> it seems the *blocked_vcpu_on_cpu* list is corrupted, but kvm only access this
>>>> list in pre_block/post_block/wakeup_handler, and these three functions seems good.
>>>>
>>>> kvm version is 4.4-stable.
>>>>
>>>> Do you have any ideas? Any suggestion would be greatly appreciated, thanks!
>>>>
>>> Is this only seen with posted interrupt support enabled? Booting with
>>> intremap=nopost on the kernel commandline would disable it. Thanks,
>>
>> We tested with PI support enabled, but we not sure if it only occurs with PI
>> enabled yet.
>
> This code should not run at all with PI disabled, since the handler is
> only reachable through an IRTE.
>
> As you said, the list manipulation in those function is fairly simple.
> If you have a reproducer, you can try running it with CONFIG_LIST_DEBUG
> and see what you get.
>
OK.
We have already started test for a long time, but didn't panic yet.
Thanks :)
> Thanks,
>
> Paolo
>
> .
>
--
Regards,
Longpeng(Mike)
next prev parent reply other threads:[~2017-05-26 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 3:57 [help] host kernel panic in kvm's wakeup_handler() Longpeng (Mike)
2017-05-24 4:34 ` Alex Williamson
2017-05-24 5:04 ` Longpeng (Mike)
2017-05-26 10:40 ` Paolo Bonzini
2017-05-26 10:53 ` Longpeng (Mike) [this message]
2017-06-05 16:21 ` Longpeng (Mike)
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=59280912.2000303@huawei.com \
--to=longpeng2@huawei.com \
--cc=alex.williamson@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=wangxinxin.wang@huawei.com \
--cc=weidong.huang@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.