From: Anton Blanchard <anton@samba.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: CPU hotplug hits oops in select_idle_sibling()
Date: Sun, 9 Oct 2016 12:16:09 +1100 [thread overview]
Message-ID: <20161009121609.7a973b5c@kryten> (raw)
In-Reply-To: <20161008140304.GH3142@twins.programming.kicks-ass.net>
Hi Peter,
> > I updated to mainline as of today and tried CPU hotplug via the
> > ppc64_cpu tool:
>
> http://lkml.kernel.org/r/1475922278-3306-1-git-send-email-wanpeng.li@hotmail.com
Thanks, this fixes the issue for me.
Anton
prev parent reply other threads:[~2016-10-09 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 11:07 CPU hotplug hits oops in select_idle_sibling() Anton Blanchard
2016-10-08 14:03 ` Peter Zijlstra
2016-10-09 1:16 ` Anton Blanchard [this message]
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=20161009121609.7a973b5c@kryten \
--to=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=svaidy@linux.vnet.ibm.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).