forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[PATCH] x86_64: Add documentation for CPU hotplug ACPI extension
Cc: [email protected], [email protected] Signed-off-by: Andi Kleen <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
- Loading branch information
Andi Kleen
authored and
Linus Torvalds
committed
Jan 12, 2006
1 parent
f62a91f
commit 7eb903f
Showing
1 changed file
with
21 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
Firmware support for CPU hotplug under Linux/x86-64 | ||
--------------------------------------------------- | ||
|
||
Linux/x86-64 supports CPU hotplug now. For various reasons Linux wants to | ||
know in advance boot time the maximum number of CPUs that could be plugged | ||
into the system. ACPI 3.0 currently has no official way to supply | ||
this information from the firmware to the operating system. | ||
|
||
In ACPI each CPU needs an LAPIC object in the MADT table (5.2.11.5 in the | ||
ACPI 3.0 specification). ACPI already has the concept of disabled LAPIC | ||
objects by setting the Enabled bit in the LAPIC object to zero. | ||
|
||
For CPU hotplug Linux/x86-64 expects now that any possible future hotpluggable | ||
CPU is already available in the MADT. If the CPU is not available yet | ||
it should have its LAPIC Enabled bit set to 0. Linux will use the number | ||
of disabled LAPICs to compute the maximum number of future CPUs. | ||
|
||
In the worst case the user can overwrite this choice using a command line | ||
option (additional_cpus=...), but it is recommended to supply the correct | ||
number (or a reasonable approximation of it, with erring towards more not less) | ||
in the MADT to avoid manual configuration. |