linux-kernel - Re: [PATCH 0/4] firmware: arm_scmi: Add xfer inflight debug and trace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250624042232.GD10415@nxa18884-linux>
Date: Tue, 24 Jun 2025 12:22:32 +0800
From: Peng Fan <peng.fan@....nxp.com>
To: Philip Radford <Philip.Radford@....com>
Cc: "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 <Sudeep.Holla@....com>,
	Cristian Marussi <Cristian.Marussi@....com>,
	Luke Parkin <Luke.Parkin@....com>
Subject: Re: [PATCH 0/4] firmware: arm_scmi: Add xfer inflight debug and trace

On Fri, Jun 20, 2025 at 09:27:52AM +0000, Philip Radford wrote:
>
>
>> -----Original Message-----
>> From: Peng Fan <peng.fan@....nxp.com>
>> Sent: Friday, June 20, 2025 9:47 AM
>> To: Philip Radford <Philip.Radford@....com>
>
>Hi,
>Thanks for the review.
>
>> Cc: linux-kernel@...r.kernel.org; linux-arm-kernel@...ts.infradead.org; arm-
>> scmi@...r.kernel.org; Sudeep Holla <Sudeep.Holla@....com>; Cristian
>> Marussi <Cristian.Marussi@....com>; Luke Parkin <Luke.Parkin@....com>
>> Subject: Re: [PATCH 0/4] firmware: arm_scmi: Add xfer inflight debug and
>> trace
>> 
>> On Thu, Jun 19, 2025 at 12:20:00PM +0000, Philip Radford wrote:
>> >Hi all,
>> >
>> >This series adds a new counter to the Arm SCMI firmware driver to track
>> >the number of in-flight message transfers during debug and trace. This
>> >will be useful for examining behaviour under a large load with regards
>> >to concurrent messages being sent and received. As the counter only gives
>> >a live value, printing the value in trace allows logging of the in-flight
>> >xfers.
>> 
>> Just a general question, is this counter count in flight messages
>> for a scmi instance or it is per transport? I ask because
>> one scmi instance could have multiple mailboxes. If counting based
>> on scmi instance, it may not be that accurate.
>> 
>> Thanks,
>> Peng
>> 
>
>Yes, you are correct that the counter is per instance, as are the other counters.
>This would mean that if you have multiple channels you would see the total
>number of inflight xfers across all channels, limited to that instance.
>If the inflight counter is non-zero and something is wrong, it would not be
>apparent which channel had an issue, however this is the same for the other
>counters.
>
>I feel like this series is a helpful addition to the current counters, but what you
>have pointed out is something that could be reworked in a future series?

Sure. It is ok from my view, you could extend the driver in future.

Regards,
Peng

>
>Regards,
>Phil