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: Re: [PATCH 0/6] [GIT PULL] x86: Workaround for NMI iret woes
Date: Fri, 16 Dec 2011 18:16:39 -0500 [thread overview]
Message-ID: <1324077399.23971.134.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20111216225906.481643317@goodmis.org>
On Fri, 2011-12-16 at 17:59 -0500, Steven Rostedt wrote:
> I have the ftrace patches pretty much ready, but I would like to get
> these in under the x86 branch.
Bah, I just realized that I based it on the perf branch. Let me rebase
it on one of the tip x86 branches or even plain 3.2-rc5, and retest.
Thanks,
-- Steve
next prev parent reply other threads:[~2011-12-16 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 22:59 Steven Rostedt
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 ` Steven Rostedt [this message]
2011-12-18 8:28 ` [PATCH 0/6] [GIT PULL] x86: Workaround for NMI iret woes 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=1324077399.23971.134.camel@gandalf.stny.rr.com \
--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
all inboxes | Powered by JetHome®