On Fri, Oct 20, 2023 at 11:58:58AM +, Huang, Kai wrote:
> On Tue, 2023-10-10 at 10:24 +, Huang, Kai wrote:
> > > /* Physical address of the Multiprocessor Wakeup Structure mailbox */
> > > @@ -74,6 +75,9 @@ int __init acpi_parse_mp_wake(union
> > > acpi_subtable_headers *header,
> > >
On Tue, 2023-10-10 at 10:24 +, Huang, Kai wrote:
> > /* Physical address of the Multiprocessor Wakeup Structure mailbox */
> > @@ -74,6 +75,9 @@ int __init acpi_parse_mp_wake(union acpi_subtable_headers
> > *header,
> >
> >
> > acpi_mp_wake_mailbox_paddr = mp_wake->base_address;
> >
On Thu, Oct 05 2023 at 16:13, Kirill A. Shutemov wrote:
>
> + /* Disable CPU onlining/offlining */
That's not what the function does.
> + cpu_hotplug_not_supported();
Thanks,
tglx
___
kexec mailing list
kexec@lists.infradead.org
On 10/5/2023 6:13 AM, Kirill A. Shutemov wrote:
> ACPI MADT doesn't allow to offline CPU after it got woke up.
>
I think you can use the term "CPU hotplug" instead of just offline.
> Currently hotplug prevented based on the confidential computing
> attribute which is set for Intel TDX. But
> /* Physical address of the Multiprocessor Wakeup Structure mailbox */
> @@ -74,6 +75,9 @@ int __init acpi_parse_mp_wake(union acpi_subtable_headers
> *header,
>
> acpi_mp_wake_mailbox_paddr = mp_wake->base_address;
>
> + /* Disable CPU onlining/offlining */
> +
ACPI MADT doesn't allow to offline CPU after it got woke up.
Currently hotplug prevented based on the confidential computing
attribute which is set for Intel TDX. But TDX is not the only possible
user of the wake up method.
Mark CPU hotplug as "not supported" on ACPI MADT wakeup enumeration.
