From: Harvey Harrison <harvey.harrison@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Masami Hiramatsu <mhiramat@redhat.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Jim Keniston <jkenisto@us.ibm.com>,
Roland McGrath <roland@redhat.com>,
Arjan van de Ven <arjan@infradead.org>,
prasanna@in.ibm.com, anil.s.keshavamurthy@intel.com,
davem@davemloft.net, systemtap-ml <systemtap@sources.redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [-mm][PATCH 0/6] (yet another) kprobes x86 code unification and boosters
Date: Mon, 17 Dec 2007 11:17:22 -0800 [thread overview]
Message-ID: <1197919042.23402.1.camel@brick> (raw)
In-Reply-To: <20071217163342.GA10495@elte.hu>
On Mon, 2007-12-17 at 17:33 +0100, Ingo Molnar wrote:
> * Masami Hiramatsu <mhiramat@redhat.com> wrote:
>
> > Hello all,
> >
> > I developed a series of patches which unifies kprobes code on x86 and
> > introduces boosters on x86-64. These patches can be applied to
> > 2.6.24-rc4-mm1.
> >
> > The purpose of this patchset is unifying kprobes_[32|64].[c|h] to
> > kprobes.[c|h] for simplifying code maintenance.
> >
> > I know these patches are conflicting with Harvey's patch. We need to
> > solve that.
>
> your series fixes the 64-bit crash that i was seeing, so i've picked it
> up. Please work it out with Harvey which cleanups of him are not
> included yet.
>
I thought the jprobe_saved_sp looked fishy on X86_64 in my unified set
but I went bug-for-bug compatible I guess :-) If you look at my cleaned
up set this was one of the main source of remaining ifdefs.
Harvey
next prev parent reply other threads:[~2007-12-17 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 16:06 [-mm][PATCH 0/6] (yet another) kprobes x86 code unification and boosters Masami Hiramatsu
2007-12-17 16:33 ` Ingo Molnar
2007-12-17 19:17 ` Harvey Harrison [this message]
2007-12-17 19:24 ` Masami Hiramatsu
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=1197919042.23402.1.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=arjan@infradead.org \
--cc=davem@davemloft.net \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=prasanna@in.ibm.com \
--cc=roland@redhat.com \
--cc=systemtap@sources.redhat.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 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.