From: Qian Cai <cai@redhat.com>
To: paulmck@kernel.org, Michael Ellerman <mpe@ellerman.id.au>
Cc: Peter Zijlstra <peterz@infradead.org>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/smp: Move rcu_cpu_starting() earlier
Date: Thu, 29 Oct 2020 09:48:36 -0400 [thread overview]
Message-ID: <50aea6567bbdf89e03d50820c19cfb16bb764338.camel@redhat.com> (raw)
In-Reply-To: <20201029003127.GJ3249@paulmck-ThinkPad-P72>
On Wed, 2020-10-28 at 17:31 -0700, Paul E. McKenney wrote:
> On Thu, Oct 29, 2020 at 11:09:07AM +1100, Michael Ellerman wrote:
> > Qian Cai <cai@redhat.com> writes:
> > > The call to rcu_cpu_starting() in start_secondary() is not early enough
> > > in the CPU-hotplug onlining process, which results in lockdep splats as
> > > follows:
> >
> > Since when?
> > What kernel version?
> >
> > I haven't seen this running CPU hotplug tests with PROVE_LOCKING=y on
> > v5.10-rc1. Am I missing a CONFIG?
>
> My guess would be that adding CONFIG_PROVE_RAW_LOCK_NESTING=y will
> get you some splats.
Well, I don't have that set, so it should be CONFIG_PROVE_RCU_LIST=y. Anyway,
this is .config to reproduce on Power9 NV:
https://cailca.coding.net/public/linux/mm/git/files/master/powerpc.config
next prev parent reply other threads:[~2020-10-29 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 18:23 [PATCH] powerpc/smp: Move rcu_cpu_starting() earlier Qian Cai
2020-10-28 20:59 ` Paul E. McKenney
2020-10-29 0:09 ` Michael Ellerman
2020-10-29 0:31 ` Paul E. McKenney
2020-10-29 13:48 ` Qian Cai [this message]
2020-10-29 12:17 ` Qian Cai
2020-11-04 11:38 ` Michael Ellerman
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=50aea6567bbdf89e03d50820c19cfb16bb764338.camel@redhat.com \
--to=cai@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulmck@kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).