Received: by 2002:a05:7412:5112:b0:fa:6e18:a558 with SMTP id fm18csp25168rdb; Mon, 22 Jan 2024 10:42:12 -0800 (PST) X-Google-Smtp-Source: AGHT+IHC3W0tY5Mkmp7675oyG+K3YgUOFJVVr4C1LQe+zphf3o1osjajvAA24JcS2L/I2ZEQFMyo X-Received: by 2002:a17:902:f542:b0:1d7:953:bc00 with SMTP id h2-20020a170902f54200b001d70953bc00mr6417374plf.73.1705948932247; Mon, 22 Jan 2024 10:42:12 -0800 (PST) Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [139.178.88.99]) by mx.google.com with ESMTPS id u1-20020a17090341c100b001d76501a1ecsi628277ple.469.2024.01.22.10.42.12 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 22 Jan 2024 10:42:12 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-33885-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99; Authentication-Results: mx.google.com; arc=fail (body hash mismatch); spf=pass (google.com: domain of linux-kernel+bounces-33885-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-33885-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 sv.mirrors.kernel.org (Postfix) with ESMTPS id BC8D5288BFF for ; Mon, 22 Jan 2024 18:28:45 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 3DE155102D; Mon, 22 Jan 2024 18:00:21 +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 8814851023; Mon, 22 Jan 2024 18:00:17 +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=1705946420; cv=none; b=COhhDyP3I0brm5h6VOn3XOFfDk7henD/Vkk9Rh2HVGKouaNvo2hl9PKnE0CzQU6hvnsFQ0ox9O8eI51UGWS8yaIrbRdyKta/xHGpyO0sB7bvsRApiwizSk6FXMDGHSsAUMuFbK+f35fHaU6bki18IAXlPUqW1ZGh0c9hSTnBgkQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1705946420; c=relaxed/simple; bh=1QPBYp1cuVlPzvmIrkvDtRmi9tk3BbCt5QfOkc4KoTA=; h=Date:From:To:CC:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=oNYcKz0LIXIuDfoVseADQ+wbhY/PxzZL+hDYsVttKEi4SsPnzZaEvgJeVY86/PdCMllRsfJ7z+6xvqJFvlpntca6QpEyLQvycsXODO/hMhE8btP6tezSbS1hs/wPOfifpYHKKmWXlqhUbH54CNAbwQOnuWcay96BUo5/yZ1Kumw= 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 4TJdGS60Srz67ZCr; Tue, 23 Jan 2024 01:57:20 +0800 (CST) Received: from lhrpeml500005.china.huawei.com (unknown [7.191.163.240]) by mail.maildlp.com (Postfix) with ESMTPS id DA1F61400F4; Tue, 23 Jan 2024 02:00:14 +0800 (CST) Received: from localhost (10.202.227.76) by lhrpeml500005.china.huawei.com (7.191.163.240) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Mon, 22 Jan 2024 18:00:14 +0000 Date: Mon, 22 Jan 2024 18:00:13 +0000 From: Jonathan Cameron To: "Rafael J. Wysocki" CC: Russell King , , , , , , , , , , , , , , , Salil Mehta , Jean-Philippe Brucker , , , James Morse Subject: Re: [PATCH RFC v3 05/21] ACPI: Rename ACPI_HOTPLUG_CPU to include 'present' Message-ID: <20240122180013.000016d5@Huawei.com> In-Reply-To: References: Organization: Huawei Technologies Research and Development (UK) Ltd. X-Mailer: Claws Mail 4.1.0 (GTK 3.24.33; x86_64-w64-mingw32) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-ClientProxiedBy: lhrpeml500004.china.huawei.com (7.191.163.9) To lhrpeml500005.china.huawei.com (7.191.163.240) On Mon, 18 Dec 2023 21:35:16 +0100 "Rafael J. Wysocki" wrote: > On Wed, Dec 13, 2023 at 1:49=E2=80=AFPM Russell King wrote: > > > > From: James Morse > > > > The code behind ACPI_HOTPLUG_CPU allows a not-present CPU to become > > present. =20 >=20 > Right. >=20 > > This isn't the only use of HOTPLUG_CPU. On arm64 and riscv > > CPUs can be taken offline as a power saving measure. =20 >=20 > But still there is the case in which a non-present CPU can become > present, isn't it there? Not yet defined by the architectures (and I'm assuming it probably never wi= ll be). The original proposal we took to ARM was to do exactly that - they pushed back hard on the basis there was no architecturally safe way to implement i= t. Too much of the ARM arch has to exist from the start of time. https://lore.kernel.org/linux-arm-kernel/cbaa6d68-6143-e010-5f3c-ec62f879ad= 95@arm.com/ is one of the relevant threads of the kernel side of that discussion. Not to put specific words into the ARM architects mouths, but the short description is that there is currently no demand for working out how to make physical CPU hotplug possible, as such they will not provide an architecturally compliant way to do it for virtual CPU hotplug a= nd another means is needed (which is why this series doesn't use the present b= it for that purpose and we have the Online capable bit in MADT/GICC) It was a 'fun' dance of several years to get to that clarification. As another fun fact, the same is defined for x86, but I don't think anyone has used it yet (GICC for ARM has an online capable bit in the flags= to enable this, which was remarkably similar to the online capable bit in the flags of the Local APIC entries as added fairly recently). >=20 > > On arm64 an offline CPU may be disabled by firmware, preventing it from > > being brought back online, but it remains present throughout. > > > > Adding code to prevent user-space trying to online these disabled CPUs > > needs some additional terminology. > > > > Rename the Kconfig symbol CONFIG_ACPI_HOTPLUG_PRESENT_CPU to reflect > > that it makes possible CPUs present. =20 >=20 > Honestly, I don't think that this change is necessary or even useful. Whilst it's an attempt to avoid future confusion, the rename is not something I really care about so my advice to Russell is drop it unless you are attached to it! Jonathan >=20 > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel