From: Salil Mehta <salil.mehta@huawei.com>
To: yuzenghui <yuzenghui@huawei.com>
Cc: Marc Zyngier <maz@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Zhuangyuzeng (Yisen)" <yisen.zhuang@huawei.com>,
"Wanghaibin (D)" <wanghaibin.wang@huawei.com>
Subject: RE: [REPORT] possible circular locking dependency when booting a VM on arm64 host
Date: Thu, 9 Jul 2020 11:59:57 +0000 [thread overview]
Message-ID: <937de9e7174f444bb4adae075213c92e@huawei.com> (raw)
In-Reply-To: <7c1bb3c1-3f64-8c24-ed59-eb3da7bf6643@huawei.com>
> From: yuzenghui
> Sent: Thursday, July 9, 2020 12:50 PM
> To: Salil Mehta <salil.mehta@huawei.com>
> Cc: Marc Zyngier <maz@kernel.org>; Thomas Gleixner <tglx@linutronix.de>; Linux
> Kernel Mailing List <linux-kernel@vger.kernel.org>;
> linux-arm-kernel@lists.infradead.org; Zhuangyuzeng (Yisen)
> <yisen.zhuang@huawei.com>; Wanghaibin (D) <wanghaibin.wang@huawei.com>
> Subject: Re: [REPORT] possible circular locking dependency when booting a VM
> on arm64 host
>
> On 2020/7/9 18:54, Salil Mehta wrote:
> > Hi Yuzenghui,
> > I will try to reproduce it today at our platform. Just one question is it easily
> > reproducible or is a rare occurrence?
>
> Salil, it's 100% reproducible once you start a guest. You don't even
> need to assign hostdev to the VM.
Thanks!
next prev parent reply other threads:[~2020-07-09 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 10:41 [REPORT] possible circular locking dependency when booting a VM on arm64 host Zenghui Yu
2020-07-09 10:54 ` Salil Mehta
2020-07-09 11:49 ` Zenghui Yu
2020-07-09 11:59 ` Salil Mehta [this message]
2020-07-15 16:08 ` Marc Zyngier
2020-07-16 0:58 ` Salil Mehta
2020-07-16 8:26 ` Marc Zyngier
2020-07-16 8:14 ` Salil Mehta
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=937de9e7174f444bb4adae075213c92e@huawei.com \
--to=salil.mehta@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=tglx@linutronix.de \
--cc=wanghaibin.wang@huawei.com \
--cc=yisen.zhuang@huawei.com \
--cc=yuzenghui@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).