Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752655AbbFRW6O (ORCPT ); Thu, 18 Jun 2015 18:58:14 -0400 Received: from terminus.zytor.com ([198.137.202.10]:38433 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751001AbbFRW6G (ORCPT ); Thu, 18 Jun 2015 18:58:06 -0400 User-Agent: K-9 Mail for Android In-Reply-To: References: <55808579.4050004@zytor.com> <20150618164912.GA8557@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: [RFC] Rename various 'IA32' uses in arch/x86/ code From: "H. Peter Anvin" Date: Thu, 18 Jun 2015 12:41:25 -0700 To: Linus Torvalds , Brian Gerst CC: Denys Vlasenko , Thomas Gleixner , Borislav Petkov , linux-tip-commits@vger.kernel.org, Andrew Morton , Andy Lutomirski , Ingo Molnar , Linux Kernel Mailing List , Peter Zijlstra Message-ID: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1111 Lines: 24 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 wrote: >On Jun 18, 2015 7:49 AM, "Brian Gerst" 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/