[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <oqon532hz5nktpgilvpmvd5ywuasppbkfw2f6z5gjluyzo62ow@n7ynrou6uykm>
Date: Fri, 24 Jan 2025 10:54:04 +0000
From: Aaron Tomlin <atomlin@...mlin.com>
To: Namhyung Kim <namhyung@...nel.org>
Cc: peterz@...radead.org, mingo@...hat.com, acme@...nel.org,
mark.rutland@....com, alexander.shishkin@...ux.intel.com, jolsa@...nel.org,
irogers@...gle.com, adrian.hunter@...el.com, kan.liang@...ux.intel.com,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf probe: Introduce --no-advice option when a new
event is created
On Thu, Jan 23, 2025 at 04:25:10PM -0800, Namhyung Kim wrote:
> Hello,
Hi Namhyung,
> Sorry for the late reply.
No problem at all.
> On Sat, Dec 14, 2024 at 07:34:52PM +0000, Aaron Tomlin wrote:
> > This patch introduces a new option namely "--no-advice" to be used with
> > the add command. Now one has the ability to avoid the generation of any
> > advice when a new event is created. Thus making the output reasonable.
> > For example:
> >
> > # perf probe --no-advice --add 'user_path_at%return return=$retval:s32'
> > Added new event:
> > probe:user_path_at__return (on user_path_at%return with return=$retval:s32)
> > #
>
> Thanks for sending the patch but why do you care? You can just ignore
> the message.
I understand.
As a frequent and avid perf-probe user, I often only need to confirm the
successful creation of a new event, ensuring its presence under
/sys/kernel/debug/tracing/events/probes for subsequent use with Ftrace.
The ability to suppress verbose output would be a valuable enhancement.
Please let me know your thoughts.
Kind regards,
--
Aaron Tomlin
Powered by blists - more mailing lists