[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240409150536.9933-1-miguel.luis@oracle.com>
Date: Tue, 9 Apr 2024 15:05:29 +0000
From: Miguel Luis <miguel.luis@...cle.com>
To: Jonathan.Cameron@...wei.com, "Rafael J. Wysocki" <rafael@...nel.org>,
Len Brown <lenb@...nel.org>, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: rmk+kernel@...linux.org.uk, miguel.luis@...cle.com
Subject: [RFC PATCH 0/4] ACPI: processor: refactor acpi_processor_{get_info|remove}
Both acpi_processor_get_info and acpi_processor_remove functions have
architecture dependent functionality enabled via CONFIG_ACPI_HOTPLUG_CPU.
Current pre-processor guards are restricting too much of functionality which
makes it dificult to integrate other features such as Virtual CPU
hotplug/unplug for arm64.
This series, applied on top of v6.9-rc3, suggests a refactoring on these two
functions with the intent to understand them better and hopefully ease
integration of more functionality.
Apart from patches 2/4 and 3/4, which could be squashed but left them separated
intentionally so it would ease reviewing, changes are self-contained.
So far I've boot tested it successfully alone and as a prefix for vCPU hotplug/unplug
patches [1], on arm64.
[1]: https://lore.kernel.org/linux-arm-kernel/Zbp5xzmFhKDAgHws@shell.armlinux.org.uk/
Miguel Luis (4):
ACPI: processor: refactor acpi_processor_get_info: evaluation of
processor declaration
ACPI: processor: refactor acpi_processor_get_info: isolate cpu hotpug
init delay
ACPI: processor: refactor acpi_processor_get_info: isolate
acpi_{map|unmap}_cpu under CONFIG_ACPI_HOTPLUG_CPU
ACPI: processor: refactor acpi_processor_remove: isolate
acpi_unmap_cpu under CONFIG_ACPI_HOTPLUG_CPU
drivers/acpi/acpi_processor.c | 138 ++++++++++++++++++++++------------
1 file changed, 91 insertions(+), 47 deletions(-)
--
2.43.0
Powered by blists - more mailing lists