From: tip-bot for Len Brown <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: tglx@linutronix.de, peterz@infradead.org, hpa@zytor.com,
linux-kernel@vger.kernel.org, mingo@kernel.org,
len.brown@intel.com
Subject: [tip:x86/idle] x86: Remove x86_test_and_clear_bit_percpu()
Date: Fri, 18 Nov 2016 03:20:57 -0800 [thread overview]
Message-ID: <tip-9694be731dc81fec5ad59e863fa6538878ac496a@git.kernel.org> (raw)
In-Reply-To: <b334ae6819507e3dfc0a4b33ed974714d067eb4a.1479449716.git.len.brown@intel.com>
Commit-ID: 9694be731dc81fec5ad59e863fa6538878ac496a
Gitweb: http://git.kernel.org/tip/9694be731dc81fec5ad59e863fa6538878ac496a
Author: Len Brown <len.brown@intel.com>
AuthorDate: Fri, 18 Nov 2016 01:23:20 -0500
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Fri, 18 Nov 2016 12:07:57 +0100
x86: Remove x86_test_and_clear_bit_percpu()
Upon removal of the "is_idle" flag, x86_test_and_clear_bit_percpu() is no
longer used.
Signed-off-by: Len Brown <len.brown@intel.com>
Acked-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: http://lkml.kernel.org/r/b334ae6819507e3dfc0a4b33ed974714d067eb4a.1479449716.git.len.brown@intel.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
arch/x86/include/asm/percpu.h | 11 -----------
1 file changed, 11 deletions(-)
diff --git a/arch/x86/include/asm/percpu.h b/arch/x86/include/asm/percpu.h
index 84f58de..9fa0360 100644
--- a/arch/x86/include/asm/percpu.h
+++ b/arch/x86/include/asm/percpu.h
@@ -507,17 +507,6 @@ do { \
#endif
-/* This is not atomic against other CPUs -- CPU preemption needs to be off */
-#define x86_test_and_clear_bit_percpu(bit, var) \
-({ \
- bool old__; \
- asm volatile("btr %2,"__percpu_arg(1)"\n\t" \
- CC_SET(c) \
- : CC_OUT(c) (old__), "+m" (var) \
- : "dIr" (bit)); \
- old__; \
-})
-
static __always_inline bool x86_this_cpu_constant_test_bit(unsigned int nr,
const unsigned long __percpu *addr)
{
next prev parent reply other threads:[~2016-11-18 11:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 6:23 [PATCH 0/5] x86: remove idle notifier Len Brown
2016-11-18 6:23 ` [PATCH 1/5] i7300_idle: remove this driver Len Brown
2016-11-18 6:23 ` [PATCH 2/5] x86: remove idle_notifier Len Brown
2016-11-18 11:19 ` [tip:x86/idle] x86/idle: Remove idle_notifier tip-bot for Len Brown
2016-12-06 16:54 ` [PATCH 2/5] x86: remove idle_notifier Pavel Machek
2016-12-07 11:46 ` Thomas Gleixner
2016-12-07 13:40 ` Pavel Machek
2016-12-08 9:18 ` Thomas Gleixner
2016-12-08 22:05 ` Pavel Machek
2016-12-08 22:53 ` Thomas Gleixner
2016-11-18 6:23 ` [PATCH 3/5] x86: remove is_idle flag Len Brown
2016-11-18 11:20 ` [tip:x86/idle] x86/idle: Remove " tip-bot for Len Brown
2016-11-18 6:23 ` [PATCH 4/5] x86: remove x86_test_and_clear_bit_percpu() Len Brown
2016-11-18 11:20 ` tip-bot for Len Brown [this message]
2016-11-18 6:23 ` [PATCH 5/5] x86: remove enter_idle(), exit_idle() Len Brown
2016-11-18 11:21 ` [tip:x86/idle] x86/idle: Remove " tip-bot for Len Brown
2016-11-18 11:19 ` [tip:x86/idle] i7300_idle: Remove this driver tip-bot for Len Brown
2016-11-18 8:17 ` [PATCH 0/5] x86: remove idle notifier Ingo Molnar
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-9694be731dc81fec5ad59e863fa6538878ac496a@git.kernel.org \
--to=tipbot@zytor.com \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome