>>
>> Hi,
>>
>> while trying to enhance a small hardware inventory script, I found that
>> cpuinfo is missing the details of L1, L2 and L3 size, although they may
>> be available at boot time. One could of cource grep them from "dmesg"
>> output, but that may scroll away on long lived systems.
>>
>
>Any particular reason this needs to be done in the kernel, as opposed
>to having your script read /dev/cpu/*/cpuid?
>
> -hpa
terse answer: probably the same reason as for most stuff in
/proc/cpuinfo :-)
Seriously, is there any kind of documentation on for the stuff you
mention? I am willing to learn. Isn't the cpuid just a kind of
serialnumber? The one that caused the big flame wars when Intel
introduced the concept? In any case, on my system(s) there seems to be
no device behind those files. On some systems, there is even no
"/dev/cpu" directory.
I agree in a way that the changes to processor.h are not neccessary -
unless other parts of the kernel are interested in those values. I
probably should change that to make the thing easier to digest.
Martin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
