[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210119191242.mna6ieiwjuyzol6j@bogus>
Date: Tue, 19 Jan 2021 19:12:42 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Chen Jun <chenjun102@...wei.com>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
lorenzo.pieralisi@....com, catalin.marinas@....com,
guohanjun@...wei.com, rui.xiang@...wei.com, houtao1@...wei.com,
will@...nel.org
Subject: Re: [PATCH] arm64: kernel: Make IPI_WAKEUP under control of
CONFIG_ARM64_ACPI_PARKING_PROTOCOL
On Tue, Jan 19, 2021 at 02:06:09PM +0000, Chen Jun wrote:
> since commit 5e89c55e4ed81d7abb1ce8828db35fa389dc0e90
> ("arm64: kernel: implement ACPI parking protocol")
>
> On arm64, IPI 6 will be wasted without setting
> CONFIG_ARM64_ACPI_PARKING_PROTOCOL.
>
> Signed-off-by: Chen Jun <chenjun102@...wei.com>
> ---
> arch/arm64/kernel/smp.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm64/kernel/smp.c b/arch/arm64/kernel/smp.c
> index ad00f99ee9b0..8b494ad1c61e 100644
> --- a/arch/arm64/kernel/smp.c
> +++ b/arch/arm64/kernel/smp.c
> @@ -73,7 +73,9 @@ enum ipi_msg_type {
> IPI_CPU_CRASH_STOP,
> IPI_TIMER,
Going by that logic, IPI_TIMER is used only when
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y and
> IPI_IRQ_WORK,
IPI_IRQ_WORK when CONFIG_IRQ_WORK=y
Not sure if we what to go down that path as it may result in confusion
about IPI number and what OS is using it for. I am not against this, just
want to know others opinion on this.
> +#ifdef CONFIG_ARM64_ACPI_PARKING_PROTOCOL
> IPI_WAKEUP,
> +#endif
Just out of curiosity, are you changing this only by code inspection or
or you running short of IPI with some downstream patches. It will be
interesting to know how you are using then if you are as it may break if
kernel decides to you them in future for its own use.
--
Regards,
Sudeep
Powered by blists - more mailing lists