From: Dave Hansen <dave@sr71.net>
To: linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, x86@kernel.org, Dave Hansen <dave@sr71.net>
Subject: [PATCH 0/2] x86, mpx: Fixes for 3.19
Date: Mon, 22 Dec 2014 12:08:03 -0800 [thread overview]
Message-ID: <20141222200803.D316DA2A@viggo.jf.intel.com> (raw)
Andi Lutomirski noticed that the current 3.19 code doesn't support
32-bit binaries on 64-bit kernels, but that it is not explicitly
disabled.
I've also noticed a small performance regression that MPX was causing
in some circumstances. The fix is simple.
include/asm/mmu_context.h | 20 +++++++++++++++++++-
mm/mpx.c | 6 ++++++
2 files changed, 25 insertions(+), 1 deletion(-)
next reply other threads:[~2014-12-22 20:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 20:08 Dave Hansen [this message]
2014-12-22 20:08 ` [PATCH 1/2] x86, mpx: explicitly disable 32-bit MPX support on 64-bit kernels Dave Hansen
2014-12-22 20:17 ` Andy Lutomirski
2014-12-22 20:21 ` Dave Hansen
2014-12-22 20:27 ` Andy Lutomirski
2014-12-23 9:19 ` Ingo Molnar
2014-12-23 18:48 ` Andy Lutomirski
2014-12-22 20:08 ` [PATCH 2/2] x86 mpx: fix potential performance issue on unmaps Dave Hansen
2014-12-23 9:14 ` Ingo Molnar
2015-01-09 18:47 ` 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=20141222200803.D316DA2A@viggo.jf.intel.com \
--to=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