Date: Mon, 6 Mar 2006 13:25:54 -0500
From: Chuck Ebbert <76306.1226@compuserve.com>
Subject: spin_lock_irqsave only re-enables interrupts while spinning
  on some archs?
To: linux-kernel <linux-kernel@vger.kernel.org>
Message-ID: <200603061327_MC3-1-B9F7-26DD@compuserve.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	 charset=us-ascii
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 876
Lines: 19

On some architectures, spin_lock_irqsave() re-enables interrupts when
spinning while waiting for the lock to become available.  The list
of archs includes i386, powerpc and ia64.  Others leave interrupts
disabled while spinning (x86_64, arm, alpha).  They just define
__raw_spin_lock_flags to be the same as __raw_spin_lock.  (And
because predication is so efficient, ia64 does the opposite:
it uses __raw_spin_lock_flags for everything -- a neat trick.)

Shouldn't there be a standard way of doing this?  Is there any practical
difference in behavior?

-- 
Chuck
"Penguins don't come from next door, they come from the Antarctic!"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/