From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: [PATCH v2 0/3] avoid secondary hold spinloop when possible
Date: Mon, 23 Oct 2017 18:05:04 +1000 [thread overview]
Message-ID: <20171023080507.21974-1-npiggin@gmail.com> (raw)
I've made this series only avoid the secondary spinloop on powernv.
pSeries is a little bit more complicated, some cases in kexec the
secondaries will be at 0x60. I haven't had time to get all that
sorted out for this merge window, so OPAL-only this time.
Nicholas Piggin (3):
powerpc/powernv: Always stop secondaries before reboot/shutdown
powerpc: use NMI IPI for smp_send_stop
powerpc/powernv: Avoid waiting for secondary hold spinloop with OPAL
arch/powerpc/include/asm/opal.h | 2 +-
arch/powerpc/kernel/head_64.S | 16 +++++++++++-----
arch/powerpc/kernel/setup_64.c | 10 +++++++++-
arch/powerpc/kernel/smp.c | 9 +++++----
arch/powerpc/platforms/powernv/opal-flash.c | 28 +---------------------------
arch/powerpc/platforms/powernv/setup.c | 15 +++++----------
6 files changed, 32 insertions(+), 48 deletions(-)
--
2.13.3
next reply other threads:[~2017-10-23 8:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 8:05 Nicholas Piggin [this message]
2017-10-23 8:05 ` [PATCH v2 1/3] powerpc/powernv: Always stop secondaries before reboot/shutdown Nicholas Piggin
2017-11-10 11:08 ` Michael Ellerman
2017-11-11 6:00 ` Nicholas Piggin
2017-11-12 11:57 ` Michael Ellerman
2017-10-23 8:05 ` [PATCH v2 2/3] powerpc: use NMI IPI for smp_send_stop Nicholas Piggin
2017-10-23 21:05 ` kbuild test robot
2017-10-23 23:15 ` kbuild test robot
2017-10-31 7:43 ` Nicholas Piggin
2017-10-23 8:05 ` [PATCH v2 3/3] powerpc/powernv: Avoid waiting for secondary hold spinloop with OPAL Nicholas Piggin
2017-11-14 11:12 ` [v2, " 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=20171023080507.21974-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.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 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.