linux-kernel - Re: [PATCH 2.6.24] x86: add sysfs interface for cpuid module

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: <47A35D55.8080708@zytor.com>
Date:	Fri, 01 Feb 2008 09:56:37 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	dean gaudet <dean@...tic.org>
CC:	Yi Yang <yi.y.yang@...el.com>, tglx@...utronix.de,
	mingo@...hat.com, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org
Subject: Re: [PATCH 2.6.24] x86: add sysfs interface for cpuid module

dean gaudet wrote:
> why do we need another kernel cpuid reading method when sched_setaffinity 
> exists and cpuid is available in ring3?

Because /dev/cpu/*/cpuid:

a) predates sched_setaffinity by quite a few years
b) is already widely used
c) doesn't have issues with relative priorities (using sched_setaffinity
    can easily wait forever.)
d) can be accessed by unprivileged processes given appropriate device
    info.

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