From: tip-bot for Jason Baron <jbaron@redhat.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
mathieu.desnoyers@efficios.com, a.p.zijlstra@chello.nl,
rostedt@goodmis.org, tglx@linutronix.de, jbaron@redhat.com
Subject: [tip:perf/core] jump label: Add _ASM_ALIGN for x86 and x86_64
Date: Wed, 27 Apr 2011 15:23:35 GMT [thread overview]
Message-ID: <tip-ef64789413c73f32faa5e5f1bc393e5843b0aa51@git.kernel.org> (raw)
In-Reply-To: <e119fbd060c9452c56063ea6148ba1070e7434cc.1300299760.git.jbaron@redhat.com>
Commit-ID: ef64789413c73f32faa5e5f1bc393e5843b0aa51
Gitweb: http://git.kernel.org/tip/ef64789413c73f32faa5e5f1bc393e5843b0aa51
Author: Jason Baron <jbaron@redhat.com>
AuthorDate: Wed, 16 Mar 2011 15:58:27 -0400
Committer: Steven Rostedt <rostedt@goodmis.org>
CommitDate: Mon, 4 Apr 2011 13:42:51 -0400
jump label: Add _ASM_ALIGN for x86 and x86_64
The linker should not be adding holes to word size aligned pointers, but
out of paranoia we are explicitly specifying that alignment. I have not
seen any holes in the jump label section in practice.
Signed-off-by: Jason Baron <jbaron@redhat.com>
LKML-Reference: <e119fbd060c9452c56063ea6148ba1070e7434cc.1300299760.git.jbaron@redhat.com>
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Acked-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
arch/x86/include/asm/jump_label.h | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/x86/include/asm/jump_label.h b/arch/x86/include/asm/jump_label.h
index f217cee..a32b18c 100644
--- a/arch/x86/include/asm/jump_label.h
+++ b/arch/x86/include/asm/jump_label.h
@@ -16,6 +16,7 @@ static __always_inline bool arch_static_branch(struct jump_label_key *key)
asm goto("1:"
JUMP_LABEL_INITIAL_NOP
".pushsection __jump_table, \"aw\" \n\t"
+ _ASM_ALIGN "\n\t"
_ASM_PTR "1b, %l[l_yes], %c0 \n\t"
".popsection \n\t"
: : "i" (key) : : l_yes);
next prev parent reply other threads:[~2011-04-27 15:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 19:58 [PATCH v2 0/4] jump label: update for .39 v2 Jason Baron
2011-03-16 19:58 ` [PATCH 1/4] jump label: introduce static_branch() interface Jason Baron
2011-03-16 20:06 ` Need ack from sparc maintainer (was: [PATCH 1/4] jump label: introduce static_branch() interface) Steven Rostedt
2011-03-16 20:13 ` Need ack from sparc maintainer David Miller
2011-03-16 20:22 ` Steven Rostedt
2011-03-16 21:29 ` [PATCH 1/4] jump label: introduce static_branch() interface Jason Baron
2011-04-27 15:23 ` [tip:perf/core] jump label: Introduce " tip-bot for Jason Baron
2011-03-16 19:58 ` [PATCH 2/4] dynamic debug: add jump label support Jason Baron
2011-03-16 19:58 ` [PATCH 3/4] jump label: add _ASM_ALIGN for x86 and x86_64 Jason Baron
2011-04-27 15:23 ` tip-bot for Jason Baron [this message]
2011-03-16 19:58 ` [PATCH 4/4] jump label: add s390 support Jason Baron
2011-04-27 15:24 ` [tip:perf/core] jump label: Add " tip-bot for Jan Glauber
2011-03-16 20:36 ` [PATCH v2 0/4] jump label: update for .39 v2 Steven Rostedt
2011-03-16 21:31 ` Jason Baron
2011-03-16 22:08 ` Mathieu Desnoyers
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-ef64789413c73f32faa5e5f1bc393e5843b0aa51@git.kernel.org \
--to=jbaron@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--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
Powered by JetHome