From: "Darryl L. Pierce" <dpierce@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Expanded CPU details report...
Date: Mon, 19 Apr 2010 14:26:22 +0000 [thread overview]
Message-ID: <20100419142622.GI3410@mcpierce-desktop.usersys.redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
In HAL it was possible to extract several pieces of information about
the processors on a machine, such as product name ("Intel(R) Xeon(R)
CPU E5430 @ 2.66GHz"), number of cores, the core number when peering a
specific core, throttling capability and the like.
With udev we can only detect the number of cores by counting the
instances of devices that report a driver of "processor".
Can we get expanded CPU details in udev, such as the processor product
name, core count and core number (on a specific core), the processor
flags (as seen in /proc/cpuinfo), cache size, speed, and other details?
Thanks.
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-04-19 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 14:26 Darryl L. Pierce [this message]
2010-04-19 14:27 ` Expanded CPU details report Marco d'Itri
2010-04-19 14:43 ` Lennart Poettering
2010-04-19 14:48 ` Kay Sievers
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=20100419142622.GI3410@mcpierce-desktop.usersys.redhat.com \
--to=dpierce@redhat.com \
--cc=linux-hotplug@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).