From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [v2, 3/3] powerpc/powernv: Avoid waiting for secondary hold spinloop with OPAL
Date: Tue, 14 Nov 2017 22:12:08 +1100 (AEDT) [thread overview]
Message-ID: <3yblG02h0Vz9sRg@ozlabs.org> (raw)
In-Reply-To: <20171023080507.21974-4-npiggin@gmail.com>
On Mon, 2017-10-23 at 08:05:07 UTC, Nicholas Piggin wrote:
> OPAL boot does not insert secondaries at 0x60 to wait at the secondary
> hold spinloop. Instead they are started later, and inserted at
> generic_secondary_smp_init(), which is after the secondary hold
> spinloop.
>
> Avoid waiting on this spinloop when booting with OPAL firmware. This
> wait always times out that case.
>
> This saves 100ms boot time on powernv, and 10s of seconds of real time
> when booting on the simulator in SMP.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/339a3293f4e493a6c40f71e4faab0c
cheers
prev parent reply other threads:[~2017-11-14 11:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 8:05 [PATCH v2 0/3] avoid secondary hold spinloop when possible Nicholas Piggin
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 ` Michael Ellerman [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=3yblG02h0Vz9sRg@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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).