Something went wrong. Try again.
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Something went wrong. Try again.
4.0 kB · 83 lines
at master
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384.. SPDX-License-Identifier: GPL-2.0.. _cpuhp_index:
====================CPU Hotplug and ACPI====================
CPU hotplug in the arm64 world is commonly used to describe the kernel takingCPUs online/offline using PSCI. This document is about ACPI firmware allowingCPUs that were not available during boot to be added to the system later.
``possible`` and ``present`` refer to the state of the CPU as seen by linux.
CPU Hotplug on physical systems - CPUs not present at boot----------------------------------------------------------
Physical systems need to mark a CPU that is ``possible`` but not ``present`` asbeing ``present``. An example would be a dual socket machine, where the packagein one of the sockets can be replaced while the system is running.
This is not supported.
In the arm64 world CPUs are not a single device but a slice of the system.There are no systems that support the physical addition (or removal) of CPUswhile the system is running, and ACPI is not able to sufficiently describethem.
e.g. New CPUs come with new caches, but the platform's cache topology isdescribed in a static table, the PPTT. How caches are shared between CPUs isnot discoverable, and must be described by firmware.
e.g. The GIC redistributor for each CPU must be accessed by the driver duringboot to discover the system wide supported features. ACPI's MADT GICCstructures can describe a redistributor associated with a disabled CPU, butcan't describe whether the redistributor is accessible, only that it is not'always on'.
arm64's ACPI tables assume that everything described is ``present``.
CPU Hotplug on virtual systems - CPUs not enabled at boot---------------------------------------------------------
Virtual systems have the advantage that all the properties the system willever have can be described at boot. There are no power-domain considerationsas such devices are emulated.
CPU Hotplug on virtual systems is supported. It is distinct from physicalCPU Hotplug as all vCPU resources are statically described in the firmwareconfiguration tables (e.g. MADT), meaning their maximum possible count isknown at boot. However, vCPUs that are not enabled at boot are not markedas ``present`` by the kernel until they are hotplugged. An example is wherea virtual machine boots with a single CPU, and additional CPUs are addedonce a cloud orchestrator deploys the workload.
For a virtual machine, the VMM (e.g. Qemu) plays the part of firmware.
Virtual hotplug is implemented as a firmware policy affecting which CPUs can bebrought online. Firmware can enforce its policy via PSCI's return codes. e.g.``DENIED``.
The ACPI tables must describe all the resources of the virtual machine. CPUsthat are hot-pluggable must have the ``online capable`` bit set and the``enabled`` bit cleared in the MADT GICC structures to indicate they can beenabled later. The boot CPU must be marked as ``enabled`` with its``online capable`` bit cleared. The 'always on' GICR structure must be usedto describe the redistributors.
CPUs described as ``online capable`` but not ``enabled`` can be set to enabledby the DSDT's Processor object's _STA method. On virtual systems the _STA methodmust always set the ``ACPI_STA_DEVICE_PRESENT`` bit, while toggling the``ACPI_STA_DEVICE_ENABLED`` bit to reflect its plug status. The kernel willthen dynamically mark the vCPU as ``present`` within the OS when the``ACPI_STA_DEVICE_ENABLED`` bit becomes set during hot-add. Changes to thefirmware policy can be notified to the OS via device-check or eject-request.
CPUs described as ``enabled`` in the static table, should not have their _STAmodified dynamically by firmware. Soft-restart features such as kexec willre-read the static properties of the system from these static tables, andmay malfunction if these no longer describe the running system. Linux willre-discover the dynamic properties of the system from the _STA method laterduring boot.