From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 0/2] arm64: fix hotplug rwsem boot fallout
Date: Fri, 28 Apr 2017 12:01:04 +0100 [thread overview]
Message-ID: <1493377266-2205-1-git-send-email-mark.rutland@arm.com> (raw)
Hi,
These patches fix a boot issue seen on some arm64 platforms as a result of the
hotplug rwsem rework.
Thomas, would you be able to take these into the tip smp/hotplug branch?
Will has acked the arm64 part, and is happy for this to go via tip [1].
I've tested this atop of the tip smp/hotplug branch, and with the arm64
for-next/core branch merged in, which git handles automatically. In both cases,
it builds cleanly and boots fine on Juno R1.
Thanks,
Mark.
Since v1 [2]:
* Fix update_cpu_capabilities() by splitting boot/secondary
Since v2 [3]:
* Align on _cpuslocked naming
* Avoid duplicating workaround string
* Add Will's Acked-by
[1] https://lkml.kernel.org/r/20170427180104.GO1890 at arm.
[2] https://lkml.kernel.org/r/20170427154806.GA6646 at leverpostej
[3] https://lkml.kernel.org/r/1493315077-19496-3-git-send-email-mark.rutland at arm.com
Mark Rutland (1):
arm64: cpufeature: use static_branch_enable_cpuslocked()
Sebastian Andrzej Siewior (1):
jump_label: Provide static_key_[enable|/slow_inc]_cpuslocked()
arch/arm64/include/asm/cpufeature.h | 3 ++-
arch/arm64/kernel/cpu_errata.c | 9 ++++++++-
arch/arm64/kernel/cpufeature.c | 5 ++++-
include/linux/jump_label.h | 7 +++++++
kernel/jump_label.c | 10 ++++++++++
5 files changed, 31 insertions(+), 3 deletions(-)
--
1.9.1
next reply other threads:[~2017-04-28 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 11:01 Mark Rutland [this message]
2017-04-28 11:01 ` [PATCHv3 1/2] jump_label: Provide static_key_[enable|/slow_inc]_cpuslocked() Mark Rutland
2017-04-28 11:01 ` [PATCHv3 2/2] arm64: cpufeature: use static_branch_enable_cpuslocked() Mark Rutland
2017-05-10 18:10 ` [PATCHv3 0/2] arm64: fix hotplug rwsem boot fallout Mark Rutland
2017-05-10 20:09 ` Thomas Gleixner
2017-05-11 8:30 ` Thomas Gleixner
2017-05-11 9:37 ` Mark Rutland
2017-05-11 10:01 ` Thomas Gleixner
2017-05-11 12:54 ` Mark Rutland
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=1493377266-2205-1-git-send-email-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.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).