From: Wanpeng Li <kernellwp@gmail.com>
To: Nitesh Narayan Lal <nitesh@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>,
Wanpeng Li <wanpengli@tencent.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Liran Alon <liran.alon@oracle.com>,
"frederic@kernel.org" <frederic@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Juri Lelli <juri.lelli@redhat.com>
Subject: Re: WARNING: suspicious RCU usage - while installing a VM on a CPU listed under nohz_full
Date: Wed, 29 Jul 2020 10:38:18 +0800 [thread overview]
Message-ID: <CANRm+CwrT=gxxgkNdT3wFwzWYYh3FFrUU=aTqH8VT=MraU7jkw@mail.gmail.com> (raw)
In-Reply-To: <CANRm+Cywhi1p5gYLfG=JcyTdYuWK+9bGqF6HD-LiBJM9Q5ykNQ@mail.gmail.com>
Hi Nitesh，
On Wed, 29 Jul 2020 at 09:00, Wanpeng Li <kernellwp@gmail.com> wrote:
>
> On Tue, 28 Jul 2020 at 22:40, Nitesh Narayan Lal <nitesh@redhat.com> wrote:
> >
> > Hi,
> >
> > I have recently come across an RCU trace with the 5.8-rc7 kernel that has the
> > debug configs enabled while installing a VM on a CPU that is listed under
> > nohz_full.
> >
> > Based on some of the initial debugging, my impression is that the issue is
> > triggered because of the fastpath that is meant to optimize the writes to x2APIC
> > ICR that eventually leads to a virtual IPI in fixed delivery mode, is getting
> > invoked from the quiescent state.
Could you try latest linux-next tree? I guess maybe some patches are
pending in linux-next tree, I can't reproduce against linux-next tree.
next prev parent reply other threads:[~2020-07-29 2:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 14:39 WARNING: suspicious RCU usage - while installing a VM on a CPU listed under nohz_full Nitesh Narayan Lal
2020-07-29 1:00 ` Wanpeng Li
2020-07-29 2:38 ` Wanpeng Li [this message]
2020-07-29 12:34 ` Nitesh Narayan Lal
2020-07-30 22:45 ` Nitesh Narayan Lal
2020-07-31 7:42 ` Wanpeng Li
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='CANRm+CwrT=gxxgkNdT3wFwzWYYh3FFrUU=aTqH8VT=MraU7jkw@mail.gmail.com' \
--to=kernellwp@gmail.com \
--cc=frederic@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=nitesh@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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).