linux-kernel - Re: [PATCH 23/27] x86: debugctlmsr kconfig

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:	Mon, 26 Nov 2007 00:06:44 -0800 (PST)
From:	Roland McGrath <roland@...hat.com>
To:	Dave Jones <davej@...hat.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH 23/27] x86: debugctlmsr kconfig

> What about the non-Intel vendors ?
> Was this msr present on AMD K6 ? Geode? Winchip? VIA C3 ?
> If not, then this patch isn't complete. 

I know modern AMD processors have it.  I don't know about any others, nor
off hand where to look to find out.  Is there a better way to compose the
"depends on" condition so that it will be true on the modern common
processors and future common flavors, but false on the various ones we
don't know about?  (I really just looked around a little and figured that
!X86_F00F_BUG about corresponded to "P6 family".)

Thanks,
Roland
-
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/