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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48224361.5080102@zytor.com>
Date:	Wed, 07 May 2008 17:03:45 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Rene Herman <rene.herman@...access.nl>
CC:	Thomas Gleixner <tglx@...utronix.de>,
	Adrian Bunk <bunk@...nel.org>,
	Yinghai Lu <yhlu.kernel@...il.com>,
	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	Pavel Machek <pavel@...e.cz>
Subject: Re: 2.6.26, PAT and AMD family 6

Rene Herman wrote:
>>
>> Okay, that is utter nonsense.  /proc/cpuinfo has always been, and will 
>> always be, the CPU *AS THE KERNEL SEES IT*.  If you want something 
>> else, use x86info(1).
> 
> What a lovely way of syncing reality with your definitions. The kernel
> _does_ see that my CPU features PAT, it just refuses to use it because
> it doesn't trust it enough. Vital difference. Maybe not to the kernel,
> but definitely to me, the user. /proc/cpuinfo is a user interface.
> 

No, /proc/cpuinfo is informing the user about the kernel's view of the 
CPU.  It has always been the "cooked" view of CPUID, whether or not you 
like it.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ