Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752050AbbLHSpw (ORCPT ); Tue, 8 Dec 2015 13:45:52 -0500 Received: from www.linutronix.de ([62.245.132.108]:51804 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751805AbbLHSpu (ORCPT ); Tue, 8 Dec 2015 13:45:50 -0500 Date: Tue, 8 Dec 2015 19:44:59 +0100 (CET) From: Thomas Gleixner To: Dave Hansen cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org, dave.hansen@linux.intel.com, linux-api@vger.kernel.org Subject: Re: [PATCH 28/34] x86: wire up mprotect_key() system call In-Reply-To: <20151204011503.2A095839@viggo.jf.intel.com> Message-ID: References: <20151204011424.8A36E365@viggo.jf.intel.com> <20151204011503.2A095839@viggo.jf.intel.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 976 Lines: 26 On Thu, 3 Dec 2015, Dave Hansen wrote: > #include > diff -puN mm/Kconfig~pkeys-16-x86-mprotect_key mm/Kconfig > --- a/mm/Kconfig~pkeys-16-x86-mprotect_key 2015-12-03 16:21:31.114920208 -0800 > +++ b/mm/Kconfig 2015-12-03 16:21:31.119920435 -0800 > @@ -679,4 +679,5 @@ config NR_PROTECTION_KEYS > # Everything supports a _single_ key, so allow folks to > # at least call APIs that take keys, but require that the > # key be 0. > + default 16 if X86_INTEL_MEMORY_PROTECTION_KEYS > default 1 What happens if I set that to 42? I think we want to make this a runtime evaluated thingy. If pkeys are compiled in, but the machine does not support it then we don't support 16 keys, or do we? Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/