linux-kernel - Re: [PATCH 3/3] x86, AMD: Disable wrongly set X86_FEATURE_LAHF

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: <4A9C1085.50204@zytor.com>
Date:	Mon, 31 Aug 2009 11:03:49 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Borislav Petkov <petkovbb@...glemail.com>, mingo@...hat.com,
	linux-kernel@...r.kernel.org, kjwinchester@...il.com,
	tglx@...utronix.de, borislav.petkov@....com,
	linux-tip-commits@...r.kernel.org
Subject: Re: [PATCH 3/3] x86, AMD: Disable wrongly set X86_FEATURE_LAHF_LM
 CPUID bit

On 08/31/2009 01:14 AM, Borislav Petkov wrote:
> On Sun, Aug 30, 2009 at 01:48:49PM -0700, H. Peter Anvin wrote:
>> The 2x32 bit interface is the legacy interface.  It turned out to be a
>> bad idea, but it's hard to clean up all the users.
> 
> By the way, do we want to switch all rd/wrmsr users to the rd/wrmsrl et
> al interfaces? I could do that gradually - there are only about 400+
> callsites :)
> 

Probably, but I don't consider it a high-priority project.  To me it's
more of a "clean it up as you go" kind of thing.

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