linux-kernel - Re: x86: cleanup - rename VM_MASK to X86_VM

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: <480F7C11.8040302@zytor.com>
Date:	Wed, 23 Apr 2008 11:12:33 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Cyrill Gorcunov <gorcunov@...il.com>
CC:	David Woodhouse <dwmw2@...radead.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: x86: cleanup - rename VM_MASK to X86_VM_MASK

Cyrill Gorcunov wrote:
> 
> Hi David,
> 
> actually, this CONFIG_VM86 was there even before the renaming was done.
> The main questions (imo) - is there any user space application who uses
> these flags? If they are - then even the idea of this patch was a bit bogus,
> and I should *not* remove all these VM86 specific flags but better define them
> as aliases on flags from processor-flags.h.
> 

Hard to know.  VM86 is only used by a handful of applications (DOSEMU, 
X.org, others?) but it's hard to know what exactly they are.

The fact that noone hollered when that CONFIG_VM86 went in is probably a 
good hint that they don't matter, but it's hard to say for sure.

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