Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752898AbbFHOrT (ORCPT ); Mon, 8 Jun 2015 10:47:19 -0400 Received: from mail-oi0-f50.google.com ([209.85.218.50]:35770 "EHLO mail-oi0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752165AbbFHOrL (ORCPT ); Mon, 8 Jun 2015 10:47:11 -0400 MIME-Version: 1.0 In-Reply-To: <20150608053537.GA18307@gmail.com> References: <1433702514-31086-1-git-send-email-dvlasenk@redhat.com> <20150608053537.GA18307@gmail.com> Date: Mon, 8 Jun 2015 10:47:10 -0400 Message-ID: Subject: Re: [PATCH] x86/asm/entry/32: Rename labels in INT 0x80 code path From: Brian Gerst To: Ingo Molnar Cc: Linus Torvalds , Denys Vlasenko , Frederic Weisbecker , Kees Cook , Borislav Petkov , Linux Kernel Mailing List , Alexei Starovoitov , Oleg Nesterov , Will Drewry , Andy Lutomirski , Steven Rostedt , "the arch/x86 maintainers" , "H. Peter Anvin" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1822 Lines: 42 On Mon, Jun 8, 2015 at 1:35 AM, Ingo Molnar wrote: > > * Linus Torvalds wrote: > >> On Jun 7, 2015 11:42 AM, "Denys Vlasenko" wrote: >> > >> > Rename it to ia32_int80_target. >> >> Btw, could we arrive to get rid of the idiotic "ia32" naming too? It's wrong, >> and it harkens back to the days when intel thought itanium makes sense and >> wanted to talk about "intel architecture". > > Absolutely, I've been slowly eliminating uses of it - that naming is very > annoying. > > Another thing I'm doing is to slowly remove references to 'emulation' - we don't > emulate 32-bit in any way, we implement various 32-bit syscall ABIs (old a new) > natively. > > I'd like to remove CONFIG_IA32_EMULATION from the .config as well - it offers > nothing real over CONFIG_COMPAT. A few months ago I started working on a set of patches to decouple the X32 support from the 32-bit compat support. There is actually quite a bit of non-shared code between the two, mainly signal handling and syscall entries. The code used by both should be CONFIG_COMPAT, but separate config defines should be kept for the non-shared code. That would allow X32 support without dragging in all of the 32-bit compat support. I never finished it because I couldn't find a current distribution that supported X32 out of the box to test with. I agree on dropping the word emulation though, since the hardware provides a full 32-bit environment. I suggest CONFIG_X86_32_COMPAT (or CONFIG_COMPAT_X86_32) as a new name. -- Brian Gerst -- 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/