linux-kernel - Re: [tip:x86/cpu] x86, cpu: RDC doesn't have CPUID, which is what c

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: <4C59CA37.4050509@linux.intel.com>
Date:	Wed, 04 Aug 2010 13:14:47 -0700
From:	"H. Peter Anvin" <hpa@...ux.intel.com>
To:	bifferos <bifferos@...oo.co.uk>
CC:	mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org,
	florian@...nwrt.org, mark@...feros.com, tglx@...utronix.de,
	Ingo Molnar <mingo@...e.hu>, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/cpu] x86, cpu: RDC doesn't have CPUID, which is what
 c_ident is

On 08/04/2010 02:12 AM, bifferos wrote:
> 
> I couldn't reproduce this with 2.6.35 (without Peter's change),
> I was trying on VirtualBox.  If the detection code is causing a 
> problem we can just skip it if the CPU has cpuid.
> 
> Incidentally if you need some hardware to test the RDC port on I can
> arrange that.
> 

Incidentally, please do note that there is no concrete benefit to this
"support", since all it does is replicate information in /proc/cpuinfo
that is already available through lspci.

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