From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/perf probe: Print a hint if adding a probe fails
Date: Mon, 21 Jun 2021 15:10:33 +0530 [thread overview]
Message-ID: <1624268198.nw42tdsihr.naveen@linux.ibm.com> (raw)
In-Reply-To: <YMycflwgCrosgTcb@kernel.org>
Hi Arnaldo,
Arnaldo Carvalho de Melo wrote:
> Em Thu, Jun 10, 2021 at 07:29:26PM +0900, Masami Hiramatsu escreveu:
>> Hi Naveen,
>>
>> On Thu, 10 Jun 2021 15:14:42 +0530
>> "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> wrote:
>>
>> > Adding a probe can fail in a few scenarios. perf already checks for the
>> > address in the kprobe blacklist. However, the address could still be a
>> > jump label, or have a BUG_ON(). In such cases, it isn't always evident
>> > why adding the probe failed. Add a hint so that the user knows how to
>> > proceed.
>> >
>>
>> Thanks for the report.
>>
>> Since now there is <tracefs>/error_log, if you see any errors in registering
>> probe-events, perf probe should dump the error_log for the hint message.
>> Also, kprobes should return the correct different error code for each
>> errors.
>
> Was there any followup on this? I think we should do as Masami suggests,
> Naveen, could you do it?
Thanks for checking. We have been discussing this on the kernel side of
things here (sorry, missed copying you on that):
http://lkml.kernel.org/r/20210610085617.1590138-1-naveen.n.rao@linux.vnet.ibm.com
I will work on the related changes to perf after the kernel changes.
Thanks,
Naveen
prev parent reply other threads:[~2021-06-21 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 9:44 [PATCH] tools/perf probe: Print a hint if adding a probe fails Naveen N. Rao
2021-06-10 10:29 ` Masami Hiramatsu
2021-06-18 13:15 ` Arnaldo Carvalho de Melo
2021-06-21 9:40 ` Naveen N. Rao [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=1624268198.nw42tdsihr.naveen@linux.ibm.com \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@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.