[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <97e2c641-9dfe-bf7c-9043-c79fa0c568f9@linux.vnet.ibm.com>
Date: Tue, 10 Apr 2018 10:15:05 +0530
From: Ravi Bangoria <ravi.bangoria@...ux.vnet.ibm.com>
To: Song Liu <songliubraving@...com>
Cc: peterz@...radead.org, rostedt@...dmis.org, mingo@...hat.com,
davem@...emloft.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, daniel@...earbox.net,
kernel-team@...com, Oleg Nesterov <oleg@...hat.com>,
"Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>
Subject: Re: [PATCH v5 0/6] enable creating [k,u]probe with perf_event_open
Hi Song,
On 12/07/2017 04:15 AM, Song Liu wrote:
> With current kernel, user space tools can only create/destroy [k,u]probes
> with a text-based API (kprobe_events and uprobe_events in tracefs). This
> approach relies on user space to clean up the [k,u]probe after using them.
> However, this is not easy for user space to clean up properly.
>
> To solve this problem, we introduce a file descriptor based API.
> Specifically, we extended perf_event_open to create [k,u]probe, and attach
> this [k,u]probe to the file descriptor created by perf_event_open. These
> [k,u]probe are associated with this file descriptor, so they are not
> available in tracefs.
Sorry for being late. One simple question..
Will it be good to support k/uprobe arguments with perf_event_open()?
Do you have any plans about that?
Thanks,
Ravi
Powered by blists - more mailing lists