From: Arjan van de Ven <arjan@infradead.org>
To: Madhukar Mythri <madhukar.mythri@wipro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to read BIOS information
Date: Mon, 08 May 2006 16:53:13 +0200 [thread overview]
Message-ID: <1147099994.2888.32.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <445F5228.7060006@wipro.com>
On Mon, 2006-05-08 at 19:44 +0530, Madhukar Mythri wrote:
> Hi,
> Im new to this group.
> I want to get some information from BIOS. i.e i want to know whether
> Hyperthreading is Enabled/Disabled(as per BIOS settings) from an user
> applications program.
there is no standard way to do this. You can use /proc/cpuinfo to see if
the kernel found ht'd processors. But that's the best you can do.
(well you could grovel through the acpi tables just like the kernel
does, but you really don't want to do that from userspace)
next prev parent reply other threads:[~2006-05-08 14:53 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 [this message]
2006-05-08 15:04 ` Madhukar Mythri
2006-05-08 15:07 ` Avi Kivity
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=1147099994.2888.32.camel@laptopd505.fenrus.org \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox