From: Bill Davidsen <davidsen@tmr.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: ACPI oddity
Date: Mon, 25 Jul 2005 17:15:38 -0400 [thread overview]
Message-ID: <42E5567A.80501@tmr.com> (raw)
On a HT system, why does ACPI recognize CPU0 and CPU1, refer to them as
such in dmesg, and then call them CPU1 and CPU2 in /proc/acpi/processor?
In uni kernels the single processor is CPU0.
This is a 2.6.10 kernel, the machine has been up since then. I have
other 2.6 machines and other SMP and/or HT machines, but all of the HT
machines running 2.6 are behind a hard firewall except one.
It's running the ASUS P4P800 board which is why I looked, BIOS 1086.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next reply other threads:[~2005-07-25 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 21:15 Bill Davidsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-26 5:01 ACPI oddity Brown, Len
2005-07-26 5:01 ` Brown, Len
2005-07-26 13:23 ` Bill Davidsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42E5567A.80501@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.