[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260106101701.7dd20845@gandalf.local.home>
Date: Tue, 6 Jan 2026 10:17:01 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: Aaron Tomlin <atomlin@...mlin.com>, mhiramat@...nel.org,
mark.rutland@....com, mathieu.desnoyers@...icios.com, corbet@....net,
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
On Mon, 5 Jan 2026 22:10:39 -0800
Randy Dunlap <rdunlap@...radead.org> wrote:
> 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?
No, patch 1/2 has:
@@ -684,6 +684,14 @@ of ftrace. Here is a list of some of the key files:
See events.rst for more information.
+ show_event_filters:
+
+ A list of events that have filters. This shows the
+ system/event pair along with the filter that is attached to
+ the event.
+
+ See events.rst for more information.
+
available_events:
It is simply a s/filter/trigger/g difference though.
-- Steve
Powered by blists - more mailing lists