From: Cristian Marussi <cristian.marussi@arm.com>
To: Luke Parkin <luke.parkin@arm.com>
Cc: Peng Fan <peng.fan@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"arm-scmi@vger.kernel.org" <arm-scmi@vger.kernel.org>,
"sudeep.holla@arm.com" <sudeep.holla@arm.com>,
"cristian.marussi@arm.com" <cristian.marussi@arm.com>
Subject: Re: [PATCH v3 3/5] firmware: arm_scmi: Track basic SCMI statistics
Date: Wed, 24 Jul 2024 15:24:41 +0100 [thread overview]
Message-ID: <ZqEOqTi9c4LAZI2l@pluto> (raw)
In-Reply-To: <57e6bded-8d10-4db8-ad2e-11dfd126205f@arm.com>
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
next prev parent reply other threads:[~2024-07-24 14:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 13:37 [PATCH v3 0/5] Add Per-transport SCMI debug statistics Luke Parkin
2024-07-15 13:37 ` [PATCH v3 1/5] firmware: arm_scmi: Remove superfluous handle_to_scmi_info Luke Parkin
2024-07-24 13:07 ` Cristian Marussi
2024-07-15 13:37 ` [PATCH v3 2/5] firmware: arm_scmi: Add support for tracking statistics Luke Parkin
2024-07-24 13:40 ` Cristian Marussi
2024-07-15 13:37 ` [PATCH v3 3/5] firmware: arm_scmi: Track basic SCMI statistics Luke Parkin
2024-07-16 12:29 ` Peng Fan
2024-07-22 12:21 ` Luke Parkin
2024-07-24 14:24 ` Cristian Marussi [this message]
2024-07-24 14:21 ` Cristian Marussi
2024-07-24 14:39 ` Luke Parkin
2024-07-15 13:37 ` [PATCH v3 4/5] firmware: arm_scmi: Create debugfs files for statistics Luke Parkin
2024-07-24 14:26 ` Cristian Marussi
2024-07-15 13:37 ` [PATCH v3 5/5] firmware: arm_scmi: Reset statistics Luke Parkin
2024-07-24 14:41 ` Cristian Marussi
2024-07-24 14:46 ` [PATCH v3 0/5] Add Per-transport SCMI debug statistics Cristian Marussi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZqEOqTi9c4LAZI2l@pluto \
--to=cristian.marussi@arm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luke.parkin@arm.com \
--cc=peng.fan@nxp.com \
--cc=sudeep.holla@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).