From: Dave Hansen <dave.hansen@linux.intel.com>
To: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
Andy Lutomirski <luto@amacapital.net>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@suse.de>, Brian Gerst <brgerst@gmail.com>,
Chen Yucong <slaoub@gmail.com>,
Chris Metcalf <cmetcalf@mellanox.com>,
Fenghua Yu <fenghua.yu@intel.com>, Huang Rui <ray.huang@amd.com>,
Jiri Slaby <jslaby@suse.cz>, Jonathan Corbet <corbet@lwn.net>,
"Michael S . Tsirkin" <mst@redhat.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Peter Zijlstra <peterz@infradead.org>,
"Ravi V . Shankar" <ravi.v.shankar@intel.com>,
Shuah Khan <shuah@kernel.org>, Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH 1/4] x86/cpufeature: Add User-Mode Instruction Prevention definitions
Date: Thu, 10 Nov 2016 09:09:43 -0800 [thread overview]
Message-ID: <0464c3f4-3810-14f5-e1bb-45eec14a7e63@linux.intel.com> (raw)
In-Reply-To: <1478748283.2551.5.camel@ranerica-desktop>
On 11/09/2016 07:24 PM, Ricardo Neri wrote:
> On Wed, 2016-11-09 at 03:02 -0800, Andy Lutomirski wrote:
...
>> > What I mean is: why does this need a config option at all?
> I intended this feature to be configurable at build time in case someone
> wants to build a kernel without it; similar to other features such as
> SMAP. Is this not needed? Should Linux be built with this feature always
> enabled?
I think marking these features with their own CONFIG's is a really good
idea. It helps the tinification effort. It's also nice for folks that
might want to turn all the Intel features off because they're running on
AMD or something.
We don't necessarily need prompts for *everything*, but I can't imagine
just slapping the code in without #ifdefs of any kind.
next prev parent reply other threads:[~2016-11-10 17:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 6:12 [PATCH 0/4] x86: enable User-Mode Instruction Prevention Ricardo Neri
2016-11-08 6:12 ` [PATCH 1/4] x86/cpufeature: Add User-Mode Instruction Prevention definitions Ricardo Neri
2016-11-08 15:32 ` Andy Lutomirski
2016-11-09 4:25 ` Ricardo Neri
2016-11-09 11:02 ` Andy Lutomirski
2016-11-10 3:24 ` Ricardo Neri
2016-11-10 8:58 ` Borislav Petkov
2016-11-11 4:08 ` Ricardo Neri
2016-11-11 10:22 ` Borislav Petkov
2016-11-12 1:24 ` Ricardo Neri
2016-11-11 18:06 ` Dave Hansen
2016-11-10 17:09 ` Dave Hansen [this message]
2016-11-08 6:12 ` [PATCH 2/4] x86: Prepare vm86 tasks to handle User-Mode Instruction Prevention Ricardo Neri
2016-11-08 16:01 ` Andy Lutomirski
2016-11-08 17:00 ` Peter Zijlstra
2016-11-09 4:26 ` Ricardo Neri
2016-11-08 6:12 ` [PATCH 3/4] x86: Enable " Ricardo Neri
2016-11-08 6:12 ` [PATCH 4/4] selftests/x86: Add tests for " Ricardo Neri
2016-11-08 13:16 ` [PATCH 0/4] x86: enable " Peter Zijlstra
2016-11-08 15:34 ` Andy Lutomirski
2016-11-08 16:52 ` Thomas Gleixner
2016-11-09 4:26 ` Ricardo Neri
2016-11-09 4:31 ` Ricardo Neri
2016-11-09 11:05 ` Andy Lutomirski
2016-11-10 6:46 ` Ricardo Neri
2016-11-10 8:52 ` Stas Sergeev
2016-11-11 4:14 ` Ricardo Neri
2016-11-11 20:51 ` Stas Sergeev
2016-11-12 1:29 ` Ricardo Neri
2016-11-14 10:59 ` One Thousand Gnomes
2016-11-14 18:36 ` Harald Arnesen
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=0464c3f4-3810-14f5-e1bb-45eec14a7e63@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=brgerst@gmail.com \
--cc=cmetcalf@mellanox.com \
--cc=corbet@lwn.net \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=jslaby@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=mst@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@intel.com \
--cc=ray.huang@amd.com \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=shuah@kernel.org \
--cc=slaoub@gmail.com \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--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