From: Nick Piggin <npiggin@suse.de>
To: Jan Beulich <jbeulich@novell.com>
Cc: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: fix ticket spin lock asm constraints
Date: Sat, 30 Aug 2008 07:28:01 +0200 [thread overview]
Message-ID: <20080830052801.GA16897@wotan.suse.de> (raw)
In-Reply-To: <48B7FFB3.76E4.0078.0@novell.com>
Hi,
All these ticket lock patches look pretty good to me. Thanks for going over
it so thoroughly.
On Fri, Aug 29, 2008 at 12:54:59PM +0100, Jan Beulich wrote:
> In addition to these changes I doubt the 'volatile' on all the ticket
> lock asm()-s are really necessary.
>
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
> Cc: Nick Piggin <npiggin@suse.de>
>
> ---
> include/asm-x86/spinlock.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> --- linux-2.6.27-rc5/include/asm-x86/spinlock.h 2008-08-21 14:37:34.000000000 +0200
> +++ 2.6.27-rc5-x86-spinlock-constraints/include/asm-x86/spinlock.h 2008-08-19 12:43:22.000000000 +0200
> @@ -101,7 +101,7 @@ static __always_inline int __ticket_spin
> "1:"
> "sete %b1\n\t"
> "movzbl %b1,%0\n\t"
> - : "=&a" (tmp), "=Q" (new), "+m" (lock->slock)
> + : "=&a" (tmp), "=&Q" (new), "+m" (lock->slock)
> :
> : "memory", "cc");
>
> @@ -146,7 +146,7 @@ static __always_inline void __ticket_spi
> /* don't need lfence here, because loads are in-order */
> "jmp 1b\n"
> "2:"
> - : "+Q" (inc), "+m" (lock->slock), "=r" (tmp)
> + : "+r" (inc), "+m" (lock->slock), "=&r" (tmp)
> :
> : "memory", "cc");
> }
> @@ -166,7 +166,7 @@ static __always_inline int __ticket_spin
> "1:"
> "sete %b1\n\t"
> "movzbl %b1,%0\n\t"
> - : "=&a" (tmp), "=r" (new), "+m" (lock->slock)
> + : "=&a" (tmp), "=&q" (new), "+m" (lock->slock)
> :
> : "memory", "cc");
>
>
>
next prev parent reply other threads:[~2008-08-30 5:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 11:54 [PATCH] x86: fix ticket spin lock asm constraints Jan Beulich
2008-08-30 5:28 ` Nick Piggin [this message]
2008-09-06 17:49 ` Ingo Molnar
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=20080830052801.GA16897@wotan.suse.de \
--to=npiggin@suse.de \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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