On 2017/2/15 11:46, Dou Liyang wrote:
Hi, Hanjun
Thank you for your help!
[...]
Sorry, a little bit confused, local APIC entries are listed in
MADT by firmware, and MADT is a static table which means the OS
will not update the orders.
Yes, MADT will never be updated after booting time.
My concern is how do the firmware arrange the order of the local
APIC entries in MADT.
I found the local APIC entries which its processor enable flag was
1 would be sorted close to the front of MADT.
I startup the computer twice,
1. I don't use the local APIC IDs with 0x10 and 0x12.
There are just 2 online CPUs in the computer in the booting time.
The MADT likes:
-------MADT---------
Apic Id | Enable Flag
0x00 1
0x02 1
Digital order.
0x04 0
0x06 0
0x10 0
0x12 0
0x14 0
0x16 0
Same here...
-------------------------------------
2. I use the local APIC IDs with 0x10 and 0x12. Then, startup the
computer. There are 4 online CPUs.
The MADT likes:
------MADT-------
Apic Id | Enable Flag
0x00 1
0x02 1
0x10 1
0x12 1
And digital order...
0x04 0
0x16 0
0x06?
0x14 0
0x16 0
The position of the 0x10 and 0x12 is changed.
So your firmware will list enabled CPUs first and
them disabled one, both in digital order, and lot of
firmware (but not all of them) doing the same thing.
Thanks
Hanjun
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
