mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: "平松雅巳 / HIRAMATU,MASAMI" <masami.hiramatsu.pt@hitachi.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
	Wang Nan <wangnan0@huawei.com>,
	"pi3orama@163.com" <pi3orama@163.com>,
	sysp-manager <cti.systems-productivity-manager.ts@hitachi.com>
Subject: Re: [PATCH 5/5] perf probe: Print deleted events in cmd_probe()
Date: Fri, 4 Sep 2015 20:53:32 +0900	[thread overview]
Message-ID: <20150904115332.GB11132@danjae.kornet> (raw)
In-Reply-To: <50399556C9727B4D88A595C8584AAB375250D256@GSjpTKYDCembx32.service.hitachi.net>

On Fri, Sep 04, 2015 at 11:46:45AM +0000, 平松雅巳 / HIRAMATU,MASAMI wrote:
> > From: Namhyung Kim [mailto:namhyung@kernel.org]
> > 
> > Showing actual trace event when deleteing perf events is only needed in
> > perf probe command.  But the add functionality itself can be used by
> > other places.  So move the printing code into the cmd_probe().
> > 
> > The output is not changed.
> > 
> 
> OK, I just have a comment below.
> 
> > diff --git a/tools/perf/util/probe-event.h b/tools/perf/util/probe-event.h
> > index 610f743671e1..d491cf69f91b 100644
> > --- a/tools/perf/util/probe-event.h
> > +++ b/tools/perf/util/probe-event.h
> > @@ -144,6 +144,11 @@ extern int convert_perf_probe_events(struct perf_probe_event *pevs, int npevs);
> >  extern int apply_perf_probe_events(struct perf_probe_event *pevs, int npevs);
> >  extern void cleanup_perf_probe_events(struct perf_probe_event *pevs, int npevs);
> >  extern int del_perf_probe_events(struct strfilter *filter);
> > +
> > +extern int probe_file__get_events(int fd, struct strfilter *filter,
> > +				  struct strlist *plist);
> > +extern int probe_file__del_strlist(int fd, struct strlist *namelist);
> 
> These should be moved into probe-file.h.

Right, will change!

Thanks,
Namhyung


> 
> > +
> >  extern int show_perf_probe_event(const char *group, const char *event,
> >  				 struct perf_probe_event *pev,
> >  				 const char *module, bool use_stdout);
> 
> Thanks!
> 

      reply	other threads:[~2015-09-04 11:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04  7:39 [PATCH 1/5] perf probe: Split add_perf_probe_events() Namhyung Kim
2015-09-04  7:39 ` [PATCH 2/5] perf probe: Attach trace_probe_event with perf_probe_event Namhyung Kim
2015-09-04 11:36   ` 平松雅巳 / HIRAMATU,MASAMI
2015-09-04 11:52     ` Namhyung Kim
2015-09-04  7:39 ` [PATCH 3/5] perf probe: Move print logic into cmd_probe() Namhyung Kim
2015-09-04 11:48   ` 平松雅巳 / HIRAMATU,MASAMI
2015-09-04  7:39 ` [PATCH 4/5] perf probe: Split del_perf_probe_events() Namhyung Kim
2015-09-04 11:52   ` 平松雅巳 / HIRAMATU,MASAMI
2015-09-04 12:14     ` Namhyung Kim
2015-09-04  7:39 ` [PATCH 5/5] perf probe: Print deleted events in cmd_probe() Namhyung Kim
2015-09-04 11:46   ` 平松雅巳 / HIRAMATU,MASAMI
2015-09-04 11:53     ` Namhyung Kim [this message]

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=20150904115332.GB11132@danjae.kornet \
    --to=namhyung@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=cti.systems-productivity-manager.ts@hitachi.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@kernel.org \
    --cc=pi3orama@163.com \
    --cc=wangnan0@huawei.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

all inboxes | Powered by JetHome®