linux-kernel - Re: [RFC] Rename various 'IA32' uses in arch/x86/ code

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>] [day] [month] [year] [list]

Date:	Thu, 18 Jun 2015 12:41:25 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Brian Gerst <brgerst@...il.com>
CC:	Denys Vlasenko <dvlasenk@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Borislav Petkov <bp@...en8.de>,
	linux-tip-commits@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Andy Lutomirski <luto@...capital.net>,
	Ingo Molnar <mingo@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [RFC] Rename various 'IA32' uses in arch/x86/ code

The issue with that is that "compat" is a cross-architecture feature of the kernel to handle *some* 32-on-64 bit ABI translations.  x32 uses *some* but not all of the compat machinery.

It is already confusing when you introduce more than two ABIs (e.g. x32 or MIPS n32) and we need a way to be able to be specific.  I suggest using i386 or just use ia32 as a legacy symbol name.

On June 18, 2015 11:14:45 AM PDT, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>On Jun 18, 2015 7:49 AM, "Brian Gerst" <brgerst@...il.com> wrote:
>>
>> As long as there is no confusion between this and X32, I am fine with
>it.
>
>I would suggest that we use "compat" for the traditional 32-bit x86
>code,
>and x32 for the x32/ones. That sounds very natural and unambiguous to
>me..
>
>      Linus

-- 
Sent from my mobile phone.  Please pardon brevity and lack of formatting.
--
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/