[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250203053208.l4o2o5g3imdzl6vj@lcpd911>
Date: Mon, 3 Feb 2025 11:02:08 +0530
From: Dhruva Gole <d-gole@...com>
To: Keita Morisaki <keyz@...gle.com>
CC: <rostedt@...dmis.org>, <mhiramat@...nel.org>,
<mathieu.desnoyers@...icios.com>, <linux-kernel@...r.kernel.org>,
<linux-trace-kernel@...r.kernel.org>, <lpieralisi@...nel.org>,
<sudeep.holla@....com>, <rafael@...nel.org>,
<daniel.lezcano@...aro.org>, <linux-pm@...r.kernel.org>,
<aarontian@...gle.com>, <yimingtseng@...gle.com>,
Kevin Hilman <khilman@...libre.com>
Subject: Re: [PATCH v4] cpuidle: psci: Add trace for PSCI domain idle
Hi Keita,
On Feb 02, 2025 at 18:46:08 +0800, Keita Morisaki wrote:
> The trace event cpu_idle provides insufficient information for debugging
> PSCI requests due to lacking access to determined PSCI domain idle
> states. The cpu_idle usually only shows -1, 0, or 1 regardless how many
> idle states the power domain has.
>
> Add new trace events namely psci_domain_idle_enter and
> psci_domain_idle_exit to trace enter and exit events with a determined
> idle state.
Thanks for this, will really ease those psci idle debugs for everyone!
>
> These new trace events will help developers debug CPUidle issues on ARM
> systems using PSCI by providing more detailed information about the
> requested idle states.
>
> Signed-off-by: Keita Morisaki <keyz@...gle.com>
> Reviewed-by: Steven Rostedt (Google) <rostedt@...dmis.org>
> Tested-by: Kevin Hilman <khilman@...libre.com>
Reviewed-by: Dhruva Gole <d-gole@...com>
--
Best regards,
Dhruva Gole
Texas Instruments Incorporated
Powered by blists - more mailing lists