[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 12 Dec 2014 13:30:48 +0100
From: Pavel Machek <pavel@....cz>
To: Dave Hansen <dave.hansen@...ux.intel.com>
Cc: Ingo Molnar <mingo@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
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
> +config X86_INTEL_MPX
> + prompt "Intel MPX (Memory Protection Extensions)"
> + def_bool y
bool?
> + 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"?
> + If unsure, say Y.
Disagreed here. Right now, N is right response to anyone but Intel.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists