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]

Date:	Wed, 04 Aug 2010 16:09:55 -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 03:59 PM, bifferos wrote:
> --- On Wed, 4/8/10, H. Peter Anvin <hpa@...ux.intel.com> wrote:
> 
>>
>> 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.
> 
> Without the patch RDC is misreported as Cyrix Cx486SLC.
> 

And what problems does that cause?  Presumably none, in which case you
have to realize that the correctness threshold for this patch is
enormous, as the benefit is extremely small compared with the potential
(and actual!) harm.

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