From: Andy Lutomirski <luto@amacapital.net>
To: Dave Hansen <dave@sr71.net>, linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, x86@kernel.org
Subject: Re: [RFC][PATCH 0/8] x86, mpx: Support 32-bit binaries on 64-bit kernels
Date: Fri, 12 Dec 2014 12:27:16 -0800 [thread overview]
Message-ID: <548B4FA4.40700@amacapital.net> (raw)
In-Reply-To: <20141212191213.579887D2@viggo.jf.intel.com>
On 12/12/2014 11:12 AM, Dave Hansen wrote:
> This is 3.20 material. I'm hoping to get some comments early
> in case folks have some issues with the way it's being done.
>
Would it make sense to disable MPX for 32-bit binaries on 64-bit kernels
for 3.19?
--Andy
> --
>
> The MPX hardware structures differ in layout in 32 and 64-bit
> mode. A 32-bit binary running on a 64-bit kernel needs the
> 32-bit structures, so we need code which switches between
> the two modes.
>
> The first patch is just a documentation update. The next 5
> patches are really just prepwork. The meat is in the last 3.
>
> x86: make is_64bit_mm() widely available
> x86: make __VIRTUAL_MASK safe to use on 32 bit
> x86, mpx: we do not allocate the bounds directory
> x86, mpx: remove redundant MPX_BNDCFG_ADDR_MASK
> x86, mpx: Add temporary variable to reduce masking
> x86, mpx: new directory entry to addr helper
> x86, mpx: do 32-bit-only cmpxchg for 32-bit apps
> x86, mpx: support 32bit binaries on 64bit kernel
>
> Documentation/x86/intel_mpx.txt | 12 +++-
> arch/x86/include/asm/mmu_context.h | 13 +++++
> arch/x86/include/asm/mpx.h | 2
> arch/x86/include/asm/page_types.h | 8 +++
> arch/x86/kernel/uprobes.c | 10 ---
> arch/x86/mm/mpx.c | 93 ++++++++++++++++++++++++++++++-------
> 6 files changed, 107 insertions(+), 31 deletions(-)
>
next prev parent reply other threads:[~2014-12-12 20:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 19:12 [RFC][PATCH 0/8] x86, mpx: Support 32-bit binaries on 64-bit kernels Dave Hansen
2014-12-12 19:12 ` [RFC][PATCH 1/8] x86: make is_64bit_mm() widely available Dave Hansen
2014-12-12 19:12 ` [RFC][PATCH 2/8] x86: make __VIRTUAL_MASK safe to use on 32 bit Dave Hansen
2014-12-12 19:12 ` [RFC][PATCH 3/8] x86, mpx: we do not allocate the bounds directory Dave Hansen
2014-12-12 19:12 ` [RFC][PATCH 4/8] x86, mpx: remove redundant MPX_BNDCFG_ADDR_MASK Dave Hansen
2014-12-12 19:12 ` [RFC][PATCH 5/8] x86, mpx: Add temporary variable to reduce masking Dave Hansen
2014-12-12 19:12 ` [RFC][PATCH 6/8] x86, mpx: new directory entry to addr helper Dave Hansen
2014-12-12 19:12 ` [RFC][PATCH 7/8] x86, mpx: do 32-bit-only cmpxchg for 32-bit apps Dave Hansen
2014-12-12 19:12 ` [RFC][PATCH 8/8] x86, mpx: support 32bit binaries on 64bit kernel Dave Hansen
2014-12-12 20:22 ` [RFC][PATCH 0/8] x86, mpx: Support 32-bit binaries on 64-bit kernels Andy Lutomirski
2014-12-12 20:27 ` Dave Hansen
2014-12-12 20:48 ` Andy Lutomirski
2014-12-12 21:41 ` Dave Hansen
2014-12-12 23:04 ` Andy Lutomirski
2014-12-12 23:16 ` Dave Hansen
2014-12-13 0:11 ` Andy Lutomirski
2014-12-13 0:23 ` Dave Hansen
2014-12-13 1:45 ` Andy Lutomirski
2014-12-13 15:50 ` Dave Hansen
2014-12-12 20:27 ` Andy Lutomirski [this message]
2014-12-12 20:35 ` Dave Hansen
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=548B4FA4.40700@amacapital.net \
--to=luto@amacapital.net \
--cc=dave@sr71.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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