From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Chase Douglas <chase.douglas@canonical.com>,
Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Mike Galbraith <efault@gmx.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
2nddept-manager@sdl.hitachi.co.jp
Subject: Re: [PATCH -tip 0/4] perf-probe updates: string support, etc.
Date: Tue, 6 Jul 2010 10:34:47 +0530 [thread overview]
Message-ID: <20100706050447.GG20680@linux.vnet.ibm.com> (raw)
In-Reply-To: <4C327D2F.4040807@hitachi.com>
> >>> Masami Hiramatsu (4):
> >>> perf probe: Support static and global variables
> >>> perf probe: Support tracing an entry of array
> >>> perf probe: Support "string" type
> >>> tracing/kprobes: Support "string" type
> >> What's the status of these patches? They seem very useful to me, but I
> >> don't see them in Arnaldo's tree at git.kernel.org.
> >
> > Thanks for reminding me about these ones, will look at them to get them
> > in perf/core.
>
> Thanks for picking it up. And I need to tell it to Sriker because this
> will affect his uprobes patchset (ftrace part).
> (Actually, my original plan was to update the patchset onto
> his uprobes patchset.)
>
> Sriker, the 1st patch in this series will add many macros/functions
> into trace_kprobe.c. This will directly affect your 8th patch of uprobes,
> which splits fetch functions out from trace_kprobe.c.
> Is that OK for you?
Okay, I will keep rebasing to the latest tip/master before sending out
patches for review. So I will continue to do the same when pushing the
v8 patches.
--
Thanks and Regards
Srikar
next prev parent reply other threads:[~2010-07-06 5:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 19:57 [PATCH -tip 0/4] perf-probe updates: string support, etc Masami Hiramatsu
2010-05-19 19:57 ` [PATCH -tip 1/4] tracing/kprobes: Support "string" type Masami Hiramatsu
2010-07-06 8:37 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-05-19 19:57 ` [PATCH -tip 2/4] perf probe: " Masami Hiramatsu
2010-07-06 8:37 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-05-19 19:57 ` [PATCH -tip 3/4] perf probe: Support tracing an entry of array Masami Hiramatsu
2010-07-06 8:37 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-05-19 19:57 ` [PATCH -tip 4/4] perf probe: Support static and global variables Masami Hiramatsu
2010-07-06 8:38 ` [tip:perf/core] " tip-bot for Masami Hiramatsu
2010-07-05 14:30 ` [PATCH -tip 0/4] perf-probe updates: string support, etc Chase Douglas
2010-07-05 17:44 ` Arnaldo Carvalho de Melo
2010-07-06 0:47 ` Masami Hiramatsu
2010-07-06 5:04 ` Srikar Dronamraju [this message]
2010-07-06 0:54 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2010-05-18 2:49 Masami Hiramatsu
2010-05-18 2:49 ` 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=20100706050447.GG20680@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=2nddept-manager@sdl.hitachi.co.jp \
--cc=acme@redhat.com \
--cc=chase.douglas@canonical.com \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.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.