Expanded CPU details report...

Expanded CPU details report...

[Darryl L. Pierce]

[-- 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 --]

Re: Expanded CPU details report...

[Marco d'Itri]

[-- 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 --]

Re: Expanded CPU details report...

[Lennart Poettering]

On Mon, 19.04.10 10:26, Darryl L. Pierce (dpierce@redhat.com) wrote:

> 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?

HAL just parsed /proc/cpuinfo to get that information, and so should
you probably, too.

The best way to query the number of processers is
sysconf(_SC_NPROCESSORS_CONF).

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/           GnuPG 0x1A015CC4

Re: Expanded CPU details report...

[Kay Sievers]

On Mon, Apr 19, 2010 at 16:26, Darryl L. Pierce <dpierce@redhat.com> wrote:
> 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?

No, udev will not try to provide such an abstraction. It will only
"expand" the information for devices showing up in /sys/class
/sys/bus. For CPUs, the kernel interfaces at /sys/devices/system/cpu
and /proc should be used directly.

Thanks,
Kay