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: <4C5A1B37.5070701@zytor.com>
Date:	Wed, 04 Aug 2010 19:00:23 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	bifferos <bifferos@...oo.co.uk>
CC:	"H. Peter Anvin" <hpa@...ux.intel.com>, mingo@...hat.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 05:27 PM, bifferos wrote:
> 
> --- On Thu, 5/8/10, H. Peter Anvin <hpa@...ux.intel.com> wrote:
>>> Without the patch RDC is misreported as Cyrix
>> Cx486SLC.
>>>
>>
>> And what problems does that cause?  Presumably none,
> 
> If I don't know the CPU how do I set the tick rate?
> 
> http://android.git.kernel.org/?p=kernel/common.git;a=commitdiff_plain;h=e1b4d1143651fb3838be1117785b6e0386fa151f
> 

That's a valid use, of course, but that wasn't sent with it.  Even so,
it's really a chipset property and not a CPU property and probably
should simply be set via a PCI quirk.

So, clean up the patch, add the usage, and then it can be put into the
-tip tree for the next merge window.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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