All of lore.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Luca Barbieri <luca@luca-barbieri.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
	luca@luca-barbieri.com, tglx@linutronix.de
Subject: [tip:x86/atomic] x86-32: Allow UP/SMP lock replacement in cmpxchg64
Date: Fri, 26 Feb 2010 05:12:52 GMT	[thread overview]
Message-ID: <tip-9c76b38476b18c45f97098a10b0176b321eba3ea@git.kernel.org> (raw)
In-Reply-To: <1267005265-27958-3-git-send-email-luca@luca-barbieri.com>

Commit-ID:  9c76b38476b18c45f97098a10b0176b321eba3ea
Gitweb:     http://git.kernel.org/tip/9c76b38476b18c45f97098a10b0176b321eba3ea
Author:     Luca Barbieri <luca@luca-barbieri.com>
AuthorDate: Wed, 24 Feb 2010 10:54:23 +0100
Committer:  H. Peter Anvin <hpa@zytor.com>
CommitDate: Thu, 25 Feb 2010 20:47:03 -0800

x86-32: Allow UP/SMP lock replacement in cmpxchg64

Use the functionality just introduced in the previous patch: mark the
lock prefixes in cmpxchg64 alternatives for UP removal.

Changes in v2:
- Naming change

Signed-off-by: Luca Barbieri <luca@luca-barbieri.com>
LKML-Reference: <1267005265-27958-3-git-send-email-luca@luca-barbieri.com>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
---
 arch/x86/include/asm/cmpxchg_32.h |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/arch/x86/include/asm/cmpxchg_32.h b/arch/x86/include/asm/cmpxchg_32.h
index ffb9bb6..8859e12 100644
--- a/arch/x86/include/asm/cmpxchg_32.h
+++ b/arch/x86/include/asm/cmpxchg_32.h
@@ -271,7 +271,8 @@ extern unsigned long long cmpxchg_486_u64(volatile void *, u64, u64);
 	__typeof__(*(ptr)) __ret;				\
 	__typeof__(*(ptr)) __old = (o);				\
 	__typeof__(*(ptr)) __new = (n);				\
-	alternative_io("call cmpxchg8b_emu",			\
+	alternative_io(LOCK_PREFIX_HERE				\
+			"call cmpxchg8b_emu",			\
 			"lock; cmpxchg8b (%%esi)" ,		\
 		       X86_FEATURE_CX8,				\
 		       "=A" (__ret),				\

  reply	other threads:[~2010-02-26  5:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24  9:54 [PATCH 0/4] x86-32: improve atomic64_t functions (v3, for tip/x86/asm) Luca Barbieri
2010-02-24  9:54 ` [PATCH 1/4] x86: add support for lock prefix in alternatives (v2) Luca Barbieri
2010-02-26  5:12   ` [tip:x86/atomic] x86: Add support for lock prefix in alternatives tip-bot for Luca Barbieri
2010-04-29 23:24   ` [tip:x86/atomic] x86: Fix LOCK_PREFIX_HERE for uniprocessor build tip-bot for H. Peter Anvin
2010-02-24  9:54 ` [PATCH 2/4] x86-32: allow UP/SMP lock replacement in cmpxchg64 (v2) Luca Barbieri
2010-02-26  5:12   ` tip-bot for Luca Barbieri [this message]
2010-02-24  9:54 ` [PATCH 3/4] lib: add self-test for atomic64_t Luca Barbieri
2010-02-26  5:13   ` [tip:x86/atomic] lib: Add " tip-bot for Luca Barbieri
2010-03-01 19:59   ` [tip:x86/atomic] x86, atomic64: In selftest, distinguish x86-64 from 586+ tip-bot for H. Peter Anvin
2010-02-24  9:54 ` [PATCH 4/4] x86-32: rewrite 32-bit atomic64 functions in assembly (v3) Luca Barbieri
2010-02-26  5:13   ` [tip:x86/atomic] x86-32: Rewrite 32-bit atomic64 functions in assembly tip-bot for Luca Barbieri

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=tip-9c76b38476b18c45f97098a10b0176b321eba3ea@git.kernel.org \
    --to=luca@luca-barbieri.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.