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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 4 Aug 2010 11:25:31 +0200
From:	Ingo Molnar <mingo@...e.hu>
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,
	hpa@...ux.intel.com, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/cpu] x86, cpu: RDC doesn't have CPUID, which is what
 c_ident is


* bifferos <bifferos@...oo.co.uk> 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.

As i reported:

> > -tip testing found that these RDC patches cause a boot
> > crash if a X86_RDC321X=y kernel is booted on a regular PC:

Those two patches caused the crash, with the config i sent, on a regular PC.

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