From: tip-bot for Waiman Long <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: mingo@kernel.org, will.deacon@arm.com,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
longman@redhat.com, bp@alien8.de, peterz@infradead.org,
hpa@zytor.com, srinivas.eeda@oracle.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org, paulmck@linux.vnet.ibm.com,
james.morse@arm.com, zhenzhong.duan@oracle.com
Subject: [tip:locking/core] locking/qspinlock: Handle > 4 slowpath nesting levels
Date: Mon, 4 Feb 2019 00:58:14 -0800 [thread overview]
Message-ID: <tip-d682b596d99345ef0000e7017db714ba7f29e017@git.kernel.org> (raw)
In-Reply-To: <1548798828-16156-2-git-send-email-longman@redhat.com>
Commit-ID: d682b596d99345ef0000e7017db714ba7f29e017
Gitweb: https://git.kernel.org/tip/d682b596d99345ef0000e7017db714ba7f29e017
Author: Waiman Long <longman@redhat.com>
AuthorDate: Tue, 29 Jan 2019 22:53:45 +0100
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Mon, 4 Feb 2019 09:03:29 +0100
locking/qspinlock: Handle > 4 slowpath nesting levels
Four queue nodes per CPU are allocated to enable up to 4 nesting levels
using the per-CPU nodes. Nested NMIs are possible in some architectures.
Still it is very unlikely that we will ever hit more than 4 nested
levels with contention in the slowpath.
When that rare condition happens, however, it is likely that the system
will hang or crash shortly after that. It is not good and we need to
handle this exception case.
This is done by spinning directly on the lock using repeated trylock.
This alternative code path should only be used when there is nested
NMIs. Assuming that the locks used by those NMI handlers will not be
heavily contended, a simple TAS locking should work out.
Suggested-by: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: Waiman Long <longman@redhat.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Will Deacon <will.deacon@arm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Borislav Petkov <bp@alien8.de>
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: James Morse <james.morse@arm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: SRINIVAS <srinivas.eeda@oracle.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Zhenzhong Duan <zhenzhong.duan@oracle.com>
Link: https://lkml.kernel.org/r/1548798828-16156-2-git-send-email-longman@redhat.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
kernel/locking/qspinlock.c | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/kernel/locking/qspinlock.c b/kernel/locking/qspinlock.c
index 8a8c3c208c5e..0875053c4050 100644
--- a/kernel/locking/qspinlock.c
+++ b/kernel/locking/qspinlock.c
@@ -412,6 +412,21 @@ pv_queue:
idx = node->count++;
tail = encode_tail(smp_processor_id(), idx);
+ /*
+ * 4 nodes are allocated based on the assumption that there will
+ * not be nested NMIs taking spinlocks. That may not be true in
+ * some architectures even though the chance of needing more than
+ * 4 nodes will still be extremely unlikely. When that happens,
+ * we fall back to spinning on the lock directly without using
+ * any MCS node. This is not the most elegant solution, but is
+ * simple enough.
+ */
+ if (unlikely(idx >= MAX_NODES)) {
+ while (!queued_spin_trylock(lock))
+ cpu_relax();
+ goto release;
+ }
+
node = grab_mcs_node(node, idx);
/*
next prev parent reply other threads:[~2019-02-04 8:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 21:53 [PATCH v3 0/4] locking/qspinlock: Handle > 4 nesting levels Waiman Long
2019-01-29 21:53 ` [PATCH v3 1/4] locking/qspinlock: Handle > 4 slowpath " Waiman Long
2019-02-04 8:58 ` tip-bot for Waiman Long [this message]
2019-01-29 21:53 ` [PATCH v3 2/4] locking/qspinlock_stat: Track the no MCS node available case Waiman Long
2019-02-04 8:58 ` [tip:locking/core] " tip-bot for Waiman Long
2019-01-29 21:53 ` [PATCH v3 3/4] locking/qspinlock_stat: Introduce a generic lockevent counting APIs Waiman Long
2019-01-29 21:53 ` [PATCH v3 4/4] locking/lock_events: Make lock_events available for all archs & other locks Waiman Long
2019-01-30 14:07 ` [PATCH v3 0/4] locking/qspinlock: Handle > 4 nesting levels Peter Zijlstra
2019-01-30 16:25 ` Waiman Long
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=tip-d682b596d99345ef0000e7017db714ba7f29e017@git.kernel.org \
--to=tipbot@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=srinivas.eeda@oracle.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
--cc=zhenzhong.duan@oracle.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