Received: by 2002:a05:7208:2204:b0:82:bbfa:f723 with SMTP id s4csp331713rbb; Thu, 18 Apr 2024 07:05:14 -0700 (PDT) X-Forwarded-Encrypted: i=3; AJvYcCUwVBfCYsTZYIrFR727hwrUfc3gwQcOJAUdeQP+RIpwxXftoWyxfcHodamHypdqB6FIRi++JHogQYjxYUf4r2Bzkfh+DRnDX6pAn5GspA== X-Google-Smtp-Source: AGHT+IH30Sr1UnDEvfnE4uhP4i4d+4at3yO+wnTPQ4APmPUYuOEDM8+YVcN6C/zAXgHrKueGLmk0 X-Received: by 2002:a05:620a:820a:b0:78e:cce7:dbdf with SMTP id ow10-20020a05620a820a00b0078ecce7dbdfmr3001650qkn.9.1713449114121; Thu, 18 Apr 2024 07:05:14 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1713449114; cv=pass; d=google.com; s=arc-20160816; b=JzYP2u6aIiH1Vc2N2jq83hZC3v5CknEGaIVi6QZ7Z/oQcvzC1wdJ8De8Wfp+GXb9+c u9nZrih3l+HxrMk9dIZydVrxfrUtOmqos3/B0wx1MiLAZRPYx9rJRiNT+Q/+dAXunSjW PlMOIfG13ViUJUQHm6ezMx2TRLlVyrrbkIvRD0ASbQ19pAtRoglvSkRgMM7vY0wNhxXE GgtfFa4rtkfGt7hqSW3ErPHUTDlaGbNO/5XQIBdiFgQhMMLvDitWm7VK48GN3A9GNYhB NDYGJIY4A3eTlNfKJvIIZS/jVMS6tU8dZGm12/upKFHDAcnrGIt7YvCTK5WMGl8iQnqY 15Tg== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:in-reply-to:message-id :date:subject:cc:to:from; bh=NG9D2ECRFZ1q+VGTCqulDSJCZ3myY58ktLCKcEcOlWM=; fh=wmH6eZgtoFCyes/zVTYi+VaxxdPmNW9hqdNd8ZTZ4XU=; b=J9nzR1zfgzIGGCW6d5PVXaa+D47WVVqTXeTSks14TQQLrakvwJS71tbJ0bWJq/CMGl kbmjs3x6qSVIfduj7EYTKJPg/0G/8yU21OJdSU+nTSHe4/NLDhGiohq8GGrqgc7Bxsow GloKA06pgYTqbOX8oE4Xplw2rfsL/oo9KIwNmsUu3ZhT1Bkm47HOo0jOCvoG+ZzmHxeX mEF8tJFQVGIP3cDLayKxBUbdY5QbBqhEsJ0oPSR6GCxcrjVjz/cHMakEHXdsYVBuy5UU jKmW9zYuGM1xCHkZgMITrGTn19BYYwxVJbuG1ow981ffKmecVa95Nfb2qUX0EqBLKxnX 5bAQ==; dara=google.com ARC-Authentication-Results: i=2; mx.google.com; arc=pass (i=1 spf=pass spfdomain=huawei.com dmarc=pass fromdomain=huawei.com); spf=pass (google.com: domain of linux-kernel+bounces-150238-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-150238-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Return-Path: Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [2604:1380:45d1:ec00::1]) by mx.google.com with ESMTPS id v17-20020a05622a189100b00436adb6885bsi1483286qtc.236.2024.04.18.07.05.13 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 18 Apr 2024 07:05:14 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel+bounces-150238-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1; Authentication-Results: mx.google.com; arc=pass (i=1 spf=pass spfdomain=huawei.com dmarc=pass fromdomain=huawei.com); spf=pass (google.com: domain of linux-kernel+bounces-150238-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-150238-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id EB2BF1C239AC for ; Thu, 18 Apr 2024 14:03:02 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id C4E10168B05; Thu, 18 Apr 2024 14:02:02 +0000 (UTC) Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1206C165FBA; Thu, 18 Apr 2024 14:01:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.176.79.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1713448922; cv=none; b=OzLxtYHIzxIDSS2+Q2erLtkUcOMSHirZPhqVD3Dn0Fyk00eSwBVRsmIYePLATJw+zbr9Vd0Y4U9OBrGgYmWlkDdseLNXnS0fqT5EjCP9yK1rCadBh7BeGxG4D+GcL6GHi2c3ZIj/P57dyazmBTen2+Pu8lMqt9/WKv3/BtHJzLc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1713448922; c=relaxed/simple; bh=17LJ8PPEslEeN+FJm+ML+5/gPpuIz6+G0l/XypqAI0M=; h=From:To:CC:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=s0xv1ccvpnyJeEz88nhMbvc+/JfhXCPi3jsmsCVgZCQJidrk8n3Yg3zuiM0pfaxokCGRnwCMd45PkdMo9CSKgvTcMxk1NOqG/WgrZ0En5/gMDf+Q5OIXc3EiESkY1F2oRGquT1cMbuUhQ0MWxTZSFA2lg64LY1rC/MFoHBFJABk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=185.176.79.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4VKztJ4X1Nz6K6Sx; Thu, 18 Apr 2024 21:59:52 +0800 (CST) Received: from lhrpeml500005.china.huawei.com (unknown [7.191.163.240]) by mail.maildlp.com (Postfix) with ESMTPS id 013D814038F; Thu, 18 Apr 2024 22:01:56 +0800 (CST) Received: from SecurePC-101-06.china.huawei.com (10.122.247.231) by lhrpeml500005.china.huawei.com (7.191.163.240) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Thu, 18 Apr 2024 15:01:55 +0100 From: Jonathan Cameron To: Thomas Gleixner , Peter Zijlstra , , , , , , , , , Russell King , "Rafael J . Wysocki" , Miguel Luis , James Morse , Salil Mehta , Jean-Philippe Brucker , Catalin Marinas , Will Deacon CC: Ingo Molnar , Borislav Petkov , Dave Hansen , , , Subject: [PATCH v7 15/16] arm64: document virtual CPU hotplug's expectations Date: Thu, 18 Apr 2024 14:54:11 +0100 Message-ID: <20240418135412.14730-16-Jonathan.Cameron@huawei.com> X-Mailer: git-send-email 2.39.2 In-Reply-To: <20240418135412.14730-1-Jonathan.Cameron@huawei.com> References: <20240418135412.14730-1-Jonathan.Cameron@huawei.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-ClientProxiedBy: lhrpeml100002.china.huawei.com (7.191.160.241) To lhrpeml500005.china.huawei.com (7.191.163.240) From: James Morse Add a description of physical and virtual CPU hotplug, explain the differences and elaborate on what is required in ACPI for a working virtual hotplug system. Signed-off-by: James Morse Reviewed-by: Jonathan Cameron Signed-off-by: Russell King (Oracle) Signed-off-by: Jonathan Cameron --- v7: No change. --- Documentation/arch/arm64/cpu-hotplug.rst | 79 ++++++++++++++++++++++++ Documentation/arch/arm64/index.rst | 1 + 2 files changed, 80 insertions(+) diff --git a/Documentation/arch/arm64/cpu-hotplug.rst b/Documentation/arch/arm64/cpu-hotplug.rst new file mode 100644 index 000000000000..76ba8d932c72 --- /dev/null +++ b/Documentation/arch/arm64/cpu-hotplug.rst @@ -0,0 +1,79 @@ +.. 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 taking +CPUs online/offline using PSCI. This document is about ACPI firmware allowing +CPUs 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`` as +being ``present``. An example would be a dual socket machine, where the package +in 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 CPUs +while the system is running, and ACPI is not able to sufficiently describe +them. + +e.g. New CPUs come with new caches, but the platform's cache toplogy is +described in a static table, the PPTT. How caches are shared between CPUs is +not discoverable, and must be described by firmware. + +e.g. The GIC redistributor for each CPU must be accessed by the driver during +boot to discover the system wide supported features. ACPI's MADT GICC +structures can describe a redistributor associated with a disabled CPU, but +can'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 will +ever have can be described at boot. There are no power-domain considerations +as such devices are emulated. + +CPU Hotplug on virtual systems is supported. It is distinct from physical +CPU Hotplug as all resources are described as ``present``, but CPUs may be +marked as disabled by firmware. Only the CPU's online/offline behaviour is +influenced by firmware. An example is where a virtual machine boots with a +single CPU, and additional CPUs are added once 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 be +brought 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. CPUs +that firmware wishes to disable either from boot (or later) should not be +``enabled`` in the MADT GICC structures, but should have the ``online capable`` +bit set, to indicate they can be enabled later. The boot CPU must be marked as +``enabled``. The 'always on' GICR structure must be used to describe the +redistributors. + +CPUs described as ``online capable`` but not ``enabled`` can be set to enabled +by the DSDT's Processor object's _STA method. On virtual systems the _STA method +must always report the CPU as ``present``. Changes to the firmware 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 _STA +modified dynamically by firmware. Soft-restart features such as kexec will +re-read the static properties of the system from these static tables, and +may malfunction if these no longer describe the running system. Linux will +re-discover the dynamic properties of the system from the _STA method later +during boot. diff --git a/Documentation/arch/arm64/index.rst b/Documentation/arch/arm64/index.rst index d08e924204bf..78544de0a8a9 100644 --- a/Documentation/arch/arm64/index.rst +++ b/Documentation/arch/arm64/index.rst @@ -13,6 +13,7 @@ ARM64 Architecture asymmetric-32bit booting cpu-feature-registers + cpu-hotplug elf_hwcaps hugetlbpage kdump -- 2.39.2