From: tip-bot for David Miller <davem@davemloft.net>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
rostedt@goodmis.org, tglx@linutronix.de, davem@davemloft.net
Subject: [tip:perf/urgent] jump_label: Fix unaligned traps on sparc.
Date: Sat, 30 Oct 2010 10:41:24 GMT [thread overview]
Message-ID: <tip-f0daed0242d514033b9ecca9187108d3c4e281a5@git.kernel.org> (raw)
In-Reply-To: <20101023.110624.226758370.davem@davemloft.net>
Commit-ID: f0daed0242d514033b9ecca9187108d3c4e281a5
Gitweb: http://git.kernel.org/tip/f0daed0242d514033b9ecca9187108d3c4e281a5
Author: David Miller <davem@davemloft.net>
AuthorDate: Sat, 23 Oct 2010 11:06:24 -0700
Committer: Steven Rostedt <rostedt@goodmis.org>
CommitDate: Fri, 29 Oct 2010 12:57:06 -0400
jump_label: Fix unaligned traps on sparc.
The vmlinux.lds.h knobs to emit the __jump_table section in the main
kernel image takes care to align the section, but this doesn't help
for the __jump_table section that gets emitted into modules.
Fix the resulting lack of section alignment by explicitly specifying
it in the assembler.
Signed-off-by: David S. Miller <davem@davemloft.net>
LKML-Reference: <20101023.110624.226758370.davem@davemloft.net>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
arch/sparc/include/asm/jump_label.h | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/sparc/include/asm/jump_label.h b/arch/sparc/include/asm/jump_label.h
index 62e66d7..d95cf44 100644
--- a/arch/sparc/include/asm/jump_label.h
+++ b/arch/sparc/include/asm/jump_label.h
@@ -14,6 +14,7 @@
"nop\n\t" \
"nop\n\t" \
".pushsection __jump_table, \"a\"\n\t"\
+ ".align 4\n\t" \
".word 1b, %l[" #label "], %c0\n\t" \
".popsection \n\t" \
: : "i" (key) : : label);\
prev parent reply other threads:[~2010-10-30 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-23 18:06 [PATCH] " David Miller
2010-10-27 21:20 ` Steven Rostedt
2010-10-30 10:41 ` tip-bot for David Miller [this message]
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-f0daed0242d514033b9ecca9187108d3c4e281a5@git.kernel.org \
--to=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--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
all inboxes | Powered by JetHome®