From: Avi Kivity <avi@argo.co.il>
To: Madhukar Mythri <madhukar.mythri@wipro.com>
Cc: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: How to read BIOS information
Date: Mon, 08 May 2006 18:07:21 +0300 [thread overview]
Message-ID: <445F5EA9.5030200@argo.co.il> (raw)
In-Reply-To: <445F5DF1.3020606@wipro.com>
Madhukar Mythri wrote:
> "proc/cpuinfo" says only HT support is their or not but, it will not
> say whether HT is Enalbled/Disabled..
> How to read ACPI tables ? Can you give little info on this...
> even from Driver program, if its possible please tell me...
Look at the 'physical id', 'siblings', 'core id', and 'cpu cores' fields
in /proc/cpuinfo. If 'siblings' exists, you are hyperthreaded and you
can detect which cpu the other thread is by matching physical id and
core id.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2006-05-08 15:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 14:14 How to read BIOS information Madhukar Mythri
2006-05-08 14:36 ` Richard Mittendorfer
2006-05-08 14:54 ` Madhukar Mythri
2006-05-08 14:57 ` Richard Mittendorfer
2006-05-08 14:53 ` Arjan van de Ven
2006-05-08 15:04 ` Madhukar Mythri
2006-05-08 15:07 ` Avi Kivity [this message]
2006-05-08 15:15 ` Arjan van de Ven
2006-05-08 15:28 ` Madhukar Mythri
2006-05-08 15:27 ` Erik Mouw
2006-05-09 5:23 ` Madhukar Mythri
2006-05-09 5:37 ` Jan-Benedict Glaw
2006-05-09 9:57 ` Erik Mouw
2006-05-09 11:03 ` Alan Cox
2006-05-09 12:29 ` Stefan Smietanowski
2006-05-09 12:51 ` Richard Mittendorfer
2006-05-09 13:18 ` Madhukar Mythri
2006-05-09 14:44 ` Roger Heflin
2006-05-08 15:15 ` Michal Piotrowski
2006-05-08 15:43 ` linux-os (Dick Johnson)
2006-05-10 8:32 ` Dan Carpenter
2006-05-12 20:02 ` Arjan van de Ven
2006-05-08 15:16 ` linux-os (Dick Johnson)
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=445F5EA9.5030200@argo.co.il \
--to=avi@argo.co.il \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madhukar.mythri@wipro.com \
/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.