From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 84011DDEA3 for ; Thu, 18 Oct 2007 11:25:51 +1000 (EST) Subject: [PATCH] synchronize_irq needs a barrier From: Benjamin Herrenschmidt To: Linus Torvalds Content-Type: text/plain Date: Thu, 18 Oct 2007 11:25:42 +1000 Message-Id: <1192670742.12879.5.camel@pasglop> Mime-Version: 1.0 Cc: linuxppc-dev list , akpm , Linux Kernel list Reply-To: benh@kernel.crashing.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , synchronize_irq needs at the very least a compiler barrier and a read barrier on SMP, but there are enough cases around where a write barrier is also needed and it's not a hot path so I prefer using a full smp_mb() here. It will degrade to a compiler barrier on !SMP. Signed-off-by: Benjamin Herrenschmidt --- Index: linux-work/kernel/irq/manage.c =================================================================== --- linux-work.orig/kernel/irq/manage.c 2007-10-18 11:22:16.000000000 +1000 +++ linux-work/kernel/irq/manage.c 2007-10-18 11:22:20.000000000 +1000 @@ -33,6 +33,7 @@ void synchronize_irq(unsigned int irq) if (irq >= NR_IRQS) return; + smp_mb(); while (desc->status & IRQ_INPROGRESS) cpu_relax(); }