From: Masami Hiramatsu <mhiramat@kernel.org>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] kprobes: Print an error if probe is rejected
Date: Tue, 15 Jun 2021 14:42:23 +0900 [thread overview]
Message-ID: <20210615144223.c4720bfdaff21ecb4d1e9101@kernel.org> (raw)
In-Reply-To: <1623684669.fagfzw6pyl.naveen@linux.ibm.com>
Hi Naveen,
On Mon, 14 Jun 2021 21:07:40 +0530
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> wrote:
> >
> >> We also have perf_event_open() as an interface to add probes, and I
> >> don't think it would be helpful to require all tools to utilize the
> >> error log from tracefs for this purpose.
> >
> > No, perf probe doesn't use perf-event interface to add probes. It uses
> > the tracefs for adding probes.
>
> Yes, but I was referring to some of the bpf tools (bcc) that now use
> perf_event_open() interface.
Yes, bpf chooses to use a special temporary perf_event, something like a
performance counter event. Those are hidden from tracefs and perf-tool.
The perf probe is the frontend of the trace event and perf event, which
will add dynamic events in tracefs, and perf will use it as same as
the other static events.
Thank you,
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2021-06-15 5:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 8:56 [PATCH] kprobes: Print an error if probe is rejected Naveen N. Rao
2021-06-10 10:16 ` Masami Hiramatsu
2021-06-10 17:33 ` Steven Rostedt
2021-06-11 1:50 ` Masami Hiramatsu
2021-06-11 13:55 ` Naveen N. Rao
2021-06-11 19:40 ` Steven Rostedt
2021-06-14 15:30 ` Naveen N. Rao
2021-06-18 16:15 ` Masami Hiramatsu
2021-06-21 9:36 ` Naveen N. Rao
2021-06-21 12:54 ` Masami Hiramatsu
2021-06-12 1:13 ` Masami Hiramatsu
2021-06-14 15:37 ` Naveen N. Rao
2021-06-15 5:42 ` 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=20210615144223.c4720bfdaff21ecb4d1e9101@kernel.org \
--to=mhiramat@kernel.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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