From: Masami Hiramatsu <mhiramat@redhat.com>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Maneesh Soni <maneesh@linux.vnet.ibm.com>,
srinivasa@in.ibm.com, Jim Keniston <jkenisto@us.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:14:12 -0500 [thread overview]
Message-ID: <476702C4.8070205@redhat.com> (raw)
In-Reply-To: <1197928823.23402.108.camel@brick>
Hi Harvey,
Harvey Harrison wrote:
> On Mon, 2007-12-17 at 16:52 -0500, Masami Hiramatsu wrote:
>> Hi Harvey,
>> Before porting, could you tell me what differences are important
>> to you? We can discuss about it.
>>
>>> I just sent out a series of 4 patches equivalent to your patches 1-4/6
>>> but based on my already unified kprobes.c/h, You may want to check your
>>> handling of restored registers in trampoline_probe_handler which I found
>>> when rebasing yours on top of my cleanups. Not sure if this is
>>> important, but it was a difference I found.
>>>
>>> X86_32:
>>> regs->cs = __KERNEL_CS | get_kernel_rpl();
>>>
>>> yours:
>>> regs->cs = __KERNEL_CS;
>> Because of kretprobe's compatibility, on x86-32 cs should be set rpl().
>> But get_kernel_rpl() does not exist on x86-64.
>>
>
> I've already ported it and sent it to you. It's not really important to
> me I just think my fine-grained patches may be of some use to see where
> the differences between X86_32/64 ended up being. Your patches end up
> being just about entirely removal of ifdefs when rebased onto my
> patches, so it's at least a good secondary check of your patches even
> if mine don't go in. Your patches end up being much smaller against
> my version too.
OK, I'll review that.
>
> I like my version slightly better because the remaining ifdefs (wrmsr,
> etc) and others could be done in a few more small patches that are more
> easily reviewable than your large final unification patch.
I agreed that your patches are including some goodness.
So let us merge it into one.
>
> But, you know the code better than I....
>
> Harvey
>
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com, masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2007-12-17 23:20 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 [this message]
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
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=476702C4.8070205@redhat.com \
--to=mhiramat@redhat.com \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=harvey.harrison@gmail.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=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