From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 799DFE71D40 for ; Fri, 29 Sep 2023 15:06:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=JxZC2cRdtgpCKZZS6L+1PGEZT0kdyOkRrf5HkyFg5Ds=; b=j4ZTGSjhPYeaWU ysyhFmuCD/9xdIzJCXg5FFPMViA5lOUTuG5Uh7UaaKdWDYuEs9uIo6f4YoU4Chm4VSMHfK7I+J18W sFoZjeA01FVKXHBec6/PhhVdivdfGXGZHroEZhcfrnTp+HHcQfdTXF84zCvDG01dEc7d/OQhatVPP tBtqD3QcKQDipXL9EZDBqvTTRkwiDydd+0pOCXMBwy2fwgqSL1EGMRbpChqILaql1uW5rIc7RsN// EmFKEQVnd+7YoqAo1cuwvGMpvqEuCU2qEdk84PtPrtVwFV9FfIuZW84xKVdXNT0lx0TV4oCHWTSkv c99poFW2xcUdvjDK33/Q==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qmF3l-0089Rw-0K; Fri, 29 Sep 2023 15:05:41 +0000 Received: from ams.source.kernel.org ([145.40.68.75]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qmF3F-0089FT-1Z for linux-arm-kernel@lists.infradead.org; Fri, 29 Sep 2023 15:05:11 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by ams.source.kernel.org (Postfix) with ESMTP id B244CB81FA2; Fri, 29 Sep 2023 15:05:05 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 709F0C433C7; Fri, 29 Sep 2023 15:05:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1695999905; bh=IvLxKbqu0MJgGbtWdNSigZb9rbYGAOtYXK50iU/aEPs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=BFxxC1pPrNlbYvtFzBpbAcD4+6LoMtcr9+nAuoZy0+t0EpMWsm2UhfDbTbzMORVJO 3m2gT+1NH4ebANnLQq4MAACqQIeyHRQDazOZJz39dKaEB+RK9BBAwVjx6gG3Ac7eU3 Qwea7jAO9LOUszza6bK5Pqf3Xz4oK8wNIqmuq2e9PLri8X6xRPufmr0fIYGJzbOc/P jKVD2ol3IC6jeYDjJTM93XWeu8LlgEe0c+v6yPg3bG2/G5acJAWmDsdizIfpek2Yyw c/Oo8LfAlGwIEvnZAU1seLIkkVL9oqItcqZpOzgUZMl5Lum2DMvjO/f0CErD/f0xV3 WxR7HHGjB1tkA== Date: Fri, 29 Sep 2023 16:04:59 +0100 From: Will Deacon To: Oza Pawandeep Cc: sudeep.holla@arm.com, catalin.marinas@arm.com, rafael@kernel.org, lenb@kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org Subject: Re: [PATCH v8] cpuidle, ACPI: Evaluate LPI arch_flags for broadcast timer Message-ID: <20230929150459.GA30623@willie-the-truck> References: <20230918172140.2825357-1-quic_poza@quicinc.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20230918172140.2825357-1-quic_poza@quicinc.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230929_080509_810173_43041E06 X-CRM114-Status: GOOD ( 29.95 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, Sep 18, 2023 at 10:21:40AM -0700, Oza Pawandeep wrote: > Arm=AE Functional Fixed Hardware Specification defines LPI states, > which provide an architectural context loss flags field that can > be used to describe the context that might be lost when an LPI > state is entered. > = > - Core context Lost > - General purpose registers. > - Floating point and SIMD registers. > - System registers, include the System register based > - generic timer for the core. > - Debug register in the core power domain. > - PMU registers in the core power domain. > - Trace register in the core power domain. > - Trace context loss > - GICR > - GICD > = > Qualcomm's custom CPUs preserves the architectural state, > including keeping the power domain for local timers active. > when core is power gated, the local timers are sufficient to > wake the core up without needing broadcast timer. > = > The patch fixes the evaluation of cpuidle arch_flags, and moves only to > broadcast timer if core context lost is defined in ACPI LPI. > = > Fixes: a36a7fecfe607 ("Add support for Low Power Idle(LPI) states") > Reviewed-by: Sudeep Holla > Acked-by: Rafael J. Wysocki > Signed-off-by: Oza Pawandeep > --- > = > Notes: > Will/Catalin: Rafael has acked and he prefers to take it via arm64 tr= ee > = > diff --git a/arch/arm64/include/asm/acpi.h b/arch/arm64/include/asm/acpi.h > index 4d537d56eb84..269d21209723 100644 > --- a/arch/arm64/include/asm/acpi.h > +++ b/arch/arm64/include/asm/acpi.h > @@ -9,6 +9,7 @@ > #ifndef _ASM_ACPI_H > #define _ASM_ACPI_H > = > +#include > #include > #include > #include > @@ -44,6 +45,23 @@ > = > #define ACPI_MADT_GICC_TRBE (offsetof(struct acpi_madt_generic_interrup= t, \ > trbe_interrupt) + sizeof(u16)) > +/* > + * Arm=AE Functional Fixed Hardware Specification Version 1.2. > + * Table 2: Arm Architecture context loss flags > + */ > +#define CPUIDLE_CORE_CTXT BIT(0) /* Core context Lost */ > + > +static __always_inline void _arch_update_idle_state_flags(u32 arch_flags, > + unsigned int *sflags) Why can't this just be 'static inline'? > +{ > + if (arch_flags & CPUIDLE_CORE_CTXT) > + *sflags |=3D CPUIDLE_FLAG_TIMER_STOP; > +} > +#define arch_update_idle_state_flags _arch_update_idle_state_flags Usually, the function and the macro have the same name for this pattern, so I think it would be more consistent to drop the leading underscore from the C function name. > + > +#define CPUIDLE_TRACE_CTXT BIT(1) /* Trace context loss */ > +#define CPUIDLE_GICR_CTXT BIT(2) /* GICR */ > +#define CPUIDLE_GICD_CTXT BIT(3) /* GICD */ > = > /* Basic configuration for ACPI */ > #ifdef CONFIG_ACPI > diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c > index dc615ef6550a..5c1d13eecdd1 100644 > --- a/drivers/acpi/processor_idle.c > +++ b/drivers/acpi/processor_idle.c > @@ -1217,8 +1217,7 @@ static int acpi_processor_setup_lpi_states(struct a= cpi_processor *pr) > strscpy(state->desc, lpi->desc, CPUIDLE_DESC_LEN); > state->exit_latency =3D lpi->wake_latency; > state->target_residency =3D lpi->min_residency; > - if (lpi->arch_flags) > - state->flags |=3D CPUIDLE_FLAG_TIMER_STOP; > + arch_update_idle_state_flags(lpi->arch_flags, &state->flags); Hmm, I know Rafael has Acked this, but I think this is pretending to be more generic than it really is. While passing in a pointer to the flags field allows the arch code to set and clear arbitrary flags, we're calling this before we've set CPUIDLE_FLAG_RCU_IDLE, so that cannot be changed. Why not just name it like it is and return the arch flags directly: state->flags |=3D arch_get_idle_state_flags(lpi->arch_flags); ? > if (i !=3D 0 && lpi->entry_method =3D=3D ACPI_CSTATE_FFH) > state->flags |=3D CPUIDLE_FLAG_RCU_IDLE; > state->enter =3D acpi_idle_lpi_enter; > diff --git a/include/linux/acpi.h b/include/linux/acpi.h > index a73246c3c35e..07a825c76bab 100644 > --- a/include/linux/acpi.h > +++ b/include/linux/acpi.h > @@ -1480,6 +1480,12 @@ static inline int lpit_read_residency_count_addres= s(u64 *address) > } > #endif > = > +#ifdef CONFIG_ACPI_PROCESSOR_IDLE > +#ifndef arch_update_idle_state_flags > +#define arch_update_idle_state_flags(af, sf) do {} while (0) I'd prefer defining this to point at an empty static inline function so that we get evaluation and type-checking of the arguments. > +#endif > +#endif /* CONFIG_ACPI_PROCESSOR_IDLE */ Why do you need the outer CONFIG_ guards here? Will _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel