public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH v2] x86: UV uv_flush_tlb_others WARN_ON
@ 2009-03-06 23:30 Cliff Wickman
  2009-03-07  5:53 ` Tejun Heo
  0 siblings, 1 reply; 4+ messages in thread
From: Cliff Wickman @ 2009-03-06 23:30 UTC (permalink / raw)
  To: linux-kernel; +Cc: mingo, tj



From: Cliff Wickman <cpw@sgi.com>

The problem WARN_ON remains in Ingo's tree, and linux-next.
It should be dropped.

uv_flush_tlb_others() (arch/x86/kernel/tlb_uv.c)
The "WARN_ON(!in_atomic())" fails if CONFIG_PREEMPT is not enabled.
And CONFIG_PREEMPT is not enabled by default in the distribution that
most UV owners will use.

We could #ifdef CONFIG_PREEMPT the warning, but that is not good form.
And there seems to be no suitable fix to in_atomic() when CONFIG_PREMPT
is not on.
  As you commented, Ingo:
  > and we have no proper primitive to test for atomicity. (mainly
  > because we dont know about atomicity on a non-preempt kernel)

I propose that we drop the WARN_ON.

Diffed against 2.6.29-rc2

Signed-off-by: Cliff Wickman <cpw@sgi.com>
---
 arch/x86/kernel/tlb_uv.c |    2 --
 1 file changed, 2 deletions(-)

Index: linux/arch/x86/kernel/tlb_uv.c
===================================================================
--- linux.orig/arch/x86/kernel/tlb_uv.c
+++ linux/arch/x86/kernel/tlb_uv.c
@@ -316,8 +316,6 @@ const struct cpumask *uv_flush_tlb_other
 	int locals = 0;
 	struct bau_desc *bau_desc;
 
-	WARN_ON(!in_atomic());
-
 	cpumask_andnot(flush_mask, cpumask, cpumask_of(cpu));
 
 	uv_cpu = uv_blade_processor_id();

^ permalink raw reply	[flat|nested] 4+ messages in thread
* [PATCH v2] x86: UV uv_flush_tlb_others WARN_ON
@ 2009-02-02 23:06 Cliff Wickman
  2009-02-05  5:57 ` Tejun Heo
  0 siblings, 1 reply; 4+ messages in thread
From: Cliff Wickman @ 2009-02-02 23:06 UTC (permalink / raw)
  To: linux-kernel; +Cc: mingo, tj



From: Cliff Wickman <cpw@sgi.com>

uv_flush_tlb_others() (arch/x86/kernel/tlb_uv.c)
The "WARN_ON(!in_atomic())" fails if CONFIG_PREEMPT is not enabled.
And CONFIG_PREEMPT is not enabled by default in the distribution that
most UV owners will use.

We could #ifdef CONFIG_PREEMPT the warning, but that is not good form.

And there seems to be no suitable fix to in_atomic() when CONFIG_PREMPT
is not on.
  As you commented, Ingo:
  > and we have no proper primitive to test for atomicity. (mainly
  > because we dont know about atomicity on a non-preempt kernel)

I propose that we drop the WARN_ON.

Diffed against 2.6.29-rc2

Signed-off-by: Cliff Wickman <cpw@sgi.com>
---
 arch/x86/kernel/tlb_uv.c |    2 --
 1 file changed, 2 deletions(-)

Index: linux/arch/x86/kernel/tlb_uv.c
===================================================================
--- linux.orig/arch/x86/kernel/tlb_uv.c
+++ linux/arch/x86/kernel/tlb_uv.c
@@ -316,8 +316,6 @@ const struct cpumask *uv_flush_tlb_other
 	int locals = 0;
 	struct bau_desc *bau_desc;
 
-	WARN_ON(!in_atomic());
-
 	cpumask_andnot(flush_mask, cpumask, cpumask_of(cpu));
 
 	uv_cpu = uv_blade_processor_id();

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2009-03-07  5:53 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-03-06 23:30 [PATCH v2] x86: UV uv_flush_tlb_others WARN_ON Cliff Wickman
2009-03-07  5:53 ` Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2009-02-02 23:06 Cliff Wickman
2009-02-05  5:57 ` Tejun Heo

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox