From: Dave Hansen <dave.hansen@linux.intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [GIT pull] x86 mpx support for 3.19
Date: Fri, 12 Dec 2014 07:47:32 -0800 [thread overview]
Message-ID: <548B0E14.6040409@linux.intel.com> (raw)
In-Reply-To: <20141212123048.GA31711@amd>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
On 12/12/2014 04:30 AM, Pavel Machek wrote:
>> + depends on CPU_SUP_INTEL
>> + ---help---
>> + MPX provides hardware features that can be used in
>> + conjunction with compiler-instrumented code to check
>> + memory references. It is designed to detect buffer
>> + overflow or underflow bugs.
>> +
>> + This option enables running applications which are
>> + instrumented or otherwise use MPX. It does not use MPX
>> + itself inside the kernel or to protect the kernel
>> + against bad memory references.
>> +
>> + Enabling this option will make the kernel larger:
>> + ~8k of kernel text and 36 bytes of data on a 64-bit
>> + defconfig. It adds a long to the 'mm_struct' which
>> + will increase the kernel memory overhead of each
>> + process and adds some branches to paths used during
>> + exec() and munmap().
>
> Should you explain what kind of CPUs support it? Basically "the kind
> you don't have, yet"?
On a practical level, you can look for mpx in cpuinfo a la:
cat /proc/cpuinfo | grep ' mpx '
to see if your CPU supports it. I will mention that in the the
Documentation/ and also point folks there from the Kconfig text.
[-- Attachment #2: x86-mpx-real-config-option-v4.patch --]
[-- Type: text/x-patch, Size: 3052 bytes --]
From: Dave Hansen <dave.hansen@linux.intel.com>
Give MPX a real config option. The CPUs that support it
(referenced here):
https://software.intel.com/en-us/forums/topic/402393
are not available publicly, so we need to make it somewhat
easy to disable.
Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
---
b/Documentation/x86/intel_mpx.txt | 6 +++++-
b/arch/x86/Kconfig | 30 ++++++++++++++++++++++++++----
2 files changed, 31 insertions(+), 5 deletions(-)
diff -puN arch/x86/Kconfig~x86-mpx-real-config-option-v4 arch/x86/Kconfig
--- a/arch/x86/Kconfig~x86-mpx-real-config-option-v4 2014-12-12 07:33:51.316565922 -0800
+++ b/arch/x86/Kconfig 2014-12-12 07:33:51.323566238 -0800
@@ -248,10 +248,6 @@ config HAVE_INTEL_TXT
def_bool y
depends on INTEL_IOMMU && ACPI
-config X86_INTEL_MPX
- def_bool y
- depends on CPU_SUP_INTEL
-
config X86_32_SMP
def_bool y
depends on X86_32 && SMP
@@ -1593,6 +1589,32 @@ config X86_SMAP
If unsure, say Y.
+config X86_INTEL_MPX
+ prompt "Intel MPX (Memory Protection Extensions)"
+ def_bool y
+ depends on CPU_SUP_INTEL
+ ---help---
+ MPX provides hardware features that can be used in
+ conjunction with compiler-instrumented code to check
+ memory references. It is designed to detect buffer
+ overflow or underflow bugs.
+
+ This option enables running applications which are
+ instrumented or otherwise use MPX. It does not use MPX
+ itself inside the kernel or to protect the kernel
+ against bad memory references.
+
+ Enabling this option will make the kernel larger:
+ ~8k of kernel text and 36 bytes of data on a 64-bit
+ defconfig. It adds a long to the 'mm_struct' which
+ will increase the kernel memory overhead of each
+ process and adds some branches to paths used during
+ exec() and munmap().
+
+ For details, see Documentation/x86/intel_mpx.txt
+
+ If unsure, say Y.
+
config EFI
bool "EFI runtime service support"
depends on ACPI
diff -puN Documentation/x86/intel_mpx.txt~x86-mpx-real-config-option-v4 Documentation/x86/intel_mpx.txt
--- a/Documentation/x86/intel_mpx.txt~x86-mpx-real-config-option-v4 2014-12-12 07:33:51.318566012 -0800
+++ b/Documentation/x86/intel_mpx.txt 2014-12-12 07:38:53.971216573 -0800
@@ -7,11 +7,15 @@ that can be used in conjunction with com
references, for those references whose compile-time normal intentions are
usurped at runtime due to buffer overflow or underflow.
+You can tell if your CPU supports MPX by looking in /proc/cpuinfo:
+
+ cat /proc/cpuinfo | grep ' mpx '
+
For more information, please refer to Intel(R) Architecture Instruction
Set Extensions Programming Reference, Chapter 9: Intel(R) Memory Protection
Extensions.
-Note: Currently no hardware with MPX ISA is available but it is always
+Note: As of December 2014, no hardware with MPX is available but it is
possible to use SDE (Intel(R) Software Development Emulator) instead, which
can be downloaded from
http://software.intel.com/en-us/articles/intel-software-development-emulator
_
next prev parent reply other threads:[~2014-12-12 15:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 14:08 [GIT pull] x86 mpx support for 3.19 Thomas Gleixner
2014-12-10 19:05 ` Linus Torvalds
2014-12-10 19:41 ` Dave Hansen
2014-12-10 19:49 ` Linus Torvalds
2014-12-10 20:39 ` Dave Hansen
2014-12-10 20:49 ` Linus Torvalds
2014-12-12 16:40 ` H. Peter Anvin
2014-12-11 6:19 ` Ingo Molnar
2014-12-11 22:02 ` Dave Hansen
2014-12-12 8:31 ` Ingo Molnar
2014-12-12 12:30 ` Pavel Machek
2014-12-12 15:47 ` Dave Hansen [this message]
2014-12-12 17:21 ` Pavel Machek
2014-12-10 19:49 ` Dave Hansen
2014-12-11 2:14 ` Eric W. Biederman
2014-12-11 2:30 ` 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=548B0E14.6040409@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pavel@ucw.cz \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).