public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Brian Gerst <brgerst@gmail.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, hpa@zytor.com,
	Borislav Petkov <bp@alien8.de>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 0/5] x86: IA32 emulation cleanups
Date: Wed, 4 Mar 2015 06:24:26 +0100	[thread overview]
Message-ID: <20150304052426.GD5158@gmail.com> (raw)
In-Reply-To: <1425439896-8322-1-git-send-email-brgerst@gmail.com>


* Brian Gerst <brgerst@gmail.com> wrote:

> This series cleans up some files in the 32-bit emulation code, by merging
> with the native 32-bit code, or in the case of the syscall audit, using the
> generic compat code that was recently added.
> 
> Brian Gerst (5):
>   x86: Remove compat_ni_syscall()
>   x86: Merge native and compat 32-bit syscall tables
>   x86: Remove sys32_vm86_warning
>   x86: Use generic compat audit code
>   x86: Clean up ia32/Makefile

So this series is looking pretty good to me, I've picked up #1-#3, 
pending clarification on #4. I've stuck them into tip:x86/asm, because 
they might interact with ongoing system call entry work.

While we are at it: CONFIG_IA32_EMULATION is a misnomer: there's 
nothing 'emulated' there, it's full software and hardware support for 
the 32-bit ABI. It's just an ugly (and somewhat confusing) replacement 
for CONFIG_COMPAT that most other architectures are using.

So could we also get rid of CONFIG_IA32_EMULATION and change most of 
its uses over to CONFIG_COMPAT et al? The only complication with that 
might be that IA32_EMULATION kconfig switch hardcodes a few features 
currently:

        select BINFMT_ELF
        select COMPAT_BINFMT_ELF
        select HAVE_UID16

allowing the binfmt formats to be undefined should be OK; the uid16 
dependency needs to be checked, whether it's safe to allow it to be 
disabled.

Thanks,

	Ingo

  parent reply	other threads:[~2015-03-04  5:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04  3:31 [PATCH 0/5] x86: IA32 emulation cleanups Brian Gerst
2015-03-04  3:31 ` [PATCH 1/5] x86: Remove compat_ni_syscall() Brian Gerst
2015-03-04  5:27   ` [tip:x86/asm] x86/compat: " tip-bot for Brian Gerst
2015-03-04  3:31 ` [PATCH 2/5] x86: Merge native and compat 32-bit syscall tables Brian Gerst
2015-03-04  5:27   ` [tip:x86/asm] x86/compat: " tip-bot for Brian Gerst
2015-03-04  3:31 ` [PATCH 3/5] x86: Remove sys32_vm86_warning Brian Gerst
2015-03-04  5:28   ` [tip:x86/asm] x86/compat: " tip-bot for Brian Gerst
2015-03-04  3:31 ` [PATCH 4/5] x86: Use generic compat audit code Brian Gerst
2015-03-04  5:14   ` Ingo Molnar
2015-03-04  6:39     ` Brian Gerst
2015-03-04  7:09       ` Ingo Molnar
2015-03-04 14:52       ` David Drysdale
2015-03-04  3:31 ` [PATCH 5/5] x86: Clean up ia32/Makefile Brian Gerst
2015-03-04  5:24 ` Ingo Molnar [this message]
2015-03-04  6:22   ` [PATCH 0/5] x86: IA32 emulation cleanups Brian Gerst
2015-03-05 22:38     ` H. Peter Anvin

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=20150304052426.GD5158@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.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