All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: Philip Radford <Philip.Radford@arm.com>
Cc: "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 <Sudeep.Holla@arm.com>,
	Cristian Marussi <Cristian.Marussi@arm.com>,
	Luke Parkin <Luke.Parkin@arm.com>
Subject: Re: [PATCH 0/4] firmware: arm_scmi: Add xfer inflight debug and trace
Date: Tue, 24 Jun 2025 12:22:32 +0800	[thread overview]
Message-ID: <20250624042232.GD10415@nxa18884-linux> (raw)
In-Reply-To: <PAWPR08MB9966E79130C52CA8460AC4B7897CA@PAWPR08MB9966.eurprd08.prod.outlook.com>

On Fri, Jun 20, 2025 at 09:27:52AM +0000, Philip Radford wrote:
>
>
>> -----Original Message-----
>> From: Peng Fan <peng.fan@oss.nxp.com>
>> Sent: Friday, June 20, 2025 9:47 AM
>> To: Philip Radford <Philip.Radford@arm.com>
>
>Hi,
>Thanks for the review.
>
>> Cc: linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org; arm-
>> scmi@vger.kernel.org; Sudeep Holla <Sudeep.Holla@arm.com>; Cristian
>> Marussi <Cristian.Marussi@arm.com>; Luke Parkin <Luke.Parkin@arm.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

  reply	other threads:[~2025-06-24  3:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 12:20 [PATCH 0/4] firmware: arm_scmi: Add xfer inflight debug and trace Philip Radford
2025-06-19 12:20 ` [PATCH 1/4] firmware: arm_scmi: Add debug decrement counter Philip Radford
2025-06-19 14:32   ` Dan Carpenter
2025-06-26 11:10   ` Cristian Marussi
2025-06-19 12:20 ` [PATCH 2/4] firmware: arm_scmi: Add xfer_inflight counter Philip Radford
2025-06-26 11:15   ` Cristian Marussi
2025-06-19 12:20 ` [PATCH 3/4] include: trace: Add inflight_xfer counter tracepoint Philip Radford
2025-06-19 12:20 ` [PATCH 4/4] firmware: arm_scmi: Add new inflight tracing functionality Philip Radford
2025-06-19 14:37   ` Dan Carpenter
2025-06-26 11:17   ` Cristian Marussi
2025-06-20  8:46 ` [PATCH 0/4] firmware: arm_scmi: Add xfer inflight debug and trace Peng Fan
2025-06-20  9:27   ` Philip Radford
2025-06-24  4:22     ` Peng Fan [this message]
2025-06-26 11:37     ` Cristian Marussi
2025-06-30  2:00       ` Peng Fan
2025-06-26 11:18 ` 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=20250624042232.GD10415@nxa18884-linux \
    --to=peng.fan@oss.nxp.com \
    --cc=Cristian.Marussi@arm.com \
    --cc=Luke.Parkin@arm.com \
    --cc=Philip.Radford@arm.com \
    --cc=Sudeep.Holla@arm.com \
    --cc=arm-scmi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.