* [PATCH v2] Documentation / cpu hotplug: Rephrase the outdated description for MADT entries
@ 2013-06-21 9:09 Hanjun Guo
2013-06-24 12:00 ` Rafael J. Wysocki
0 siblings, 1 reply; 2+ messages in thread
From: Hanjun Guo @ 2013-06-21 9:09 UTC (permalink / raw)
To: Rob Landley, Rafael J. Wysocki
Cc: Rusty Russell, Srivatsa Vaddagiri, linux-acpi, linux-doc,
linux-kernel, patches, linaro-kernel, Hanjun Guo
More than 256 entries in ACPI MADT is supported from ACPI 3.0, so the
information should be updated.
-v2: Rephrase the information instead of simply removing it according
to Rafael's advice.
Suggested-by: Rafael J. Wysocki <rjw@sisk.pl>
Signed-off-by: Hanjun Guo <hanjun.guo@linaro.org>
---
Documentation/cpu-hotplug.txt | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/cpu-hotplug.txt b/Documentation/cpu-hotplug.txt
index 9f40135..67f733d 100644
--- a/Documentation/cpu-hotplug.txt
+++ b/Documentation/cpu-hotplug.txt
@@ -370,8 +370,10 @@ A: There is no clear spec defined way from ACPI that can give us that
CPUs in MADT as hotpluggable CPUS. In the case there are no disabled CPUS
we assume 1/2 the number of CPUs currently present can be hotplugged.
- Caveat: Today's ACPI MADT can only provide 256 entries since the apicid field
- in MADT is only 8 bits.
+ Caveat: ACPI MADT can only provide 256 entries in systems with only ACPI 2.0c
+ or earlier ACPI version supported, because the apicid field in MADT is only
+ 8 bits. From ACPI 3.0, this limitation was removed since the apicid field
+ was extended to 32 bits with x2APIC introduced.
User Space Notification
--
1.7.9.5
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH v2] Documentation / cpu hotplug: Rephrase the outdated description for MADT entries
2013-06-21 9:09 [PATCH v2] Documentation / cpu hotplug: Rephrase the outdated description for MADT entries Hanjun Guo
@ 2013-06-24 12:00 ` Rafael J. Wysocki
0 siblings, 0 replies; 2+ messages in thread
From: Rafael J. Wysocki @ 2013-06-24 12:00 UTC (permalink / raw)
To: Hanjun Guo
Cc: Rob Landley, Rusty Russell, Srivatsa Vaddagiri, linux-acpi,
linux-doc, linux-kernel, patches, linaro-kernel
On Friday, June 21, 2013 05:09:18 PM Hanjun Guo wrote:
> More than 256 entries in ACPI MADT is supported from ACPI 3.0, so the
> information should be updated.
>
> -v2: Rephrase the information instead of simply removing it according
> to Rafael's advice.
Queued up for 3.11.
Thanks,
Rafael
> Suggested-by: Rafael J. Wysocki <rjw@sisk.pl>
> Signed-off-by: Hanjun Guo <hanjun.guo@linaro.org>
> ---
> Documentation/cpu-hotplug.txt | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/cpu-hotplug.txt b/Documentation/cpu-hotplug.txt
> index 9f40135..67f733d 100644
> --- a/Documentation/cpu-hotplug.txt
> +++ b/Documentation/cpu-hotplug.txt
> @@ -370,8 +370,10 @@ A: There is no clear spec defined way from ACPI that can give us that
> CPUs in MADT as hotpluggable CPUS. In the case there are no disabled CPUS
> we assume 1/2 the number of CPUs currently present can be hotplugged.
>
> - Caveat: Today's ACPI MADT can only provide 256 entries since the apicid field
> - in MADT is only 8 bits.
> + Caveat: ACPI MADT can only provide 256 entries in systems with only ACPI 2.0c
> + or earlier ACPI version supported, because the apicid field in MADT is only
> + 8 bits. From ACPI 3.0, this limitation was removed since the apicid field
> + was extended to 32 bits with x2APIC introduced.
>
> User Space Notification
>
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-06-24 11:51 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-06-21 9:09 [PATCH v2] Documentation / cpu hotplug: Rephrase the outdated description for MADT entries Hanjun Guo
2013-06-24 12:00 ` Rafael J. Wysocki
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).