public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: Masami Hiramatsu <mhiramat@redhat.com>, Ingo Molnar <mingo@elte.hu>
Cc: Jim Keniston <jkenisto@us.ibm.com>,
	Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Maneesh Soni <maneesh@linux.vnet.ibm.com>,
	srinivasa@in.ibm.com,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	Masami Hiramatsu <hiramatu@sdl.hitachi.co.jp>,
	Rusty Lynch <rusty.lynch@intel.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>
Subject: Re: FInal kprobes rollup patches
Date: Mon, 17 Dec 2007 18:15:36 -0800	[thread overview]
Message-ID: <1197944136.5828.4.camel@brick> (raw)
In-Reply-To: <47671407.7050607@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]

On Mon, 2007-12-17 at 19:27 -0500, Masami Hiramatsu wrote:
> Masami Hiramatsu wrote:
> >> These are:
> >>
> >> -add stack_addr() macro
> >> -I prefer the table defintion macros in mine as it avoids the need
> to
> >> cast the pointer passed to test_bit, but if you want them
> >> to be u32 as in your patch, I can change it.
> > 
> >  please do so. we'd like to reduce ifdefs as less as possible:-)
> > 
> >> -wrmsr/wrmsrl - use wrmsr() for both
> >> -call is_IF_modifier with p->ainsn.insn in both
> >> -check casting of jprobe_saved_sp, I get some compile warnings
> currently
> >> with pointer comparisons to signed/unsigned types.
> > 
> > Could you also add below?
> > - fix some comments (it clarifies the meanings of the code)
> > - add fix_riprel(). this useful to reduce ifdefs.
> > - expand reenter_kprobe(). I think it treat above two blocks.
> > - reassignment of regs->ip in kprobe_handler can be unified
> >   to "regs->ip = (unsigned long)addr;"
> 
> Oh, I forgot to point out important thing.
> - please make bugfix patches first. I think my bugfix patches
>   need to go upstream before unification. It would cause some
>   crashes.
> 

It's pretty hard to move those bugfixes to the head of the queue.

Attached is an mbox of my unification work.  Maybe you could get your
two bugfixes applied to mainline kprobes_32/64.c, then my series
could go in as a merge later on.  Most of my stuff is in kprobes.c
post-unify so the merge would be trivial later.


Ingo, what do you think?  This rollup replaces all of my kprobes
patches to date.  So you could apply patched 1,2/6 from Masami
into 2.6.24 and let mine come in during 2.6.25 as a merge, which
would avoid the conflicts in kprobes_32|64.c?


Harvey

[-- Attachment #2: final_kprobes_rollup.mbox.gz --]
[-- Type: application/x-gzip, Size: 47071 bytes --]

  reply	other threads:[~2007-12-18  2:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-15  8:45 FInal kprobes rollup patches Harvey Harrison
2007-12-15  8:50 ` Ingo Molnar
2007-12-15  9:04   ` Harvey Harrison
2007-12-15 13:12     ` Ingo Molnar
2007-12-17 14:12       ` Srikar Dronamraju
2007-12-17 14:13       ` Masami Hiramatsu
2007-12-17 14:30         ` Final " Ingo Molnar
2007-12-17 15:29           ` Masami Hiramatsu
2007-12-17 16:06             ` Ingo Molnar
2007-12-17 16:19               ` Masami Hiramatsu
2007-12-17 20:17               ` Harvey Harrison
2007-12-17 14:22       ` FInal " Srikar Dronamraju
2007-12-17 19:20         ` Harvey Harrison
2007-12-17 21:28           ` Masami Hiramatsu
2007-12-17 21:36             ` Harvey Harrison
2007-12-17 21:52               ` Masami Hiramatsu
2007-12-17 22:00                 ` Harvey Harrison
2007-12-17 23:14                   ` Masami Hiramatsu
2007-12-17 23:27                     ` Harvey Harrison
2007-12-17 23:56                       ` Masami Hiramatsu
2007-12-18  0:27                         ` Masami Hiramatsu
2007-12-18  2:15                           ` Harvey Harrison [this message]
2007-12-18  3:10                           ` [PATCH] x86: kprobes use stack_addr() macro Harvey Harrison

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=1197944136.5828.4.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=ananth@in.ibm.com \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=hiramatu@sdl.hitachi.co.jp \
    --cc=jkenisto@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maneesh@linux.vnet.ibm.com \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mhiramat@redhat.com \
    --cc=mingo@elte.hu \
    --cc=rusty.lynch@intel.com \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=srinivasa@in.ibm.com \
    /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