From: Daniel Hellstrom <daniel@gaisler•com>
To: davem@davemloft•net
Cc: sparclinux@vger•kernel.org, sfr@canb•auug.org.au,
peterz@infradead•org, tglx@linutronix•de, mingo@elte•hu,
hpa@zytor•com, linux-next@vger•kernel.org,
linux-kernel@vger•kernel.org
Subject: [PATCH 2/2] SCHED_TTWU_QUEUE is not longer needed since sparc32 now implements IPI
Date: Fri, 20 May 2011 16:01:10 +0200 [thread overview]
Message-ID: <1305900070-23492-2-git-send-email-daniel@gaisler.com> (raw)
In-Reply-To: <1305900070-23492-1-git-send-email-daniel@gaisler.com>
Signed-off-by: Daniel Hellstrom <daniel@gaisler•com>
Reported-by: Peter Zijlstra <peterz@infradead•org>
Acked-by: Peter Zijlstra <peterz@infradead•org>
---
init/Kconfig | 5 -----
kernel/sched.c | 2 +-
2 files changed, 1 insertions(+), 6 deletions(-)
diff --git a/init/Kconfig b/init/Kconfig
index df64627..a66b656 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -827,11 +827,6 @@ config SCHED_AUTOGROUP
desktop applications. Task group autogeneration is currently based
upon task session.
-config SCHED_TTWU_QUEUE
- bool
- depends on !SPARC32
- default y
-
config MM_OWNER
bool
diff --git a/kernel/sched.c b/kernel/sched.c
index c62acf4..0516af4 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -2564,7 +2564,7 @@ static void ttwu_queue(struct task_struct *p, int cpu)
{
struct rq *rq = cpu_rq(cpu);
-#if defined(CONFIG_SMP) && defined(CONFIG_SCHED_TTWU_QUEUE)
+#if defined(CONFIG_SMP)
if (sched_feat(TTWU_QUEUE) && cpu != smp_processor_id()) {
ttwu_queue_remote(p, cpu);
return;
--
1.6.0.3
next prev parent reply other threads:[~2011-05-20 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 14:01 [PATCH 1/2] Fix merge problem between sparc32 IPI patches and schedule_ipi() callback Daniel Hellstrom
2011-05-20 14:01 ` Daniel Hellstrom [this message]
2011-05-20 20:13 ` David Miller
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=1305900070-23492-2-git-send-email-daniel@gaisler.com \
--to=daniel@gaisler$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=peterz@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sparclinux@vger$(echo .)kernel.org \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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