From: Pavel Machek <pavel@ucw.cz>
To: Dave Hansen <dave.hansen@linux.intel.com>
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 13:30:48 +0100 [thread overview]
Message-ID: <20141212123048.GA31711@amd> (raw)
In-Reply-To: <548A147E.1020507@linux.intel.com>
> +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
next prev parent reply other threads:[~2014-12-12 12:30 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 [this message]
2014-12-12 15:47 ` Dave Hansen
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=20141212123048.GA31711@amd \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.