[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZqEOqTi9c4LAZI2l@pluto>
Date: Wed, 24 Jul 2024 15:24:41 +0100
From: Cristian Marussi <cristian.marussi@....com>
To: Luke Parkin <luke.parkin@....com>
Cc: Peng Fan <peng.fan@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
"arm-scmi@...r.kernel.org" <arm-scmi@...r.kernel.org>,
"sudeep.holla@....com" <sudeep.holla@....com>,
"cristian.marussi@....com" <cristian.marussi@....com>
Subject: Re: [PATCH v3 3/5] firmware: arm_scmi: Track basic SCMI statistics
On Mon, Jul 22, 2024 at 01:21:31PM +0100, Luke Parkin wrote:
> > Just wonder that since ftrace is there, why need this?
>
> Hi, this series aims to provide a useful debug aid for running tests on the SCMI
> subsystem. As you mentioned, ftrace does report some of these statistics,
> however DEBUG_STATISTICS will allow a programatic interface to access the count
> of failures, successes and an extended variety of other specific
> errors/statistics for automated (or manual) testing.
>
> Hope this clears things up,
> Luke
Yes, the idea was to have some continuosuly running counters that can be looked
up (when compiled-in, NOT in production) to check for anomalies...ftrace
are certainly more detailed in these regards BUT you have to enable them
at runtime and then dig into the log, and moreover do not cover all of
the cases like these stats...
Thanks,
Cristian
Powered by blists - more mailing lists