public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 0/2] [GIT PULL][v3.3] x86: Fix up CFI for the nested NMI
Date: Mon, 27 Feb 2012 08:39:05 +0100	[thread overview]
Message-ID: <20120227073905.GB3397@elte.hu> (raw)
In-Reply-To: <20120225173548.977089274@goodmis.org>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> 
> Ingo,
> 
> Jan posted a patch that fixes the CFI annotations. I recommend getting
> this into 3.3 as this is new code and it would be nice to have CFI
> correct. It also does a little simplification of it as well.
> 
> The second patch is comment changes only (very low impact on messing
> anything up). I realized that the comments had some references to
> previous approaches that I tried, and I fixed them to reflect what
> the final result was. I also added some more comments to describe
> the code a bit better.
> 
> Thanks,
> 
> -- Steve
> 
> Please pull the latest tip/x86/urgent tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> tip/x86/urgent
> 
> Head SHA1: 79fb4ad63e8266ffac1f69bbb45a6f86570493e7
> 
> 
> Jan Beulich (1):
>       x86-64: Fix CFI annotations for NMI nesting code
> 
> Steven Rostedt (1):
>       x86: Fix the NMI nesting comments
> 
> ----
>  arch/x86/kernel/entry_64.S |   64 ++++++++++++++++++++++++--------------------
>  1 files changed, 35 insertions(+), 29 deletions(-)

I don't think we want a 30+ lines diffstat to this rather 
non-trivial NMI codepath - and it changes real instructions, not 
just the CFI annotations.

Also, the 'update comments' commit does not belong into 
x86/urgent either.

So either you do an obviously trivial patch that only adds CFI 
annotations and nothing else, or I can pull these bits into 
tip:x86/debug, for a v3.4 merge.

Thanks,

	Ingo

  parent reply	other threads:[~2012-02-27  7:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25 17:35 [PATCH 0/2] [GIT PULL][v3.3] x86: Fix up CFI for the nested NMI Steven Rostedt
2012-02-25 17:35 ` [PATCH 1/2] x86-64: Fix CFI annotations for NMI nesting code Steven Rostedt
2012-02-25 17:35 ` [PATCH 2/2] x86: Fix the NMI nesting comments Steven Rostedt
2012-02-27  7:39 ` Ingo Molnar [this message]
2012-02-27 13:23   ` [PATCH 0/2] [GIT PULL][v3.3] x86: Fix up CFI for the nested NMI Steven Rostedt
2012-02-28  9:06     ` Ingo Molnar
2012-02-28  9:16       ` Jan Beulich
2012-02-28  9:39         ` 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=20120227073905.GB3397@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --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