[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230426210750.tonhsstc4xhrzd3c@skbuf>
Date: Thu, 27 Apr 2023 00:07:50 +0300
From: Vladimir Oltean <vladimir.oltean@....com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
Masami Hiramatsu <mhiramat@...nel.org>, netdev@...r.kernel.org,
Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH net-next 0/2] DSA trace events
On Wed, Apr 26, 2023 at 03:47:13PM -0400, Steven Rostedt wrote:
> I also want to add that if a tool does use a trace event that was not your
> intention, you can then fix the tool to do it properly.
>
> I had this with powertop. It had hardcoded events (did not use
> libtraceevent) and when I modified the layout, it broke, and Linus reverted
> my changes. After fixing powertop to do things properly, I was able to get
> my changes back in.
>
> So even if you do break user space, you can still fix it later.
Thanks, this is helpful.
Powered by blists - more mailing lists