2023-01-25 11:35:03

by Krzysztof Kozlowski

[permalink] [raw]
Subject: [PATCH v4] cpuidle: psci: Do not suspend topology CPUs on PREEMPT_RT

The runtime Power Management of CPU topology is not compatible with
PREEMPT_RT:
1. Core cpuidle path disables IRQs.
2. Core cpuidle calls cpuidle-psci.
3. cpuidle-psci in __psci_enter_domain_idle_state() calls
pm_runtime_put_sync_suspend() and pm_runtime_get_sync() which use
spinlocks (which are sleeping on PREEMPT_RT).

Deep sleep modes are not a priority of Realtime kernels because the
latencies might become unpredictable. On the other hand the PSCI CPU
idle power domain is a parent of other devices and power domain
controllers, thus it cannot be simply skipped (e.g. on Qualcomm SM8250).

Disable the idle callbacks in cpuidle-psci and mark the domain as
always on. This is a trade-off between making PREEMPT_RT working and
still having a proper power domain hierarchy in the system.

Cc: Adrien Thierry <[email protected]>
Cc: Brian Masney <[email protected]>
Cc: [email protected]
Signed-off-by: Krzysztof Kozlowski <[email protected]>

---

Changes since v3:
1. Rework - disable idle states, mark as always on (Ulf).
2. Extend Kconfig warning (Ulf).

Changes since v1:
1. Re-work commit msg.
2. Add note to Kconfig.

Several other patches were dropped, as this is the only one actually
needed. It effectively stops PSCI cpuidle power domains from suspending
thus solving all other issues I experienced.
---
drivers/cpuidle/Kconfig.arm | 8 ++++++++
drivers/cpuidle/cpuidle-psci-domain.c | 7 +++++--
drivers/cpuidle/cpuidle-psci.c | 3 +++
3 files changed, 16 insertions(+), 2 deletions(-)

diff --git a/drivers/cpuidle/Kconfig.arm b/drivers/cpuidle/Kconfig.arm
index 747aa537389b..8deaa2e05206 100644
--- a/drivers/cpuidle/Kconfig.arm
+++ b/drivers/cpuidle/Kconfig.arm
@@ -24,6 +24,14 @@ config ARM_PSCI_CPUIDLE
It provides an idle driver that is capable of detecting and
managing idle states through the PSCI firmware interface.

+ The driver has limitations when used with PREEMPT_RT:
+ - If the idle states are described with the non-hierarchical layout,
+ all idle states are still available.
+
+ - If the idle states are described with the hierarchical layout,
+ only the idle states defined per CPU are available, but not the ones
+ being shared among a group of CPUs (aka cluster idle states).
+
config ARM_PSCI_CPUIDLE_DOMAIN
bool "PSCI CPU idle Domain"
depends on ARM_PSCI_CPUIDLE
diff --git a/drivers/cpuidle/cpuidle-psci-domain.c b/drivers/cpuidle/cpuidle-psci-domain.c
index c80cf9ddabd8..6ad2954948a5 100644
--- a/drivers/cpuidle/cpuidle-psci-domain.c
+++ b/drivers/cpuidle/cpuidle-psci-domain.c
@@ -64,8 +64,11 @@ static int psci_pd_init(struct device_node *np, bool use_osi)

pd->flags |= GENPD_FLAG_IRQ_SAFE | GENPD_FLAG_CPU_DOMAIN;

- /* Allow power off when OSI has been successfully enabled. */
- if (use_osi)
+ /*
+ * Allow power off when OSI has been successfully enabled.
+ * PREEMPT_RT is not yet ready to enter domain idle states.
+ */
+ if (use_osi && !IS_ENABLED(CONFIG_PREEMPT_RT))
pd->power_off = psci_pd_power_off;
else
pd->flags |= GENPD_FLAG_ALWAYS_ON;
diff --git a/drivers/cpuidle/cpuidle-psci.c b/drivers/cpuidle/cpuidle-psci.c
index 312a34ef28dc..6de027f9f6f5 100644
--- a/drivers/cpuidle/cpuidle-psci.c
+++ b/drivers/cpuidle/cpuidle-psci.c
@@ -222,6 +222,9 @@ static int psci_dt_cpu_init_topology(struct cpuidle_driver *drv,
if (!psci_has_osi_support())
return 0;

+ if (IS_ENABLED(CONFIG_PREEMPT_RT))
+ return 0;
+
data->dev = psci_dt_attach_cpu(cpu);
if (IS_ERR_OR_NULL(data->dev))
return PTR_ERR_OR_ZERO(data->dev);
--
2.34.1



2023-01-25 16:47:11

by Daniel Lezcano

[permalink] [raw]
Subject: Re: [PATCH v4] cpuidle: psci: Do not suspend topology CPUs on PREEMPT_RT


Hi Krzysztof,


On 25/01/2023 12:34, Krzysztof Kozlowski wrote:
> The runtime Power Management of CPU topology is not compatible with
> PREEMPT_RT:
> 1. Core cpuidle path disables IRQs.
> 2. Core cpuidle calls cpuidle-psci.
> 3. cpuidle-psci in __psci_enter_domain_idle_state() calls
> pm_runtime_put_sync_suspend() and pm_runtime_get_sync() which use
> spinlocks (which are sleeping on PREEMPT_RT).
>
> Deep sleep modes are not a priority of Realtime kernels because the
> latencies might become unpredictable. On the other hand the PSCI CPU
> idle power domain is a parent of other devices and power domain
> controllers, thus it cannot be simply skipped (e.g. on Qualcomm SM8250).
>
> Disable the idle callbacks in cpuidle-psci and mark the domain as
> always on. This is a trade-off between making PREEMPT_RT working and
> still having a proper power domain hierarchy in the system.

Wouldn't make sense to rely on the latency constraint framework ?


> Cc: Adrien Thierry <[email protected]>
> Cc: Brian Masney <[email protected]>
> Cc: [email protected]
> Signed-off-by: Krzysztof Kozlowski <[email protected]>
>
> ---
>
> Changes since v3:
> 1. Rework - disable idle states, mark as always on (Ulf).
> 2. Extend Kconfig warning (Ulf).
>
> Changes since v1:
> 1. Re-work commit msg.
> 2. Add note to Kconfig.
>
> Several other patches were dropped, as this is the only one actually
> needed. It effectively stops PSCI cpuidle power domains from suspending
> thus solving all other issues I experienced.
> ---
> drivers/cpuidle/Kconfig.arm | 8 ++++++++
> drivers/cpuidle/cpuidle-psci-domain.c | 7 +++++--
> drivers/cpuidle/cpuidle-psci.c | 3 +++
> 3 files changed, 16 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/cpuidle/Kconfig.arm b/drivers/cpuidle/Kconfig.arm
> index 747aa537389b..8deaa2e05206 100644
> --- a/drivers/cpuidle/Kconfig.arm
> +++ b/drivers/cpuidle/Kconfig.arm
> @@ -24,6 +24,14 @@ config ARM_PSCI_CPUIDLE
> It provides an idle driver that is capable of detecting and
> managing idle states through the PSCI firmware interface.
>
> + The driver has limitations when used with PREEMPT_RT:
> + - If the idle states are described with the non-hierarchical layout,
> + all idle states are still available.
> +
> + - If the idle states are described with the hierarchical layout,
> + only the idle states defined per CPU are available, but not the ones
> + being shared among a group of CPUs (aka cluster idle states).
> +
> config ARM_PSCI_CPUIDLE_DOMAIN
> bool "PSCI CPU idle Domain"
> depends on ARM_PSCI_CPUIDLE
> diff --git a/drivers/cpuidle/cpuidle-psci-domain.c b/drivers/cpuidle/cpuidle-psci-domain.c
> index c80cf9ddabd8..6ad2954948a5 100644
> --- a/drivers/cpuidle/cpuidle-psci-domain.c
> +++ b/drivers/cpuidle/cpuidle-psci-domain.c
> @@ -64,8 +64,11 @@ static int psci_pd_init(struct device_node *np, bool use_osi)
>
> pd->flags |= GENPD_FLAG_IRQ_SAFE | GENPD_FLAG_CPU_DOMAIN;
>
> - /* Allow power off when OSI has been successfully enabled. */
> - if (use_osi)
> + /*
> + * Allow power off when OSI has been successfully enabled.
> + * PREEMPT_RT is not yet ready to enter domain idle states.
> + */
> + if (use_osi && !IS_ENABLED(CONFIG_PREEMPT_RT))
> pd->power_off = psci_pd_power_off;
> else
> pd->flags |= GENPD_FLAG_ALWAYS_ON;
> diff --git a/drivers/cpuidle/cpuidle-psci.c b/drivers/cpuidle/cpuidle-psci.c
> index 312a34ef28dc..6de027f9f6f5 100644
> --- a/drivers/cpuidle/cpuidle-psci.c
> +++ b/drivers/cpuidle/cpuidle-psci.c
> @@ -222,6 +222,9 @@ static int psci_dt_cpu_init_topology(struct cpuidle_driver *drv,
> if (!psci_has_osi_support())
> return 0;
>
> + if (IS_ENABLED(CONFIG_PREEMPT_RT))
> + return 0;
> +
> data->dev = psci_dt_attach_cpu(cpu);
> if (IS_ERR_OR_NULL(data->dev))
> return PTR_ERR_OR_ZERO(data->dev);

--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


2023-01-26 12:37:42

by Ulf Hansson

[permalink] [raw]
Subject: Re: [PATCH v4] cpuidle: psci: Do not suspend topology CPUs on PREEMPT_RT

On Wed, 25 Jan 2023 at 12:34, Krzysztof Kozlowski
<[email protected]> wrote:
>
> The runtime Power Management of CPU topology is not compatible with
> PREEMPT_RT:
> 1. Core cpuidle path disables IRQs.
> 2. Core cpuidle calls cpuidle-psci.
> 3. cpuidle-psci in __psci_enter_domain_idle_state() calls
> pm_runtime_put_sync_suspend() and pm_runtime_get_sync() which use
> spinlocks (which are sleeping on PREEMPT_RT).
>
> Deep sleep modes are not a priority of Realtime kernels because the
> latencies might become unpredictable. On the other hand the PSCI CPU
> idle power domain is a parent of other devices and power domain
> controllers, thus it cannot be simply skipped (e.g. on Qualcomm SM8250).
>
> Disable the idle callbacks in cpuidle-psci and mark the domain as
> always on. This is a trade-off between making PREEMPT_RT working and
> still having a proper power domain hierarchy in the system.
>
> Cc: Adrien Thierry <[email protected]>
> Cc: Brian Masney <[email protected]>
> Cc: [email protected]
> Signed-off-by: Krzysztof Kozlowski <[email protected]>

Reviewed-by: Ulf Hansson <[email protected]>

Kind regards
Uffe

>
> ---
>
> Changes since v3:
> 1. Rework - disable idle states, mark as always on (Ulf).
> 2. Extend Kconfig warning (Ulf).
>
> Changes since v1:
> 1. Re-work commit msg.
> 2. Add note to Kconfig.
>
> Several other patches were dropped, as this is the only one actually
> needed. It effectively stops PSCI cpuidle power domains from suspending
> thus solving all other issues I experienced.
> ---
> drivers/cpuidle/Kconfig.arm | 8 ++++++++
> drivers/cpuidle/cpuidle-psci-domain.c | 7 +++++--
> drivers/cpuidle/cpuidle-psci.c | 3 +++
> 3 files changed, 16 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/cpuidle/Kconfig.arm b/drivers/cpuidle/Kconfig.arm
> index 747aa537389b..8deaa2e05206 100644
> --- a/drivers/cpuidle/Kconfig.arm
> +++ b/drivers/cpuidle/Kconfig.arm
> @@ -24,6 +24,14 @@ config ARM_PSCI_CPUIDLE
> It provides an idle driver that is capable of detecting and
> managing idle states through the PSCI firmware interface.
>
> + The driver has limitations when used with PREEMPT_RT:
> + - If the idle states are described with the non-hierarchical layout,
> + all idle states are still available.
> +
> + - If the idle states are described with the hierarchical layout,
> + only the idle states defined per CPU are available, but not the ones
> + being shared among a group of CPUs (aka cluster idle states).
> +
> config ARM_PSCI_CPUIDLE_DOMAIN
> bool "PSCI CPU idle Domain"
> depends on ARM_PSCI_CPUIDLE
> diff --git a/drivers/cpuidle/cpuidle-psci-domain.c b/drivers/cpuidle/cpuidle-psci-domain.c
> index c80cf9ddabd8..6ad2954948a5 100644
> --- a/drivers/cpuidle/cpuidle-psci-domain.c
> +++ b/drivers/cpuidle/cpuidle-psci-domain.c
> @@ -64,8 +64,11 @@ static int psci_pd_init(struct device_node *np, bool use_osi)
>
> pd->flags |= GENPD_FLAG_IRQ_SAFE | GENPD_FLAG_CPU_DOMAIN;
>
> - /* Allow power off when OSI has been successfully enabled. */
> - if (use_osi)
> + /*
> + * Allow power off when OSI has been successfully enabled.
> + * PREEMPT_RT is not yet ready to enter domain idle states.
> + */
> + if (use_osi && !IS_ENABLED(CONFIG_PREEMPT_RT))
> pd->power_off = psci_pd_power_off;
> else
> pd->flags |= GENPD_FLAG_ALWAYS_ON;
> diff --git a/drivers/cpuidle/cpuidle-psci.c b/drivers/cpuidle/cpuidle-psci.c
> index 312a34ef28dc..6de027f9f6f5 100644
> --- a/drivers/cpuidle/cpuidle-psci.c
> +++ b/drivers/cpuidle/cpuidle-psci.c
> @@ -222,6 +222,9 @@ static int psci_dt_cpu_init_topology(struct cpuidle_driver *drv,
> if (!psci_has_osi_support())
> return 0;
>
> + if (IS_ENABLED(CONFIG_PREEMPT_RT))
> + return 0;
> +
> data->dev = psci_dt_attach_cpu(cpu);
> if (IS_ERR_OR_NULL(data->dev))
> return PTR_ERR_OR_ZERO(data->dev);
> --
> 2.34.1
>

2023-01-26 12:45:58

by Ulf Hansson

[permalink] [raw]
Subject: Re: [PATCH v4] cpuidle: psci: Do not suspend topology CPUs on PREEMPT_RT

On Wed, 25 Jan 2023 at 17:46, Daniel Lezcano <[email protected]> wrote:
>
>
> Hi Krzysztof,
>
>
> On 25/01/2023 12:34, Krzysztof Kozlowski wrote:
> > The runtime Power Management of CPU topology is not compatible with
> > PREEMPT_RT:
> > 1. Core cpuidle path disables IRQs.
> > 2. Core cpuidle calls cpuidle-psci.
> > 3. cpuidle-psci in __psci_enter_domain_idle_state() calls
> > pm_runtime_put_sync_suspend() and pm_runtime_get_sync() which use
> > spinlocks (which are sleeping on PREEMPT_RT).
> >
> > Deep sleep modes are not a priority of Realtime kernels because the
> > latencies might become unpredictable. On the other hand the PSCI CPU
> > idle power domain is a parent of other devices and power domain
> > controllers, thus it cannot be simply skipped (e.g. on Qualcomm SM8250).
> >
> > Disable the idle callbacks in cpuidle-psci and mark the domain as
> > always on. This is a trade-off between making PREEMPT_RT working and
> > still having a proper power domain hierarchy in the system.
>
> Wouldn't make sense to rely on the latency constraint framework ?

The main problem is that for runtime PM there is a per device spinlock
being used, which becomes a sleepable lock on PREEMPT_RT.

In other words, the only simple solution is to avoid the calls to
runtime PM in the idle path.

[...]

Kind regards
Uffe

2023-01-26 22:07:08

by Adrien Thierry

[permalink] [raw]
Subject: Re: [PATCH v4] cpuidle: psci: Do not suspend topology CPUs on PREEMPT_RT

Hi Krzysztof,

I tested your patch on the Qdrive3/sa8540p-ride on 6.2.0-rc3-rt1, and it
fixes the issue I encountered in [1].

Tested-by: Adrien Thierry <[email protected]>

Thank you,

Adrien

[1] https://lore.kernel.org/all/[email protected]/


2023-02-07 13:48:31

by Adrien Thierry

[permalink] [raw]
Subject: Re: [PATCH v4] cpuidle: psci: Do not suspend topology CPUs on PREEMPT_RT

Is there still something preventing this patch from being picked up?

Best,

Adrien


2023-02-09 17:09:04

by Rafael J. Wysocki

[permalink] [raw]
Subject: Re: [PATCH v4] cpuidle: psci: Do not suspend topology CPUs on PREEMPT_RT

On Tue, Feb 7, 2023 at 2:47 PM Adrien Thierry <[email protected]> wrote:
>
> Is there still something preventing this patch from being picked up?

Well, I've been waiting for Daniel to do that. Or should I pick it up
directly? Daniel?

2023-02-13 16:17:27

by Rafael J. Wysocki

[permalink] [raw]
Subject: Re: [PATCH v4] cpuidle: psci: Do not suspend topology CPUs on PREEMPT_RT

On Thu, Feb 9, 2023 at 6:08 PM Rafael J. Wysocki <[email protected]> wrote:
>
> On Tue, Feb 7, 2023 at 2:47 PM Adrien Thierry <[email protected]> wrote:
> >
> > Is there still something preventing this patch from being picked up?
>
> Well, I've been waiting for Daniel to do that. Or should I pick it up
> directly? Daniel?

Allright, applied as 6.3 material now, thanks!