From: Ingo Molnar <mingo@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Brian Gerst <brgerst@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Denys Vlasenko <dvlasenk@redhat.com>,
Andy Lutomirski <luto@amacapital.net>,
linux-tip-commits@vger.kernel.org
Subject: Re: [RFC] Rename various 'IA32' uses in arch/x86/ code
Date: Fri, 19 Jun 2015 09:13:05 +0200 [thread overview]
Message-ID: <20150619071305.GB14768@gmail.com> (raw)
In-Reply-To: <9E143C8F-1F0D-4528-B354-30BB68CCBC0E@zytor.com>
* H. Peter Anvin <hpa@zytor.com> wrote:
> We have generally used i386 as opposed to x86 for that purpose. [...]
So 'i386' is really the original name that stuck.
'x86-32' sounds more appropriate to me - we should not perpetuate the i386 name,
as we don't run on an original i386 anymore ;-)
Here's what I think sounds pretty natural:
CONFIG_X86_32_ABI
CONFIG_X86_64_ABI
CONFIG_X86_X32_ABI
- CONFIG_X86_X32_ABI and CONFIG_X86_32_ABI selects CONFIG_COMPAT.
- CONFIG_X86_32_ABI enables the 32-bit/32-bit system call ABI.
- CONFIG_X86_X32_ABI enables the extra 64-bit/32-bit system call entries.
- CONFIG_IA32_EMULATION goes away.
> [...] IA32 in MSR names is part of the MSR name and should not be taken out.
Yes, of course.
Thanks,
Ingo
next prev parent reply other threads:[~2015-06-19 7:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-bace7117d3fb59a6ed7ea1aa6c8994df6a28a72a@git.kernel.org>
2015-06-16 20:22 ` [tip:x86/asm] x86/asm/entry: (Re-) rename __NR_entry_INT80_compat_max to __NR_syscall_compat_max H. Peter Anvin
2015-06-18 16:49 ` [RFC] Rename various 'IA32' uses in arch/x86/ code Ingo Molnar
2015-06-18 17:49 ` Brian Gerst
2015-06-18 19:37 ` H. Peter Anvin
2015-06-19 7:13 ` Ingo Molnar [this message]
2015-06-19 17:19 ` H. Peter Anvin
2015-06-21 13:44 ` Ingo Molnar
[not found] ` <CA+55aFzKOyZ4ZA6zFvCNqqqkYT8hLQOXAgJRj-k+LRqvQ1iiyQ@mail.gmail.com>
2015-06-18 19:41 ` H. Peter Anvin
2015-06-18 21:13 ` Ingo Molnar
2015-06-18 22:11 ` Brian Gerst
2015-06-19 7:08 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150619071305.GB14768@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome