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 0/3] perf/probe: Fix available line bugs
Date: Fri, 25 Oct 2019 08:22:49 +0900 [thread overview]
Message-ID: <20191025082249.2ef5cdbe89f6c5176d785c06@kernel.org> (raw)
In-Reply-To: <20191024202327.GA19678@kernel.org>
On Thu, 24 Oct 2019 17:23:27 -0300
Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> But why can't I probe this thing again?
>
> [root@quaco ~]# perf probe clear_tasks_mm_cpumask:0
> Probe point 'clear_tasks_mm_cpumask' not found.
> Error: Failed to add events.
> [root@quaco ~]# perf probe clear_tasks_mm_cpumask:1
> Failed to get entry address of clear_tasks_mm_cpumask
> Error: Failed to add events.
> [root@quaco ~]# perf probe clear_tasks_mm_cpumask:2
> Failed to get entry address of clear_tasks_mm_cpumask
> Error: Failed to add events.
> [root@quaco ~]# perf probe clear_tasks_mm_cpumask:11
> Failed to get entry address of clear_tasks_mm_cpumask
> Error: Failed to add events.
> [root@quaco ~]# perf probe clear_tasks_mm_cpumask:12
> Failed to get entry address of clear_tasks_mm_cpumask
> Error: Failed to add events.
> [root@quaco ~]# perf probe clear_tasks_mm_cpumask:13
> Failed to get entry address of clear_tasks_mm_cpumask
> Error: Failed to add events.
> root@quaco ~]#
Oops, it's a verification error in convert_to_trace_point().
I'll fix it too!
Thank you,
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2019-10-24 23:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 9:12 [BUGFIX PATCH 0/3] perf/probe: Fix available line bugs Masami Hiramatsu
2019-10-24 9:12 ` [BUGFIX PATCH 1/3] perf/probe: Fix to find range-only function instance Masami Hiramatsu
2019-11-12 11:18 ` [tip: perf/core] perf probe: " tip-bot2 for Masami Hiramatsu
2019-10-24 9:12 ` [BUGFIX PATCH 2/3] perf/probe: Walk function lines in lexical blocks Masami Hiramatsu
2019-11-12 11:18 ` [tip: perf/core] perf probe: " tip-bot2 for Masami Hiramatsu
2019-10-24 9:12 ` [BUGFIX PATCH 3/3] perf/probe: Fix to show function entry line as probe-able Masami Hiramatsu
2019-11-12 11:18 ` [tip: perf/core] perf probe: " tip-bot2 for Masami Hiramatsu
2019-10-24 13:43 ` [BUGFIX PATCH 0/3] perf/probe: Fix available line bugs Arnaldo Carvalho de Melo
2019-10-24 15:36 ` Masami Hiramatsu
2019-10-24 20:23 ` Arnaldo Carvalho de Melo
2019-10-24 23:22 ` 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=20191025082249.2ef5cdbe89f6c5176d785c06@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;
as well as URLs for NNTP newsgroup(s).