linux-kernel - Re: Is sysfs the right place to get cache and CPU topology info?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <486B9B3A.4060709@firstfloor.org>
Date:	Wed, 02 Jul 2008 17:14:02 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Nathan Lynch <ntl@...ox.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Paul Mackerras <paulus@...ba.org>,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	greg@...ah.com
Subject: Re: Is sysfs the right place to get cache and CPU topology info?

Nathan Lynch wrote:
> Andi Kleen wrote:
>> Andrew Morton <akpm@...ux-foundation.org> writes:
>>> sysfs is part of the kernel ABI.  We should design our interfaces there
>>> as carefully as we design any others.
>> The basic problem is that sysfs exports an internal kernel object model
>> and these tend to change. To really make it stable would require 
>> splitting it into internal and presented interface.
> 
> True, but... /sys/devices/system/cpu has been there since around 2.6.5
> iirc.  A google code search for that path shows plenty of programs
> (including hal) that hard-code it.  Exposed object model or not,
> changing that path would break lots of software.

Yes it would.

But Greg is making noises of getting rid of sysdevs and it wouldn't
surprise me if that ended up being user visible since most object
model changes end up being visible.

> 
> 
>> I would be all
>> for it, but it doesn't seem realistic to me currently. If we cannot
>> even get basic interfaces like the syscall capability stable how would
>> you expect to stabilize the complete kobjects? 
>>
>> And the specific problem with the x86 cache sysfs interface is that it's so
>> complicated that no human can really read it directly. This means to
>> actually use it you need some kind of frontend (i have a cheesy
>> lscache script for this).
> 
> Human readability is nice, 

When it's not human readable, then it's usually also not Joe Normal Programmer
usable.

> but a more important issue IMO is whether
> the cache interface can be considered stable enough for programs to
> rely on it.  I notice there's no entry for it in Documentation/ABI.

For x86 it follows closely the Intel CPUID  architectural specification, which
can be considered stable (at least for Intel, other vendors do not
necessarily implement it. But for AMD it is faked at least)

-Andi

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/