From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: Expanded CPU details report...
Date: Mon, 19 Apr 2010 14:27:06 +0000 [thread overview]
Message-ID: <20100419142706.GA15529@bongo.bofh.it> (raw)
In-Reply-To: <20100419142622.GI3410@mcpierce-desktop.usersys.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 336 bytes --]
On Apr 19, "Darryl L. Pierce" <dpierce@redhat.com> wrote:
> 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?
Do you have use cases for this?
--
ciao,
Marco
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-04-19 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 14:26 Expanded CPU details report Darryl L. Pierce
2010-04-19 14:27 ` Marco d'Itri [this message]
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=20100419142706.GA15529@bongo.bofh.it \
--to=md@linux.it \
--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).