linux-kernel - Re: [PATCH/RFC v1 0/2] Human readable performance event description in sysfs

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: <1263996080.4283.1064.camel@laptop>
Date:	Wed, 20 Jan 2010 15:01:20 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	Jamie Iles <jamie.iles@...ochip.com>, jpihet@...sta.com,
	p.osciak@...sung.com, will.deacon@....com,
	Michał Nazarewicz <m.nazarewicz@...sung.com>,
	linux-kernel@...r.kernel.org, kyungmin.park@...sung.com,
	mingo@...e.hu, m.szyprowski@...sung.com,
	linux-arm-kernel@...ts.infradead.org,
	Tomasz Fujak <t.fujak@...sung.com>
Subject: Re: [PATCH/RFC v1 0/2] Human readable performance event
 description in sysfs

On Wed, 2010-01-20 at 13:55 +0000, Russell King - ARM Linux wrote:
> 
> Unfortunately, it isn't.  CPU identification has become a fairly murky
> business on ARM that the information exported from /proc/cpuinfo can
> no longer precisely identify the CPU itself.
> 
> For example, we just treat Cortex A8 and A9 as "ARMv7" because from the
> kernel's point of view, they're the same. 

Would it make sense to extend arm's cpuinfo to include enough
information so that userspace can indeed do this?

It seems to me userspace might care about the exact platform they're
running on.

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