From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>, Jason Baron <jbaron@redhat.com>
Subject: [PATCH 0/7] [GIT PULL] jump-labels: Implement 2 and 5 byte jumps
Date: Thu, 08 Mar 2012 17:17:30 -0500 [thread overview]
Message-ID: <20120308221730.807074710@goodmis.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1757 bytes --]
Ingo,
A while ago I posted this series and you discovered a bug. I fixed that
bug, but due to traveling and other responsibilities I'm not sure
I posted the fix.
The fix is the last patch in this series.
As things have changed since the last post, there were a lot of conflicts,
and I had to rebase the patch set against tip/perf/jump-labels and
fix up the patches. Mostly the changes from JUMP_LABEL_* to STATIC_KEY_*.
But I got this done and retested them.
-- Steve
Please pull the latest tip/perf/jump-label-5 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
tip/perf/jump-label-5
Head SHA1: b0fdf8910bf8e30fd3542b05062ca9a9721cf26f
Steven Rostedt (7):
x86/jump-label: Use best default nops for inital jump label calls
x86/jump-label: Do not bother updating nops if they are correct
x86/jump-label: Add safety checks to jump label conversions
jump labels: Add infrastructure to update jump labels at compile time
x86/jump labels: Use etiher 5 byte or 2 byte jumps
x86/jump lables: Show where and what was wrong on errors
x86/jump labels: Handle initialization of enabled nops
----
Makefile | 7 +
arch/Kconfig | 6 +
arch/x86/Kconfig | 1 +
arch/x86/include/asm/jump_label.h | 14 ++-
arch/x86/kernel/jump_label.c | 121 ++++++++++++-
scripts/Makefile | 1 +
scripts/Makefile.build | 15 ++-
scripts/update_jump_label.c | 341 +++++++++++++++++++++++++++++++++++++
scripts/update_jump_label.h | 208 ++++++++++++++++++++++
9 files changed, 700 insertions(+), 14 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-03-08 22:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 22:17 Steven Rostedt [this message]
2012-03-08 22:17 ` [PATCH 1/7] x86/jump-label: Use best default nops for inital jump label calls Steven Rostedt
2012-03-08 22:17 ` [PATCH 2/7] x86/jump-label: Do not bother updating nops if they are correct Steven Rostedt
2012-03-08 22:17 ` [PATCH 3/7] x86/jump-label: Add safety checks to jump label conversions Steven Rostedt
2012-03-08 22:17 ` [PATCH 4/7] jump labels: Add infrastructure to update jump labels at compile time Steven Rostedt
2012-03-08 22:17 ` [PATCH 5/7] x86/jump labels: Use etiher 5 byte or 2 byte jumps Steven Rostedt
2012-03-12 16:17 ` Jason Baron
2012-03-12 16:29 ` Steven Rostedt
2012-03-12 17:27 ` Steven Rostedt
2012-03-12 18:03 ` Jason Baron
2012-03-08 22:17 ` [PATCH 6/7] x86/jump lables: Show where and what was wrong on errors Steven Rostedt
2012-03-08 22:17 ` [PATCH 7/7] x86/jump labels: Handle initialization of enabled nops Steven Rostedt
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=20120308221730.807074710@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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