From: Daniel Walker <dwalker@mvista.com>
To: linux-kernel@vger.kernel.org
Cc: mm-commits@vger.kernel.org, kiran@scalex86.org, ak@suse.de,
md@google.com, mingo@elte.hu, pravin.shelar@calsoftinc.com,
shai@scalex86.org
Subject: Re: + spin_lock_irq-enable-interrupts-while-spinning-i386-implementation.patch added to -mm tree
Date: Sat, 06 Jan 2007 14:35:53 -0800 [thread overview]
Message-ID: <1168122953.26086.230.camel@imap.mvista.com> (raw)
In-Reply-To: <200701032112.l03LCnVb031386@shell0.pdx.osdl.net>
On Wed, 2007-01-03 at 13:12 -0800, akpm@osdl.org wrote:
> -# define __raw_spin_lock_irq(lock) __raw_spin_lock(lock)
> +
> +static inline void __raw_spin_lock_irq(raw_spinlock_t *lock)
> +{
> + asm volatile("\n1:\t"
> + LOCK_PREFIX " ; decb %0\n\t"
> + "jns 3f\n"
> + STI_STRING "\n"
> + "2:\t"
> + "rep;nop\n\t"
> + "cmpb $0,%0\n\t"
> + "jle 2b\n\t"
> + CLI_STRING "\n"
> + "jmp 1b\n"
> + "3:\n\t"
> + : "+m" (lock->slock) : : "memory");
> +}
> #endif
>
This doesn't compile when CONFIG_PARAVIRT is enabled. It changes the
CLI_STRING and STI_STRING values.
Daniel
next parent reply other threads:[~2007-01-06 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200701032112.l03LCnVb031386@shell0.pdx.osdl.net>
2007-01-06 22:35 ` Daniel Walker [this message]
2007-01-07 7:26 ` + spin_lock_irq-enable-interrupts-while-spinning-i386-implementation.patch added to -mm tree Andrew Morton
2007-01-07 13:24 ` Daniel Walker
2007-01-07 14:39 ` Zachary Amsden
2007-01-07 15:17 ` Zachary Amsden
2007-01-07 20:05 ` Andrew Morton
2007-01-07 21:06 ` Ravikiran G Thirumalai
2007-01-07 21:27 ` Ravikiran G Thirumalai
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=1168122953.26086.230.camel@imap.mvista.com \
--to=dwalker@mvista.com \
--cc=ak@suse.de \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=md@google.com \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=pravin.shelar@calsoftinc.com \
--cc=shai@scalex86.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).