RE: ACPI oddity

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>On a HT system, why does ACPI recognize CPU0 and CPU1, refer 
>to them as such in dmesg

This is the Linux CPU number. ie the namespace where 0
is the boot processor and the others are numbered in
the order that they were started.

> and then call them CPU1 and CPU2 in 
>/proc/acpi/processor?

These are arbitrary device identifiers written
by the BIOS developer and foolishly advertised
to the user by Linux.  The BIOS writer could have
also called them ABC9 and XYZ4 and it would be
equally valid.

We're planning to get rid of all the ACPI stuff
in /proc and move to sysfs.  At that time we'll
use device identifies that are deterministic,
like cpu%d that /sys/devices/system uses today.

cheers,
-Len
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]
  Powered by Linux