From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andi Kleen <andi@firstfloor.org>
Subject: [PATCH 0/6] [GIT PULL] x86: Workaround for NMI iret woes
Date: Fri, 16 Dec 2011 17:59:06 -0500 [thread overview]
Message-ID: <20111216225906.481643317@goodmis.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]
Ingo,
As there hasn't been much discussion about these patches, and I know
that Thomas would really like to get rid of the stop-machine requirement
for ftrace, jump_labels and kprobes, this is the required patch set
for such.
Nothing changed since the RFCs except I added the debug stack counter
to address the issue that Mathieu Desnoyers brought up.
I have the ftrace patches pretty much ready, but I would like to get
these in under the x86 branch. I hope to get this patch series into
3.3, and then I'll push the x86 ftrace patches on top of these for
3.4, along with jump_labels and kprobes.
I'll have ftrace patches that get all the infrastructure needed
for removing stop_machine() out for 3.3 too. This way I can let
powerpc use it and be our guinea pig ;)
Thanks!
-- Steve
Please pull the latest tip/x86/core tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
tip/x86/core
Head SHA1: babcd54c41922214ff5dae3a6d832638d105f1d0
Linus Torvalds (1):
x86: Do not schedule while still in NMI context
Steven Rostedt (5):
x86: Document the NMI handler about not using paranoid_exit
x86: Add workaround to NMI iret woes
x86: Keep current stack in NMI breakpoints
x86: Allow NMIs to hit breakpoints in i386
x86: Add counter when debug stack is used with interrupts enabled
----
arch/x86/include/asm/desc.h | 12 ++
arch/x86/include/asm/processor.h | 10 ++
arch/x86/kernel/cpu/common.c | 34 ++++++
arch/x86/kernel/entry_64.S | 208 ++++++++++++++++++++++++++++++++------
arch/x86/kernel/head_64.S | 4 +
arch/x86/kernel/nmi.c | 101 ++++++++++++++++++
arch/x86/kernel/traps.c | 20 ++++
7 files changed, 356 insertions(+), 33 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2011-12-16 23:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 22:59 Steven Rostedt [this message]
2011-12-16 22:59 ` [PATCH 1/6] x86: Do not schedule while still in NMI context Steven Rostedt
2011-12-16 22:59 ` [PATCH 2/6] x86: Document the NMI handler about not using paranoid_exit Steven Rostedt
2011-12-16 22:59 ` [PATCH 3/6] x86: Add workaround to NMI iret woes Steven Rostedt
2011-12-16 22:59 ` [PATCH 4/6] x86: Keep current stack in NMI breakpoints Steven Rostedt
2011-12-16 22:59 ` [PATCH 5/6] x86: Allow NMIs to hit breakpoints in i386 Steven Rostedt
2011-12-16 22:59 ` [PATCH 6/6] x86: Add counter when debug stack is used with interrupts enabled Steven Rostedt
2011-12-16 23:16 ` [PATCH 0/6] [GIT PULL] x86: Workaround for NMI iret woes Steven Rostedt
2011-12-18 8:28 ` Ingo Molnar
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=20111216225906.481643317@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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