From: Ingo Molnar <mingo@elte.hu>
To: Masami Hiramatsu <mhiramat@redhat.com>
Cc: Harvey Harrison <harvey.harrison@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Prasanna S Panchamukhi <prasanna@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 15:30:50 +0100 [thread overview]
Message-ID: <20071217143050.GA13290@elte.hu> (raw)
In-Reply-To: <4766841B.1040500@redhat.com>
Masami,
* Masami Hiramatsu <mhiramat@redhat.com> wrote:
> Hi Harvey and Ingo,
>
> I'm working on another version of patches for unification.
> Currently cleaning up the patches.
> http://sources.redhat.com/ml/systemtap/2007-q4/msg00457.html
> I'll cleanup and repost it today.
cool! Please Cc: lkml and Harvey as well so that there's less overlap in
unification work - Harvey spent quite some time unifying and cleaning up
the kprobes code during the past week.
So i think we could/should use Harvey's latest series as a base, those
are pretty finegrained already. Note that they break 64-bit kprobes
though, with such a config:
CONFIG_KPROBES=y
CONFIG_NET_TCPPROBE=y
so it crashes with an int3 in the TCP code. It's probably some trivial
typo somewhere, as 32-bit works fine.
the coordinates for x86.git#mm can be found below - that tree already
includes Harvey's latest kprobes series. I'll try to bisect the 64-bit
breakage now.
Ingo
------------------>
git-clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-2.6.git
cd linux-2.6.git
git-branch x86
git-checkout x86
git-pull git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86.git mm
(do subsequent pulls via "git-pull --force", as we frequently rebase the
git tree. NOTE: this might override your own local changes, so do this
only if you dont mind about losing thse changes in that tree.)
next prev parent reply other threads:[~2007-12-17 14:31 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 ` Ingo Molnar [this message]
2007-12-17 15:29 ` Final " 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
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=20071217143050.GA13290@elte.hu \
--to=mingo@elte.hu \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=harvey.harrison@gmail.com \
--cc=hiramatu@sdl.hitachi.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mhiramat@redhat.com \
--cc=prasanna@in.ibm.com \
--cc=rusty.lynch@intel.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