[RFC PATCH v3 14/19] smp, sh: kill SMP single function call interrupt

2013-12-04 Thread Jiang Liu
Commit 9a46ad6d6df3b54 "smp: make smp_call_function_many() use logic
similar to smp_call_function_single()" has unified the way to handle
single and multiple cross-CPU function calls. Now only one intterupt
is needed for architecture specific code to support generic SMP function
call interfaces, so kill the redundant single function call interrupt.

Cc: Andrew Morton 
Cc: Shaohua Li 
Cc: Peter Zijlstra 
Cc: Ingo Molnar 
Cc: Steven Rostedt 
Cc: Jiri Kosina 
Cc: Paul Mundt 
Signed-off-by: Jiang Liu 
---
 arch/sh/include/asm/smp.h | 1 -
 arch/sh/kernel/smp.c  | 5 +
 2 files changed, 1 insertion(+), 5 deletions(-)

diff --git a/arch/sh/include/asm/smp.h b/arch/sh/include/asm/smp.h
index 78b0d0f4..93ce87b 100644
--- a/arch/sh/include/asm/smp.h
+++ b/arch/sh/include/asm/smp.h
@@ -25,7 +25,6 @@ extern int __cpu_logical_map[NR_CPUS];
 enum {
SMP_MSG_FUNCTION,
SMP_MSG_RESCHEDULE,
-   SMP_MSG_FUNCTION_SINGLE,
SMP_MSG_TIMER,
 
SMP_MSG_NR, /* must be last */
diff --git a/arch/sh/kernel/smp.c b/arch/sh/kernel/smp.c
index 86a7936..c944d5d 100644
--- a/arch/sh/kernel/smp.c
+++ b/arch/sh/kernel/smp.c
@@ -282,7 +282,7 @@ void arch_send_call_function_ipi_mask(const struct cpumask 
*mask)
 
 void arch_send_call_function_single_ipi(int cpu)
 {
-   mp_ops->send_ipi(cpu, SMP_MSG_FUNCTION_SINGLE);
+   mp_ops->send_ipi(cpu, SMP_MSG_FUNCTION);
 }
 
 void smp_timer_broadcast(const struct cpumask *mask)
@@ -309,9 +309,6 @@ void smp_message_recv(unsigned int msg)
case SMP_MSG_RESCHEDULE:
scheduler_ipi();
break;
-   case SMP_MSG_FUNCTION_SINGLE:
-   generic_smp_call_function_single_interrupt();
-   break;
case SMP_MSG_TIMER:
ipi_timer();
break;
-- 
1.8.1.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


[RFC PATCH v3 14/19] smp, sh: kill SMP single function call interrupt

2013-12-04 Thread Jiang Liu
Commit 9a46ad6d6df3b54 smp: make smp_call_function_many() use logic
similar to smp_call_function_single() has unified the way to handle
single and multiple cross-CPU function calls. Now only one intterupt
is needed for architecture specific code to support generic SMP function
call interfaces, so kill the redundant single function call interrupt.

Cc: Andrew Morton a...@linux-foundation.org
Cc: Shaohua Li s...@kernel.org
Cc: Peter Zijlstra a.p.zijls...@chello.nl
Cc: Ingo Molnar mi...@elte.hu
Cc: Steven Rostedt rost...@goodmis.org
Cc: Jiri Kosina triv...@kernel.org
Cc: Paul Mundt let...@linux-sh.org
Signed-off-by: Jiang Liu liu...@gmail.com
---
 arch/sh/include/asm/smp.h | 1 -
 arch/sh/kernel/smp.c  | 5 +
 2 files changed, 1 insertion(+), 5 deletions(-)

diff --git a/arch/sh/include/asm/smp.h b/arch/sh/include/asm/smp.h
index 78b0d0f4..93ce87b 100644
--- a/arch/sh/include/asm/smp.h
+++ b/arch/sh/include/asm/smp.h
@@ -25,7 +25,6 @@ extern int __cpu_logical_map[NR_CPUS];
 enum {
SMP_MSG_FUNCTION,
SMP_MSG_RESCHEDULE,
-   SMP_MSG_FUNCTION_SINGLE,
SMP_MSG_TIMER,
 
SMP_MSG_NR, /* must be last */
diff --git a/arch/sh/kernel/smp.c b/arch/sh/kernel/smp.c
index 86a7936..c944d5d 100644
--- a/arch/sh/kernel/smp.c
+++ b/arch/sh/kernel/smp.c
@@ -282,7 +282,7 @@ void arch_send_call_function_ipi_mask(const struct cpumask 
*mask)
 
 void arch_send_call_function_single_ipi(int cpu)
 {
-   mp_ops-send_ipi(cpu, SMP_MSG_FUNCTION_SINGLE);
+   mp_ops-send_ipi(cpu, SMP_MSG_FUNCTION);
 }
 
 void smp_timer_broadcast(const struct cpumask *mask)
@@ -309,9 +309,6 @@ void smp_message_recv(unsigned int msg)
case SMP_MSG_RESCHEDULE:
scheduler_ipi();
break;
-   case SMP_MSG_FUNCTION_SINGLE:
-   generic_smp_call_function_single_interrupt();
-   break;
case SMP_MSG_TIMER:
ipi_timer();
break;
-- 
1.8.1.2

--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/