public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "tip-bot for H. Peter Anvin" <hpa@zytor.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: Fix LOCK_PREFIX_HERE for uniprocessor build
Date: Thu, 29 Apr 2010 23:24:43 GMT	[thread overview]
Message-ID: <tip-b701a47ba48b698976fb2fe05fb285b0edc1d26a@git.kernel.org> (raw)
In-Reply-To: <1267005265-27958-2-git-send-email-luca@luca-barbieri.com>

Commit-ID:  b701a47ba48b698976fb2fe05fb285b0edc1d26a
Gitweb:     http://git.kernel.org/tip/b701a47ba48b698976fb2fe05fb285b0edc1d26a
Author:     H. Peter Anvin <hpa@zytor.com>
AuthorDate: Thu, 29 Apr 2010 16:03:57 -0700
Committer:  H. Peter Anvin <hpa@zytor.com>
CommitDate: Thu, 29 Apr 2010 16:08:54 -0700

x86: Fix LOCK_PREFIX_HERE for uniprocessor build

Checkin b3ac891b67bd4b1fc728d1c784cad1212dea433d:
x86: Add support for lock prefix in alternatives

... did not define LOCK_PREFIX_HERE in the case of a uniprocessor
build.  As a result, it would cause any of the usages of this macro to
fail on a uniprocessor build.  Fix this by defining LOCK_PREFIX_HERE
as a null string.

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

diff --git a/arch/x86/include/asm/alternative.h b/arch/x86/include/asm/alternative.h
index 55fee12..e29a6c9 100644
--- a/arch/x86/include/asm/alternative.h
+++ b/arch/x86/include/asm/alternative.h
@@ -38,6 +38,7 @@
 #define LOCK_PREFIX LOCK_PREFIX_HERE "\n\tlock; "
 
 #else /* ! CONFIG_SMP */
+#define LOCK_PREFIX_HERE ""
 #define LOCK_PREFIX ""
 #endif
 

  parent reply	other threads:[~2010-04-30 17:06 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-bot for H. Peter Anvin [this message]
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:x86/atomic] x86-32: Allow UP/SMP lock replacement in cmpxchg64 tip-bot for Luca Barbieri
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-b701a47ba48b698976fb2fe05fb285b0edc1d26a@git.kernel.org \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=luca@luca-barbieri.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox