All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
	linux-kernel@vger.kernel.org,
	Fengguang Wu <fengguang.wu@intel.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	x86@kernel.org
Subject: Re: Re: [PATCH -tip/x86/jumplabel] x86: call out into int3 handler directly instead of using notifier
Date: Tue, 23 Jul 2013 10:24:27 +0900	[thread overview]
Message-ID: <51EDDB4B.6030609@hitachi.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1307222256120.14024@pobox.suse.cz>

(2013/07/23 6:00), Jiri Kosina wrote:
> On Mon, 22 Jul 2013, H. Peter Anvin wrote:
> 
>>  What is the baseline for this patch?
> 
> Hi!
> 
> it's x86/jumplabel branch, as a followup to commit 
> fd4363fff3d96 ("x86: Introduce int3 (breakpoint)-based instruction 
> patching") sitting there.

AFAICS, tip/master already merged Jiri's works on tip/x86/jumplabel.
Thus both branches need this. (especially, since this is actual
bugfix, it should go into tip/master.)


> This branch however seems to be broken by Ingo's mismerge; this e-mail 
> from earlier today:
> 
> 	https://lkml.org/lkml/2013/7/22/147
> 
> implied that he fixed this ("all is fine"), however x86/jumplabel still 
> contains just 3/3 of Masami's series, and therefore is broken; 3/3 is not 
> enough, it needs also
> 
> 	kprobes/x86: Remove an incorrect comment about int3 in NMI/MCE
> 	kprobes/x86: Use text_poke_bp() instead of text_poke_smp*()
> 
> included or
> 
> 	kprobes/x86: Remove unused text_poke_smp() and text_poke_smp_batch() functions
> 
> dropped to be in consistent state again.

I hope to pull entire of this series in :)

> 
> I pinged Ingo about this:
> 
> 	https://lkml.org/lkml/2013/7/22/281
> 
> but the branch still seems to be in an odd state, containing last patch of 
> Masami's series.
> 
> Thanks in advance for fixing this and applying mi fix as well,	
> 

Thanks!

-- 
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com



  reply	other threads:[~2013-07-23  1:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-20 13:12 [x86] Kernel panic - not syncing: Fatal exception in interrupt Fengguang Wu
2013-07-21  0:23 ` H. Peter Anvin
2013-07-21  8:30   ` Jiri Kosina
2013-07-21 16:21     ` Fengguang Wu
2013-07-21 17:21     ` H. Peter Anvin
2013-07-22 11:18       ` Jiri Kosina
2013-07-22  1:07     ` Fengguang Wu
2013-07-22 11:14 ` [PATCH -tip/x86/jumplabel] x86: call out into int3 handler directly instead of using notifier Jiri Kosina
2013-07-22 11:24   ` Masami Hiramatsu
2013-07-22 20:53   ` H. Peter Anvin
2013-07-22 21:00     ` Jiri Kosina
2013-07-23  1:24       ` Masami Hiramatsu [this message]
2013-07-23  7:45         ` Ingo Molnar
2013-07-23  8:09           ` Jiri Kosina
2013-07-24  3:55             ` [tip:perf/core] kprobes/x86: Call out into INT3 " tip-bot for Jiri Kosina
2013-07-24 14:33               ` H. Peter Anvin
2013-07-29  9:06                 ` Jiri Kosina
2013-07-29  9:14                   ` H. Peter Anvin
2013-07-29  9:18                     ` Jiri Kosina
2013-07-29  9:23                       ` H. Peter Anvin

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=51EDDB4B.6030609@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=fengguang.wu@intel.com \
    --cc=hpa@linux.intel.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.