All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Masami Hiramatsu <mhiramat@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 11:16:55 -0300	[thread overview]
Message-ID: <20191028141655.GA4943@kernel.org> (raw)
In-Reply-To: <157208041894.16551.2733647209130045685.stgit@devnote2>

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.

- 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

  parent reply	other threads:[~2019-10-28 14:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-26  9:00 [BUGFIX PATCH V2 0/6] perf/probe: Additional fixes for range only functions 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 ` Arnaldo Carvalho de Melo [this message]
2019-10-28 14:53   ` [BUGFIX PATCH V2 0/6] perf/probe: Additional fixes for range only functions 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=20191028141655.GA4943@kernel.org \
    --to=arnaldo.melo@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@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 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.