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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20071126015757.GA16807@redhat.com>
Date:	Sun, 25 Nov 2007 20:57:57 -0500
From:	Dave Jones <davej@...hat.com>
To:	Roland McGrath <roland@...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

On Sun, Nov 25, 2007 at 02:08:02PM -0800, Roland McGrath wrote:
 > 
 > This adds the (internal) Kconfig macro CONFIG_X86_DEBUGCTLMSR,
 > to be defined when configuring to support only hardware that
 > definitely supports MSR_IA32_DEBUGCTLMSR with the BTF flag.
 > 
 > The Intel documentation says "P6 family" and later processors all have it.
 > I think the Kconfig dependencies are right to have it set for those and
 > unset for others (i.e., when 586 and earlier are supported).

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. 

	Dave

-- 
http://www.codemonkey.org.uk
-
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/