From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753789AbbIPRtO (ORCPT ); Wed, 16 Sep 2015 13:49:14 -0400 Received: from mga02.intel.com ([134.134.136.20]:48239 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753171AbbIPRtF (ORCPT ); Wed, 16 Sep 2015 13:49:05 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,540,1437462000"; d="scan'208";a="805856504" Subject: [PATCH 02/26] x86, pkeys: Add Kconfig option To: dave@sr71.net Cc: x86@kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org From: Dave Hansen Date: Wed, 16 Sep 2015 10:49:04 -0700 References: <20150916174903.E112E464@viggo.jf.intel.com> In-Reply-To: <20150916174903.E112E464@viggo.jf.intel.com> Message-Id: <20150916174904.996E5E23@viggo.jf.intel.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I don't have a strong opinion on whether we need a Kconfig prompt or not. Protection Keys has relatively little code associated with it, and it is not a heavyweight feature to keep enabled. However, I can imagine that folks would still appreciate being able to disable it. We will hide the prompt for now. --- b/arch/x86/Kconfig | 4 ++++ 1 file changed, 4 insertions(+) diff -puN arch/x86/Kconfig~pkeys-01-kconfig arch/x86/Kconfig --- a/arch/x86/Kconfig~pkeys-01-kconfig 2015-09-16 10:48:12.006999694 -0700 +++ b/arch/x86/Kconfig 2015-09-16 10:48:12.010999875 -0700 @@ -1694,6 +1694,10 @@ config X86_INTEL_MPX If unsure, say N. +config X86_INTEL_MEMORY_PROTECTION_KEYS + def_bool y + depends on CPU_SUP_INTEL && X86_64 + config EFI bool "EFI runtime service support" depends on ACPI _