[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5488A3C0.1080403@linux.intel.com>
Date: Wed, 10 Dec 2014 11:49:20 -0800
From: Dave Hansen <dave.hansen@...ux.intel.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>
CC: LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [GIT pull] x86 mpx support for 3.19
On 12/10/2014 11:05 AM, Linus Torvalds wrote:
> On Tue, Dec 9, 2014 at 6:08 AM, Thomas Gleixner <tglx@...utronix.de> wrote:
> Why would I want to enable this in my kernel when there are no actual
> CPU's out yet that support it? And even when there are, why would I do
> it if the CPU I have doesn't support it?
There's no good reason to enable it except for testing (compile, or
making sure we didn't screw up the #BR code for CPUs without MPX).
Patch is attached to add the following:
> config X86_INTEL_MPX
> prompt "Intel MPX (Memory Protection Extensions)" if EXPERT
> 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.
>
> Enabling this option will make the kernel larger and
> slightly increase the size of some data structures.
>
> If unsure, say Y.
View attachment "x86-mpx-real-config-option.patch" of type "text/x-patch" (1462 bytes)
Powered by blists - more mailing lists