[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <95feb439-2298-4539-8833-e05ed06f273b@infradead.org>
Date: Mon, 5 Jan 2026 22:10:39 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Aaron Tomlin <atomlin@...mlin.com>, rostedt@...dmis.org,
mhiramat@...nel.org, mark.rutland@....com, mathieu.desnoyers@...icios.com,
corbet@....net
Cc: neelx@...e.com, sean@...e.io, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [v2 PATCH 2/2] tracing: Add show_event_triggers to expose active
event triggers
Hi,
On 1/5/26 6:29 AM, Aaron Tomlin wrote:
> diff --git a/Documentation/trace/ftrace.rst b/Documentation/trace/ftrace.rst
> index 4ce01e726b09..b9efb148a5c2 100644
> --- a/Documentation/trace/ftrace.rst
> +++ b/Documentation/trace/ftrace.rst
> @@ -692,6 +692,14 @@ of ftrace. Here is a list of some of the key files:
>
> See events.rst for more information.
>
> + show_event_triggers:
> +
> + A list of events that have triggers. This shows the
> + system/event pair along with the trigger that is attached to
> + the event.
> +
> + See events.rst for more information.
> +
Isn't this the same chunk that was in patch 1/2?
> available_events:
>
> A list of events that can be enabled in tracing.
--
~Randy
Powered by blists - more mailing lists