From: Dave Jones <davej@codemonkey.org.uk>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Subject: Re: x86/umip: Enable User-Mode Instruction Prevention at runtime
Date: Sun, 26 Nov 2017 22:36:09 -0500 [thread overview]
Message-ID: <20171127033608.GA22924@codemonkey.org.uk> (raw)
In-Reply-To: <20171113234402.8B2F821C51@pdx-korg-gitolite-1.ci.codeaurora.org>
On Mon, Nov 13, 2017 at 11:44:02PM +0000, Linux Kernel wrote:
> Web: https://git.kernel.org/torvalds/c/aa35f896979d9610bb11df485cf7bb6ca241febb
> Commit: aa35f896979d9610bb11df485cf7bb6ca241febb
> Parent: c6a960bbf6a36572a06bde866d94a7338c7f256a
> Refname: refs/heads/master
> Author: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
> AuthorDate: Sun Nov 5 18:27:54 2017 -0800
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitDate: Wed Nov 8 11:16:23 2017 +0100
>
> x86/umip: Enable User-Mode Instruction Prevention at runtime
> +config X86_INTEL_UMIP
> + def_bool n
> + depends on CPU_SUP_INTEL
> + prompt "Intel User Mode Instruction Prevention" if EXPERT
> + ---help---
> + The User Mode Instruction Prevention (UMIP) is a security
> + feature in newer Intel processors.
Can we start defining which CPU generation features appear in in Kconfigs ?
In six months time, "newer" will mean even less than it does today.
It'd be nice to be able to answer oldconfig without having to look
things up in the SDM.
Dave
next parent reply other threads:[~2017-11-27 3:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171113234402.8B2F821C51@pdx-korg-gitolite-1.ci.codeaurora.org>
2017-11-27 3:36 ` Dave Jones [this message]
2017-11-27 5:38 ` x86/umip: Enable User-Mode Instruction Prevention at runtime Ingo Molnar
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=20171127033608.GA22924@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=ricardo.neri-calderon@linux.intel.com \
/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.