From: Masami Hiramatsu <mhiramat@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [BUGFIX PATCH V2 0/6] perf/probe: Additional fixes for range only functions
Date: Mon, 28 Oct 2019 23:53:47 +0900 [thread overview]
Message-ID: <20191028235347.8167bb3b56eeb86be3d93606@kernel.org> (raw)
In-Reply-To: <20191028141655.GA4943@kernel.org>
On Mon, 28 Oct 2019 11:16:55 -0300
Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> Em Sat, Oct 26, 2019 at 06:00:19PM +0900, Masami Hiramatsu escreveu:
> > Hi Arnaldo,
> >
> > I've updated examples in patch description in this v2.
> > No changes in the code itself. I ran it on Ubuntu 19.04
> > (linux-5.0.0-32-generic).
> >
> > Please replace previous one with this.
>
> Can you please take a look at my perf/core branch? I have these already
> there:
>
> 5e72f4349eff perf probe: Fix to show ranges of variables in functions without entry_pc
> 50fc0fda5f2c perf probe: Fix to show inlined function callsite without entry_pc
> d7bf48229b85 perf probe: Fix to list probe event with correct line number
> 39cee497850a perf probe: Fix to probe an inline function which has no entry pc
> 6150bad27ebd perf probe: Fix to probe a function which has no entry pc
> fdaea9eea92d perf probe: Fix wrong address verification
>
> And I added committer notes doing the tests.
Yes, I confirmed your comments on the patches. It looks good to me.
Thank you!
>
> - Arnaldo
>
> > Thank you,
> >
> > ---
> >
> > Masami Hiramatsu (6):
> > perf/probe: Fix wrong address verification
> > perf/probe: Fix to probe a function which has no entry pc
> > perf/probe: Fix to probe an inline function which has no entry pc
> > perf/probe: Fix to list probe event with correct line number
> > perf/probe: Fix to show inlined function callsite without entry_pc
> > perf/probe: Fix to show ranges of variables in functions without entry_pc
> >
> >
> > tools/perf/util/dwarf-aux.c | 6 +++---
> > tools/perf/util/probe-finder.c | 40 ++++++++++++++--------------------------
> > 2 files changed, 17 insertions(+), 29 deletions(-)
> >
> > --
> > Masami Hiramatsu (Linaro) <mhiramat@kernel.org>
>
> --
>
> - Arnaldo
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2019-10-28 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-26 9:00 Masami Hiramatsu
2019-10-26 9:00 ` [BUGFIX PATCH V2 1/6] perf/probe: Fix wrong address verification Masami Hiramatsu
2019-10-26 9:00 ` [BUGFIX PATCH V2 2/6] perf/probe: Fix to probe a function which has no entry pc Masami Hiramatsu
2019-10-26 9:00 ` [BUGFIX PATCH V2 3/6] perf/probe: Fix to probe an inline " Masami Hiramatsu
2019-10-26 9:00 ` [BUGFIX PATCH V2 4/6] perf/probe: Fix to list probe event with correct line number Masami Hiramatsu
2019-10-26 9:01 ` [BUGFIX PATCH V2 5/6] perf/probe: Fix to show inlined function callsite without entry_pc Masami Hiramatsu
2019-10-26 9:01 ` [BUGFIX PATCH V2 6/6] perf/probe: Fix to show ranges of variables in functions " Masami Hiramatsu
2019-10-28 14:16 ` [BUGFIX PATCH V2 0/6] perf/probe: Additional fixes for range only functions Arnaldo Carvalho de Melo
2019-10-28 14:53 ` Masami Hiramatsu [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=20191028235347.8167bb3b56eeb86be3d93606@kernel.org \
--to=mhiramat@kernel.org \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome