diff mbox series

[v3] SUPPORT: downgrade Physical CPU Hotplug to Experimental

Message ID 20230927232004.1981595-1-sstabellini@kernel.org (mailing list archive)
State New, archived
Headers show
Series [v3] SUPPORT: downgrade Physical CPU Hotplug to Experimental | expand

Commit Message

Stefano Stabellini Sept. 27, 2023, 11:20 p.m. UTC
From: Stefano Stabellini <stefano.stabellini@amd.com>

The feature is not commonly used, and we don't have hardware to test it,
not in OSSTest, not in Gitlab, and not even ad-hoc manually by community
members. We could use QEMU to test it, but even that it is known not to
work.

Also take the opportunity to rename the feature to "ACPI CPU Hotplug"
for clarity.

Signed-off-by: Stefano Stabellini <stefano.stabellini@amd.com>
---
Changes in v3:
- add note to CHANGELOG.md
---
 CHANGELOG.md | 2 ++
 SUPPORT.md   | 4 ++--
 2 files changed, 4 insertions(+), 2 deletions(-)

Comments

Henry Wang Sept. 27, 2023, 11:50 p.m. UTC | #1
Hi Stefano,

> On Sep 28, 2023, at 07:20, Stefano Stabellini <sstabellini@kernel.org> wrote:
> 
> From: Stefano Stabellini <stefano.stabellini@amd.com>
> 
> The feature is not commonly used, and we don't have hardware to test it,
> not in OSSTest, not in Gitlab, and not even ad-hoc manually by community
> members. We could use QEMU to test it, but even that it is known not to
> work.
> 
> Also take the opportunity to rename the feature to "ACPI CPU Hotplug"
> for clarity.
> 
> Signed-off-by: Stefano Stabellini <stefano.stabellini@amd.com>

Release-acked-by: Henry Wang <Henry.Wang@arm.com>

Kind regards,
Henry
Roger Pau Monné Sept. 28, 2023, 8:32 a.m. UTC | #2
On Wed, Sep 27, 2023 at 04:20:04PM -0700, Stefano Stabellini wrote:
> From: Stefano Stabellini <stefano.stabellini@amd.com>
> 
> The feature is not commonly used, and we don't have hardware to test it,
> not in OSSTest, not in Gitlab, and not even ad-hoc manually by community
> members. We could use QEMU to test it, but even that it is known not to
> work.

I think this last sentence is ambiguous.  QEMU ACPI CPU hotplug
implementation does work AFAIK, it's Xen implementation of ACPI
hotplug that explodes (or so I've been told).  I would drop or reword
the "but even that it is known not to work." part of the sentence.

> 
> Also take the opportunity to rename the feature to "ACPI CPU Hotplug"
> for clarity.
> 
> Signed-off-by: Stefano Stabellini <stefano.stabellini@amd.com>

Acked-by: Roger Pau Monné <roger.pau@citrix.com>

Thanks, Roger.
Jan Beulich Sept. 28, 2023, 9:32 a.m. UTC | #3
On 28.09.2023 10:32, Roger Pau Monné wrote:
> On Wed, Sep 27, 2023 at 04:20:04PM -0700, Stefano Stabellini wrote:
>> From: Stefano Stabellini <stefano.stabellini@amd.com>
>>
>> The feature is not commonly used, and we don't have hardware to test it,
>> not in OSSTest, not in Gitlab, and not even ad-hoc manually by community
>> members. We could use QEMU to test it, but even that it is known not to
>> work.
> 
> I think this last sentence is ambiguous.  QEMU ACPI CPU hotplug
> implementation does work AFAIK, it's Xen implementation of ACPI
> hotplug that explodes (or so I've been told).  I would drop or reword
> the "but even that it is known not to work." part of the sentence.

Maybe simply add "... on our end"?

Jan
Roger Pau Monné Sept. 28, 2023, 9:51 a.m. UTC | #4
On Thu, Sep 28, 2023 at 11:32:22AM +0200, Jan Beulich wrote:
> On 28.09.2023 10:32, Roger Pau Monné wrote:
> > On Wed, Sep 27, 2023 at 04:20:04PM -0700, Stefano Stabellini wrote:
> >> From: Stefano Stabellini <stefano.stabellini@amd.com>
> >>
> >> The feature is not commonly used, and we don't have hardware to test it,
> >> not in OSSTest, not in Gitlab, and not even ad-hoc manually by community
> >> members. We could use QEMU to test it, but even that it is known not to
> >> work.
> > 
> > I think this last sentence is ambiguous.  QEMU ACPI CPU hotplug
> > implementation does work AFAIK, it's Xen implementation of ACPI
> > hotplug that explodes (or so I've been told).  I would drop or reword
> > the "but even that it is known not to work." part of the sentence.
> 
> Maybe simply add "... on our end"?

WFM.

Thanks, Roger.
Stefano Stabellini Sept. 28, 2023, 8:48 p.m. UTC | #5
On Thu, 28 Sep 2023, Roger Pau Monné wrote:
> On Thu, Sep 28, 2023 at 11:32:22AM +0200, Jan Beulich wrote:
> > On 28.09.2023 10:32, Roger Pau Monné wrote:
> > > On Wed, Sep 27, 2023 at 04:20:04PM -0700, Stefano Stabellini wrote:
> > >> From: Stefano Stabellini <stefano.stabellini@amd.com>
> > >>
> > >> The feature is not commonly used, and we don't have hardware to test it,
> > >> not in OSSTest, not in Gitlab, and not even ad-hoc manually by community
> > >> members. We could use QEMU to test it, but even that it is known not to
> > >> work.
> > > 
> > > I think this last sentence is ambiguous.  QEMU ACPI CPU hotplug
> > > implementation does work AFAIK, it's Xen implementation of ACPI
> > > hotplug that explodes (or so I've been told).  I would drop or reword
> > > the "but even that it is known not to work." part of the sentence.
> > 
> > Maybe simply add "... on our end"?
> 
> WFM.

Just to be clear we are going for:

"The feature is not commonly used, and we don't have hardware to test it,
not in OSSTest, not in Gitlab, and not even ad-hoc manually by community
members. We could use QEMU to test it, but even that it is known not to
work on our end."

Can the change be done on commit?
Roger Pau Monné Oct. 2, 2023, 11:46 a.m. UTC | #6
On Thu, Sep 28, 2023 at 01:48:59PM -0700, Stefano Stabellini wrote:
> On Thu, 28 Sep 2023, Roger Pau Monné wrote:
> > On Thu, Sep 28, 2023 at 11:32:22AM +0200, Jan Beulich wrote:
> > > On 28.09.2023 10:32, Roger Pau Monné wrote:
> > > > On Wed, Sep 27, 2023 at 04:20:04PM -0700, Stefano Stabellini wrote:
> > > >> From: Stefano Stabellini <stefano.stabellini@amd.com>
> > > >>
> > > >> The feature is not commonly used, and we don't have hardware to test it,
> > > >> not in OSSTest, not in Gitlab, and not even ad-hoc manually by community
> > > >> members. We could use QEMU to test it, but even that it is known not to
> > > >> work.
> > > > 
> > > > I think this last sentence is ambiguous.  QEMU ACPI CPU hotplug
> > > > implementation does work AFAIK, it's Xen implementation of ACPI
> > > > hotplug that explodes (or so I've been told).  I would drop or reword
> > > > the "but even that it is known not to work." part of the sentence.
> > > 
> > > Maybe simply add "... on our end"?
> > 
> > WFM.
> 
> Just to be clear we are going for:
> 
> "The feature is not commonly used, and we don't have hardware to test it,
> not in OSSTest, not in Gitlab, and not even ad-hoc manually by community
> members. We could use QEMU to test it, but even that it is known not to
> work on our end."
> 
> Can the change be done on commit?

LGTM.

Feel free to add my Reviewed-by: Roger Pau Monné
<roger.pau@citrix.com>.

Thanks.
diff mbox series

Patch

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 24636b8eaf..e33cf4e1b1 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -13,6 +13,8 @@  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
    known user doesn't use it properly, leading to in-guest breakage.
  - The "dom0" option is now supported on Arm and "sve=" sub-option can be used
    to enable dom0 guest to use SVE/SVE2 instructions.
+ - Physical CPU Hotplug downgraded to Experimental and renamed "ACPI CPU
+   Hotplug" for clarity
 
 ### Added
  - On x86, support for features new in Intel Sapphire Rapids CPUs:
diff --git a/SUPPORT.md b/SUPPORT.md
index 3461f5cf2f..3472b6edfa 100644
--- a/SUPPORT.md
+++ b/SUPPORT.md
@@ -46,9 +46,9 @@  For the Cortex A77 r0p0 - r1p0, see Errata 1508412.
 
 ## Host hardware support
 
-### Physical CPU Hotplug
+### ACPI CPU Hotplug
 
-    Status, x86: Supported
+    Status, x86: Experimental
 
 ### Physical Memory